If I were creating a technical interview for a full-stack engineer, I would:
1. Give the candidate a mock codebase, let them explore it
2. Present them with a customer problem, discuss it with a product manager, gather requirements for a solution
(1/7)
3. Have a designer present a proposed UI, then discuss any modifications that need to be made
4. Pair program with an engineer to implement the solution
5. Demo the project and discuss how it went
(2/7)
This format is 3 interviews in one (PM, designer, engineer). Better yet, it's a working session with each of those people. The onsite interview could essentially be an hour chat with the hiring manager and then the 3 hour session outlined above.
(3/7)
Unlike most technical interviews, this is representative of the work I do in a day as a full-stack engineer. My job is about 50% working with other people, 50% coding. And the coding that I do is highly influenced by those other people I work with.
(4/7)
The type of coding that I do looks very little like a HackerRank or Leetcode kind of test. So much of full-stack development is just hooking things up. Add a column to a table, define a new endpoint, push some data to the UI. I've written like, 2 real algorithms ever.
(5/7)
Here are some topics I've been asked about in interviews that I've never encountered on the job in 8 years as a developer:
- Tries
- Heaps
- Graphs
- Recursive backtracking
- Linear algebra
(6/7)
Why does this process have to be so demoralizing? It's fucked that the industry expects you to study for 100+ hours each time you want to switch jobs. This is my second time doing this in under a year. I'm exhausted, y'all. Something's gotta give.
(7/7)
You can follow @techdebtor.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:
Those who think consciousness raising & movement building are disconnected, or even a distraction from electoral politics have not paid attention to the history of social change.In this thread, we
Read more
The 2020s will be known as the Remote Work decadeA few predictions of what is likely to emerge[ a thread ] Third Space: Office and Working from Home will
Read more
1/29: Have you ever had a concept explained to you that helps frame complex issues you’ve been wrestling with and opens your eyes to new possibilities? A concept that I
Read more
By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.