Note: The job is a remote job and is open to candidates in USA. Straddle, Inc. builds an open-banking payments platform for account-to-account money movement. The Product Engineer owns customer-facing product surfaces end to end, from customer insight and API design through implementation, launch, and operational health. The role also directs and reviews agent-generated code, builds quality guardrails, and integrates banking and identity partners.
Responsibilities
- Own a product surface end to end. The problem, the decision about what to build and what to refuse, the implementation, the outcome metric you defined before you started, and the operational health after launch. On-call for your surface included
- Develop customer insight. Talk to customers and to the people who support them. Read the tickets, watch the analytics, integrate against your own surface and feel where it's awkward. Bring a defensible point of view to planning
- 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
- Integrate partners. Open banking APIs (Plaid, Finicity, MX) and KYC providers. Handle webhooks reliably and design around partners that fail
- Own security. Authentication, authorization, encryption, common vulnerabilities, PCI and SOC 2 controls. Assume generated code isn't secure until you've verified it
- Raise the bar. Set standards, mentor other engineers on directing and reviewing agentic work, and push hard feedback into our platform tooling
Skills
- 5+ years in .NET and TypeScript
- Comfortable with CQRS, IoC, Clean Architecture, DDD, SOLID, and Entity Framework
- Data model through API to interface
- A track record of shipping things customers used, and evidence you cared whether they did
- You can describe a feature you argued against building, or a decision you reversed after seeing data
- Intent, constraints, and edge cases expressed unambiguously
- Coding agents as a serious part of your workflow, with calibrated judgment about where they fail
- Take a loose problem, ask the right questions, commit with incomplete information
- Schemas, queries, and performance work in MySQL, PostgreSQL, or similar
- External API integration, message queues, and asynchronous processing for background jobs and webhook handling
- Secure coding practices, awareness of data privacy and compliance in fintech, and a sense of what makes a test suite protective rather than decorative
- Explain a tradeoff to a non-engineer, talk to customers without a translator, give and take direct feedback
- Data structures, algorithms, complexity
- If you've built evals, harnesses, or guardrails for agent output, say so
- From a degree or from work: data structures, algorithms, complexity
- Fintech or payments: ledgers, reconciliation, ACH file processing, Nacha and PCI DSS
- Open banking APIs (Plaid, Stripe, PayPal): bank auth flows and token handling
- Developer experience work: SDKs, embeddable widgets, API docs, sandboxes
- Ownership on a small team: founder, first engineer, or sole owner of a surface
- Azure (App Service, Container Apps, Functions, Cosmos DB, Service Bus) or AWS and GCP equivalents
- Observability and product analytics: Application Insights, Datadog, PostHog
- Event sourcing or NoSQL
- Design sensibility: able to make reasonable calls without a designer
Benefits
- Equity
- Hybrid and remote flexibility
Company Overview