---
title: "Comment by Linkjob AI on \"8 Tips to Consider when Preparing for FAANG & Other Competitive Interviews\" | Hashnode"
description: "The autopilot point is the one I wish someone had told me earlier. A trick that helped me: before writing any code on a \"familiar\" problem, say out loud the one"
url: "https://hashnode.com/posts/8-tips-to-consider-when-preparing-for-faang-other-competitive-interviews/66254d5c4be1d9b3c1ad152a/comment/6ae59b780d178d1173e13f1b"
---

[Discussion](https://hashnode.com/posts/8-tips-to-consider-when-preparing-for-faang-other-competitive-interviews/66254d5c4be1d9b3c1ad152a)

Comment [8 Tips to Consider when Preparing for FAANG & Other Competitive Interviews](https://hashnode.com/posts/8-tips-to-consider-when-preparing-for-faang-other-competitive-interviews/66254d5c4be1d9b3c1ad152a)

[Linkjob AI](https://hashnode.com/@linkjob)

[Oct 31](https://hashnode.com/posts/8-tips-to-consider-when-preparing-for-faang-other-competitive-interviews/66254d5c4be1d9b3c1ad152a/comment/6ae59b780d178d1173e13f1b)

The autopilot point is the one I wish someone had told me earlier. A trick that helped me: before writing any code on a "familiar" problem, say out loud the one constraint that makes this version different (sorted input, duplicates allowed, streaming data, etc.). If you can't name one, ask the interviewer — that single question catches most of the subtle twists.

I'd add one thing to the time-allocation section: decide in advance what you'll do at the 50% mark if you don't have a working approach yet (usually: commit to the brute force, code it cleanly, and optimise afterwards). Having that rule removes the panic of deciding under pressure.

For the mental-coding phase, I also rehearse explaining my approach in a quick mock round; disclosure, I work on [AI tool for job interviews](https://www.linkjob.ai/) which we use for that kind of practice. Great list, thanks for writing it up.
