2 ms·
My current stumbling block is the "design" interview. I get what they're going for and what I have to practice, but as someone with 25 years of experience I ju
by LanceH 2mo ago
My current stumbling block is the "design" interview. I get what they're going for and what I have to practice, but as someone with 25 years of experience I just can't help but have my experience creep into my thoughts.
Chief among those thoughts is that we can't design a clearinghouse for a banking system that already has 11 components and the request is just two simple sentences asking for a design. I apparently have an hour to complete this design task. An hour is so laughably small a time to get onto the design phase.
Again, I understand what they are going (I'm just not practicing it) for but it all feels like they're hiring for tennis but interviewing for ping pong.
- cloverich 2mo agoComing from another experienced dev who was frustrated (early) - one tip. Don't over think it. I was tripping up in two system design interviews that ultimately boiled down to them wanting laughably basic answers (one pagination, the other a db transaction). Don't be afraid to deal in basics and then directly ask if they'd like something more detailed, or not. Many places, especially non-elite ones, treat system design as a _very_ basic test of knowing how pieces fit together.