Great Question logo

Engineering Manager - Great Question

About Great Question

Great Question is the all-in-one AI customer research platform for understanding your customers. Our platform enables teams to recruit participants, run research, and share insights – all in one place. Backed by world-class investors and trusted by industry-leading teams like Gusto, Experian, Canva, and Brex, we’re building the future of customer research.

We believe AI is a multiplier for creativity, speed, and scale. Everyone on the team is encouraged to lean into AI, not just to be more efficient, but to push boundaries and unlock new possibilities. Whether you’re writing, designing, coding, or analyzing, we expect you to explore how AI can elevate your craft.

Our culture is built on high trust, high agency, and high emotional intelligence. Research, design, and product teams at ServiceNow, Brex, and Canva run their customer research on us, and we raised a $13M Series A led by Inovia late last year after going through YC in 2021.

This year we’ve been rebuilding core parts of our product agent-first, and the engineering team is growing to match. We are hiring an Engineering Manager to lead two of the teams at the center of that work.

The Role

You’ll lead our Methods and Insights teams and report to our Director of Engineering. Alongside our Research Operations team, these are the pillar teams behind most of the product. Methods powers every study and the experience participants see; Insights makes sense of the data and helps customers act on it.

The job has three core pillars:

  • People: Hiring and staffing, 1:1s, coaching, feedback, performance management, and growth. You're the person your engineers trust to tell them the truth about their work and to push hard for their growth.
  • Delivery and operations: You run the cycle for your teams: planning, sequencing, unblocking, managing risk, and working with stakeholders. You make sure commitments ship at high quality and own operational health once live, from monitoring to red-teaming.
  • Building the factory: Our engineers each run several agents, so the slow part is no longer writing code—it’s specs, review, and judgment. You help build that system for your teams: the harness, conventions, CI gates, and shared components that let agents do good work quickly and reliably.

What We're Looking For

  • Leadership track record: This isn’t your first EM role; you’ve hired, run performance cycles, and grown people into bigger scope.
  • Technical strength: At least a solid senior engineer level. You don’t need to be the best engineer on the team, but you’ve built and run production systems yourself.
  • Agentic coding fluency: Live in an agentic coding harness (Claude Code, Codex, Cursor, etc.), with real opinions about how a team works with agents to ship fast without letting quality slip.
  • Resourcefulness under ambiguity: You add just enough process to keep a team unblocked, and no more.
  • Product focus: You care whether what shipped actually worked for customers, not just whether it shipped.
  • Strong communication: Clear written communication. We’re remote and async-heavy; people who write clearly think and prompt clearly.

How We Build

  • 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 team members onboard quickly.
  • Running a few agents in parallel is standard. Sandboxes and preview environments are trivial to spawn.
  • Access to the latest tools and models, with generous token usage.
  • Light on ceremony, high on accountability and communication.

Your First 90 Days

  • Week 1: A 1:1 with every engineer on your teams. Use the harness to learn the codebase and merge your first PR. Dive into customer data and team Slack channels to identify bottlenecks.
  • First 30 days: Understand each engineer's goals and identify delivery risks. Take over the operational rhythms of both teams and ship something alongside them.
  • By 60 days: Own delivery for Methods and Insights. Improve how the teams plan and execute with PMs, and ship a shared component or developer-experience improvement.
  • By 90 days: Both teams ship predictably, engineers are growing, you have a clear strategy on hiring and team shape, and you are contributing to broad engineering strategy.

Who Shouldn't Apply

  • Managers who rely purely on heavy process, ceremonies, and status meetings.
  • Leaders who have completely stopped touching code, tools, and architecture.
  • Anyone looking for a full-time IC coding role.
  • First-time managers without prior people management experience.
  • Those skeptical of AI-native workflows or uncomfortable with ambiguity and shifting roadmaps.

Why You’ll Love Working Here

  • 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
  • Competitive compensation & equity
  • Generous PTO, health benefits, and learning stipend

Timezone overlap

UTC-8–-4

Culture

Async-friendly

Open to

US

Sign in to track applications and earn points.

More roles at Great Question

Similar remote roles