Company Context
You’re the PM for CodeCanvas, a cloud-based IDE and dev platform (think GitHub Codespaces + VS Code) used by 4.5M monthly active developers and 38K paying teams. CodeCanvas makes money via seat-based subscriptions ($25–$60/seat/month) plus usage-based compute for cloud workspaces. The product is strong on desktop: deep extension ecosystem, fast keyboard-driven workflows, and reliable remote dev environments.
Over the last 12 months, CodeCanvas has seen a surge in mobile/tablet interest driven by (a) iPad Pro-class devices becoming common in engineering orgs, (b) distributed teams wanting “work from anywhere,” and (c) students learning to code on tablets. Leadership believes tablets could become a meaningful growth lever, but only if developers feel they can be equally creative and productive as on desktop.
User / Market Scenario
Personas
| Persona | Share of target | Primary jobs-to-be-done | Current behavior on tablet | Top frustration |
|---|
| On-call Engineer (SRE/Backend) | 30% | Triage incidents, hotfix, roll back | Uses phone/tablet for dashboards; switches to laptop for code | “I can’t confidently edit/debug on tablet.” |
| Student / Learner | 25% | Learn, run small projects, submit assignments | Codes on tablet with external keyboard | “Setup is painful; tooling is inconsistent.” |
| Indie Builder | 20% | Build features, ship quickly, manage repos | Uses tablet while traveling; relies on cloud | “Extensions and shortcuts don’t work the same.” |
| Engineering Manager / Reviewer | 25% | Review PRs, comment, minor edits | Reviews on tablet; rarely edits | “Review is OK, but editing is risky and slow.” |
Competitive landscape
- VS Code Desktop remains the gold standard for power users.
- GitHub Codespaces offers strong cloud workspaces but tablet UX is inconsistent.
- Replit is strong on web/tablet for learners, but lacks enterprise-grade workflows.
- JetBrains Fleet is emerging with remote dev, but tablet support is limited.
Market signals & internal data
- CodeCanvas has 1.1M monthly tablet sessions (web) but only 6% of those sessions include a code edit.
- Among paying teams, 22% have at least one member who attempted to use CodeCanvas on a tablet in the last quarter.
- D30 retention for tablet users is 19%, vs 41% for desktop users.
- Support tickets mentioning “tablet” increased 3.2× YoY; top themes: keyboard shortcuts, multi-file navigation, debugging, and extension compatibility.
Problem / Opportunity
Your VP Product asks: “How do we ensure a developer on a tablet has the same creative power as a developer on a desktop?”
The board has approved a bet: if CodeCanvas can deliver a credible tablet experience, Sales believes it can unlock $18–$25M in incremental ARR over 12–18 months via education and enterprise expansion (especially for teams standardizing on iPads).
However, there are real risks:
- A poor tablet experience could damage the brand (“toy IDE”).
- Enterprise customers require strong security controls.
- Performance on mobile browsers and constrained devices can degrade quickly.
Deliverables (what you must cover)
- Define “creative power” for developers in a measurable way. What user outcomes are you optimizing for (not features)?
- Choose a primary target segment for the first 6 months and justify why (impact, feasibility, strategic fit).
- Identify the top unmet needs / pain points for tablet development and map them to Jobs-to-be-Done.
- Propose an MVP solution (product experience + key features) that meaningfully closes the gap vs desktop.
- Prioritize your roadmap (MVP + next iteration) and explain trade-offs using a structured method (e.g., RICE/Kano).
- Define success metrics and an evaluation plan (how you’d know you achieved “desktop-level power” for the chosen segment).
Constraints
- Timeline: MVP must ship in 12 weeks with a public beta.
- Resourcing: 8 engineers total (3 frontend, 3 backend, 1 infra, 1 QA), plus 1 designer shared across two teams.
- Platform: Must work in mobile Safari and Chrome; a native app is not available this half.
- Security: Must support enterprise requirements: SSO/SAML, workspace isolation, and no copying of repo contents to the local device by default.
- Performance: P95 editor input latency must remain <50ms on iPad Pro-class devices; workspace reconnect must be <3 seconds on typical Wi-Fi.
Additional research snippets
- Usability tests show tablet users struggle with: (a) switching between files, terminal, and browser preview; (b) selecting text precisely; (c) running/debugging with breakpoints; (d) multi-cursor edits.
- 60% of tablet sessions include an external keyboard, but only 25% include a pointing device.
- Teams say they’d accept a tablet experience that is “90% of desktop” if the last 10% is clearly documented and there’s a seamless handoff to desktop.
You have 35–45 minutes in the interview. Assume the interviewer will ask follow-ups on scope, trade-offs, and measurement.
