Senior Backend Engineer (Node.js & SQL)

Since launching Infracost in 2021, we’ve been pulled by engineers who all want to Shift FinOps Left. We enable them to proactively find and fix cloud cost issues before they hit production. We plug directly into developer workflows (like GitHub and Azure Repos), show cost impact in pull requests, enforce tagging and FinOps best practices, and even generate PRs to fix issues automatically.

We're backed by Sequoia, YC and trusted by Fortune 500 enterprises. You'll join a small, experienced, and supportive team that's shipping fast, solving real infrastructure problems, and having fun while doing it.

Help engineers fix what matters. You’ll work closely with PMs, designers, and engineers to build fast, reliable backends that power real-time infrastructure insights for thousands of engineers.

What we’re looking for:

• GMT+2 to GMT-6 time zone. We work primarily async via Slack, with regular overlap for pairing, reviews, and design discussions.

• Strong Node.js and TypeScript experience. You know how to track down memory leaks and performance issues.

• You can write complex PostgreSQL queries, understand query plans, and know when to reach for indexes, window functions, or CTEs. You’ve debugged deadlocks, optimized slow queries, and can untangle gnarly data models.

• You have a strong bias for action. You take ownership of problems end-to-end, make pragmatic decisions, ship iteratively, and jump on production issues when they matter.

• You've built something you're proud of.

• You’ll thrive in an amazing, experienced, hardworking, respectful, supportive, and fun team.

• You fix problems with tooling rather than adding process. We build and maintain our own internal CLI to streamline day-to-day engineering work, and we appreciate other good tools like Linear and Notion.

• (Preferred) You've worked with GraphQL and understand how to design flexible, efficient schemas.

Examples of challenges we have worked on recently:

• Scaled to support customers with thousands of GitHub organizations and tens of thousands of repositories. This has required us to overhaul our APIs, interfaces, onboarding processes, infrastructure, and more.

• Automatically fixing infrastructure issues. With infrastructure changes there's a lower tolerance for AI-generated slop - there's not the same safety nets in terms of testing and the risk is often higher. We've been iterating on our system that combines the AI-generated changes with our best-in-class static analysis engine to robustly open good-quality PRs to fix the most important issues for our customers.

• Built the Issue Explorer**,** a frontend and backend system for surfacing infrastructure issues at scale. We had to balance performance, UX, and data complexity to let enterprise customers filter, group, and chart tens of thousands of issues across their entire codebase.

What we value:

1. Ustomer, not customer: It is all about seeing us and the customer as one. We like to be a part of the user’s team, and help them however we can. If the user is not successful, then we will not be either so we try to walk in their shoes. It's more than work - we build relationships and community with users and customers.

2. Open is our core: Put yourself out there. Show your learning. Transparency builds confidence. Encourage sharing the good and the bad. The best decisions are made when everyone has access to all the data. Be straightforward and kind, feedback is about your work not your person.

3. Let's JEDI: Let’s Just Effing Do It! Own it and move fast. A good plan fiercely executed now is better than a perfect plan later. We ask for help and unblock each other. The main thing is to keep the main thing the main thing.

Benefits:

• Fully remote team with no office to go back to

• Two meetups a year - last year we went to Barcelona and Berlin

• Employee-friendly equity terms, including a 10 year exercise window

• 401k matching / pension contributions (US, UK, Germany & Canada)

• Health, dental, and vision insurance (US, Germany & Canada)

• 31 days paid leave per year (includes national holidays)

• 12 weeks paid parental leave

• 25 minute initial chat

• Two or three 55 minute technical interviews (including code walkthrough)

• 55 minute value-based interview