Interview guides

Connect your current work or studies, one relevant achievement and your reason for pursuing this role. Focus on the experience that helps the interviewer understand your fit rather than reciting every line of your CV.

Describe the shared goal and the source of disagreement without blaming anyone. Explain how you listened, checked assumptions and agreed on a next step. Finish with the outcome and what you would repeat or change.

Link specific responsibilities in the job description to work you enjoy and skills you can demonstrate. Refer to something you have learned about the employer, then explain what you hope to contribute and develop.

Start with the metric definition, reporting period and source of truth. Explain checks for missing records, duplicates, joins, aggregation and refresh timing. Reconcile totals and review unusual movements with the business owner before publishing.

Check the intended grain of each table and whether the join keys are unique. Compare row counts before and after the join and test for many-to-many matches. Explain why you would fix the grain rather than hide the issue with DISTINCT.

Explain who used it, the decision they needed to make and the measures you selected. Discuss how you checked accuracy and usability. Describe the resulting action; use measured impact only when you can substantiate it.

Begin with the user need, expected workload and constraints. Draw the main components and explain the flow of data. Discuss one trade-off, a failure mode, how you tested the system and what you would improve next.

Clarify the affected endpoints and compare typical and tail latency. Use logs, metrics or traces to separate application, database and network time. Form a hypothesis, measure it, make a targeted change and check the result.

Describe how you detected the issue, limited its impact and communicated with the team. Explain the evidence behind the root cause and the fix. Close with the tests, monitoring or process changes that helped prevent a repeat.

Confirm the comparison period and definition first. Break the movement into plausible drivers such as volume, price, timing or classification. Reconcile to source records, document assumptions and explain the supported cause rather than guessing.

Explain how you identify high-risk steps, set review criteria and automate repeatable checks. Describe when you would escalate an unresolved discrepancy instead of submitting an unverified figure to meet a deadline.

Outline the original bottleneck and how you measured it. Explain the change, who needed to agree and how you tested it. Discuss the outcome and any new controls needed to keep the process reliable.

Explain how you research the account and ask about goals, processes, constraints and decision-making. Reflect the problem back before proposing a solution. Describe how you confirm what a successful outcome would mean.

Clarify whether the concern is budget, value, timing or comparison with another option. Connect the discussion to the customer's priorities and explain available trade-offs. Avoid promising a discount or capability you cannot deliver.

Describe the expectation gap and how you took ownership. Explain how you listened, agreed on a realistic plan and kept the customer informed. Share the outcome honestly, including any limit to what you could resolve.

Choose a relevant project, internship, volunteering experience or responsibility from your studies. Explain the goal, your contribution, how you checked the result and what you learned. Distinguish practice work from commercial experience.

Explain what attracted you to the new field and how you tested that interest through learning or practical work. Connect transferable skills to the role and acknowledge the areas you are still developing.

Describe how you break the problem down, find reliable material and practise on a small example. Explain when you ask for help, how you check your understanding and how you apply feedback.