Menu
Main Menu
Preparing for a job interview is one of the highest-leverage things you can do in your career. Most people under-prepare. They skim the company website the night before, rehearse a couple of answers in their head, and hope for the best. Then they wonder why they didn’t get the offer.
At Gogotechy, we’ve coached hundreds of candidates into roles at Google, Amazon, Meta, TikTok and the most competitive startups in Europe. What separates the people who get hired from the ones who don’t almost always comes down to preparation — not talent.
This guide walks you through exactly how to prepare for a job interview, step by step. These aren’t generic tips. They’re the same 15 steps we use inside our 1:1 coaching programme.
Preparing for an interview means doing the work before the room — understanding the company deeply, knowing your own story cold, practising out loud, and building the kind of confidence that only comes from real preparation. It is not about memorising scripted answers. It is about showing up ready to have a genuine, informed conversation.
Most candidates glance at the job description once. That’s a mistake. Read it three times.
First read: understand the role. Second read: identify the skills and behaviours they’re actually asking for. Third read: map every bullet point to a specific story or example from your own experience.
The job description is a preview of every question you’re going to be asked. Treat it that way.
Surface-level research is easy to spot. Interviewers at top tech companies can tell within two minutes whether you’ve done your homework.
Go deeper:
The goal is to walk in with opinions, not just facts.
Every company has a public mission — and then there’s what they’re actually focused on this quarter. These are not always the same thing.
Ask yourself: what problem is this team trying to solve right now? What would make this hire a success six months in? Understanding the company’s current priorities lets you position your experience in a way that feels immediately relevant.
This sounds obvious. It isn’t.
A lot of candidates can describe what they did. Very few can articulate why it mattered, what they learned and how it connects to the next role. Before any interview, write down your three or four most relevant career moments. For each one, be ready to explain the context, your specific contribution and the outcome — with numbers where possible.
At Gogotechy, we call this your “story bank.” Build it before you need it.
You can’t predict every question, but you can prepare for the most likely ones. These come up in almost every interview at top tech companies:
Write your answers out. Then say them out loud. The difference is significant. Don´t forget to prepare General Cognitive Ability questions (logical) and be ready for tough cultural fit questions too. If in need of preparation, contact us.
STAR stands for Situation, Task, Action, Result. It is the standard framework for answering behavioural interview questions and it works.
Most people know what STAR is. Most people don’t use it well. The most common mistake is spending too long on the Situation and not enough on the Action. Interviewers want to hear what you specifically did — not what the team did, not what happened around you.
A good STAR answer takes about 90 seconds. Any shorter and it lacks depth. Any longer and you’ve lost them.
Before the interview, look up everyone you’re meeting. Understand their background, their tenure at the company, and — if they post publicly — what topics they care about.
This isn’t about flattery. It’s about context. Knowing that your interviewer came from a startup background, or spent five years in a specific function, helps you calibrate how you speak and what you emphasize.
The question “Do you have any questions for us?” is not a formality. It is part of the evaluation.
Weak questions: “What does a typical day look like?” Strong questions show you’ve thought about the role, the team and the challenges.
Try questions like:
Prepare five questions. You’ll likely only use two or three, but you want options.
Thinking through an answer and saying it out loud are completely different experiences. Most people only do the first one.
Practice with a friend, a coach, or even just record yourself on your phone. You will notice things — filler words, answers that go too long, moments where you lose confidence — that you’d never catch by just thinking.
At Gogotechy, mock interviews are a core part of our coaching. The candidates who do them consistently perform significantly better in real interviews.
You will be asked about your CV. Be ready to speak to every line on it — not just the impressive parts.
Pay particular attention to:
Have honest, confident explanations ready. Trying to avoid these topics in an interview is worse than addressing them directly.
This is not the glamorous part of interview prep. Do it anyway.
Arriving calm is part of the performance.
Top tech companies will ask about compensation expectations at some point in the process — sometimes earlier than you’d expect.
Do your research beforehand. Use Glassdoor, Levels.fyi (for tech roles) and LinkedIn Salary to understand the market range. Know your number and be ready to say it confidently.
Saying “I’m open” when you clearly have a number in mind doesn’t come across as flexible — it comes across as underprepared.
How you show up physically matters. Interviews are high-stakes conversations and your energy is part of the impression you make.
The night before: sleep matters more than a last-minute cram session. The morning of: eat something, move your body, give yourself time.
Preparation builds confidence. Confidence comes across in the room. These things are connected.
Most candidates let the interview end passively. The best candidates close it actively.
Before you leave (or end the call), restate your interest in the role clearly: “I’ve really enjoyed this conversation. The more I hear about [specific aspect], the more excited I am about this opportunity.”
Then ask directly: “Is there anything about my background that gives you pause, or anything you’d want me to clarify?”
This gives you a chance to address any lingering doubts on the spot — and it signals genuine confidence.
A brief, specific follow-up message after an interview is something most candidates skip. That’s exactly why you should do it.
Keep it short. Reference something specific from the conversation — not just “thank you for your time.” Connect it to your interest in the role.
It takes five minutes. It keeps you top of mind. And in a competitive process where multiple strong candidates are being evaluated, it can make a real difference.
There is no single answer, but as a general guide: for a first-round interview at a top tech company, plan for three to five hours of focused preparation for each round of interviews. For a final-stage or panel interview, a full day or two is more is reasonable — especially if it includes a presentation or case study.
The biggest mistake is treating preparation as something you do the night before. Start early.
Getting hired at a top tech company isn’t just about having the right experience. It’s about communicating that experience clearly, showing genuine knowledge of the company, and performing well under pressure. All of that is trainable.
At Gogotechy, we help people prepare for interviews at Google, Amazon, Meta, TikTok and the most exciting startups in Europe — not with generic advice, but with tailored 1:1 coaching built around your specific target role.
If you have an interview coming up and want to walk in genuinely prepared, drop us a message at info@gogotechy.com and we’ll take it from there.
Pilar Alfonso is the Founder of Gogotechy and former team member at Google and TikTok. She coaches tech professionals on career strategy, interview preparation and offer negotiation.
How can we help you?
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |