Software Engineer, Payments Infrastructure

Job Description

Brex is building the new global standard for financial services, starting with corporate cards. We are designing the product from first principles, enabling us to have unparalleled features and a seamless, modern experience for our customers. With backing from top venture firms and industry veterans such as Peter Thiel and Max Levchin, Brex is one of the fastest-growing startups to date, and we’re looking for someone to help scale the company with incredible people across the board. As a backend systems engineer, you will expand our core systems, add new products and features, and build new libraries. Based in San Francisco, our team is committed to creating a driven and diverse company with ambitious people from wide-ranging backgrounds.

We’re looking for people with a strong background or interest in building distributed financial systems, comfortable in dealing with lots of moving pieces, with a keen eye towards detail, and a high bar for correctness - any bug can lead. Most importantly, you should be enthusiastic about working deep in the core of our financial stack, building the payment rails that power Brex.

Responsibilities:

• Work with engineers across the company to build new systems, products and features.
• Create highly reliable and accurate systems that power the payment rails and money movement aspects of Brex
• Own problems end-to-end, thinking through everything from system design, data modeling, scalability, operability and ongoing metrics.
• Uphold our high engineering standards and bring consistency to the codebases, infrastructure, and processes you will encounter.
• Collaborate with experts in product, design, finance, and operations.

What We Value:

• Thinking about distributed systems and services, and writing high quality code.
• We work in Elixir, however languages can be learned: we care much more about your general engineering skill than knowledge of a particular language or framework.
• Similarly, we like to have a mix of people with and without payment backgrounds. We believe that the fintech aspects of the job can be learned much more easily than solid engineering skills.
• Caring about system design and building things correctly from day one, without cutting corners.
• Taking pride in working on projects to successful completion, involving a wide variety of technologies and systems.
• Holding yourself and others to a high bar when working with production systems.
• Ability to stitch many different services and processes together, even if you have not worked with them before.
• Thriving in a collaborative environment, filled with a diverse group of people with different expertise and backgrounds (we currently have around 30 nationalities represented, with more than 1⁄2 the company working in a country different from the one they grew up in).

Engineering at Brex:

• We work in an environment where it matters to make the right design decisions the first time, and as a result, take on less technical debt than other companies.
• We’re big fans of functional programming, especially given the effect of bugs in this space! We work closely with the Elixir community, and are always looking at increasing our open source contributions more broadly.
• Product is a highly collaborative initiative across multiple teams. Engineers are expected to understand and have product input, designing systems towards our long-term product vision.
• We'd rather have one strong, well-compensated engineer, instead of having 5 average engineers. Our customers are fine with fewer features, but are not ok with broken features.
• We believe in two equal track career growths between senior individual contributors and managers. We want people to contribute where they feel most impactful.
• We believe in small, accountable and autonomous teams of amazing people, eager to learn, teach and constantly improve our way of working.
• People have a strong sense of ownership and accountability for what they’re building. What we build today will be the foundation for dozens of other systems in the future.
• We are very frank on discussing technical matters. If one disagrees with how things are being done, we encourage them to speak up and help us get to the truth faster.