# Answer Guide: Motivation and Cross-Functional Collaboration ## 1. Why TikTok? Strong structure: - Product hook. - Business or user challenge. - Your fit. - How you hope to contribute. Example: "I am excited about TikTok because it turns creativity into community at global scale. The product is simple to use, but the underlying PM challenges are complex: balancing creator growth, viewer satisfaction, recommendation quality, safety, and monetization across markets. I am especially interested in products where small UX and ranking decisions affect both creators and viewers. In my past work, I have used experimentation, user research, and cross-functional execution to improve activation and retention, and I would like to bring that approach to a product with TikTok's scale and pace." TikTok-specific angles: - Creator-viewer ecosystem. - Recommendation and discovery. - Responsible growth and safety. - Internationalization. - Ads or commerce if relevant. - Fast experimentation culture. Avoid: - "I use TikTok a lot." - "It is a popular company." - Generic startup energy. ## 2. Current Role and Key Results Use a compact narrative: - Scope. - Users. - Team. - Metrics. - Results. Example: "In my current role, I own the onboarding experience for a B2B product used by enterprise admins. I work with design, engineering, data, sales, and support. The main problem was that new customers were not reaching first value quickly enough, which hurt activation and created support load. I led discovery through funnel analysis, support-ticket review, and customer interviews. We found that a permissions step caused most drop-off, so I prioritized a focused MVP instead of a full redesign. The launch improved activation and reduced onboarding-related tickets. My key contribution was aligning the team around one measurable outcome and making scope trade-offs explicit." If you have real metrics, use them. If not, describe the metric direction and timeframe. ## 3. Cross-Functional Collaboration Story Use STAR. **Situation:** We were launching a product improvement that required design, frontend, backend, data, and operations. Each team had different concerns: design wanted a polished flow, engineering wanted to reduce technical risk, and sales wanted a launch before a customer deadline. **Task:** I needed to deliver the customer outcome without overloading the team or creating quality issues. **Action:** I wrote a launch brief with the user problem, success metrics, must-have scope, trade-offs, and risks. I set up a weekly cross-functional review and a decision log. When scope conflict emerged, I separated must-have customer value from nice-to-have polish. We shipped the highest-impact flow first, added guardrails, and moved lower-priority enhancements to the next milestone. **Result:** We launched on time, improved the target metric, and avoided major quality issues. The decision log also reduced late-stage disagreement because stakeholders could see why trade-offs were made. **Learning:** Cross-functional leadership is not about having authority over every team. It is about creating clarity, making trade-offs explicit, and keeping the team focused on the user outcome. ## 4. Metrics to Mention Depending on your example: - Activation. - Retention. - Conversion. - Time to first value. - Creator publishes. - Viewer satisfaction. - Support tickets. - Revenue or cost. - Latency or reliability. - Safety guardrails. ## 5. Common Mistakes - Too much career history. - No clear role or ownership. - Motivation that could apply to any company. - Collaboration story with no conflict or trade-off. - Results with no metrics.