Head of Engineering
- Compensation
- Not disclosed
- Location
- San Francisco, US
- Work setup
- Not specified
- Seniority
- C level
- Employment
- Not specified
- Experience
- Not specified
- Category
- Not specified
- Posted
Skills
Must have
- You've built the machine before. You've led a 10-30 person engineering organization at a startup and personally installed the processes that made it work. You can walk us through what was broken, what
- Player-coach. You're a strong engineer who chose to lead, and you haven't stopped being an engineer. You don't lead from a distance.
- AI-pilled. You're not just excited about AI. You have rebuilt your own and your team's workflow around agents, and you have real opinions about what works and what is theater.
- You hold a high bar. You create an intense environment to do great work. You give feedback frequently, quickly, kindly, and specifically.
- You have backbone. The team is direct and will tell you when it disagrees. We want someone who brings data and holds the line when they think they're right.
- You have taste for reliability. You've owned a production system where failures were visible to customers, and you know the difference between a system that mostly works and one that's rock solid.
Nice to have
- Experience with LLM applications, agent infrastructure, or eval systems.
- Background in SRE, production engineering, or developer experience.
- Experience with products that are simultaneously consumer-grade in polish and B2B in requirements.
- You've hired and grown engineers who went on to do great things.
Full description
About Lindy
Our mission is to free humanity from work. We're starting by building an AI employee, not another tool people have to operate.
Lindy is like any other teammate: it joins your Slack, can be @-mentioned for help about anything, uses all your tools, and even builds its own if needed. It already saves countless hours to grateful teams who could no longer imagine working without it.
Our Culture
Lindy's Culture
You can expect an environment with little process and high empowerment, paired with high expectations and a strong sense of urgency. We're a small team of smart, intense people dedicated to doing the best work of our lives.
We are an in-office company, working from our downtown San Francisco office 4+ days a week. We sponsor visas and cover relocation costs up to $20,000.
The Role
We're looking for someone to own engineering at Lindy.
We build a genuinely complex product: an agent that acts on real people's email, calendars, meetings, and company data, where being wrong has consequences.
You'll own the operating system and delivery: how work gets planned, reviewed, shipped, and kept running, plus the reliability bar, hiring, and standards. You'll report to the CEO and partner closely with our Senior Engineering Manager, our engineers, and product.
This is a builder's job. You'll still read code, review PRs, occasionally write them, and make architecture calls.
Key Responsibilities
- Own engineering execution. Planning cadence, prioritization, and delivery. We must ship!
- Build the operating system. On-call that works, CI that's fast, fast code reviews, clean project handoffs, incident response, and a standup and review cadence people actually get value from.
- Own reliability. Our agent's reliability is the company's top priority. You own driving it up, and the eval infrastructure and self-improvement loops that get it there.
- Build an AI-native engineering organization. Engineering itself is being rewritten. You'll push agentic development, AI code review, and the internal tooling that lets a small team out-ship a large one, and you'll measure whether it's actually working.
- Own hiring and onboarding. Raise the bar, run a tight process, and get new engineers productive and clear about their responsibilities.
- Dive deep. Review code, weigh in on architecture, and keep enough context to have real opinions.
Who You Are
- You've built the machine before. You've led a 10-30 person engineering organization at a startup and personally installed the processes that made it work. You can walk us through what was broken, what you changed, and what happened to cycle time and quality.