How I prepare for the final-round interview

In early 2024 I was job hunting in Canada and reached the final round at a company. It was a hiring-manager interview: 25 minutes, and nobody tells you what will be asked. The technical rounds were already done. This one checks three things: whether you understand the role, whether you’ll fit the team, and whether your past holds evidence for both.

My method was unglamorous. I listed every question I might be asked, wrote an answer for each, and read them aloud until I could do it without the page. English isn’t my first language; understanding the question and answering fluently are two separate hurdles, and writing everything down was the only way to clear both at once. Below is the list I used, with company-specific details removed and replaced by the general version.

Three things to do before the interview

Copy the job description and map every line to your own experience. For each responsibility and requirement, find a project or a number on your resume that matches. When the interviewer asks “what do you know about this role”, that mapping is the answer.
Research the company. Founding year, core business, recent news, the public values page. Not to recite it, but so that “why do you want to join us” contains at least one sentence that is only true of this company.
Prepare five or six stories. Behavioural questions look numerous, but they keep testing the same handful of experiences. Write each one in STAR form (situation, task, action, result) and end with a line about what you learned.

The frequent questions and how I answered them

1. What do you know about this position?

Restate the core responsibilities from the job description, then say which of your experiences match. Don’t stop at restating; follow each line immediately with “I did this on such-and-such project”.

2. Why do you want to join our company?

I use three layers: industry, role, personal.

Industry: why this industry has a future, backed by one or two trends.
Role: how this role connects to my career plan, and why my past experience means I’ll be productive quickly.
Personal: which specific policy or cultural trait of the company fits my situation right now. If a remote-work policy matters to you, say so plainly.

Each layer needs one concrete sentence that applies only to this company. Otherwise it sounds like a template.

3. Walk me through your work history

Chronological, three sentences per job: what the company does, what I owned, what I delivered. Keep it under two minutes.

Mine went roughly like this: graduated in 2014 and joined an e-commerce platform during China’s internet boom, owning the Android home page, product detail, cart, order and payment modules. Moved to a shared-mobility company in 2019, responsible for the app home page, ride-hailing and car-sharing, plus mobile infrastructure: Gradle plugins, APM, an H5 container, performance and stability. In 2023 joined a former colleague’s startup, built a voice and video social platform from zero with React Native, got the chance to work remotely, and moved to Canada.

4. What is your career plan?

My answer: more than ten years of software development gave me a deep understanding of computer science and confirmed that I genuinely enjoy writing code. I’ve built up experience across Android, iOS, React Native, backend and machine learning, and I treat every technology as a tool for solving problems. I’m open to new technology, but my focus is on doing this role well.

The trap here is looking too far ahead. The interviewer wants to know whether you’ll stay in this role.

5. Tell me about a project you’re proud of

I talked about the zero-to-one project at the startup:

Small team, little technical debt, so I pushed for React Native: one codebase for Android and iOS, which noticeably shortened the schedule.
Led the setup of an APM system, giving us live performance and stability data so problems surfaced early.
Introduced a CI/CD pipeline that automated builds, tests and releases and gave developers their time back.
Fixed legacy problems such as unreliable push notifications and memory leaks, which lifted retention.
The project launched on time and quickly gained users and orders.

Every bullet needs a “what I did” and a “what the result was”. Not just “what we did”.

6. Tell me about a mistake you made at work

My story: at the e-commerce company, one evening the app suddenly started crashing. Not many users were affected, but it was worth fixing fast. I fixed it at home, didn’t have enough test devices to verify, and shipped it through hotfix on the assumption it would be fine. The next day the crash rate was worse, and I had to fix it again in a hurry.

What I learned: engineers follow the process, treat every release as serious, and keep a healthy respect for the people using the product.

Don’t pick a trivial mistake, and don’t pick a catastrophe. Pick one that’s real, whose consequences were contained, and where you actually changed how you work.

7. In this role, what success indicators would you keep in mind?

I listed seven and expanded on three or four in the interview:

Code quality and maintainability: code review, automated test coverage, long-term maintenance cost.
On-time delivery: finishing within the timeframe, meeting the requirements and the quality bar.
Collaboration and communication: software is a team sport; how you communicate and resolve disagreement decides project outcomes.
User satisfaction: feedback, usage frequency, retention.
Technical leadership and innovation: learning new technology and applying it; proposing ways to raise efficiency or cut cost.
Performance and stability: response times, failure rates, availability.
Continuous learning: certifications, conferences, technical writing.

8. Tell me something that isn’t on your resume

I said: over the past few months, alongside the job search, I’ve built several AI-related web apps and mobile apps. I’d read about a project where users submit a deceased relative’s name, relationship and stories, and the site simulates that relative in conversation. After trying a few similar projects I thought adding a voice would make it better, so I built a demo with the ElevenLabs and OpenAI APIs. It worked well and I kept refining it.

This question is your chance to show the person behind the resume. Something you’re building right now works best.

9. Give an example of a time you had to resolve a conflict

Mine, in STAR form:

Situation: at the shared-mobility company I led Project A, upgrading the Gradle version across all our libraries. I was both the lead and a core developer, coordinating other colleagues. I was also a member of Project B. At first the two didn’t compete for resources.
Challenge: schedules and staffing changed and both projects started pulling the same people. Left alone, both would slip.
Action: I compared the two and decided to finish A first, since I owned it, which guaranteed at least one on-time delivery. Then I brought the conflict and my proposal to B’s lead and our manager. We agreed to pause B, secure A, and then move extra people onto B.
Result: both projects finished on time.
Lesson: resource conflicts are routine in project work. Prioritising, communicating early and solving it together beats grinding through alone.

10. How do you handle your workload?

Tools: a calendar for the schedule, a Gantt chart for project progress, weekly or daily reports for the workload itself.
A to-do app for daily priorities, sorted into four buckets: urgent and important, urgent but not important, important but not urgent, neither.
A short daily stand-up to sync progress and allocation.
When the load is heavy, stay calm, take regular breaks, and check with my manager that expectations are realistic. Ask for resources when they’re needed.

11. What are your greatest strength and weakness?

Strength: deep Android development and project experience; I can deliver a project independently. Weakness: my English still isn’t where I want it, and I’m new to the North American workplace, so I’ll need a little time to adapt.

The weakness has to be real and has to be something you’re actively working on. Interviewers can tell.

12. How did you realise you needed a new job?

I prepared three categories and picked whichever fit:

The role: the work became repetitive, with no challenge or room to grow.
The company or industry: the industry was hit by a pandemic, policy or new technology and the market contracted.
Personal: for example, emigrating to another country and needing a new working environment.

A few lessons

Write it, then read it aloud. Not to memorise, but to shrink the gap between thinking and speaking to zero. The first read-through exposes sentences that don’t flow; fix them until they do.
Every story should answer three different questions. The conflict story above also answers “tell me about a time you took ownership” and “tell me about a time you disagreed with a coworker but still delivered”. You don’t need many stories. You need to know them cold.
Numbers. “Retention went up” is weaker than “retention rose by X%”. Give the number when you have it; give the scale when you don’t.
Prepare two or three questions of your own. The final round almost always ends with “do you have any questions”. Ask about the team’s technical challenges, what success looks like in the first three months, or why the interviewer has stayed. All better than asking about benefits.

I’ve reused this list several times since, changing a little each time. If you’re preparing for this round, I hope it saves you some hours. 中文版.