I straight up refuse coding challenges. I code in the open on GitHub quite often and have built plenty of very high quality (and complex) web applications which I can go into intricate detail about. If your company can’t figure out I’m a good hire without having me jump through your hoops then your process is trash and I have no interest in working for you. In fact, I’ve been thinking how I would approach interviewin…
That’s great. But for some reason every github profile I get to review is just an empty shell or a bunch of one commit Mooc templates. I’ve almost stopped looking at them.
Senior Developers Are Getting Rejected for Jobs
111–120 of 384 posts
Re: Senior Developers Are Getting Rejected for Jobs
#112Can someone describe what is a 'senior'? This might be controversial but I see senior title promotions being thrown around just for retention reasons, could it be possible that once you start looking for another 'senior' role at another company they have different expectations of that title? Not to mention you can obtain a 'senior' title by mastering your team's code base and who knows if that knowledge is transferab…
Re: Senior Developers Are Getting Rejected for Jobs
#113The important skill to learn is figuring out how to do it. Coding is no different. For example, I've yet to use React to build an app, but I have taken the time to learn the basics of how it works. If I needed to use it I could, and would, and it wouldn't slow me down much, if at all.
I think what's important is discovering how adaptable one is. If one gets whiny about using a specific toolset they're going to be a problem no matter what you put them on that requires something different than their existing skill set.
Re: Senior Developers Are Getting Rejected for Jobs
#114Earlier quoted context omitted.
So? Bias isn't illegal unless your pattern of bias lines up with a protected class.
Ageism is illegal in US under Age Discrimination in Employment Act if that person is 40 or older.
I look younger than I am, but my patience for over-working too many hours is at an end. Years of stress have led to health issues that have to be managed.
But this all rolls into "not a cultural fit."
Re: Senior Developers Are Getting Rejected for Jobs
#115Re: Senior Developers Are Getting Rejected for Jobs
#116I started in software over 10 years ago. At that time all of the exciting jobs where for small startups and the best way to get hired was to have a great github profile or some cool projects to show off.
But small startups need a hand full of really talented devs who can solve a variety of problems, and quickly get up to speed on new domains and tech stacks. A few good developers could make a company. So hiring focused on individuals who stood out and had something unique they could bring to the team.
But FAANG companies want to hire engineers that they can treat as replaceable parts. The "rockstar" talent that was required a decade ago is a liability. This may sound like a critique but it makes perfect sense from the business standpoint, and while you can protest this all you want it won't change a landscape dominated by large software giants to one fill with disrupting startups.
It's just a different world and if you want to show that your "experienced" and not just "old" you need to show that you can adapt just as well as a decade ago. I had a moment of enlightenment when waxing nostalgic about github profiles to a really talented new engineer doing prestigious work in deep learning. I told them how much better profiles based interviews where and they reacted with horror. "How am I supposed to build a profile when I'm so busy with school, interning on the side and studying for interviews!?"
Software used to be dominated by passionate hackers, and now it's one increasingly of skilled professionals. The best work people just as hard but in a very different way.
Like it or not, software is not like it was a decade a go, and if you still want to be seen as a top tier engineer you're going to have to do it by the standard of today.
Re: Senior Developers Are Getting Rejected for Jobs
#117We need to admit that the interview process isn't about determining the relative qualifications of the applications in the pool, because we all know that 3 hours and whiteboard can't tell anything you need to know about whether or not that person will perform over the years. We need to acknowledge that we perform this pantomime in order to satisfy layers of management that are unable to accept that you can't hire for…
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 navigating their enterprise processes and dodging responsibility.
Maybe this is what you mean by 'being good at working with others', but it's definitely not what I want in a software developer.
Source: I've interviewed a great deal of people for lots of positions over the years.
Re: Senior Developers Are Getting Rejected for Jobs
#118I get the frustration of senior devs at going through this stuff, but the alternative is a weird form of credentialism based on seniority.
Re: Senior Developers Are Getting Rejected for Jobs
#119Earlier quoted context omitted.
Saying they "can't tell you anything" is one-bit thinking. Yes, there is a lot that interviews don't tell you, but they are still a useful signal.
Yeah that's fair. Im just frustrated with how low-bandwidth those things are. I definitely get a bit of a sense of how a person thinks by watching them do those CS 201-style problems, which isn't nothing.
I don't ask algorithm questions, and I wouldn't even dream of asking brain teasers. I ask questions like "Here's a pile of text that claims to be CSV, let's explore how you'd generate an HTML report out of it", and branch out from there depending on how the interview goes. I've got all sorts of directions I can go from there, from screwing up the input in various real-world ways, discussing HTML security and injection attacks, algorithmic complexity of the report, how to build a service out of this, how we're going to handle reporting errors, there's just an endless number of ways you can take the interview from there.
CS 201 doesn't usually come up.
Re: Senior Developers Are Getting Rejected for Jobs
#120I was rusty from traveling from 6 months and definitely wasn't prepared. But I finally landed a job at a place that was a little more old-school in their hiring process, and as soon as they could they converted me from contractor to full time. So I guess it's working out for them (and me).