[throwaway298477]

I don't want to sound cynical, but is the interview process likely to change any time soon?

Looking at the HN history, it's been a better part of a decade, if not longer, since people have been complaining about the hiring process.

It doesn't seem like much has changed except that it's worse, in the sense that you're usually asked to spend several hours on a coding project for screening AND have a subsequent whiteboard/leetcode interview or 10.

When you take into account all of the 'signals' that you're supposed to provide to even get a job, let alone be successful, maybe this isn't a good profession to be in anymore? Example:

- Several hours - several days coding projects. Some are screening tests.

- Having to practice leetcode continuously in order to keep it fresh in your head, because you never use it in actual work.

- Robust open source portfolio is highly encouraged, in some places required.

- Constantly keeping up with new libraries, frameworks and languages. It's unusual to get to learn these on the job, usually you have to do this on your own time.

Let's face it:

When you take into account all of that extra time, it seems like Software Engineers are not being paid very well.

Especially if you value your leisure time.

Why is it like this? Maybe it's just too competitive, too many Software Engineers applying for too few positions. Whatever the reason, it doesn't sound at all what it used to be, and maybe it's time to get out.

[quietbritishjim]

Maybe there are some places that require everything you've listed (open source repos, take-home project, whiteboard coding). But I think many, or maybe most, only require one of them.

At the end of the day, I'm sure we've all met someone that justifies requiring sight of some sort of code of the candidate before hiring them. But different people will find different types of coding test better or worse ("I don't want to spend loads of my free time on a take-home project" vs "I can't code under pressure in front of a white board even though I'm great at coding in general"). So Hacker News will always be filled with endless debate trashing all forms of assessment with no agreement on what to use instead.

[throwaway298477]

That definitely has not been my experience at all.

My experience is that almost every place I've interviewed requires both a coding project and at least one whiteboard interview, with open-source as a huge plus in your favor.

Maybe it's not an either-or thing and just requires a little bit more consideration of how it's affecting the industry as a whole.

- If someone has stellar experience on what's desired, they shouldn't have to jump through the other hoops.

- If they have a strong open source portfolio that reflects exactly what's desired, they shouldn't need the other hoops.

- If there's a whiteboard interview, don't ask about anagrams or anything that an experience dev wouldn't already be using in their day-to-day. Ask something relevant, like their understanding of databases, networking, etc if they are going to be Senior Backend dev. Ask about something a strong, experience dev actually knows that a junior doesn't. If you suspect possible gaming, then go deeper into the questions to filter out bs.

- If there's a coding exercise, keep it timed to a max of 1 hour if it's a screening test, up to 3 hours if it's a final interview. Have the project already set up for them so they're spending time on the problem and not on config. Clarify exactly what you're looking for in the results.

It's basic common sense.

I've heard on other threads a lot about being 'too old' to code. This doesn't happen in other engineering disciplines, where age is highly valued because of the experience it brings.

I'm suspecting this kind of hazing ritual to be screening out very good older devs that have a lot to bring to the table, but don't have the time to do all this extra stuff because they have a family.

[atomicity]

There are definitely not too many SWEs out there. Total compensation above $300k is something that at least thousands of engineers receive.

A lot of these engineers work 8 hour days. A lot of 7-3 and 10-5/6 hours being worked. They learn on the job, because they understand that you aren't supposed to code for 7 hours a day. You are responsible for learning on the way. You communicate with your boss so they understand you aren't slacking off.

These engineers get cold emails from recruiters and complain about getting too many. The late 2010s are actually a golden age for SWEs (some exceptions around entry level)

[Rounin]

And let's not forget what kind of treatment awaits you if by some astronomical coincidence you do get hired. There are some shit jobs out there. Highly paid shit jobs, though. So we've got that going for us.