Product Engineer, Foundernest

• We are not hiring for a specific seniority, but you’ll need around 2 years of professional experience shipping software. Beyond that, how you think matters more than your title
• You are either full-stack or strong on the backend. Most of this work (integrations with APIs and SDKs, data pipelines, LLMs) lives on the backend, so that is where we need you to be solid
• Knowing your way around the frontend, or being up for learning it, is a plus
• You take ownership of problems, not tickets. You want to know who the user is and what actually helps them before you start building, and here you can just ask, because they’re one Slack message away
• You are lean and pragmatic. You would rather ship something small and useful this week than something perfect next quarter. You choose solutions proportional to the problem, and you can explain the tradeoffs you made
• You can work with people who are not engineers, explaining your reasoning without jargon, and taking a half-formed request from someone in sales and turning it into a real problem statement
• You pick things up fast and you like doing it. Most of what this role needs you can learn here

Desirable

• You would join our GTM Engineering team, where your closest teammates would be engineers and people from product, marketing and sales
• Our job is to automate the repetitive, mechanical work in sales, marketing and customer success, so those teams spend their time on the things only a human can do: closing deals, nurturing prospects, and building the relationships that turn into upsells
• We do that through experimentation, scrappy by design: find the shortest path to something that works, put it in front of people who will use it, learn and keep going
• In practice:
• Find where the most expensive friction is and build the thing that removes it, usually before the person drowning in it has to ask for help
• Build it end-to-end, mostly on the backend: integrations with the tools our teams already use, data pipelines, LLM-powered workflows, and whatever interface makes it usable
• Be measured on the outcome: leads, meetings booked, revenue generated
• A few things stand out about this role. Very few engineers get to draw a straight line from something they built to money the company made
• The feedback loop is short: you ship on Tuesday, someone is using it on Wednesday, by Friday you know whether it worked. And you’ll work on AI systems in production from day one
• Our stack:
• TypeScript, Python, PostgreSQL, MongoDB, BigQuery, AWS, LangChain, LangSmith, New Relic

• Please include the url of your LinkedIn profile