>but when they describe the process it adds up to around 4-5 hours total.
4-5 hours for an entry level role does seem excessive yes (if you're not a top tier tech company). How much do you really need to gleam from a new grad? Why does a new grad need to talk to the CTO to show their eagerness?
I've gone through longer hurdles (one interview I did for a potential 2nd job with 2YOE at the time was HR call, 2 stages, and an all day interview with 3 technical stages and 2 "culture fits". So evaluate the stages as you will there), but that doesn't mean I saw it as reasonable. I don't hold the cards in these processes though.
>I frequently have to convince people to do simple take-home problems
everyone's experience will vary, but I've never had a "simple take home problem". Ironically enough my shortest problems were timed 90 minute leetcode medium-hard questions. most other takehomes are just 4-12+ hour miniprojects or quizzes spanning coding, math, language domain questions, and system design. I did it for my first few jobs, but I really can't these days unless I am already far along. Especially when you get a few from last year that ghost you after you turn it in.
> 4-5 hours for an entry level role does seem excessive yes (if you're not a top tier tech company).
Not really? Between a half hour with the recruiter, an hour with the manager, an hour or 90 minutes with the broader team, a little time with HR, you’re bumping right up there on 4 hours. I agree with the parent, people’s expectations have been warped recently.
I don't really count the recruiter call. This is basically just "tell me about yourself" and "can we align on compensation/localtion"? Not much to study for outside of remembering your resume. I don't count the offer stage with HR for similar reasons (though these days, even the offer stage doesn't guarantee an offer, even if you don't negotiate).
So maybe it's a misalignment. that's a 2-3 hour interview gauntlet in my eyes.
>I agree with the parent, people’s expectations have been warped recently.
I've done much much worse in my experience. Doesn't mean I think it's okay, productive, nor respectful. Recruiter -> manager -> Team is a fine 3 step process process (with a potential take home test. so 4 stages) I agree with responses questining the marginal value of the 5th stage with another team member, the 6th stage with some C class you'll never directly talk to, and beyond. Very few people are are applying for director roles, which is the only place I can see such stages needed.
4-5 hours for an entry level role does seem excessive yes (if you're not a top tier tech company). How much do you really need to gleam from a new grad? Why does a new grad need to talk to the CTO to show their eagerness?
I've gone through longer hurdles (one interview I did for a potential 2nd job with 2YOE at the time was HR call, 2 stages, and an all day interview with 3 technical stages and 2 "culture fits". So evaluate the stages as you will there), but that doesn't mean I saw it as reasonable. I don't hold the cards in these processes though.
>I frequently have to convince people to do simple take-home problems
everyone's experience will vary, but I've never had a "simple take home problem". Ironically enough my shortest problems were timed 90 minute leetcode medium-hard questions. most other takehomes are just 4-12+ hour miniprojects or quizzes spanning coding, math, language domain questions, and system design. I did it for my first few jobs, but I really can't these days unless I am already far along. Especially when you get a few from last year that ghost you after you turn it in.