Great Question - Engineering Manager

Remote - United States2w ago

Remote Staff NA Engineering Manager Claude Cursor Close Harness Slack

Requirements

• How you lead. You manage people, not tickets. You know what each engineer on your team is trying to grow into, you give direct feedback early, and you’ve had the hard conversations: the engineer who’s checked out, the promotion that isn’t ready yet, the call that upsets someone. Strong engineers want to work for you because you make them better and get out of their way. • How you lead. • How you deliver. You turn half-shaped problems into a sensible sequence of work, spot the project that’s quietly slipping before it slips, and know when a plan needs more structure and when it needs less. You have the system design chops to help an engineer through a hard design, and to tell when an estimate or a blocker doesn’t hold up. • How you deliver. • Who you are. We’re a small team of exceptional engineers, and we only hire people who raise the bar. • This isn’t your first EM role; you’ve hired, run performance cycles and grown people into bigger scope. • Technically strong: at least a solid senior engineer by our bar. You don’t need to be the best engineer on the team, but you’ve built and run production systems yourself, and the engineers you lead respect you because you’ve done the work. • Live in an agentic coding harness (Claude Code, Codex, Cursor — we don’t care which), with real opinions about how a team, not just an individual, should work with agents to ship fast without letting quality slip. • Resourceful under ambiguity. You add just enough process to keep a team unblocked, and no more. • Close to the product. You care whether what shipped actually worked for customers, not just whether it shipped. • Write clearly. We’re remote and async-heavy; people who write clearly think (and prompt) clearly. • HOW WE BUILD • HOW WE BUILD • We’ve rebuilt how we work around AI agents, so our engineers are unblocked to work at AI-native speeds. Part of your job is keeping it that way as the team grows. • Main goes to production and approvals aren’t always required. Fast, automated CI is the gate, and we trust people to make the right judgments. • We invest in making the codebase easy to work in: written runbooks and conventions that help agents and new people find their way around quickly. • Running a few agents in parallel is easy, and expected. Sandboxes and preview environments are trivial to spawn. • You’ll always have the latest tools and models, and we’re generous with tokens. • Light on ceremony, high on accountability and communication. • This might not be for everyone, but if it excites you, please apply. We’re especially keen to meet managers who’ll challenge some of these ideas with their own hard-won lessons from the arena. • YOUR FIRST 90 DAYS • YOUR FIRST 90 DAYS • We expect you to hit the ground running, and fast. • Week 1: a 1:1 with every engineer on your teams. Use the harness to learn the codebase and merge your first PR. You’re in the customer data and the team’s Slack channels, learning where work gets stuck. • Week 1: • First 30 days: you know what each engineer is working toward and where each team’s delivery is at risk. You’ve taken over the rhythms of both teams and shipped something alongside them. • First 30 days: • By 60 days: you own delivery for Methods and Insights. You’ve fixed at least one thing about how the teams plan and execute with their PMs, and shipped a shared component or developer-experience improvement your teams lean on.

Responsibilities

• By 90 days: both teams ship predictably, and your engineers would tell you they’re growing. You have a view on hiring and team shape, and you’re pushing engineering strategy with Marcelo and the founders. • WHO SHOULDN'T APPLY • WHO SHOULDN'T APPLY • You manage through process. If your instinct is more ceremonies, more tickets and more status meetings, our engineers will tell you so, quickly. • You’ve stopped building. You don’t need to be the strongest IC on the team, but you need to be in the code, the tools and the architecture. • You want to build full-time. The people come first here, and that has to be the part you’re excited about. • This would be your first time managing. We’d love to meet you for a future role, but this one needs someone who’s done it before. • You’re not all-in on AI, or you think moving fast means lowering the bar. Agents are how we work, and you’ll set the example: shipping fast with them while holding a high technical and quality bar. Anyone can vibe-ship; getting that balance right is the job. • Ambiguity and shifting priorities wear you down. Problems arrive here half-shaped, and the roadmap has changed under our feet more than once this year.

Benefits

• A culture of customer obsession and curiosity • Opportunity to shape and scale a critical business function • Remote-first culture with high trust and high autonomy • Annual team retreats and virtual events • Opportunity to work on cutting-edge AI integrations that matter • Generous PTO, health benefits, and learning stipend • Equal Opportunity Statement • Great Question is committed to providing a workplace free from discrimination or harassment. We expect every member of the Great Question community to do their part to cultivate and maintain an environment where everyone has the opportunity to feel included, and is afforded the respect and dignity they deserve. • Decisions related to hiring, compensating, training, evaluating performance, or terminating are made fairly, and we provide equal employment opportunities to all qualified candidates and employees. We examine our unconscious biases and take responsibility for always striving to create an inclusive environment that makes every employee and candidate feel welcome.