Why join us

Brex is the AI-powered spend platform. We help companies spend with confidence with integrated corporate cards, banking, and global payments, plus intuitive software for travel and expenses. Tens of thousands of companies from startups to enterprises — including Door Dash, Flexport, and Compass — use Brex to proactively control spend, reduce costs, and increase efficiency on a global scale.

Working at Brex allows you to push your limits, challenge the status quo, and collaborate with some of the brightest minds in the industry. We’re committed to building a diverse team and inclusive culture and believe your potential should only be limited by how big you can dream. We make this a reality by empowering you with the tools, resources, and support you need to grow your career.

Engineering at Brex

Engineering at Brex is about building systems that scale with speed and intention. Our teams span Software, Data, Security, and IT, and operate with high autonomy and deep collaboration. We tackle hard technical problems, own our outcomes, and push for excellence at every level — from architecture to deployment. It’s an environment where engineering is a craft, and builders become leaders.

About the Team:

The Frontend Platform team builds and maintains the core web, mobile, and design systems infrastructure behind every customer-facing experience at Brex. The team is responsible for the stability, performance, and scalability of our frontend applications, and for creating an excellent developer experience for the teams that build them.

In this role, you’ll join a high-impact Web pod that partners closely with designers, product teams, and other engineers across the company. Together, you’ll drive the adoption of frontend architectural patterns, improve our product experience, and help define the future of frontend at Brex.

What you’ll do

• Own and contribute to platform, infrastructure, and developer experience improvements that impact all frontend engineers at Brex.

• Define and implement scalable patterns for data fetching, state management, and cross-product reusability in partnership with design system and product engineers.

• Set and uphold a high bar for quality, including performance, testing, accessibility, and observability.

• Own problems end-to-end: designing, implementing, testing, managing stakeholders, and measuring impact.

Where you’ll work

• This role will be based in our New York City office. We are a hybrid environment that combines the energy and connections of being in the office with the benefits and flexibility of working from home. We currently require a minimum of three coordinated days in the office per week
• Monday, Wednesday and Thursday. As a perk, we also have up to four weeks per year of fully remote work!

Requirements:

• Several years of experience building modern web applications using React, JavaScript/TypeScript, GraphQL, and modern CSS.

• Demonstrated interest in developer experience and platform engineering, with experience improving shared infrastructure, standards, or tooling.

• Solid testing practices and experience building reliable, maintainable client-side systems across browsers.

• Comfort managing projects and collaborating cross-functionally to balance competing requirements and priorities.

Bonus points:

• Familiarity with complex frontend migrations, refactors, or large-scale architectural changes.

• Strong intuition for balancing pragmatism with innovation when evaluating new technologies.

• Interest in emerging developer productivity tools, including agentic coding workflows.

Compensation:

The expected salary range for this role is $152,000 - $190,000 + equity. However, the starting base pay will depend on a number of factors including the candidate’s location, skills, experience, market demands, and internal pay parity.

Please be aware, job-seekers may be at risk of targeting by malicious actors looking for personal data. Brex recruiters will only reach out via LinkedIn or email with a brex.com domain. Any outreach claiming to be from Brex via other sources should be ignored.