8 Nov 2022, 10:02 UTC≈6,110 views13 reactionsread 8 August 2026 Photo
[ANNOUNCEMENT!] Tech Question Bank
Feeling underprepared for your upcoming interview 😩? Unsure on the type of live coding question you are going to be asked?
Introducing the brand new Question Bank! 🏛 The Question Bank is a growing repository of extensive interview questions from different roles, companies, and types. Prepare with ✨REAL✨interview questions posted by the community❤️.
Check out our video for a sneak…
❤9👍2🤩2
7 Nov 2022, 12:05 UTC≈4,730 views13 reactionsread 8 August 2026 [ANNOUNCEMENT!] Tech Offers Repo
Getting offers is hard, and choosing between them is even harder: "Am I being lowballed? Are my offers competitive enough?"🤔 Well, you don’t have to worry anymore! Introducing the Tech Offers Repo 🥳 Over the past few weeks, we have been working hard to create this platform for you. Here, you can view a range of latest salary information tech salary information! On top of that, you ca…
🔥8👍3❤1💩1
6 Nov 2022, 22:31 UTC≈4,350 views8 reactionsread 8 August 2026 Photo
[ANNOUNCEMENT!] Resume Review Portal
As you apply for your dream jobs or internships, have you ever felt unsure about your resume? Have you wondered about how others got past resume screening in a breeze? 😨
Wonder no more! Tech Interview Handbook is launching a new resume review portal where you can upload your resumes and get feedback from the tech community! 🔥
How do I start? 🤔
Watch our 1-minute walkthrough vid…
⚡5👍2❤1
2 Aug 2022, 00:45 UTC≈3,810 views14 reactionsread 8 August 2026 In case you weren’t aware, Tech Interview Handbook is using Docusaurus 2.0 to build its website. Both the handbook and Docusaurus 2.0 were built by the same person, me 🙂
Docusaurus is a project used by many open source projects to quickly build static websites, suitable for docs and blogs. I started contributing to Docusaurus in 2018 part-time and started Docusaurus 2.0 in the same year, and released a few alpha ver…
👍14
10 Jul 2022, 09:22 UTC≈3,190 views3 reactionsread 8 August 2026 We have a Discord channel now - https://discord.gg/usMqNaPczq
Feel free to ask any questions there 🙂
👍2❤1
28 May 2022, 04:15 UTC≈3,250 views3 reactionsread 8 August 2026 11. You might never feel ready for interviews and that's perfectly normal. Interviewing is a numbers game. Interview performance is a function of luck and preparation. The more you prepare, the "luckier" you get. You will fail some and you will pass some. You just need to pass one.
👍3
28 May 2022, 04:15 UTC≈3,110 viewsread 8 August 2026 10. LeetCoding is a marathon, not a sprint. If you start too early, you run out of steam. Start too late and there's not enough time for spaced repetition to take effect. Recommend starting a few months in advance and spending 1hr a day doing a few questions per day. You should be in top shape when it's time for interviews. If you've completed all recommended practice questions, do the weekly contests. If you can sol…
28 May 2022, 04:15 UTC≈2,910 views1 reactionsread 8 August 2026 9. You don't need to practice too many questions. 100-200 is sufficient for most. After a while, the questions are variations of previous questions and are based off the same patterns. The returns on practicing above 300 questions is marginal at best. The full list of 169 questions in Grind 75 (https://grind75.com) is 90% of what you need.
👍1
28 May 2022, 04:14 UTC≈2,500 viewsread 8 August 2026 8. The chosen language doesn't matter as much as your mastery of the language. You don't have to pick up Python just because it's the best language for interviews. But if you have enough time (more than two months), it might be worth doing so.
28 May 2022, 04:14 UTC≈2,360 viewsread 8 August 2026 7. Some topics are more important than the others. DFS, BFS, binary search, trees, graphs are the most important and common ones. If you're going for Google, practice DP. If you suck at DP like me, at least be good at backtracking with memoization.
28 May 2022, 04:14 UTC≈2,250 viewsread 8 August 2026 6. You might not get to run your code during interviews. Interviewers aren't just evaluating how correct your code is, the signals you exhibit during the process matters as well. You can end up failing even though you wrote correct code but it's messy and not readable. You can also end up passing even if your code had a minor mistake but your code is super clean and well-structured. Getting an Accepted doesn't mean y…
28 May 2022, 04:13 UTC≈2,080 viewsread 8 August 2026 5. If you find yourself stuck after half an hour on a question. Determine if you are close enough to cracking it. If you're close, try for a while longer. Otherwise read the solutions and move on. Learn the technique that was crucial to solving the question and internalize it. Revisit in a few day's time and try to solve it without referring to the answer this time. LeetCode also shows you similar questions for a pro…
Showing the 12 most recent of 20 posts we hold for @techinterviewhandbook. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.