What sort of person do these exercises? Is it fresh college graduates?
I also at the same time, interviewed with the fastest growing startup in the area, who had way better comp, slightly better benefits, etc. They asked me to do a take home homework assignment that would've taken like 20 hours, so they could see how I work.
I ghosted the second contact, and after another round of interviews, accepted with the first company, and I'm by far happier with my work and the respect given to my input at this job than any previous one I've had. I'm certain that wouldn't have been the case at the latter company.
I truly believe that once you are beyond the junior level, interviews really are a two way street, and you should jump with the utmost caution unless you already dislike where you are.
Knowing more about an entire system and architecting it requires a lot of variety of experience and it's just a more fun interview for everyone involved.
When I interview people, I also hope I'm assigned to conduct our architecture one because it really makes you learn a lot about an engineer.
They feel very much like the sort of thing you use in an environment where you've got way more qualified candidates than you have open positions, so you're optimising for screening people out. Certainly not a place I've ever been in over here, where the norm is to be desperately looking for even one qualified candidate.
I'm 11 years into the profession. Solving leetcode is somewhat different from the problems I solve at work, so I struggled at first and had to practice, and practice a lot. I have yet to find out how useful this is outside of job interviews, but my brain started to forget some topics from CS after doing so much web stuff and it was a good way to remember these and practice problem solving.
Also what constitutes an awesome GitHub? Because unless you run a project with > 100 stars it’s little more than academic and doesn’t matter.
At my current company I'll probably pay less than half as what you'd make at a "nice" company though, so maybe you won't interview with me anyway.
Thankfully, where I live, most companies don't really ask for hard-core algorithm questions - if they did, I would never get a job, as I really suck at these.
I was able to answer the question. Many did not, but the process was more about how you handled yourself through the process, how you communicated with the interviewer as you walked through the problem, than it was about reaching the actual solution. I know several people, bright people, that were hired there even though they never solved the puzzle.
After I got the proper solution, I asked the person that administered the quiz "Is this an indication of what kind of code gets written here?" He just started laughing and saying "no, no no". Because I would not take a job at any company that actually wrote code like that.
That interviewer ended up being my first manager, and we had a good work relationship. It was a great few years of my career.
I don't at all believe I magically got 10x better at coding though... just 10x better at recognizing and remembering patterns.
I think the best type of interview for everyone is the "walk me through X" type. You can almost always spot BS in those and if you can't... should you even be interviewing? I would 100% rather have someone that knows how to glue pieces together vs someone that is good at leetcode... don't get me wrong, I'm amazed at how awesome people are at it and I've met people who excel at both... but I feel its just too weighted in interviews.
It started with big tech companies, but I’ve also seen smaller or less prestigious companies doing that, too. There’s a whole small industry around the big tech interview preparation.
And it’s not only for fresh grads - a year ago I interviewed with some SV companies for senior positions (including EM) and I had to go through Leetcode interview as well
I dont care about your skill if nobody gets along with you. You will be the reason top tier talent leaves. A good engineering team is the one where everyone gets along. Everyone has memories of working with toxic people. Imagine if you replaced all those toxic people in former jobs with people you got along with. Would you have left at all? It makes a huge difference.
Effectively we have switched from quantitative to qualitative where the questions are similar to start but because of the fluid nature of conversation, drift further from other candidates.
amount of data to be stored. Amount of traffic / users. Amount of servers and services you need. Architecture, scalability, infra, etc etc.
Where is 99% of the cases a small group of people would suffice, no micro services, and in terms of infra, a cheap VPS is more than capable enough.
People just don’t have a clue, bc they don’t understand what actual work needs to be done.
You're a good programmer if you've made something good. Most people who are good at leetcode have never made anything significant. When is the last time you saw someone who is well-known for some successful product linking to their leetcode account?
That's not playing is safe, though, that's playing it wrong.
If the cost of interviewing candidates were zero and the was an infinite supply of actually good programmers, then it would be fine to err on the side of many false negatives for the sake of avoiding false positives, especially since the cost of false positives is high.
But that's not true. You pay a price for every interview, and pay a further price for every day without the qualified help you need. And you're probably in a competitive market -- a relatively small delta between you and your competitors' hiring efficiency might mean they get almost all the good candidates while you get almost none.
Anyway, like I said, any half-decent CTO should be able to fix such an obvious mistake. Hiring is a high-stakes move and it pays to be picky, but it really doesn't pay to be dumb about it.
Just based on my personal experience, I doubt very many people beyond junior or entry-level are going to study leetcode exercises, so you're walking away from almost everyone useful past that level.
Maybe you could give people a choice of problems only good programmers could solve, but of different types, and let them choose the one they want. Leetcode, sure. Or: here's a windows system and windbg, tell me what's wrong. You've doubled your chances. Spend some effort to come up with five or six or seven different ones and you might have something.
Of course has to be technical, hast to have a huge background in development, and been in many of the areas he will oversee... but you cannot ask him to excel at every one.
People who work full-time as developers spend hundreds of hours practicing leetcode and hackerrank so that they can pass the interview, but a CTO who's 5 levels above and hasn't logged to Github for 3 years should excel at it? Come on.
I agree with the premise of the article, CTO should be technical, but I don't think that "technical" and "great at coding" are the same. One of the best CTOs I've had came from a product background. He was technical enough to understand the technical discussions and he was able to support his directors in hiring plans, technical decisions etc. but he wouldn't pass any coding test more complex than FizzBuzz. Still, he was great at his job.