3 ms·

Yes, ask give interview tasks which are realistic depictions of the actual job tasks. No, the hiring managers that are into cargoogle culting are not actually

by pydry 2y ago

Yes, ask give interview tasks which are realistic depictions of the actual job tasks. No, the hiring managers that are into cargoogle culting are not actually that interested in how to do interviewing properly. Not unless, say, google does it and they can copy it. For them the important thing is that leetcode is a safe, defensible choice because "everyone else does it that way".

FartyMcFarter 2y ago
> Yes, ask give interview tasks which are realistic depictions of the actual job tasks. I think this is exactly what a lot of companies try to do when interviewing. Depending on how much time they want candidates and interviewers to spend on the task, this ranges from leetcode-style problems to bigger coding challenges (possibly with some debugging or collaboration involved). What would you suggest concretely?
- pydry 2y ago
  A lot of companies do do it this way but the ones that set leetcode problems are deliberately avoiding setting realistic interview tasks. If you think leetcode is representative of real life programming you're probably a college student.
SatvikBeri 2y ago
One of the main questions I ask in interviews is basically "we have a data pipeline with goal X and constraints A, B, and C. How would you design it?" Depending on how they do, we'll discuss various tradeoffs, other possible goals/constraints, and so on. This is based on a real system I designed and have been maintaining for ~5 years, and is also very similar to other systems I've run at previous jobs. About half the candidates complain that it's not a realistic question.
ball_of_lint 2y ago
As you climb the engineering IC ladder your responsibilities involve larger and larger tasks and timescales. It's not possible to measure whether someone can make the right decisions about the architecture of a service as requirements change over years in a 1-day interview. Anything that isn't "be the engineer maintaining this service for 1 year" is going to be a proxy for that, which can be learned and gamed. What would be a "proper" interview in your opinion?

by pydry 2y ago

FartyMcFarter 2y ago

> Yes, ask give interview tasks which are realistic depictions of the actual job tasks. I think this is exactly what a lot of companies try to do when interviewing. Depending on how much time they want candidates and interviewers to spend on the task, this ranges from leetcode-style problems to bigger coding challenges (possibly with some debugging or collaboration involved). What would you suggest concretely?

pydry 2y ago
A lot of companies do do it this way but the ones that set leetcode problems are deliberately avoiding setting realistic interview tasks. If you think leetcode is representative of real life programming you're probably a college student.

SatvikBeri 2y ago

One of the main questions I ask in interviews is basically "we have a data pipeline with goal X and constraints A, B, and C. How would you design it?" Depending on how they do, we'll discuss various tradeoffs, other possible goals/constraints, and so on. This is based on a real system I designed and have been maintaining for ~5 years, and is also very similar to other systems I've run at previous jobs. About half the candidates complain that it's not a realistic question.

ball_of_lint 2y ago

As you climb the engineering IC ladder your responsibilities involve larger and larger tasks and timescales. It's not possible to measure whether someone can make the right decisions about the architecture of a service as requirements change over years in a 1-day interview. Anything that isn't "be the engineer maintaining this service for 1 year" is going to be a proxy for that, which can be learned and gamed. What would be a "proper" interview in your opinion?