Staff Frontend Engineer at bunch

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.

How the role contributes to our vision

bunch is building the backbone of private markets, combining exceptional expertise, operational excellence, and frictionless technology. Our platform enables funds and private investors to seamlessly and securely set up and manage their investment entities.

As a Staff Frontend Engineer, you will play a pivotal role in turning complex workflows into intuitive, robust, and scalable product experiences. You will help ensure our frontend foundation enables rapid delivery across teams while maintaining high standards for usability, performance, accessibility, and maintainability.

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.

Your first 90 days

• 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.

About you

• 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. People listen to you because of what you have delivered, how clearly you think, and how effectively you collaborate.

• 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. You have a considered view on where they genuinely help, where they don't, and what a codebase needs to be a good place to work in with agents.

• Product judgment — You care about the user experience as much as the technical solution. You can translate ambiguous workflows and business constraints into pragmatic, elegant product experiences.

• 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. You drive cross-team change through credibility, clear writing, architectural reasoning, and strong stakeholder alignment — not through authority.

• Collaborative Leadership: A proactive relationship-builder who can set technical direction and influence without formal authority, manage diverse stakeholders and build alignment on difficult technical decisions, while mentoring engineers.

• Language — Fluent English, written and spoken. You can make complex technical decisions legible to engineers, product partners, design partners, and leadership alike.

Our tech stack

• Frontend: TypeScript, React, Svelte — we are consolidating on React, and this role leads that migration.

• Backend: TypeScript, Node.js, Nest.js

• Database: MySQL

• Infrastructure: Kubernetes on AWS

• Source Control & CI/CD: GitHub

• Authentication: FusionAuth, Okta

• Internal Tools: Retool

• Messaging: Twilio, SendGrid

• Forms: Tally