Interview preparation you can practise out loud
Send me the job description. I help you pick your best stories, ask you the likely questions and let you rehearse until the answers sound like you.
What usually gets in the way
“I go blank when it matters”
You know your work, then the interviewer asks about a time you failed and nothing comes out.
“I don’t know what they’ll ask”
Every interview loop is different, and generic question lists don’t match the role in front of you.
“They asked my expected CTC”
The salary question comes up in the first call and you either lowball yourself or dodge it badly.
How we work through it together
- 01
Read the role
Send me the JD and your resume as a PDF or Word (.docx) file. I list what they’re testing for and the questions most likely to come up.
- 02
Build your stories
We pick five or six stories from your work and shape them with situation, task, action and result, so one story can answer several questions.
- 03
Rehearse out loud
I run a mock interview by voice in the web app, ask follow-ups, and tell you where an answer ran long or missed the point.
What you leave with
Answers that sound like you, ready before the call.
- A list of likely questions for this role and level
- Five or six stories in STAR shape, mapped to those questions
- Feedback on your answers after a mock round
- A line for the salary question that doesn’t box you in
- Three questions to ask the interviewer
You: Final round for a data engineer role on Thursday. Can we practise?
Zia: Yes. The JD leans on pipeline reliability. Tell me about a time a pipeline broke in production.
You: We had a job fail every month-end, so I added retries and alerting and it stopped.
Zia: Good bones. Say what the failure cost the business and how you found the root cause. That’s the part they’ll probe. Try it again?
How to prepare for a job interview
A plan that works for most roles.
Start from the job description
Underline the skills and outcomes the JD repeats. Those are what the interviewers are scoring. Match each one to something you’ve actually done.
Prepare stories, not answers
Five or six well-told stories cover most behavioural questions. Use situation, task, action and result, keep each to about two minutes, and end with a number or a clear outcome where you can.
Practise out loud
An answer that reads well can still sound rambling when spoken. Say it aloud, time it, and cut. Practising with someone who asks follow-ups is better than reading notes.
Research the company properly
Read their recent news, the product, and the team you’d join. Prepare questions that show you’ve thought about the work, such as how success is measured in the first six months.
Have a line ready for the salary question
If asked early, give a researched range for the role, or say you’d like to understand the scope first. Avoid a number you’d regret, and don’t let it be the first thing you improvise.
What people ask
How do I prepare for an interview in one day?
Read the JD closely, pick four or five stories that match it, practise them out loud twice, research the company for half an hour, and prepare two questions to ask. Sleep matters more than one more hour of cramming.
What is the STAR method?
A way to structure an answer: the Situation, your Task, the Action you took, and the Result. It keeps answers focused and makes your contribution clear.
How do I answer “Tell me about yourself”?
Give a short version of where you are now, the one or two things you’ve done that matter for this role, and why you want this job. Aim for about a minute.
What should I say when asked for my expected salary?
Give a researched range for the role and city, or ask to discuss it once you understand the scope. Base it on the market, not on your current pay.
Can Zia do a mock interview with me?
Yes. In the web app you can talk to me by voice, and I’ll ask questions for your role, follow up, and give you feedback on your answers.
Rehearse before the real one.
Send me the job description. I’ll ask the questions they’re likely to ask, out loud.