Skip to content
aitrainer.work - AI Training Jobs Platform
Engineering Full-Time
Yogi

Senior Software Engineer, Platform (US)

Yogi • New York, NY

Company

Yogi

Annual salary

$180k – $200k/yr

Location

New York, NY

Listed

45d ago

Experience:
3 to 6 years
Workplace:
On-site at Yogi's office in downtown New York City, at least 4 days per week. The company is centralizing its engineering team in New York, so New York-based candidates are strongly preferred, which also makes the on-site interview easy. On the call, the team said they're open to relocation for the right candidate. Travel: a company onsite once a year, plus client visits as needed.
Equity:
0.1% equity, 4-year vest with 1-year cliff

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

  • Design and build data models, data integrations, and data pipelines that support Yogi's AI-native Voice of Customer platform, which analyzes millions of consumer feedback records
  • Own platform capabilities end-to-end, including data models, pipelines, APIs, backend infrastructure, and observability, and make sure they have broad product impact
  • Work closely with product managers and product engineers to turn customer needs into new traditional and agentic features
  • Build internal tools and data-management interfaces inside the product. Customers won't see them, but they're key to how the platform runs
  • Lead the build of agentic workflows from research and model selection to production, using LLMs, APIs, and MCP
  • Find and adopt new AI and dev tools to improve team speed, code quality, and maintainability. Give technical support to Customer Success and Sales when needed Who you'll work with: You'll report directly to Chad Becker, Yogi's co-founder and CTO, and join an engineering team of about 8 people that the company is bringing together in New York. Who may not be a fit: Engineers who have only worked at big tech (for example, Meta or AWS) on narrow parts of large systems, people whose training is mainly from a coding bootcamp (an undergraduate degree is required, from any school), people focused on academic research rather than applied engineering, and resumes with a pattern of many jobs lasting under a year.

What you need

  • We need someone with 3+ years of professional software engineering experience, ideally at an AI product company, who has designed and built scalable data models, data pipelines, and data integrations. You should be comfortable taking the reins on a small, autonomous, New York-based team where nobody micromanages you, and you should have a track record of owning projects and shipping them. Bonus points if you have used LLMs to build agentic workflows (for example, researching and choosing the right model for a problem, beyond OpenAI or Claude), and if you work in Python.

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, Platform (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 – $200k/yr.

Is this role remote? +

The listing gives the location as New York, NY. On-site at Yogi's office in downtown New York City, at least 4 days per week. The company is centralizing its engineering team in New York, so New York-based candidates are strongly preferred, which also makes the on-site interview easy. On the call, the team said they're open to relocation for the right candidate. Travel: a company onsite once a year, plus client visits as needed.

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.

See all 10 Software Engineer interview questions →

Related roles

Yogi

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 →