Platform Engineer

The Problem

Our platform processes millions of sensitive financial documents for customers. As we onboard more lenders and expand into new verticals, the systems underneath need to get better, not just bigger. That means:

• Reliability at scale: Our customers handle large volumes of documents and data, and we operate at the core of their business. When they process an application through Heron, it needs to work every time.
• Developer experience: We have a ~15-person engineering team shipping features across multiple product lines. You'll build the internal tools, abstractions, and platform primitives that let product engineers move fast without breaking things.
• Product thinking (yes, even for internal tools): You're building for an internal audience (namely our pre-sales and post-sales teams, and other engineers), but you treat it like a product. That means understanding what we are trying to achieve for customers, designing intuitive tooling that makes that easy to do, and then iterating based on 'customer' feedback.
• Security and compliance: This is critical to our customers — sensitive financial and deal data must be handled to exacting standards. This isn't an afterthought; it's a core platform requirement.

Who Thrives Here

The ideal candidate is a backend engineer with 3-6 years of experience who has worked at a startup or growth-stage company and knows what it feels like to build something that actually matters. You're more drawn to the systems layer than the UI layer, and you get satisfaction from making other engineers more productive. More specifically:

• You have a strong CS foundation (degree or equivalent depth) and have a track record of writing clean, well-tested Python in production.
• You've built backend systems at a startup or growth-stage company and understand the trade-offs between speed and quality at that stage.
• You're comfortable with cloud infrastructure (we're on GCP), databases, CI/CD, and the unglamorous work that keeps a platform running.
• You care about reliability and developer experience. You might have fixed a flaky test suite in a previous job or built a simple but killer internal tool that everyone uses.
• You don't need to be told what to do - pilot not passenger. You see problems, propose solutions, and ship them. You're less interested in being the person on customer calls and more interested in being the person who makes sure the platform can handle whatever customers throw at it.