SkillsSkill 3 of 5
Show the slope, not the snapshot
Worked example
Tell me about something you had to get good at quickly.
Tests: an honest start, a method, and a measured curve.
Zapier’s Tracy St.Dic: “we look at the slope and not just the snapshot.” (Tracy St.Dic, opens the source) Jul 19, 2026
The question
Maya is an operations analyst at a 120-store grocery chain: 40 high-volume stores and 80 low-volume. She and every number here are invented.
| Week 1 | Week 4 | |
|---|---|---|
| Queries the engineer rewrote | 8 of 10 | 1 of 10 |
| Report turnaround | 2 days | 4 hours |
Invented figures, the same ones she uses in the communication question.
“Tell me about something you had to get good at quickly.”
Your turn
Say your answer out loud, or jot notes below. Both work. Or skip to the worked answer.
Not saved by this site. Your browser may restore text when you navigate back.
The shape of a strong answer
- An honest starting point
- Why it mattered
- Method: sources, reps, feedback
- Before and after evidence
- What you’re learning now
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Start honestly
“I had three weeks to take over the store reports in SQL, and I’d never written a join.”
Why it works: A low start makes the curve believable.
Step 2: Describe a method someone could copy
“Thirty minutes a day on our own tables, AI to explain errors but never to write my final queries, and a weekly review with a data engineer.”
Why it works: A method, with AI use stated.
Step 3: Show the curve
“In week 1 the engineer rewrote 8 of my 10 queries; by week 4 it was 1 of 10. Report turnaround fell from 2 days to 4 hours.”
Why it works: Two measured before-and-afters.
Step 4: Say what you’re learning now
“Now I’m learning forecasting in Python the same way, and I can show you my week 1.”
Why it works: The slope continues.
The answer, in short
- Decision
- I went from never writing a join to running the store reports in SQL in four weeks.
- Because
- Rewrites fell from 8 of 10 queries to 1 of 10, and report turnaround from 2 days to 4 hours.
- What would change it
- If the rewrites hadn’t fallen by week 4, I’d have asked to pair with the engineer daily instead of weekly.
Common traps
- “I’m a fast learner” with no evidence.
- Effort without method.
- Using AI to skip the learning, and saying so without noticing.
Weak vs strong
“I picked up SQL really quickly and it went well.”
Fails all four checks: no starting point, no method, no evidence, nothing she’s learning now.
“From never writing a join to 1 in 10 queries needing a rewrite in four weeks; here’s the method.”
Check your answer
- Did I show where I started?
- Did I describe a method?
- Did I give before and after evidence?
- Did I say what I’m learning now?
Practice learning agility out loud with follow-up questions → Socratify
Last reviewed Nov 9, 2026