Build customer-facing fintech features end-to-end on Brex's Vancouver engineering team

Brex is hiring a Software Engineer II for its Vancouver-based Engineering org to build new products end-to-end, from data models to client-side code, for its corporate card and spend-management platform. The role requires 4+ years of full-stack experience and close collaboration with Sales and Support to shape banking-experience features, working hybrid three days a week in office.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

End-to-end feature ownership (data model to client-side to metrics)
Full-stack development including client-side architecture and testing
Cross-functional collaboration with Sales and Support
Engineering quality bar and iterative polish
Building for a fintech/banking customer experience

Common question themes

Walk through a feature you owned end-to-end, from data model to shipped UI

Describe a time customer or support feedback changed your technical design

How do you architect and test client-side code so it's reliable

Tell me about a time you had to 'polish' a feature beyond just making it work

How would you think about reliability when building a customer-facing banking feature

How candidates describe it

Real Software Engineer II interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Brex Software Engineer interviews

All Brex interviews