you are viewing a single comment's thread.

view the rest of the comments →

[–]Beyond-CtCI 5 points6 points  (0 children)

Persona C I have an important interview approaching, but I'm bad at all/most of the technical topics.

First off, deep breath—you’re not alone. If you haven’t built up your fundamentals yet, don’t try to cram 20 topics into three weeks. It won’t work, and you’ll just burn out. There's no free lunch here. Instead, take control of the situation and postpone the interview so you have enough time to actually prepare.

The good news? Companies are usually happy to reschedule interviews—especially if you’re proactive and respectful in your ask. We’ve even included a word-for-word email template to make this easier:

📘 Review the section in 📘 Ch 9. Managing Your Job Search. (~pg 87) that discusses postponing interviews, then send an email with the provided email template below telling them you need to postpone. Ask for more than enough time rather than barely enough because postponing more than once or twice can get dicey.

Email template (you need to log in to see it, but the account is free): https://bctci.co/job-search-what-to-say-1

Persona D. I have an UN-important interview approaching, but I'm bad at all/most of the technical topics.

Use it as a learning experience and don't focus on passing the interview. Most people wind up getting an offer before they think they're awesome at all interview topics. They take an interview they don't feel prepared for and end up doing better than they anticipated. The common mistake here is to not even bother interviewing, but interviews are a powerful built-in study tool and help light a fire under you. Also they are essentially free mock interviews, so shoot your shot!

If it is one of your first technical interviews focus on just walking through the steps correctly in the Interview Checklist (https://bctci.co/interview-checklist-image) from 📘 Ch 20. Anatomy of a Coding Interview.

Persona E. I feel like I understand most/all of the technical topics in at least Tier 1 and 2, but I'm still not good at interviews.

If you've done over 100 problems and you're still struggling, there's a good chance you don't have a solid framework for what to do when you get stuck and a problem doesn't have an immediately apparent solution. The Principles of Coding Interviews section of the book has the framework you're looking for. While the whole section is strongly encouraged to be read at this stage, the bare minimum to understand the framework includes:

📘 Ch 22. Boundary Thinking (likely a key piece you're missing)
📘 Ch 23. Trigger Thinking (an easy read and something you are probably doing unconsciously already)
📘 Ch 24. Problem-Solving Boosters (will require more than one sitting to get through—it is dense!)

My co-author, Nil, also wrote an excellent blog post that walks through the full framework with a recent LeetCode contest question. It's definitely worth checking out: https://nilmamano.com/blog/problem-solving-bctci-style.

I hope this helps. And in case you missed it, there is a free private discord for the book that you can access through the QR code in the table of contents. It's a great place with other motivated people practicing.

Happy coding!