Company
Yogi
Annual salary
$180k – $220k/yr
Location
New York, NY
Listed
31d ago
- Experience:
- 3 to 6 years
- Workplace:
- On-site 4 days/week at Yogi's downtown New York City office. The company is centralizing engineering in NYC. NYC-local candidates are strongly preferred (it makes the onsite interview easy). The intake form lists no formal relocation support, but on the call the team said they are open to candidates willing to move to NYC. Remote-first candidates are not a fit.
- Equity:
- Competitive Equity
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 New York, NY.
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.
What you'll do
- Scale Yogi's agent platform, which runs thousands of agents, by evolving its infrastructure with a focus on reliability, orchestration, and performance.
- Take ownership of the insights inventory, the system that tracks, deduplicates, and catalogs the insights our agents find, so users and agents can act on them over time.
- Work closely with our PM, designer, two AI engineers, front-end engineer, and sales team to build a strong mental model of customer needs and turn it into product features.
- Drive data modeling and performance across PostgreSQL and ClickHouse as data volume and agent workloads grow, raising the team's backend and data modeling bar.
- Lead features from problem definition to production, including analytics features that both humans and agents can use, and Yogi's MCP server and the tools our agents use to work with Yogi data.
- Set and enforce standards for code quality, API design (versioning, backward compatibility, clear contracts), and data modeling to improve reliability and engineering velocity. Team and reporting: You'll report to Derrick Blakely and join a New York-based engineering team of about 8. Watch-outs: Be careful with candidates who have only worked in Big Tech on narrow scope, coding-bootcamp-only backgrounds (an undergrad degree is expected, CS preferred, though strong self-taught candidates are considered), many job stints under one year, mostly front-end recent work with unclear AI experience, people who want well-defined specs or pure infrastructure work away from product, and anyone looking for remote-first.
What you need
- We need someone with 3+ years of experience building and operating production backend systems who has strong data modeling and PostgreSQL skills, and who can be the "backbone" of a small, specialist-heavy product engineering team. You should be comfortable working full stack (contributing backend and front-end code equally, without being a front-end specialist) in a fast-moving, AI-native startup with very little micromanagement, and you should have a track record of owning and shipping meaningful projects end-to-end. Bonus points if you've built user-facing LLM, chatbot, or agent features, MCP servers, or agent tooling, or if you've helped set engineering standards at an early-stage startup.
About the engineering team
Yogi's engineering team has about 8 people and works out of the office in downtown New York City. A few engineers are based elsewhere right now, but the company is bringing the team together in New York. Engineers work in the office at least 4 days a week.
The team is split into two groups:
- Platform Engineering is led by Chad Becker, Yogi's co-founder and CTO. This team works mostly on the backend: data pipelines, data modeling, data integrations, agentic workflows with LLMs at the center, and internal data tools that live inside the product.
- Product Engineering is led by Derrick Blakely. It includes full-stack engineers, a front-end specialist and two AI-focused engineers. They work directly with Yogi's product manager and designer.
Yogi is also hiring a second engineer and a platform product manager, so the team is growing.
How the team works:
- No micromanagement: Senior engineers own whole capabilities, from data models and pipelines to APIs, UI, infrastructure and observability. They're expected to take charge and drive their work without hand-holding.
- AI-forward: Engineers use AI tools in their daily work. They look into new models beyond OpenAI and Claude and pick the right one for the problem.
- Works across the company: Engineers work closely with product, design, Sales and Customer Success. That helps them understand what customers need, speed up implementations and fix issues quickly.
- Learns from experience: The team values engineers who've seen how other teams solve hard problems, such as avoiding data modeling mistakes, and who bring those lessons with them.
Across the company, people say on every team survey that one of their favorite things about Yogi is the people.
Common questions
How do I apply for the Senior Software Engineer, Product (US) role at Yogi? +
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 Yogi role pay? +
The listing gives $180k – $220k/yr.
Is this role remote? +
The listing gives the location as New York, NY. On-site 4 days/week at Yogi's downtown New York City office. The company is centralizing engineering in NYC. NYC-local candidates are strongly preferred (it makes the onsite interview easy). The intake form lists no formal relocation support, but on the call the team said they are open to candidates willing to move to NYC. Remote-first candidates are not a fit.
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 →