Live data from Hacker News

Senior Developers Are Getting Rejected for Jobs

glenmccallum.com

211–220 of 384 posts

Re: Senior Developers Are Getting Rejected for Jobs

#211
post #89

I reject senior software engineers all the time. I give interviews on whatever language you're most comfortable in, I'm not interested in time or space complexity, I just care about how well you can use your tools and debug. I'm continually astounded at the number of people who can't sort a list (with their language's standard library), clone an array, or do basic string manipulation. I've had a staff engineer at Goo…

Lol. At my job, I code in several different languages. Sometimes, a new project requires me to to learn to write in a new language. It's not a big deal... Programming is pretty general, so new syntax doesn't slow me down too much. But I can't tell you what the sleep command is any of these languages. I look it up every single time :P

LOL, agreed.

I'm good with the sleep command in my many different languages. It's dealing with dates in any language...

I suspect 10% of of StackOverFlow hits are developers remembering how to parse a date in some form or another.

Re: Senior Developers Are Getting Rejected for Jobs

#212

I reject senior software engineers all the time. I give interviews on whatever language you're most comfortable in, I'm not interested in time or space complexity, I just care about how well you can use your tools and debug. I'm continually astounded at the number of people who can't sort a list (with their language's standard library), clone an array, or do basic string manipulation. I've had a staff engineer at Goo…

I've written in so many languages that I wouldn't be able to answer how to sleep in language X off the top of my head. Is it time.Sleep()? delay()? wait_for()? nsleep()? timer().delayUntil()? something else? No clue, but I know how to find out. You're not hiring me for my encyclopedic knowledge; you're hiring me because I get the job done quickly and effectively, using a proper design and clean, tested code.

Not to mention, there is no sleep command (I assume he meant setTimeout, which has very different functionality than a typical language's sleep command) in javascript, which kind of makes me question the credibility of someone insisting on gatekeeping the senior developer title so hard.

Re: Senior Developers Are Getting Rejected for Jobs

#213

I reject senior software engineers all the time. I give interviews on whatever language you're most comfortable in, I'm not interested in time or space complexity, I just care about how well you can use your tools and debug. I'm continually astounded at the number of people who can't sort a list (with their language's standard library), clone an array, or do basic string manipulation. I've had a staff engineer at Goo…

You're missing the forest for the trees here. In these larger companies, senior engineers tend not to work directly with code that much anymore, they're usually working on higher level problems like system design or management. These require different skill sets such as leadership and social skills that take years to develop; the ability to google quickly for a function name isn't really valued as much.

If you're working in a small company or a startup, then you don't need BigCo senior engineers, you can get away with people who haven't developed these skill sets. However if you have intentions of growing, either in your system size or in your headcount, you shouldn't discount these engineers over minor details like this. Ask them higher-level design questions if you actually want to test their abilities, otherwise you're looking at the wrong metrics.

Re: Senior Developers Are Getting Rejected for Jobs

#214
post #87

I interviewed ~500 people in a fairly large (~2000 devs) company. Interviews used to take about 6-8 hours of my week, and I was usually completely destroyed by the context switch. I remember many days when a deadline was very close, and I absolutely did not want to do the interview, but had to. In general some days I was in good mood, some in bad mood and even though I tried to make the interview as objective as poss…

I noticed that my job enjoyment took a hit during a period of heavy interviewing for new devs for all the reasons you mention. A one hour interview required a minimum of 30 minutes prep to read the resume, etc and generate questions. Then at least 30 minutes to write up my findings in a way that would allow me to participate in the roundup, which could be up to a month away if I was the phone screen. The roundup itse…

I really hated the cases were when "no" can not be explained.

In some cases when there is "no" it comes with clear instructions like: hey you need to know v8 more or understand hotspot better and try again in 6 months, but then there were those cases where the committee was incapable of giving feedback.

Re: Senior Developers Are Getting Rejected for Jobs

#215

Earlier quoted context omitted.

Absolutely untrue. Whiteboard problems absolutely do work. The vast majority of applicants cannot code at all. And I mean that literally: they're at a loss at how to write a function that adds two numbers or counts the number of elements in a list. Worse is that these guys can be employed as developers (even 'senior' ones!) for years and years in 'serious' enterprises. How, you ask? By using copy-paste and cleverly n…

The problem is there are a lot of people who are still good coders who suck at white-boarding for one reason or another. I became one of them due a combination of age, rustiness and an escalation of nervousness after failing a couple whiteboards out of the gate. Of course once I did land a job it took about a week to shake off the rustiness, and the company that hired me is thrilled. The point is that companies like…

There's also a lot of senior devs who think they are a false negative who are not.

I speak from personal experience. I failed my first FAANG style interview both because I had not prepared nor understood how white board interviews really work and because a huge subset of my skill had gotten rusty over the years. But when I first failed I was really upset and very quickly wrote off the entire process as a ridiculous test. Looking back I was a true negative and needed to brush up on a range of skills.

When I was a junior dev I spent nearly all my time studying programming, CS and software. But as I got more senior I definitely relaxed a bit on all of that and coasted more on the inertia of past successes than I should have. Yes I was good at my current job, and the ones before it, but those only represent a small subset of the skills a senior engineer should have. What made me a great engineer in one specific company allowed me to let other skills that I wasn't using decline a bit.

By being a bit more honest with myself I spent a long time getting back into the things that I used to love and also learned how to practice whiteboards. All my white board interviews after that were a success.

I think a huge push back by senior devs against these interviews is that they don't want to admit that, while they have gained a ton of valuable experience, they might not be as strong of a software engineer as they once were.

Re: Senior Developers Are Getting Rejected for Jobs

#216

Earlier quoted context omitted.

+1. I’ve interviewed senior guys, with medium to high salaries, who couldn’t do fizzbuzz. What’s worse, a lot of them were fully confident in awful solutions, and didn’t even want to test them. Talented people frustrated at the process just don’t get how bad bad coders are. I would never have believed it myself until I experienced it.

This is incredible to me. How can one get to senior or middle software engineering positions without the ability to write such trivial code?

It was incredible to me too. But it’s reality.

As another poster said above, best guess is some version of copypasta and navigation of bureaucracy.

Re: Senior Developers Are Getting Rejected for Jobs

#218
I am not a Senior. Not junior, not senior. I have been interviewing lately after my company staffed me as the only remote member of a team based in Argentina. (Live in the midwest USA, don't speak a lick of spanish).

I typically won't do programming challenges. I don't believe it's fair for the applicant, because if it becomes the industry norm then applying for 10 jobs means 10 separate programming challenges just for the opportunity to get an onsite. But, recently, during a phone interview with a shipping logistics company with a common first name in their name, I vibed with the lead I spoke to and decided I would give their hackerrank a go.

There was an interpolate json feed into an object question. There was a semi-complex array sorting / manipulation question. There was a javascript quirks question. There was a sql question that I probably would have solved using both code and sql rather than just sql. The solution I came up with was using a temp table, that hackerrank permissions did not allow. The array question, my (working) solution timed out because one of the tests used an array with several million units in it. There was no indication of a certain time this should run under. It took about five minutes after submitting to realize a way that probably wouldn't have timed out, but at the time I was happy with my solution given the whole test was timed and I had written six lines of code to solve this problem.

The final question of the test, after all of these and a few I won't go into, was to write an html form field that updated a list via javascript and had alternating CSS colors. I was so frustrated that they would throw in something so very menial and time consuming after the rest of the (timed!) test that I didn't even attempt it. (to be clear, basic javascript knowledge had already been demonstrated on the prior fizzbuzz).

I had really thought my answers would grant me an onsite, but it didn't. So yeah, back to not doing stupid timed tests.

This was a month ago. The position is still open and I expect it to be for the near future.

If anyone read this far, I have given some thought about my various interviews after some interesting ones recently (another recent time at a .net shop I was asked to demonstrate sorting a list so i did a toarray() then sort and they were like no, do it manually).

I'm probably going to put together a blog about my interviews over the years since I've had all sorts. I feel like as deep as retrospective as I can remember over my decade of interviewing might give me some insight as how I should be better.

Re: Senior Developers Are Getting Rejected for Jobs

#219

So there are multiple things that are true with people applying for development roles: 1. These "dev gate" programming challenges are filtering out senior devs, talented devs, creative devs etc. people who would be great at the role. 2. There are people applying for these roles who can't knock out a decent Fizzbuzz solution (in any amount of time). 3. For many roles, there's a flood of applicants Any solutions to thi…

I think my team has gotten pretty good at this. We address the "flood of applicants" by tossing out any resumes that don't have some sort of CS or programming on them (about 25%), and favoring, in order, people who have held a programming job, people who have done programming internships, and people who have taken CS classes. A decent GitHub profile will bump you up in the two later categories. Next is a five minute…

Your last point is interesting and hits close to home for me, from the other end. My current gig is python, but when I got hired I new exactly zero python. But I had been writing software a long time and in the same area (networking & automation) so they scooped me up. Let's just say it's worked out very well, for everyone involved.

I still don't know Java that well, though ;-)

Re: Senior Developers Are Getting Rejected for Jobs

#220
post #56

Earlier quoted context omitted.

That seems much worse than programming tests IMO. If I have a bachelor's degree, and you're asking me to retake the SAT, you're just insulting my qualifications. At least programming tests have some legitimate rationale. Let's not pretend IBM has any fucking idea what they are doing.

It wasn't an IQ test, and IBM definitely knew what it was doing in ways today's "move fast and break things" culture cannot fathom. Their software was and still is used in many mission-critical applications because the company was rigorously focused on quality. When was the last time you heard of a bug in mainframe software affecting anyone?

Maybe you're talking about something else, but have you heard about IBM's infamous Phoenix Pay System?

https://en.wikipedia.org/wiki/Phoenix_pay_system

In short, it's costing Canada billions of dollars and has affected countless people's livelihoods.

Post reply on HN