FinOps Engineer
PostHog
full-time
Posted on:
Location Type: Remote
Location: United States
Visit company websiteExplore more
About the role
- Most companies treat FinOps like a janitorial service: engineers make a mess, and the FinOps person follows them around with a broom and a spreadsheet of "unattached EBS volumes."
- At our scale, we aren't interested in "saving money" in the abstract. We’re interested in efficiency as a product feature. Every dollar we shave off our unit economics is a dollar we can pass directly back to our customers, making our product more competitive and our margins healthier.
- We’re shifting FinOps left!
- We believe the most expensive line of code is the one written without considering how it scales. We want to move cost conversations from the billing cycle to the design doc. In this role, you aren’t a gatekeeper; you’re an enabler. You’ll be successful when:
- cost is a first-class citizen: Engineers treat "cost per query" or "cost per ingest" with the same rigor they treat latency or availability. You’ll be the person engineers go to when asking, "Will this architecture be expensive?" and have the credibility to provide the right answer.
- the "hot potato" dies: No more reactive scrambles when the AWS bill hits. You’ll build the systems that give teams the autonomy to own their own margins.
- cultural compounding: You shouldn't be a hero who personally finds $2M in a closet. You’ll be the architect who builds a culture where 100 engineers make 1% better decisions every day.
- Own the strategy and enable cost-aware engineering: You build the systems and attribution structures (tagging, showbacks) that give teams ownership of their impact.
- Partner with Finance: Explain variances, maintain clean cost allocation, and help the business understand margins by product line.
Requirements
- Previous experience in FinOps, cloud cost management, or cloud governance: We’re looking for experts, not just "I looked at AWS bills sometimes"
- Deep cloud fluency: You don't just know AWS/GCP are expensive; you understand the nuances of cross-AZ data transfer, NAT gateway costs, and the price-performance ratios of different instance families.
- Kubernetes expertise: You understand how to allocate costs in K8s (which we know is notoriously hard).
- the hybrid brain: You can speak SQL and CI/CD with engineers in the morning, then pivot to forecasting and margin analysis with the Finance Lead in the afternoon.
- Bias for action: You’re able to write scripts to automate tagging hygiene rather than send a nagging Slack message.
- CI/CD awareness: You understand how deployment patterns affect cost
- Communication skills: You can explain cost insights to both engineers and finance without losing either audience.
Benefits
- Transparency: Everyone can read about our roadmap, how we pay (or even let go of) people, our strategy, and how we work, in our public company handbook. Internally, we share revenue, notes and slides from board meetings, and fundraising plans, so everyone has the context they need to make good decisions.
- Autonomy: We don’t tell anyone what to do. Everyone chooses what to work on next based on what's going to have the biggest impact on our customers, and what they find interesting and motivating to work on. Engineers lead product teams and make product decisions. Teams are flexible and easy to change when needed.
- Shipping fast: Why not now? We want to build a lot of products; we can't do that shipping at a normal pace. We've built the company around small teams – autonomous, highly-efficient groups of cracked engineers who can outship much larger companies because they own their products end-to-end.
- Time for building: Nothing gets shipped in a meeting. We're a natively remote company. We default to async communication – PRs > Issues > Slack. Tuesdays and Thursdays are meeting-free days, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.
- Ambition: We want to solve big problems. We strongly believe that aiming for the best possible upside, and sometimes missing, is better than never trying. We're optimistic about what's possible and our ability to get there.
- Being weird: Weird means redesigning an already world-class website for the 5th time. It means shipping literally every product that relates to customer data. It means building an objectively unnecessary developer toy with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.
Applicant Tracking System Keywords
Tip: use these terms in your resume and cover letter to boost ATS matches.
Hard Skills & Tools
FinOpscloud cost managementcloud governanceAWSGCPKubernetesSQLCI/CDcost allocationscripting
Soft Skills
communication skillsbias for actioncollaborationstrategic thinkingproblem-solvingautonomycredibilitycultural compoundingcost awarenessanalytical thinking