Engineering Manager

Simple runs on a different engineering model. People make the judgment calls, and LLMs do the coding and research, many of them ry engineer here has several projects moving in parallel, and that changes what an engineering manager is for. Your job is to make sure all of that work lands with the quality our customers trust: clear ownership, sound decisions, a review and testing system that catches what tests miss, and a team that gets better every week.

You're a strong engineer who has led teams, and you still work hands‑on in the same tools, because this way of working can't be judged from the outside.

• Own delivery across the team: what's in flight, who owns it, what order it lands in, and what stands between each project and production
• Run the engineering system: the skills, rules, gates, and review standards that every person and every agent works within
• Hold the quality bar. Work gets tested where it will run, reviewed adversarially before anyone calls it done, and reported with what was run and what was seen.
• Stay hands‑on: run your own LLM sessions, read the diffs, and take real projects to the finish line
• Hire, coach, and grow engineers who work this way, and help strong engineers from traditional backgrounds make the move
• Treat model usage as a real budget, and keep quality high while cutting waste
• Turn incidents and mistakes into lasting fixes: a new gate, a new skill, a clearer rule
• Partner with Product, Design, and customers so the team builds what takes work away from people

• 8+ years of engineering experience, including 3+ years managing engineers on production software
• You're a self‑starter. You own the outcome and get projects to the finish line quickly and efficiently, without being chased.
• Solid, hands‑on experience with LLM‑driven engineering using tools like Claude Code and Codex. You run many sessions and projects at once in worktrees yourself.
• You've brought LLM‑driven practice to a whole team: shared skills, software factories, adversarial reviews, and the habits that make them stick
• Enough technical depth to challenge an architecture, and to read a Type Script, Go, Rust, or GraphQL change and say what's wrong with it
• A record of hiring and developing senior engineers
• You ask for evidence. A green check or a confident summary doesn't settle a question for you.
• Clear writing. Someone who hasn't read the code can act on your decisions and reports.
• You can show the work.

• You've been an early engineering leader at a startup
• Experience shipping AI products or enterprise platforms
• Working knowledge of Elixir and distributed systems
• Public writing or talks on how engineering teams work with LLMs

We review every application personally. You'll hear back from us within a week.