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 DoorDash, 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
The Engineering team includes Data, IT, Security, and Software, and is responsible for building innovative products and infrastructure for both internal and external users. We have multiple autonomous and collaborative teams who are eager to learn, teach, and constantly improve how things work. Together, we strive to build robust and scalable systems that enable Brex to grow rapidly and help our customers reach their full potential.
What you’ll do
The Application Infrastructure team sits in the Infrastructure group alongside Release Infrastructure and Cloud Infrastructure. We simplify writing code for every product developer at Brex.
As an engineer on the Application Infrastructure team you will build and own a suite of platforms and tools that Product Engineers use to deliver quality software solutions quickly. You’ll have the opportunity to work with a diverse range of technologies enabling remote development environments, pre-merge testing, Brex-wide dependency management, fast Kotlin builds, developer CLIs, federated GraphQL APIs, and more.
You’ll need to be comfortable regularly working on complex systems across multiple programming languages and levels of abstraction. You’ll have the opportunity to learn and push the frontier of providing the best financial software experience to help companies grow. You’ll be encouraged to be metric and data-driven and to think creatively to help Brex scale into new markets and verticals.
Where you’ll work
This role will be based in our Seattle office. You must be willing to work in office at least 2 days per week on Wednesday and Thursday. Employees will be able to work remotely for up to 4 weeks per year, for a minimum of one week at a time.
Responsibilities
- Analyze internal developer experience feedback to advocate for and iterate on developer platforms
- Own and maintain critical API infrastructure serving all of Brex’s frontends
- Upgrade critical shared library dependencies in our Kotlin stack
- Identify and implement reliability and performance improvements
- Uphold our high engineering standards and bring consistency to the codebases, infrastructure, and processes you will encounter
Requirements
- 3+ years of professional experience in a platform engineering role
- Kotlin or Golang fluency
- Kubernetes familiarity
- Platform or Full-Stack development background
- Strong communication, interpersonal, and project planning skills
Bonus points
- GraphQL experience, especially familiarity with Federated GraphQL
- Experience working with Bazel; bonus points if you’ve written rules or maintained Bazel as a platform
- Extensive experience with other multi-language build systems
- Experience extending Jetbrains IDEs
Compensation
The expected salary range for this role is $152,000 - $190,000. 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. Depending on the position offered, equity and other forms of compensation may be provided as part of a total compensation package.
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.