[Hiring] Staff Frontend Engineer @bunch

Role Description

As a Staff Frontend Engineer at bunch, you will shape the architecture, quality, and developer experience of the product surfaces our customers and internal teams rely on every day. You will work across product teams to make our frontend systems scalable, reliable, accessible, and fast — while helping engineers ship with clarity and confidence.

This is not only a delivery role. Your decisions will influence how frontend engineering at bunch evolves: the standards we adopt, the patterns we reuse, the quality bar we hold, and the way product, design, and engineering collaborate to build excellent user experiences.

Top priorities:

• Lead our migration from Svelte to React.
• Hold the architectural picture across both stacks, sequence the work against product delivery, and land it without stalling teams.
• Maintain and evolve our design system, together with the frontend guild, so product teams ship consistent, accessible UI faster.
• Support and guide frontend initiatives across teams, with the frontend guild — application architecture, performance, testing strategy, developer experience, and technical debt reduction — from diagnosis through measurable delivery.
• Be the bar raiser for UX and UI quality, raising the standard through design reviews, reusable patterns, mentoring, and thoughtful technical writing.
• Advance how we build with AI — find where agentic tooling genuinely improves engineering practice, and shape the codebase (module boundaries, API contracts, documentation) so it works well for people and agents alike.

Qualifications

• Track record: You have already operated at Staff scope, with or without the title, and have shipped systemic frontend or product-engineering improvements across multiple teams.
• Frontend craft: Deep expertise in modern frontend engineering, with strong command of TypeScript, component architecture, state management, design systems, accessibility, performance, testing, and maintainable application architecture.
• AI-native practice: You use AI coding tools daily and have gone past autocomplete into agentic workflows.
• Product judgment: You care about the user experience as much as the technical solution.
• Systems thinking: You are comfortable reasoning across frontend, backend, APIs, infrastructure, observability, security, and compliance when the problem requires it.
• Operating style: You think in quarters and years, not only sprints.
• Collaborative Leadership: A proactive relationship-builder who can set technical direction and influence without formal authority.
• Language: Fluent English, written and spoken.

Requirements

• 30 days: Map the frontend architecture, product domains, design system, team workflows, and the main bottlenecks affecting delivery and quality.
• 60 days: Publish a structured problem analysis and proposal for one cross-team frontend initiative with clear trade-offs, stakeholders, and success measures.
• 90 days: Lead a systemic improvement from kickoff to measurable progress across teams, while helping Senior Engineers grow through collaboration, reviews, and shared ownership.

Benefits

• Customizable benefits package covering wellbeing, sport, mobility, food, and more.
• 28 days of vacation, plus 2 company days and local public holidays.
• Remote setup, contract via EoR.
• A great tech and work setup.
• Work with a diverse team of 130+ bunchies from 40+ countries, with leaders who are best-in-class in their domains.

Hiring Process

• Initial screening with Talent Acquisition (30 min): Get acquainted with bunch, explore your motivation, and understand whether what we offer matches what you are looking for.
• Hiring Manager call — Engineering (60 min): A conversation with Engineering leadership focused on your scope, frontend leadership, product-engineering mindset, and how you diagnose and lead systemic improvements.
• Technical Interview (60 min): A hands-on technical conversation focused on frontend engineering craft, TypeScript, component design, maintainability, testing, and pragmatic problem-solving.
• Technical Interview — System Design (60 min): A frontend/system design conversation focused on architecture, data flow, performance, accessibility, reliability, and trade-offs in complex product systems.
• VP Product conversation (45 min): A cross-functional conversation focused on product thinking, customer empathy, business acumen, and how you partner with Product and Design on ambiguous problems.
• Final round (45 min): A closing conversation to align on what we heard across the process, answer remaining questions, and discuss expectations for the role and trial period.