← Back to Career Prep

Asana Interview Prep

Background Summary (2–3 min arc)

Arc: Marketplaces/logistics → Telecom/infrastructure → AI-focused next chapter

  1. Early career (1 sentence) — Marketing/growth background, Hong Kong and Canada
  2. Lalamove (1–2 sentences) — First real platform/ops strategy role, marketplace dynamics, logistics
  3. Ting/Tucows (bulk) — PM → Senior PM → Senior Manager Solutions Ops. Thread: ambiguous cross-functional problems → clear roadmaps → shipped. Website redesign + brand transition. Migration: 50k customers, 10+ teams, 99% uptime. AI Council member, co-authored Responsible AI Policy.
  4. Now (1 sentence) — Parental leave done, targeting AI + integrations space
  5. Skip or minimize: Uniwell, One Community, Creatology (unless asked)

Why Asana

Why This Role

Communications Integrations

AI Growth (backup/alternate)

Enterprise Gap Reframe

The gap: No direct enterprise PM experience. Sophia "prefers large enterprise experience background."

Honest acknowledgment: Haven't navigated the buyer/user split or sales-driven prioritization directly.

Reframe arguments:
- Internal platform work at Ting = proxy for enterprise dynamics (security, procurement, stakeholder conflicts)
- PLG enterprise software (Asana, Slack, Figma) wins by blurring the buyer/user line — users become evangelists who pull product into org
- Consumer-grade UX is the competitive advantage against legacy enterprise (SAP, Salesforce)
- Consumer experience is an asset, not a gap
- "Best enterprise tools win by being user-loved first — that's where my consumer instincts apply"
- ServiceMax implementation — enterprise change management, enterprise software adoption

What enterprise experience provides that Andrea doesn't have:
- Buyer ≠ User dynamics (IT/procurement buys, admins configure, end users consume)
- Sales-influenced roadmap (large accounts demanding features)
- Deployment as a product surface (admin consoles, SSO/SCIM, audit logs, permission models)
- Different feedback loops (can't A/B test easily, signal through Sales/CS)
- Platform partnerships at scale (Google/Microsoft/Slack partner programs, certification requirements, API governance)

Partnerships Angle

Transferable partnership experience:
- ServiceMax (self-scheduling) — technical feasibility with their platform
- Google Maps API (address serviceability) — worked around its limitations
- Zendesk integration work during brand transition

AI Positioning

Role Comparison: Which Fits Better?

Dimension Comms Integrations AI Growth
Enterprise exp. Sophia prefers it (gap) Not mentioned (non-issue)
AI fit Nice-to-have Core requirement (strength)
Growth exp. Not required Required — Lalamove counts
0→1 fit Extending existing Building new (strength)
Ambiguity Moderate High (strength)
Referral momentum Yes Introduced during screen

Decision: Focus on Comms Integrations (has momentum and referral backing). Keep AI Growth as backup if Comms doesn't progress. AI Growth is arguably the stronger natural fit.

Questions to Ask

Process/logistics:
- What does the interview process look like from here?
- What's the timeline you're working toward?

Role clarity:
- Is this a new role or backfill?
- How large is the Communications Integrations team currently?
- Who would this role report to?

What they're looking for:
- What's the difference between Senior PM and Principal PM in Asana's leveling?
- What would make someone successful in this role in the first year?

Culture/team:
- How does the hybrid schedule typically work?
- How does the PM team collaborate across different product areas?

Genuine curiosity:
- I saw the Claude integration just launched — how does the team think about the pace of AI partnerships right now?