The First Interview is a Filter, Not a Test ♟️
[4 min read] 🌀 Let's dive deeper into how to nail the first interview - especially in today's brutal tech market
Alright, today let’s talk about how not to stumble on the very first step — that initial 30-minute screening call with an interviewer.
I’ve done quite a few screening rounds myself at startups I’ve worked at, and over the past few years, I’ve also talked with a bunch of tech recruiters about how they run interviews and, more importantly, why they end up rejecting candidates 🤷
And it’s almost never “they didn’t know enough about data structures” or “their Python skills weren’t strong enough.” It almost always came down to something much simpler. It was about clarity, professionalism, and whether the candidate was, in their words, a “safe bet” to pass along to the engineering team.
Here is how I understand this - most of us get nervous, treat the first interview like an exam, and end up getting a polite "we'll keep your resume on file" email a week later.
📝 HQ Tip: Think about it from the company's perspective: interviews are incredibly expensive for a company. Every hour a candidate spends with an engineer is an hour that engineer isn't building a product. Because of that, the first interview has one simple goal: to decide if you are worth the investment of a second, more expensive interview.
So the goal isn't to be perfect. It’s to give them an easy "yes."
Let’s dive into the signals you can send in your first interview which move you ahead in the process 👇
Signal #1: Show them you get it (with your 30-second story) 😇
When they hit you with "So, tell me about yourself," this is your moment. They want to know if you can connect your experience to their needs in a clear, compelling story.
It might sound like this: "Hi, I'm Alex. I just graduated with a CS degree. I know Python, Java, and JavaScript. I had an internship where I worked on a web app, and I’m looking for a software engineering role."
It's not bad, but it's forgettable because but it's what they hear all day. Now, imagine if you said this instead:
"Well, I'm Alex, and I just graduated and I focus on building full-stack applications. I really enjoy working on back-end systems to make them clean and fast. In my last internship, I actually got to rebuild a core API with Python, which ended up improving its speed by about 20%. I was really excited when I saw this role because it looks like I'd get to tackle similar performance challenges, but at a much bigger scale."
That's the stuff. You’re not making them do the work of connecting the dots. You’ve already done it for them. You’ve shown what you do, that you did it well (that 20% number is gold), and how it connects to their job.
✅ That’s a huge signal of competence!
Signal #2: Show them you actually care (the "why us?" check) 😏
Look, we both know you're probably applying to a bunch of places. But from their side, they are drowning in applicants who would take any job. Genuine interest is your secret weapon.
Before the call, just spend 10 minutes on their website or engineering blog. All you need is one little nugget.
"I saw you just launched that new dashboard feature. I was playing around with it and was really curious how your team handled the real-time updates."
"I read a blog post from your team about your migration to a new database. It sounded like a huge challenge, and I’d love to hear more about it."
✅ This little bit of effort sends a massive signal that you're intentional. It tells them they aren't just another line on your spreadsheet.
Signal #3: Show them you're a pro (the E.Q. check) 😌
Okay, this last one is the tie-breaker. It’s what separates the good candidates from the ones who get the offer. You have to show them you’re a professional who they can trust to work with their team.
The best way to do this is with the questions you ask at the end. Your questions show what you care about. So instead of the basics you can find online, try asking things like:
"What would a successful first six months look like for someone in this role?"
“What kind of a person would you consider perfect for this role?”
"What's your favorite part about working here?"
✅ These questions show you're thinking about your future impact, about what the team is looking for, and that you’re a real person trying to connect with another real person.
📝 HQ Tip: The reason I'm telling you all this is because it's a skill that goes way beyond this one job search. Knowing how to communicate your value is how you’ll get picked for interesting projects and how you’ll argue for a promotion later.
This is how you start building a career, not just looking for a job.
Additional Topics and How To Prep For Them 🗒️
1 - Your resume and about any online content you have (including github projects, or blogs you’ve written)
Think of your online presence as your 24/7 advocate, working for you before you even get in the room. Your GitHub tells a story about your coding habits. Your LinkedIn shows how you think about your industry. Before they ever speak to you, interviewers are looking you up—make sure what they find is telling the story you want.
📝 HQ Tip: One more thing—if you're interviewing at a startup, don't be surprised if behavioral questions pop up right away. My go-to resource for this is this fantastic post on dev.to that breaks down different storytelling frameworks, like the STAR method.
2 - Why you left/are leaving your previous role and what you are looking for in the new role
When an interviewer asks, "So, why are you interested in this role?" they're testing your motivation. It's easy to walk into one of two traps -
⚠️ The Logistics: This is when you mention things like compensation, a short commute, or remote work. Of course these things matter. But they aren't your motivation. Leading with them makes it sound like you want a paycheck, not a purpose. Keep them separate for the negotiation phase after you get an offer.
⚠️ The Rear-view Mirror: This is where you complain about a past job. Even if you're fleeing a genuinely toxic culture, never say, "I'm trying to escape my terrible boss." Instead, you must reframe what you're running from into what you're running towards.
Instead of: "My old job was chaotic and had no direction."
Try: "I'm looking for a team that has mentors who I can learn from and a defined vision which I can help make progress towards."
See the difference? One is a complaint; the other is an ambition.
Yeah, the market's tough. No doubt. But it's not a lottery after you get that first interview. Stop trying to "pass a test." and just show them you're a safe bet who is competent, interested, and professional.
Show you care 🌱,
Frame it forward 🚀,
and know how to communicate your story 🤝.
That's it for today! What's the trickiest question you've ever been asked in a first interview (and how did you handle it)? Let me know by replying to this email or in the comments – we can all learn from each other's experiences!
If you are finding this newsletter valuable, consider doing any of these:
1) Subscribe — Every week I write a short actionable post on something I have learnt in my career so far working at software companies in Silicon Valley. I cover things that I struggled with, which I have developed some mind maps for - how to navigate your tech job, network with people, and grow your net worth along the way. Read more about me and my journey which lead me to start writing Onboarded. Consider subscribing to get this content directly in your inbox:
2) Read with your friends — Help grow the onboarded team by sharing this post with a friend who may be in a similar boat. You can simply send them the email as well.
I wish you a great week!
Until next time,
Sonika
A tricky question I was asked:
How have your past experiences specifically prepared you to be the ideal candidate for this role?