Deliver a crisp self-introduction

90-Second Self-Introduction: Senior Data Scientist (Figma)

Context

You are preparing for an HR screen (behavioral/leadership) for a Senior Data Scientist role at Figma. Deliver a concise, structured self-introduction.

Prompt

In roughly 90 seconds, include the following:

1. One-line background: education, years of experience, and core analytics focus.
2. Two quantifiable, product-analytics wins relevant to a collaborative design SaaS (e.g., an experiment that increased activation; an analysis that improved DAU/WAU or onboarding).
3. One cross-functional partnership example with Design/PM/Eng showcasing influence without authority.
4. Why Figma specifically (mission, user base, experimentation culture).

Make it specific: cite concrete metrics (e.g., +8% activation, +0.4 pp retention, 20% faster experiment velocity). End with one sentence on what you want to drive in your first 90 days.

Target length: ~200 words (about 90 seconds at a typical speaking pace).

Solution

Ready-to-deliver 90-second script

Hi, I'm Alex - MS in Statistics with 8 years in product analytics focused on growth experiments and collaboration flows.

Two relevant wins: 1) At a collaborative SaaS, I redefined activation to 'create first project and invite a collaborator in 24h' and shipped guided onboarding plus an invite nudge; activation rose +8% and D30 retention +0.4 pp. 2) At a B2B design-adjacent tool, analysis of sharing and template adoption led us to streamline the share modal and surface team templates; DAU/WAU increased +12% and time-to-first-collab fell 22%. I also built a reusable metric layer that sped experiment velocity by 20%.

Cross-functionally, I convened PM, Design, and Eng to de-risk a template-gallery change; telling the user story with funnels and session replays helped prioritize a low-lift MVP without authority, cutting drop-off by 18%.

Why Figma: I'm drawn to the mission to make design multiplayer, the scale of the community and plugins, and an experiment-driven culture - especially chances to improve FigJam and design-systems onboarding.

In my first 90 days, I'd align on activation/retention definitions (e.g., first file + invite + multiplayer edit), audit instrumentation, and ship two experiments on onboarding and share flows targeting +5% activation and +15% faster experiment velocity.

Personalize this quickly

• One-liner: Degree or training + years + focus (experimentation, onboarding, collaboration).
• Win 1 (activation): Redefine activation for collaborative behavior; cite activation and retention lift.
• Win 2 (DAU/WAU or onboarding): Show behavioral insight -> product change -> metric lift; mention process impact (e.g., speed).
• Cross-functional influence: How you aligned PM/Design/Eng without authority; include a concrete outcome.
• Why Figma: Mission (multiplayer design), community scale, experimentation culture; mention FigJam/design systems if relevant.
• 90 days: Metrics you will own, 1-2 experiments, instrumentation audit.

Timing and delivery tips

• Aim for ~200 words; keep each section to 15-20 seconds.
• Lead with metrics and user behavior, not tooling. Mention tools only if asked.
• Use Figma-relevant activation language: first file + invite + multiplayer edit.
• Pitfalls: being generic, skipping numbers, exceeding time, or forgetting the 90-day goal.