Re:A Senior Engineer's Guide to the System Design Interview
by travem on Thursday March 02, 2023 @08:05PM
(#35004437)
I imagine a concern is that for many candidates who are under NDA with the current and past gigs, sharing detailed system design info is not something that they would be willing to do. Do you want to penalize candidates who are careful about leaking confidential IP. Given that case the fair evaluation is to start from a blank slate to see what they would build given the requirements and constraints shared in the interview.
Re:A Senior Engineer's Guide to the System Design Interview
by rednerrus on Thursday March 02, 2023 @08:11PM
(#35004502)
We don’t ask people to describes systems the worked on previously. We ask them to diagram a technical system that they understand well.
Re:A Senior Engineer's Guide to the System Design Interview
by kridsdale1 on Thursday March 02, 2023 @08:32PM
(#35004669)
If you are an expert one one system that you have built and maintained for ten years, then that’s all you know.
Re:A Senior Engineer's Guide to the System Design Interview
by lightbendover on Thursday March 02, 2023 @08:05PM
(#35004439)
Also big tech, we ask senior candidates both hypothetical systems and ones they have experience with.
Re:A Senior Engineer's Guide to the System Design Interview
by HWR_14 on Thursday March 02, 2023 @11:58PM
(#35005999)
> asking candidates to describe real world systems that they have actually built is much more useful at checking their skills than building imaginary systems.
Except those systems are owned by other companies and I have signed agreements not to talk about them.
This seems completely backwards to me. Is like saying "hey, do you know that relevant on the job experience that you have? we don't want to hear anything about it, here you have a made up scenario".
Ok ok, that is a bit cynical. Asking to design novel systems can give you some good insights about the candidate, or help with people who don't have experience building systems yet. Still it seems to me that asking candidates to describe real world systems that they have actually built is much more useful at checking their skills than building imaginary systems.
One argument against this is that candidates can "cheat" by preparing in depth a made up example. But how is that much different than the current approach?