News for hackers. Stuff that matters.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by the_only_law on Thursday August 19, 2021 @12:00PM (#28235504)
> You radically overestimate the average skill of the competition because of the crowd you hang around with: Many people already successfully employed as senior engineers cannot actually implement FizzBuzz. Just read it and weep. Key takeaway: you probably are good enough to work at that company you think you’re not good enough for. They hire better mortals, but they still hire mortals.

As much as I want to believe this, I think the ability of developers separates itself in different “classes”. The senior devs who can’t complete a fizzbuzz are probably not the competition for the jobs I want.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by borski on Thursday August 19, 2021 @12:07PM (#28235594)
You’re wrong, from my experience. I’ve interviewed many a “senior developer” who simply cannot code any longer because they’ve spent all their time doing other things or at a higher level.

Some can still code, and that’s your competition. Many cannot.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by eysquared on Thursday August 19, 2021 @12:20PM (#28235763)
As someone that has held that title at multiple FAANGS and done hundreds of interviews: please don't equate performance in the absurd interview process with ability to code.

Most of the best developers I know would fail a technical interview for their current job.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by thatjoeoverthr on Thursday August 19, 2021 @12:41PM (#28236053)
I think I just did last week. The interviewer asked me to explain SOLID. I could only remember the O and the L. All of these practices are deeply internalized but without having interviewed in a while, or even used English at work, the little speeches and buzzwords escaped me. Then he brought up REST. “What are important principles of REST?” Ummm, nounifaction? Uff.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by gampleman on Friday August 20, 2021 @05:19AM (#28244201)
I usually google SOLID before job interviews just in case someone actually asks about this.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by pdimitar on Thursday August 19, 2021 @01:04PM (#28236370)
I fully sympathize and I had to mute my mic once so the interviewer doesn't hear that I am searching for what SOLID stands for, and then I proceeded to explain each of the characters.

But to be fair... is that an actual technical interview?

Re:Don't Call Yourself A Programmer, And Other Career Advice... by borski on Saturday August 21, 2021 @05:35PM (#28260776)
I agree with you, but I’m talking about literal FizzBuzz-esque questions. Experienced or not, any “senior developer/engineer” should be able to write a for loop.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by otabdeveloper4 on Friday August 20, 2021 @03:43AM (#28243644)
> Most of the best developers I know would fail a technical interview for their current job.

Yes, that's because they can't code.

(No, connecting APIs and navigating information complexity landmines isn't coding.)

Re:Don't Call Yourself A Programmer, And Other Career Advice... by swader999 on Thursday August 19, 2021 @12:32PM (#28235916)
Amen to that.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by cactus2093 on Thursday August 19, 2021 @12:38PM (#28235999)
I'm sure it depends on your industry and location.

In silicon valley software companies (e.g. Google, FB, Twitter, Stripe, Airbnb, Uber, and all the smaller companies following the same interview & career ladder playbook) a senior engineer or L5 is just someone with around 5+ years of experience. They might have a few more meetings and spend a bit more time working on design docs, planning, mentoring others, etc. compared to more junior engineers, but their primary job is still writing code. Even at higher levels like Staff and Principal engineers, less time might be spent writing code and more time in meetings, leading committees, approving the largest in scope design docs, etc. but there are so few of these people and the bar is so high to get there that they were at least at one time some of the strongest engineers at the company, and they still code sometimes even at this level. In the entire IC track at these companies, I suspect you'll find approximately 0% of people that are so incompetent they are just unable to implement fizzbuzz. In the management track you'd find some, but even there I suspect quite a low percentage.

In other industries, maybe banking, large contractors, more old fashioned megacorps like the GE's of the world, I think there might be more "architect" and other technical tracks that are allegedly still programmer IC tracks but where the senior folks are much further removed from programming and wouldn't be able to implement fizzbuzz.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by borski on Saturday August 21, 2021 @05:37PM (#28260792)
I was referring to SV software companies, as that’s where I’m based.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by sethammons on Thursday August 19, 2021 @06:46PM (#28240297)
true story: I give out a problem to code up a cache with some specific requirements. I've written this thing up in several languages, I've given this particular interview problem to maybe a hundred or more people. I know this problem.

I got asked this problem and my mind went completely blank and I had to solve it from first principals, making some of the same blunders I see others making when I work with them through it.

When I see people claim that senior devs can't FizzBuzz, I have to imagine what they mean is that they do some silly error because they are under pressure and you have to remind them about "what about 15?" or something. I've interviewed hundreds of developers and only two had trouble implementing a loop and conditionals as a concept.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by slumdev on Thursday August 19, 2021 @12:18PM (#28235741)
The people who can't code any longer are still typically able to describe an algorithm, at least in pseudocode.

Whiteboarding Yet Another Graph Search Problem With Perfect Syntax[1] might be beyond their current short-term abilities, but I'd be surprised if they couldn't produce pseudocode and architectural design that solves most real-world problems.

On the other hand, there are plenty of "seniors" who couldn't write code in the first place.

[1]Everyone knows which employer does this.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by ldjkfkdsjnv on Thursday August 19, 2021 @12:13PM (#28235666)
I work with a bunch of senior engineers making 400-600k, I would say there isnt a huge difference between them and ones making 175k at a startup/non tech business. The biggest thing is comfort with scale, and high scale thinking. But its nothing thats difficult, just something to learn. If anything, I have seen much higher proficiency at startups where delivering across the stack is critical. Really, the interview process is segmenting engineers in ways that dont correlate with job performance (though there definitely is some signal)