SDE-1 @Amazon

Having strong problem-solving skills is non-negotiable, but a tech interview requires much more than just writing code.Your confidence and communication skills are the real key.How you structure your approach, explain your thoughts out loud, and handle situations when you're stuck matters just as much as getting the final optimal solution.
Here are 5 core rules that helped me clear my rounds:
📌 Rule 1: Understand the question completely
Never jump straight into coding. Ask clarifying questions and confirm the constraints upfront so you can design your approach accordingly.
📌 Rule 2: Be honest about what you don't know
If you get a topic or specific algorithm you haven't covered, tell the interviewer straightforwardly instead of guessing or wasting time. In one of my rounds, I was asked about string-matching algorithms like Rabin-Karp, which I hadn't studied. I admitted it directly, and the interviewer gladly adjusted the requirement. Admitting limits shows confidence, self-awareness, and respect for the time given.
📌 Rule 3: Avoid silence at all costs
Dead air creates awkwardness and makes you look unprepared. Think out loud! Say things like: "This setup reminds me of a two-pointer pattern; let me double-check if that applies here..." Interviewers want to collaborate, but they can only guide you if they know what's happening in your head.
📌 Rule 4: Don't hesitate to ask for a hint
If you hit a wall, ask for guidance professionally:
👉 "This is a variation I haven't seen before. Could you offer a quick hint to help me get started?"
👉 "It's been a while since I reviewed this specific concept, but with a small pointer, I can build from there."
📌 Rule 5: Get alignment before coding
Verbally walk through your logic, edge cases, and expected time/space complexity first. Only start typing your code once the interviewer confirms they are satisfied with your proposed approach.
💡 Takeaway: Great problem-solving gets you into the room, but strong communication and confidence seal the deal.