There is no "correct" answer to it. It is an investigation into how you break the problem down and approach it. When presented with a challenge to it, how do you then look at it and consider how to solve it.
The Codeless Code - Case 83 Consequences http://thecodelesscode.com/case/83?topic=interviews
re: your last question - I interviewed for both SWE and EM positions, depending on what was available at any given company. At companies that had both roles open, I talked to folks to understand what they expected out of EMs vs engineers, as it varied a lot - and then I picked whatever was more appealing to me. In aggregate I went for 70% SWE / 30% EM roles (roughly)
I'm curious about the rough models which exist.
My first company out of college actually banned it as a practice - EMs were not allowed to be active contributors.
I know at some companies, it’s actually a requirement, or at least heavily encouraged, for a manager to spend at least 20% time writing code.
And then some places are a mixed bag.
I can see both arguments! Just good to know that a company has a coherent philosophy on the issue.
Pure people manager - HR admin (compensation evaluation etc), professional development, project management, team resourcing, etc. Tend to see this less in very small companies.
TLM (Tech Lead / Manager) - Does all of the above, plus also acts as a tech lead for the project - technical design, mentoring, and possibly some coding. Tend to see this less in very big companies. TLM are typically first-line managers, I've not seen a TLM that manages managers (i.e. Director level).
Rarely, hybrid engineer/manager - Does all the above, plus expected to contribute significantly to coding. Honestly it's a red flag for me to see a team hiring for this archetype, in my opinion it's a pragmatic stopgap you might find yourself with as a small company, until you can hire an engineer or manager to split the role; it's not something you should explicitly hire for.
Sometimes, product lead as "mini-CEO" - manages the team/org and owns product direction. Typically will have a tech lead on the team to own that side of things. This can grow into a Director position, managing the team managers and still owning the product function.
Some archetyes for dedicated Staff engineers (typically the equivalent IC-track level to a team manager): https://staffeng.com/guides/staff-archetypes
I honestly think I'd be physically incapable of doing this. I'm on the HSP side and even a single set of interviews is enough to drive me into an insomnia/anxiety cycle for weeks. I can't even imagine what this would be like for me. Albeit I admit it's the best way to get the job you want. Maybe I'm in the wrong industry...
More people than you might imagine take Xanax to get through interviews.
You know, that's actually a great idea I never thought about. I'll see if I can get a script next time I go through interview loops. Might make the process less hellish for me, I hope.
But if a normally functioning person needs to start Xanax for the purpose of getting through (let's admit it) a power-play hazing ritual that has little to do with the job, then maybe that person and the rest of us should go tell those companies to take a hike. The EEOC should, as well.
I prefer the 'choose your battles' approach. Interviewing at 3-5 places (not 35), and being prepared to 'win' before I start, as well as possible.
I do find the marathon interviews are difficult, but the difficult parts for me are front-loaded - the initial anxiety, gradually building to being desperate for a break (or to escape) around halfway through. But then like a runner in the zone or coasting through the second half of a double shift on sleep deprivation, the latter part is relatively smooth.
Interviews are conversations, not fights.
Hard to find the right balance.
https://www.goodrx.com/conditions/generalized-anxiety-disord...
Kind of says something about the amount of cultural sway technologists actually have.
> Maybe I'm in the wrong industry...
I wonder this as well. I really like software development as a career, but the interviewing is just getting to be too much. It would suck to have to change careers away from something you're pretty good at and really like just because of what basically amounts to hazing.
As a married man nearing his 40s I can't imagine doing this. I need to keep my full time job to support my family, so just quit and focus 100% on prepping is not an option. Assuming a 5 1-hour round interview, I would need to take PTO or somehow juggle my calendar to take interviews. I'm horrified at the thought of taking one week off and doing interviews for 5 days straight. I guess I'll cross that bridge when I get there.
Fortunately, there are still lots of good startups, small and medium sized companies that pay well and actually respect your time.
Along with past experience on CV this should be enough to assess whether a candidate is suitable for the 3 or 6 months probation employment.
If after all this you still can’t decide whether the candidate is a match and worth keeping permanently post probation, your hiring and working processes are seriously broken. I don’t understand then need for multiple, hours long, dozen interviewers processes.
For senior positions, I would rather spend an hour or two talking through hypothetical scenarios, including design decisions and teamwork. I want to hear deeper knowledge from a candidate, not "do they know valid syntax and are they able to solve trivial problems".
As in all things, it depends on the company that is doing the hiring and the role they are being hired for. In some cases, "senior" roles are basically individual contributors with a few years of experience. In others, a senior should be able to translate business requirements into a big picture technical solution, break down the portions of the stack they are familiar with, and explain what assumptions are made and what unknown factors need to be sussed out in order to plan a proper implementation.
The latter portion is difficult to do with a take home assignment without careful planning for the follow-up interviews. 5 hour round-robin interviews typically (in my experience) end up being "live leet code" sessions that don't represent day-to-day work at all.
Or just do a few interviews per week while working like most people.
“Well my notice expires at my current job in two weeks but I’d like to take a short break in between to decompress / spend time with my family.”
“Obviously we’d like to have you as soon as possible but we don’t want to keep you from your family. How about six weeks from now?”
“Works for me.”
Obviously different companies/roles will be differently flexible and bigger companies will be more tolerant of delaying start by longer. And you can only do that if you get a job offer somewhere. But the parent comment wasn’t even suggesting taking holiday to interview for a week straight right?
As a kid, I went to Disneyland exactly zero times. There are hasher realities for many.
Before you respond that I don’t know what it’s like juggling a family and I must be a fresh college grad, the 74 in my username has significance
A pity since the TC game is played by pitting companies against each other in a bidding war. I guess I'll have to figure out my strategy when the time comes.
One needn’t interview at so many companies. If one is in no rush to quit then just spread interviews out over a much longer time.
So the game becomes to avoid hiring someone like that at all costs, because once they are hired they are impossible to get rid of.
I wish employment was more like contracting - you give someone a trial for a few weeks and then end it it’s not a mutual fit. No long interview necessary - the job is the interview.
If they are a NNPP, gathering the necessary documentation and putting them on a PIP or shuffling them to another team is likely an easier path.
I think what might be happening is a vicious feedback loop of
* companies hiring too many smart engineers
* those engineers are in turn very bored and don’t have much to do so they check out
* not much gets done so more people get hired to do more stuff.
First, many more applicants than positions. If you've got 100 for a single position, then selecting the best 10 out of that set will look like a high hiring bar when it is 'just' a "we don't have time to interview everyone." And many positions get many more than 100 applicants per position.
Next, the aspect of job hoping that has become fairly common in the past decade. If the average tenure of the person hired in the last 10 years is decreasing because the person can get paid more by switching companies then the other side of the push will be to raise the bar so that the new hire will require less onboarding and be able to be productive faster. If the company is using Kafka in house, and it takes two months to really get to the point of understanding it and the person leaves after a year, that's two months lost. So, instead hire someone who understands it and only requires a week to pick up the peculiarities here so that when they leave in a year you haven't lost a portion of the time getting them familiar with the tech stack.
Lastly, it is a pain to fire someone. You need documentation about their issues and that it is performance related and that its not done during a 30 day window where they've fired 49 other people and that HR is ensuring that they've got the CYA on a wrongful dismissal documented. And then, even when you do fire someone, you've got to go back and reopen the position and hire again and that takes two months from the time you submit the job description to HR to starting a new person along with at least a week of manager and interviewer time in the process.
The safest thing for a company to do is move them over to a team that does low priority, low impact things and never promote them in an engineering capacity. Note that sometimes when you move a person from a dev job to a QA or operations job you'll get the person coming back with constructive dismissal which takes time to handle.
Yes - I can manage my calendar better, but then people would get suspicious, or I'd be worried some emergency comes up.
When I used to interview, I'd just start having more "doctor appointments" or what not and block off a few hours. Also, these were back in the days of going on-site for interviews. My engineers who quit did it all remotely, even the final round (covid times...) so it's more manageable.
That’s by design. Most places don’t want people like you. They want pliable, naive employees who will kill themselves for the company and not count their hours.
The key takeaways, coming from someone with a similar background:
* Rely heavily on your personal network to both identify worthwhile opportunities and for referrals which, in the Before Times, pretty much guaranteed an interview
* It's worth thinking through what type of job would make you happy _before_ you get an exploding offer
* They had a _full_ pipeline, interviewing every day for three weeks straight. It's a grind, but you definitely get "in the zone". Additionally, setting this goal ensures that you are being properly proactive/aggressive in pursuing opportunities.
* You will probably see a design interview at any FAANG or hot startup. The classic one I've seen like 5 times is "how would you design a social media feed?" I still do not know the "correct" answer to this question.
I don't have hard evidence for this but it seems that the demand is still very strong for experienced engineering managers. I am curious to hear if the author interviewed for SWE positions or engineering manager positions have they have filled both roles in the past.