Loading
This is a sample. Priya Fernando is not a real candidate and this interview never happened — everything below is the report HireMonkey produces, rendered by the same screen you would see after your own interview.
Create free accountA strong, well-evidenced interview. Priya explained the migration she led in concrete terms and was candid about what went wrong with it, which is the answer that moved the score most. The gap is depth on query performance: she described the symptoms of the slow dashboard accurately but reached for caching before measurement, and could not say what the query plan showed.
This was a good interview and the recommendation reflects that. Your communication is the strongest thing you have — the lineage answer was the best answer of the hour, and the way you signpost your reasoning makes you easy to follow. Two things to work on. First, on the slow-dashboard question you proposed a materialised view before you had established what was slow; practise saying what you would measure, and what each result would rule out, before you name a fix. Interviewers read that as diagnosis rather than guesswork, and it is the single change that would have moved that answer from a 2 to a 4. Second, get a query plan in front of you before your next interview: you clearly understand indexes conceptually, but you could not point at evidence of having used one in anger.
Built from the job description before the interview started. Must-haves are marked: missing one of those is what caps the recommendation.
Designed the star schema she described, and justified the grain of the fact table.
Comfortable with pandas and with the trade-off against pushing the work into the warehouse.
Reached for a cache before measuring. Could not say what the query plan showed.
Two unprompted examples of translating a technical constraint into a business one.
Named her own mistake on the migration before being asked what went wrong.
Reviews her team's SQL; no examples of growing someone over a longer arc.
What was asked, what the interviewer took from your answer, and the part of the story that was missing.
Four years in analytics engineering, most recently owning the billing warehouse. Wants a role where the data work is closer to the product decision.
No red flags. This is the good outcome here.
10 turns, as transcribed during the interview.
Scored by an AI interviewer against a rubric written for this role from the job description you gave it. Scores are calibrated to the level of the role, not to an absolute scale. Treat it as practice and as guidance — a real panel is people.
HireMonkey · Senior Data Analyst · September 18, 2026
Your own report is private to your account. How we handle your data.