Cracking Interviews is an art!
Who Am I?
Hi! I’m Sarvesh, an SDE 2 at AWS, and over the last few years, I’ve conducted 150+ interviews for roles ranging from interns to senior engineers. Through this journey, I’ve realized something profound: Cracking interviews isn’t just about technical skills—it’s an art form. And like any art, it requires a mix of intuition, practice, and emotional intelligence that not everyone naturally possesses.
Let me explain why.
Why Interviews Are More Art Than Science
Sure, coding rounds test your knowledge of algorithms, and system design interviews gauge your architectural chops. But here’s the secret: Every interviewer is secretly evaluating you on traits that mirror real-world collaboration. Technical skills get your foot in the door, but these four “artistic” traits decide whether you’ll thrive in the role—or crash and burn.
The 4 Traits Interviewers Obsess Over (But Never Tell You)
1. “Are You Receptive to Feedback? (Hint: This is Non-Negotiable)”
Why it matters: In the workplace, feedback is oxygen. Can you adapt when a senior engineer critiques your approach? Or do you double down defensively?
What I look for: If I suggest a tweak to your code, do you say, “Oh, I didn’t consider that—let me adjust!” or ignore it? The best candidates treat feedback as a collaborative tool, not a personal attack.
Pro tip: Practice mock interviews where a mentor intentionally critiques your solution. Train yourself to respond with curiosity, not ego.
2. “Are You Thinking Out Loud? (Your Thoughts > Your Code)”
Why it matters: Silent coding is a red flag. At work, you’ll brainstorm with peers, debug with teammates, and explain your logic to stakeholders. Your interviewer wants to see that process in real time.
What I look for: Are you narrating your assumptions, trade-offs, and doubts? For example: “I’ll use a hashmap here because… but wait, what if collisions occur?” This shows you’re not just solving a problem—you’re communicating how you solve it.
Pro tip: Pretend the interviewer is a teammate who’s “pair-programming” with you. Talk through every decision, even the wrong ones.
3. “Are You Balancing Independence and Collaboration?”
Why it matters: Do you ask for hints too quickly? Or stubbornly grind for 30 minutes without progress? Neither extreme works. In real projects, you’re expected to seek help strategically but also showcase grit.
What I look for: If stuck, do you say, “I’m considering approach X, but I’m stuck on edge case Y. Can I get a nudge?” This signals self-awareness and teamwork. Bonus points if you later explain how that hint reshaped your thinking!
Pro tip: Frame questions as targeted asks, not please for rescue. Show you’ve tried 2-3 angles first.
4. “Do You Dry Run Your Code? (Accuracy > Speed)”
Why it matters: Sloppy code that “mostly works” is a liability. Great engineers test their logic before hitting “run”—just like you’d review a design doc before shipping.
What I look for: After writing code, do you walk through a test case line-by-line? For example: “If the input is [2,3], step 1 does X, step 2 updates Y…” This habit prevents bugs and proves you care about getting it right.
Pro tip: Always allocate 2-3 minutes to verbally dry run your solution. It’s the difference between “works” and “elegantly works.”
Why Can’t Everyone Master This Art?
Because these traits aren’t about memorizing LeetCode patterns. They’re about how you handle uncertainty, critique, and collaboration—soft skills that take years to refine. Some candidates panic under pressure; others over-index on speed. The “artists”?
- They stay calm when stuck.
- They turn feedback into momentum.
- They treat the interview as a conversation, not an interrogation.
Final Brushstrokes
Cracking interviews is less about being the “smartest” and more about painting a vivid picture of how you’ll add value to a team. Hone these four traits, and you’ll transform from a candidate who solves problems to one who solves them in a way people want to work with.
So, the next time you prep, ask yourself: Am I practicing code, or am I practicing the art of being a great teammate?
—Sarvesh
P.S. Struggling with interviews? DM me here or on LinkedIn at https://linkedin.com/in/dubesar—I’ll share my favourite “artistic” hack.
Too long? Here’s the TL;DR:
Interviews test collaboration, not just coding. Master 4 things:
- Love feedback.
- Think aloud like a storyteller.
- Ask for hints like a pro.
- Dry run like your job depends on it (it does).
Now go create your masterpiece. 🎨