Docker
Staff UX Researcher
Canada · posted 2026-11-17 · listed from another job board
Source: ASHBY
At a glance
- Workplace
- Remote
- Location
- Canada
- Hiring in
- CA (as named in the listing)
- Region
- North america
- Time zones
- UTC−8 to UTC−3
- Employment type
- Full time
- Seniority
- Mid senior
- Skills
- AI, Docker
- Posted
- 2026-11-17
About the job
ABOUT DOCKER
Docker has been one of the most loved brands in developer tooling, trusted by more than 20 million monthly users and over 20 billion container image pulls. From solo founders to the world's largest companies, developers rely on Docker to build, share, and run their applications across our suite of products including Docker Desktop, Docker Hub, and Docker Scout.
We are a globally distributed, remote-first team building the tools that define how software gets built and delivered. As AI agents redefine software development, Docker is at the center of that shift, providing the sandboxed environments, verified images, and secure infrastructure that make autonomous workflows trustworthy by default.
_______________________________________________________________________
THE ROLE
Docker is seeking a Staff UX Researcher to own research strategy for a major area of our product ecosystem, such as developer, agentic, or desktop experiences. You will decide what that area needs to learn, run the research that answers it, and make sure the evidence changes what gets built.
You will operate as a hands-on leader embedded with product, design, and engineering. You will partner directly with area leadership, coach PMs, designers, and engineers in customer-driven engineering practices, and mentor other researchers. You will also keep product marketing and field teams aligned on what customers need, and share tested AI-enabled methods with the wider research team.
_______________________________________________________________________
WHAT YOU'LL OWN
- Area Research Strategy: Own research strategy for a product area or program that spans several teams, and set its priorities. Identify the target customers for the area, influence product area decisions, and lead research initiatives that shape the roadmap. Plan research across teams so findings arrive when decisions are made, hold the craft bar for the area's research, and track whether research moved measurable outcomes in the area.
- Mixed-Methods Research & Synthesis: Lead end-to-end qualitative and quantitative studies, from discovery to evaluation, that guide product direction in complex developer, agentic, and technical contexts. Combine methods in new ways for ambiguous problems, and find ways to reach customers that the area has not tried before. Help the area test its strongly held assumptions against competing explanations, so the team discovers what is true together. Turn evidence from many studies, including behavioral data, into explanations that guide the area's decisions.
- AI-Enabled Research Practice: Build reusable AI workflows for your area and use AI to learn from more customers, faster, with every finding traceable to evidence and every AI output checked before it reaches a partner. Use human judgment and discernment to decide where AI moderation fits and where AI analysis is not reliable enough to act on. Share what works and what fails.
- Coaching & Mentorship: Build customer-driven habits into how your area plans and ships. Make customer learning something the whole team does, so research is never a handoff, and win adoption in small steps. Set guidance on when to be scrappy and when to be rigorous, based on the risk of the decision. Mentor researchers on craft and give clear, actionable feedback. Help shape how the team onboards and develops new researchers.
- Leadership Partnership: Resolve disagreements between teams with evidence and earn the trust of area leaders. Keep product marketing and field teams informed and aligned, so the area's customer story is the same in the product and in the market. Facilitate conversations across product, design, and engineering, and with marketing, sales, and support, so everyone is clear on what customers need and what to do about it. Use real customer stories, not invented personas, to move partners to act. Apply the Operations standards in unclear cases, escalate what they do not cover, and tell Operations where they are too heavy or too light.
- Team & Customer-Driven Culture: Teach a shared language of assumptions, hypotheses, and experiments, reward learning over being proven right, and spotlight teams doing it well. Spotlight teams that do this well. Set team norms of peer review, constructive challenge, and credit for others' work. Seek out new ground for the practice, shape the team's approach as research practice changes, and make it easy for other researchers to learn and grow from it.
_______________________________________________________________________
WHAT GOOD LOOKS LIKE IN THIS ROLE
- Decisions Change: Product and design leaders in your area point to specific roadmap choices, pivots, or cancelled work that your research shaped, and your area has a research roadmap that stakeholders understand and use.
- Rigor That Holds Up: Findings are traceable to evidence, tested against competing explanations, and trusted by engineers as well as designers.
- Teams Learn Without You: PMs