Startups

Product Engineer

straddle · Broomfield, CO · On-site

← All jobs
About straddle

About Straddle, Inc. Straddle is an open-banking payments platform for account-to-account money movement. Backed by Drive Capital.

About the role

We have multiple openings on our Product Engineering team, which builds the customer-facing surfaces of our account-to-account payments platform. Each engineer owns an entire surface: onboarding, bank connectivity, the payment lifecycle, payouts, or the customer dashboard. Not a queue of tickets inside it. You own what gets built, why, whether it works, and what it costs the customer when it doesn't.

What they're looking for

  • Specify work for agents. Turn a product decision into intent, constraints, edge cases, and acceptance criteria. Ambiguity a teammate would resolve by asking, an agent resolves by guessing
  • Review adversarially. Hunt the plausible but wrong: missed edge cases, swallowed errors, queries that only work at current scale, security assumptions that don't hold. Reject work below the bar and say why
  • Build guardrails. Tests, evals, and CI checks that let generated code be trusted, so the second feature in your surface ships faster than the first
  • Design APIs as products. Naming, error semantics, pagination, webhook contracts, docs. Every breaking change is a cost paid by someone else
  • Ship interfaces people can use. Responsive TypeScript frontends, including the loading states, empty states, and error copy that agents deprioritize and users notice immediately
  • Model the domain. Data models and storage decisions behind your surface. Getting this wrong is expensive in a way agents can't rescue
More about this role

About the role

We have multiple openings on our Product Engineering team, which builds the customer-facing surfaces of our account-to-account payments platform. Each engineer owns an entire surface: onboarding, bank connectivity, the payment lifecycle, payouts, or the customer dashboard. Not a queue of tickets inside it. You own what gets built, why, whether it works, and what it costs the customer when it doesn't.

Most of the code is written by our agentic system, and you're accountable for it. You specify work precisely enough for an agent to execute, review the output harder than you'd review your own, build the guardrails that make it trustworthy, and know when to write it yourself. This is not a role for someone who wants to stop being an engineer. You have to tell good code from bad at speed, because you're the last check before production.

The scarce input is customer insight. If shipping is no longer bounded by how fast code gets written, it's bounded by knowing what to build. Our product is an API and the surfaces around it, so API design is product design here. Platform Engineering owns the infrastructure, so your time goes to product rather than plumbing.

Full-time in...

Read the full posting on straddle's site ↗

Engineering

Build your edge while you search

Free tools for founders and investors, plus VC Unfiltered, our take on startups, venture and the people who build them.