45-60 minutes. Just you and me. This is where I find out if you're the real deal.
This isn't a trick-question interview designed to make you fail. I'm not trying to catch you out. I'm trying to understand how you think and whether you can do the job.
We'll talk for 45-60 minutes over Google Meet. I'll dig into your projects, ask you to solve a problem or two, and get a sense of how you communicate. If you actually built the things on your resume and can think through problems, you'll do fine.
Walk me through something you built. What decisions did you make? What broke? What did you learn? I'll ask follow-up questions to see how well you actually understand what you did.
One or two problems to solve together. Could be algorithmic, could be system design, could be debugging. I want to see your thought process, not just your answer. Think out loud.
You can ask me anything about the role, the company, or the process. Then I'll tell you what happens next.
Be ready to explain any project on your resume in detail. What did you build? Why did you make the technical choices you made? What was the hardest part?
When I give you a problem, I want to hear your thought process. Silence followed by an answer tells me nothing. Talk through your approach, even if you're not sure.
Saying "I don't know, but here's how I'd figure it out" is better than faking it. I've done 100+ interviews. I know when someone is bluffing.
If something I ask is unclear, ask me to clarify. That's not weakness. That's good communication. Better to ask than to answer the wrong question.
I'm not looking for perfection. I'm looking for signals that you can do the job and grow.
Do you understand the code you wrote? Can you explain why you made certain choices? Can you reason about tradeoffs? You don't need to know everything, but you need to understand what you've built.
How do you break down a problem? Do you ask clarifying questions? Do you consider edge cases? Do you test your thinking? The process matters as much as the answer.
Can you explain your thinking clearly? Do you listen to hints? Can you adjust when you're going down the wrong path? Working with you should feel like collaboration, not interrogation.
Do you know what you don't know? Can you admit when you're stuck? Do you take feedback well? I'd rather work with someone who says "I'm not sure" than someone who confidently bullshits.
I'll send your profile to the company with my personal recommendation. You'll move to Stage 4: Referred. I'll keep you updated on the company's response and help you prepare for their interview process.
I'll tell you exactly why. Not vague "we decided to move forward with other candidates" nonsense. Specific feedback on what you need to work on. That's more valuable than a polite rejection.