The Team Matching Round: The Interview Where You Should Be Doing the Interviewing

What I learned about team matching across loops at Canva, Mercari and Google, including the mechanics that quietly decide whether you even get an offer, and the questions that tell you what a team is really like.

(Non-Medium members can READ the full article for FREE: here)

When I was interviewing at Canva, I had already cleared every technical round, the system design, the code review, and the behavioural conversations with the engineering manager. I assumed the hard part was over. Then the recruiter mentioned one more conversation, a team matching round with a hiring manager and an engineering director. I almost relaxed and treated it as a victory lap, which would have been a mistake, because this round really decides what your day-to-day life will look like once you join, and at some companies, whether you get an offer at all.

I have now been through this stage at several companies, in slightly different shapes each time, and my view of it has completely changed. So let me walk through what team matching is, the mechanics that catch people out, how to make a manager want you, and the questions that tell you whether a team is somewhere you want to be.

What team matching actually is, and why it is higher stakes than it looks

Larger companies often split two decisions that smaller ones bundle together. The first is whether to hire you at all, the technical and behavioural bar you have already cleared. The second is which team you land on, and that is what team matching decides: a team with open headcount talks to you, you talk to them, and both sides have to opt in.

The part nobody tells you is where this round sits in the pipeline. At some companies the match happens after you have cleared the bar but before any formal offer, so the offer itself is contingent on a team saying yes. At Google the loop comes first, and only once your feedback is in do you start looking for a team. Either way there is a failure mode that has nothing to do with how good you are: you can clear the bar and still sit in limbo for weeks or months, waiting for a team with headcount at your level to pick you up. Candidacies can expire, and in rare cases an offer that felt certain never comes through.

I learned this the hard way at Google. I cleared the phone screen for an L4 role in Warsaw, did the onsite, and then went into team matching, but my feedback was mixed rather than a clear hire, which made landing a team much harder. One team was not the right fit, another conversation never got scheduled, and once the layoffs and re-prioritisation hit, the process quietly stalled until I stepped away. So when you reach this stage, ask your recruiter the unglamorous questions: how long is my candidacy valid, how many matching attempts do I get, and how many teams are you putting me in front of. That window can be more limited than you expect, so knowing the clock changes how aggressively you should move.

Be honest about which situation you are in

How team matching feels depends a lot on how your interviews went. If your scores were strong and your resume makes your strengths obvious, managers will be keen and some will bend a role around you, so you can afford to be a bit selective. If you had a mixed day, or your background does not explain itself, you are still proving yourself, and your job is to remove the doubt by being specific about what you have done and how it maps to the team's needs.

Do a little homework before the call

Nothing puts a hiring manager off faster than a candidate who clearly has no idea what the team does, because it signals you either are not interested or could not be bothered to look. A little digging goes a long way: look the manager up on LinkedIn, skim what their team owns and what they have shipped recently, and if your recruiter sent a one-pager, read it properly.

What you are after is a hook or two that let you ask a sharper question instead of a generic one. Even a rough sense of what they own lets you walk in sounding interested rather than waiting to be sold to, and it does not matter if your picture is a little off, because the effort itself is what shows.

Give the manager a reason to pick you

In the earlier rounds you were graded against a rubric. Team matching is different, because the manager has real freedom to decide you are a good fit, and may have spoken to five or ten people before you. So the work here is to be the one they remember and want on the team.

The thing that worked for me was not pretending to be something I was not. When I spoke to the Trust and Safety team at Canva, I was honest that I had not worked in the domain before but was genuinely keen to move into it. What I had done was the homework. I was at Agoda then, so I read up on how account protection, fraud and platform abuse work, and in that first conversation I told them what I thought their team owned, just from the team name and the role description. My guess was not perfect, but they could see the interest was real and that I had bothered to dig in, and that landed far better than any rehearsed answer about my strengths.

A few more things that helped:

• Do not recite your resume. The manager has already read it, and walking through your career chronologically just burns time. Lead with two or three major accomplishments and tie each one to the future role.
• Be clear about the tech, without being rigid. It is fine to care about the stack or to want a particular kind of work, and you should say so. Just be aware that some managers get wary of anyone who seems unwilling to touch anything outside their favourite tool, so signal that you can adapt where it makes sense.
• Talk business, not just technology. Every engineer talks about systems. The ones managers remember also ask how the team moves the wider organisation, where revenue or cost shows up, and what a good half looks like. Caring about outcomes, not just architecture, is what reads as senior.
• Show some excitement. It is easy to go flat under the pressure of a call and sound indifferent, especially over video. If you notice that in yourself, push the other way, because a simple, honest "this genuinely excites me" lands better than you expect.

Now turn it around and interview them

This is the half that is easy to let slip by. You are not only trying to get an offer, but you are also trying to work out whether this is somewhere you want to spend the next chunk of your career, and the only way to find that out is to ask real questions while you still have the upper hand.

When I went through this for Canva, I prepared a list designed to get at the reality of the job rather than the marketing version. The questions I would not skip:

• Scope. Can you give me an overview of the primary responsibilities and functions of the team, and is it a platform team or a product team?
• Structure. How is the team structured, and where are the members located?
• Success. What KPIs does the team track to measure itself?
• Domain expertise. Do you expect any specific domain expertise for this role?
• Tech stack. Is there any specific tech stack experience required?
• Current challenges. What are some of the challenges or problems the team is working on right now?
• Future. Are there any upcoming projects or initiatives the team is excited about?
• On-call. How heavy are the on-call and support duties?
• Collaboration. How do other teams collaborate with you, and the other way round?
• Onboarding. What do the first 90 days look like?

One thing I got wrong early was the order. Do not open with the comfort questions, the on-call load, the remote-work policy, or the perks, because leading with those makes you look like you are shopping for an easy life before showing any interest in the work. On-call matters enormously, since no salary fixes a pager that goes off every other night, but ask it once you have shown you care about the problems, or better still, ask the team rather than the manager.

Whatever you ask, listen for the texture and not just the words. A neat, problem-free answer to "what are your biggest challenges" is itself a small warning sign, because every real team is wrestling with something. The same goes for evasive answers when you push on anything uncomfortable, a team that has reorganised three times in a year, or a string of recent departures, all of which you want to understand before you sign rather than after.

Remember, it is your decision too

If something gives you pause during the conversation, the best move is to name it, framed like someone who wants to make it work. I have said things like "I really like the goals and think I can help with X, my one hesitation is mentorship, what does that look like week to week?" That lets the manager answer it directly, and gives you a straight answer to weigh up rather than a worry you carry home.

Because in the end, this is your call as much as theirs. When the offer comes, the compensation is only part of the picture, and the rest is what you gathered in these conversations: the mission, the people, and whether on-call will eat your weekends. Open roles are limited, so when a strong team you like wants you, saying yes usually beats holding out for a hypothetical better one. But joining the wrong team can mean a year or more of quiet unhappiness, so do not be afraid to say a clear no when the fit is not there.

If the matches are not landing

If you do get stuck, do not panic or try to reinvent yourself into whatever you think they want, because that rarely reads as genuine. Lean on your recruiter, ask what feedback is coming back, sharpen how you introduce yourself and what you are looking for, and if nothing moves, ask them to introduce you to a different set of teams. Often, the problem is not you at all, just how you were pitched.

The team matching rounds I have been through

If you want the full stories, here are the three loops this came from, each a different shape:

Canva, my most recent one. The match was a single conversation with the hiring manager and an engineering director, and I joined the team I wanted.

Canva Australia Backend Engineer Interview Experience Towards the end of 2023, after what felt like an endless marathon of job applications and "we'll be in touch" emails, I…

Mercari in Japan. A straight choice between two teams, the Identity Platform team and Web Growth, and I picked Web Growth.

Mercari Japan — Software Engineer (MG3) Interview Experience From a LinkedIn DM to an offer: My full Mercari SWE interview experience and the lessons I learned.

Google in Warsaw. Mixed feedback and the layoffs that followed meant the process stalled, and I never landed a team.

Google Warsaw — L4 Software Engineer Onsite Interview Experience I finally went through my Google onsite rounds, and the overall experience was excellent. In this article, I will share…

Final thoughts

When I look back at my move to Canva, the thing I am most glad about is not that I negotiated the offer, but that I used the team matching round to ask the uncomfortable questions. It meant I started the job knowing what I was walking into, the mission, the on-call reality, and the first 90 days, instead of finding all of that out after I had signed.

The flip side taught me just as much. When the Google process quietly fell apart, it could have felt like a failure, but the same habit of asking and listening is what told me early that waiting around for an uncertain role was not worth it, and I walked away without much regret. Team matching is the one part of the whole loop where the power is balanced, where you get to be as selective as they are. So do the homework, give a good team a reason to want you, and then turn it around and find out what you are actually signing up for.

The interviews get you in the door, but this round decides what is behind it, so treat it as the two-way conversation it really is.

Thanks for reading! If this story resonated with you, I'd appreciate a few claps 👏. It really helps more people discover this post.

If my work provided some value today, you can support me here 🤝.

To view my full portfolio or connect with me on other platforms, visit:

Freeze Francis Official: Instagram, X | Linktree Senior Software Engineer @ Canva | Australia

For anyone interested, check out all my interview experiences here:

Cracking the Tech Interview: My Personal Experiences at 10+ Companies (Google, Amazon & More) A complete index of my detailed software engineer interview experiences