Updated September 4, 2026

<aside> <img src="notion://custom_emoji/df39f813-ef21-81af-8128-00035c330f1e/3499f813-ef21-809d-a932-007a03736a42" alt="notion://custom_emoji/df39f813-ef21-81af-8128-00035c330f1e/3499f813-ef21-809d-a932-007a03736a42" width="40px" />

About Hammock

Hammock (usehammock.co) exists to help people live healthier lives and save money while they do it. We’re building the first HSA/FSA that actually works for modern life by letting people spend pre-tax dollars on everyday wellness like the gym, recovery, and prevention. Founded by repeat healthcare founders, we’re backed by a16z Speedrun, Opal Ventures, and founders from companies like Thirty Madison, Clay, and Papa.

</aside>

About Us

• We’re a small team, based in Union Square, NYC
• We work 4 days in person, 1 day flexible, indexing on tight collaboration and fast feedback loops

The Role

We’re looking for a product-minded backend engineer to help us build the financial and data infrastructure powering Hammock.

This is a high-ownership role working on systems at the intersection of payments, healthcare, and consumer products. You’ll make foundational decisions on architecture, data models, and how we handle sensitive financial and health information.

Today, we’re a very small team building quickly. The focus right now is on building things well and shipping fast, not on management. That said, this role can evolve over time as the team grows.

What You’ll Do

• Design and build core backend systems across payments, ledgers, and health eligibility
• Own architectural decisions around data integrity, fault tolerance, and security
• Build reliable integrations with external providers and APIs
• Work closely with product and design to ship quickly without sacrificing quality
• Use AI coding tools and build agentic workflows to automate development and produce well-tested, elegant code quickly

What we're looking for

• Strong experience in backend systems, ideally in payments, fintech, or healthcare.
• Experience with providers like Stripe, Plaid, or similar ecosystems
• Strong understanding of relational and transactional data systems (consistency, atomicity, concurrency, locking)
• Comfort making high-impact architectural decisions with minimal oversight
• A builder mindset with a bias toward shipping and iteration
• Deep familiarity with AI coding tools and interest in building agentic workflows that generate well-tested, maintainable code with faster iteration cycles