About Anjali Iyer
Anjali Iyer is 29 and a senior data analyst in the growth pod of a Series C marketplace software company in Chicago — about 400 people, $80M in recurring revenue. Five years in the field and two and a half here leave her owning the acquisition and activation funnels, the model that feeds the executive dashboard, and the experimentation framework. She sits in an eight-person data organisation, mentors a junior analyst, and reports to a head of analytics. She studied statistics and rents in Logan Square with a partner who is also a data engineer. What makes her distinct is her position in the org chart’s blind spot: every product manager messages her at 4:45 asking for a number by nine, and the promotion she wants requires less of exactly that.
She optimises for intellectual honesty and calm rigour, and the phrase she reaches for is the question behind the question — she builds the query the stakeholder needs rather than the one they asked for. She is patient, warm and dryly funny, and gets sharp when someone disrespects a number. In chat she gives a clean answer and a caveat in two to four sentences; in meetings she speaks quietly with receipts. She rejects data-driven used as a boast, single source of truth when there are demonstrably five, and any query described as magic. It would be wrong to call her anti-automation — she uses model assistance for first drafts — but the line is precise: a feature that invents its own metric definitions instead of reading the ones her team maintains is disqualifying.
She is a strong subject at consideration and onboarding for analytics, business intelligence, data observability and metric-layer products. She is good at exposing a hollow modern-stack claim, asking to see the transformation-layer integration in a real repository and telling a native one from a wrapper that merely reads a manifest. She prefers usage-based pricing with a cap and describes per-seat pricing with viewer multipliers as a trap. She is alert to warehouse cost surprises and to demos populated with three rows of fabricated data. She writes the documentation and runs the enablement session, so she notices when reliability slips. She is weak at awareness stage: she ignores advertising and responds only to peers.
Her media is narrow, technical and community-shaped. Search, Reddit, X and podcasts score high, and the spine is two practitioner communities she is active in daily, backed by a data engineering subreddit, two essayists she reads closely and one industry newsletter. Her rhythm is heads-down query work from nine to noon, meetings from one to four, and the ad-hoc requests that pile up between four and six. The people she trusts are those communities, two analyst friends from university, a handful of named practitioners, and her partner, who does adjacent work. Instagram, Threads, YouTube, LinkedIn, email and app notifications sit in the middle; TikTok, connected television, out-of-home and text messages are low; Facebook, Snapchat, direct mail and print are absent.
