451–460 of 1001 posts
Earlier quoted context omitted.
> better qualified candidates in the pipeline Probably the ones that read the spec and delivered what was required. If you're going to gloss over something trivial, what does that say about your attention to detail?
Silver lining: people make mistakes. Especially under stress. You don’t want to work with a group that thinks we are machines.
It's unreal that will people will bitch and moan about having to invest a couple days, maybe even a whole week in cramming/prepping/interviewing, to perform on-demand, one time, for a job that realistically will earn them $100k, $200k, $300k, $400k+ a year. Meanwhile people that work harder than us 5 days a week for the entire duration of their career will make 1/2, 1/4, 1/6th, or less of income, with none of the per…
As is quite normal in this industry, both of us occasionally have to put in large amounts of unpaid overtime in order to make deadlines. That doesn't translate into more money or career fulfilment for us, because the city we live in has a very low ceiling for this sort of thing. Not everyone lives in LA, SFA, or NYC.
It's unreal that will people will bitch and moan about having to invest a couple days, maybe even a whole week in cramming/prepping/interviewing, to perform on-demand, one time, for a job that realistically will earn them $100k, $200k, $300k, $400k+ a year. Meanwhile people that work harder than us 5 days a week for the entire duration of their career will make 1/2, 1/4, 1/6th, or less of income, with none of the per…
Happy to discuss this, though (and i assure without any downmodding!) I disagree with you in part. One issue is the amount of time required early in the process. A whole day of whiteboard exercisis plus prep time is a lot to ask wheon only, say, 4% of the people who go through it are offered a position. Keep in mind that unlike the bar exam or med boards, devs go through this every time they apply. This pushes a tremendous inefficiency out onto the field and almost certainly deters people fromapplyingfor jobs at all.
Which brings me to my next point- who is doing the majority of the complaining? Tech companies are constantly bemoaning the shortage of good developers. Im ok with a company not hiring me because i wont spend 40 hours on their unpaid homework assignment or exam. Seems they need to accept that just as i may not be hired, they may not do any hiring, and their own processes are the reason.
Earlier quoted context omitted.
If you're only applying to one job and you get it, sure. But when you're looking for a new job and sending out dozens of resumes, it adds up pretty quickly! On top of that, it makes rejections all the more dispiriting when you spend hours or days working on one job application.
IMHO, if you can't land, say, 1 out of 3 interviews, there is a systemic personal problem, not just a bad day, and "the problem is u" -- sadly you will just need to work harder because something in your skill set is not up to snuff.
That was annoying, but considering I was unemployed and job searching full-time, it was manageable. If it becomes more common, as seems to be happening, it'll absolutely become an issue for anyone who has to do more than a couple of job applications, which probably includes most people trying to move up in position or relocate.
Earlier quoted context omitted.
I used to hate it, but have now performed enough interviews of supposedly senior devs with decades of experience. I've literally seen someone who did firmware for the space shuttle grind for 45 minutes on fizz buzz without making progress. Like, I'd they struggle for ten minutes or so, I take a step back and say "Ok, screw syntax, let's just vaguely talk about what needs to happen and mock up some pseudo code.". Even…
I’m going to show some vulnerability… this happened to me this week. I’m probably like a lot of you here: professional software developer for 20 years, have shipped countless products in multiple languages / technologies. Work has appeared on tv and print media multiple times. Have generated millions and millions in cost savings and revenue for employers and clients. But I totally failed a technical screen. It’s been…
Our industry's hiring practices are absolutely obnoxious. In an ideal world, you could trust someone's resume. e.g. "I've written large production programs in C." Ok, great, so then clearly this person knows C so there should be no need to dissect code or run them thru some linked list algorithm and see if they know how to use pointers correctly. Yet, we do. Ok, then what about open source contributions (if they have…
The hiring process is a response to the fact that employers cannot trust a single word candidates say about their experience. This isn't paranoia. Literally, most candidates we see cannot code, even when they supposed have a decade or more of industry experience. If the industry wasn't so full of lying incompetents, it wouldn't be an issue.
Here's the thing tho': my CV is honest and my track record is pretty good: some small companies and some name-brand, well respected in their industries, known for probing interviews, over about 20 years. There may be some bad actors in the global candidate pool. But seriously, asking me these questions is like tearing my CV up in front of me and calling me a liar to my face.
I am not in the market right now and hope not to be for a good while, but I dream of being asked a stupid whiteboard question, solving it, then throwing the board eraser at the interviewer's head and walking out...
Earlier quoted context omitted.
> How many engineers would accept an offer which is conditional on "a week or two of contract work"? Unless you work on Google or something with the same size, more than you expect to hire. And yes, you will biasing your candidate pool. Every kind of procedure will bias the candidate pool. Again, unless your company is Google-sized, the only important thing about that bias is if it align with the preponderant bias (w…
> Again, unless your company is Google-sized, the only important thing about that bias is if it align with the preponderant bias (what is bad) or not. If you mean (which is bad) then I agree completely. You want your set of biases (biases being errors in hiring, meaning the things you select on that don't match with what the job needs) to be as different as possible from the rest of the industry. Whenever you can pic…
If you are not one of those companies, your focus should be on making sure you are not biased the same way as them. Other means of avoiding rejecting good candidates have a much lower return.
It's unreal that will people will bitch and moan about having to invest a couple days, maybe even a whole week in cramming/prepping/interviewing, to perform on-demand, one time, for a job that realistically will earn them $100k, $200k, $300k, $400k+ a year. Meanwhile people that work harder than us 5 days a week for the entire duration of their career will make 1/2, 1/4, 1/6th, or less of income, with none of the per…
Amazon, Facebook, Google? Those are hard salaries to get in my experience. I'm reasonably well respected in my field; attending conferences, speaking, leading meetups, and tirelessly researching computer science in my free time. Can't get a job at those 3, but going to try and take the hedge fund route I guess (I'm in NYC).
Our industry's hiring practices are absolutely obnoxious. In an ideal world, you could trust someone's resume. e.g. "I've written large production programs in C." Ok, great, so then clearly this person knows C so there should be no need to dissect code or run them thru some linked list algorithm and see if they know how to use pointers correctly. Yet, we do. Ok, then what about open source contributions (if they have…
I'm not sure its just the recruiting side. We're seeing some concerning positions in the market: 1. Expectation of long work hours (Frequent and short deadlines due to agile) 2. Micromanagment being the standard (agile) 3. Terrible environments (open desk/office) 4. Removal of vacation time (unlimited PTO means you have no vacation days)
That's just not universally true at all. Using my current employer as an example, they have been very good about encouraging employees to take advantage of unlimited PTO.
Managers take PTO and encourage people that haven't taken it in a while to do so. Even the CEO goes in front of the company at all hands every once in a while and tells people "I just came back from a week vacation, you guys should too, remember to take time to recharge". It's something you have to get right in the company culture early on, granted.
I personally am so spoiled by this that the thought of having a set number of vacation days gives me anxiety. I don't want to count vacation days. It's not that I take a ton of vacation, I'm not a big traveler. But I like knowing that I can go to my manager and say "I'm taking friday off cause I'm going on a road trip this weekend" and he can just say "cool, just put it on the calendar" without worrying about counting days.
That said, I know this is really dependent on the company and have been in the opposite position at a company where PTO wasn't counted but was culturally discouraged, so I get where people are coming from. But I wouldn't just flat out dismiss the idea like so many on HN do.
Earlier quoted context omitted.
What is working with them like?
I mean, they're people. I'm still close friends with a few of them, and I didn't like some of them. It's no different than working with anybody with a disability or an illness (or kids, or elderly parents, or any of the million other human things that can make you a less-than-full-functionality worker bot) - you make the necessary accommodations, work around issues when they arise, and live with it. Specifically, it…
He wasn't going to come to any works nights out or even lunches and like you said certain accomodations have to be made, e.g. access to a private quiet room for him at certain times... Able to work from home when he had to etc.
His father had to go to his interview with him, luckily the company allowed this. We have since gone our seperate ways but wherever he is working now got a great developer. I'd happily work with him again.