Prompt
“Tell me about yourself” or “Walk me through your background.”
What interviewers are testing
- Whether you can summarize a non-linear career without rambling.
- Whether examples show increasing ownership, not just more years.
- Whether your close matches this role’s scope (Staff vs Senior, platform vs product-facing).
Senior/Staff DE angle
At senior levels, “about you” is really how you create leverage: reliability of data, cost of pipelines, time-to-insight for partners, and how you’ve influenced architecture and people, not only tickets shipped. Name scale (volume, SLAs, org breadth) in one sentence.
Framework (90 seconds)
- Now: Current scope — team, systems you touch (batch/streaming/warehouse), and what you own end-to-end.
- Path: One or two prior chapters with clear escalation in ambiguity and impact (smaller tasks → multi-team programs).
- Wins: One or two quantified outcomes (latency, cost, incidents prevented, experiment velocity).
- Why here: What you want next and why this company/team matches (specific, not generic “great culture”).
Keep tech stack mentions purpose-driven (why Spark vs SQL-only), not a résumé dump.
Follow-ups to expect
- “What’s the hardest technical trade-off you’ve made?”
- “How do you work with PMs / analytics?”
- “Why leave your current role?”
Bridge each back to a story you can expand — don’t invent new examples on the spot.
Mistakes to avoid
- Starting from college when your recent signal is stronger.
- Listing tools without problems they solved.
- Closing with only money or title — pair with impact and learning.
Drill
Record two versions: 90 seconds and 45 seconds. Same spine, tighter detail in the short one. Listen for filler words and whether every sentence earns its place.