Sr/Staff Software Engineer (US)
Hyphenate • Midtown South (Bryant Park), New York City, NY
Company
Hyphenate
Annual salary
$180k – $270k/yr
Location
Midtown South (Bryant Park), New York City, NY
Listed
151d ago
- Experience:
- 4 to 12 years
- Workplace:
- 5 days in-office near Bryant Park, Midtown South, New York City
- Visa:
- Visa sponsorship available
- Equity:
- 0.1-0.5%
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in Midtown South (Bryant Park), New York City, NY. Visa sponsorship available.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are looking for a Sr/Staff Software Engineer with 4-12 years of experience to own the foundational platform systems that every module at Hyphenate depends on. You'll build the agent frameworks, context systems, orchestration, and data infrastructure that multiply the output of the entire engineering team, all while working directly with customers, accountants, and founders at a company racing to become the undisputed #1 in AI-powered finance automation.
What will you be doing?
Building and owning the core platform layer, agent frameworks, orchestration, verification, observability, and developer tooling that every engineering pod ships on top of
Designing the financial data platform that ingests, normalizes, and reconciles data from ERPs, banks, billing, payroll, and CRMs into a trustworthy source of truth
Working directly with end customers and controllers to understand finance workflows and translate them into reusable platform abstractions
Leading architectural decisions under ambiguity, identifying bottlenecks, making technical bets, and shipping full-stack when the work calls for it
Driving horizontal, cross-functional work that raises the ceiling for the entire engineering team as the company scales from ~$3M to $10M ARR this year
Common questions
How do I apply for the Sr/Staff Software Engineer (US) role at Hyphenate? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Hyphenate role pay? +
The listing gives $180k – $270k/yr.
Is this role remote? +
The listing gives the location as Midtown South (Bryant Park), New York City, NY. 5 days in-office near Bryant Park, Midtown South, New York City. Visa sponsorship available.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →