CODING_INTERVIEW_README.md π
1. CLARIFY
Many people jump straight into solving the problem. Take time to ask clarifying questions β some people intentionally underspecify as a way to catch you out.
The BIG reason you want to clarify: demonstrating clear communication skills. Every employer wants this πββοΈ
Many people jump straight into solving the problem. Take time to ask clarifying questions β some people intentionally underspecify as a way to catch you out.
The BIG reason you want to clarify: demonstrating clear communication skills. Every employer wants this πββοΈ
2. EXAMPLES
To confirm understanding, come up with examples. Write some sample inputs, and then the expected outputs.
This doubles as TDD β as you write your solution, you should constantly rerun it against what you've agreed upon.
To look for edge cases, think like a QA πββοΈ
To confirm understanding, come up with examples. Write some sample inputs, and then the expected outputs.
This doubles as TDD β as you write your solution, you should constantly rerun it against what you've agreed upon.
To look for edge cases, think like a QA πββοΈ
3. APPROACH
Engineering is the art of breaking big problems down into smaller problems. Separate your problem into stages and explain this thought process **out loud**.
Even if you don't end with a working solution, you can get credit for the right approach πββοΈ
Engineering is the art of breaking big problems down into smaller problems. Separate your problem into stages and explain this thought process **out loud**.
Even if you don't end with a working solution, you can get credit for the right approach πββοΈ
4. TAKE THE HINT
Believe it or not, interviewers want you to succeed! Everyone wants find a good hire ASAP.
When they give you a hint, they're trying to help. Ignoring hints is a big red flag β they want to guide you back on track.
Take the hint πββοΈ
Believe it or not, interviewers want you to succeed! Everyone wants find a good hire ASAP.
When they give you a hint, they're trying to help. Ignoring hints is a big red flag β they want to guide you back on track.
Take the hint πββοΈ
5. PSEUDOCODE
Write out steps before implementing details.
Most people pseudocode like South Park's Underpants Gnomes:
1: Collect Underpants
2: ???
3: Profit
Go deeper - plan out the argument and return profile of major functions, how you will store and mutate state πββοΈ
Write out steps before implementing details.
Most people pseudocode like South Park's Underpants Gnomes:
1: Collect Underpants
2: ???
3: Profit
Go deeper - plan out the argument and return profile of major functions, how you will store and mutate state πββοΈ
6. DATA STRUCTURES
Pick the wrong data structure, and spend the rest of the interview compensating for it in your algorithm with spaghetti code.
Pick the right data structure, and you simplify the problem to its essential complexity.
Data Structures > Algorithms πββοΈ
Pick the wrong data structure, and spend the rest of the interview compensating for it in your algorithm with spaghetti code.
Pick the right data structure, and you simplify the problem to its essential complexity.
Data Structures > Algorithms πββοΈ
7. LAMPSHADING
Make it work, make it right, then make it fast β in that order.
Most interviews are ~45mins long - let go of your inner perfectionist.
People understand that this is a stressful setting - lampshade weaknesses and carry on πββοΈ
swyx.io/lampshading/
Make it work, make it right, then make it fast β in that order.
Most interviews are ~45mins long - let go of your inner perfectionist.
People understand that this is a stressful setting - lampshade weaknesses and carry on πββοΈ
swyx.io/lampshading/
8. TALK WHILE YOU CODE
Not for everyone, but it's impressive when done right. It's not as hard as it looks:
Lvl 1: *what* you are currently doing
Lvl 2: *why* you are doing it
Lvl 3: what you *will* do next
Lvl 4: what you're *not* doing
You can do this during pauses πββοΈ
Not for everyone, but it's impressive when done right. It's not as hard as it looks:
Lvl 1: *what* you are currently doing
Lvl 2: *why* you are doing it
Lvl 3: what you *will* do next
Lvl 4: what you're *not* doing
You can do this during pauses πββοΈ
9. MOCK INTERVIEWS
Nothing like practice, practice, practice.
@Coding_Career Community members can book a mock interview anytime, but pro tip: there are dedicated sites for this:
- @prampco
- @byteboardDev
- @interviewingio
- @clemmihai's channel
πββοΈ
Nothing like practice, practice, practice.
@Coding_Career Community members can book a mock interview anytime, but pro tip: there are dedicated sites for this:
- @prampco
- @byteboardDev
- @interviewingio
- @clemmihai's channel
πββοΈ
Technical Interview Resources
The reason we don't cover interviews in our book β bc it's already covered!
- @gayle's Cracking the Coding Interview
- @EmmaBostian's technicalinterviews.dev
- @danieldelcore's github.com/danieldelcore/β¦
- @startupnextdoor's github.com/jwasham/codingβ¦
πββοΈ
The reason we don't cover interviews in our book β bc it's already covered!
- @gayle's Cracking the Coding Interview
- @EmmaBostian's technicalinterviews.dev
- @danieldelcore's github.com/danieldelcore/β¦
- @startupnextdoor's github.com/jwasham/codingβ¦
πββοΈ
Once you've read this thread, cracked the interview, and got the offer:
**Now what?**
That's what The Coding Career Handbook aims to solve: the VAST gap in knowledge between Junior to Senior.
learninpublic.org
π #shamelessplug
**Now what?**
That's what The Coding Career Handbook aims to solve: the VAST gap in knowledge between Junior to Senior.
learninpublic.org
π #shamelessplug
P.S. If you "bomb" your interview, don't worry...
We've all done it!
We've all done it!
https://twitter.com/engineering_bae/status/1395447011902636033?s=20
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
