Earlier quoted context omitted.
I agree in principle, but not in experience. I've interviewed a few people lately, Senior Eng somehow, who have impressive resumes. I ask basic coding tasks just to make sure they actually know the language claimed - just something like converting numbers to strings, and you'd be amazed how many people had no idea where to start.
You are testing if they have how to convert a number to string in working memory. Is that really helpful.. in real life they would look it up refresh themselves. You just filtered people who can look up answers and learn things. Aren't those skills more inline with what most positions need?
Why is recruiting developers so difficult?
171–180 of 233 posts
Re: Why is recruiting developers so difficult?
#172Earlier quoted context omitted.
Ok. What would you suggest instead? I need to know you can, you know, actually code.
Talk to the candidate. If you (and the candidate) cannot communicate well enough in 30 minutes to discover that then either (a) you don't know enough to work well with a really good developer or (b) the developer doesn't know enough to work with you or (c) both are true. I have never been let down by this rule, either as a candidate or an interviewer. In my experience coding exercises as part of an interview process…
Re: Why is recruiting developers so difficult?
#173Earlier quoted context omitted.
We're a terrible employer? Let me tell you what kind of employer we are. We pay top 1% of market. We work to have a low stress environment. We put life before work instead of work before life. We prioritize having the best benefits on the market, including platinum health care with $0 employee contribution and full mental health coverage for therapy and medication not covered through insurance. We don't overload our…
I could have missed it since I’m reading on my phone before my morning coffee, but you don’t appear to have stated where you work. I’m curious where it is since if you would employ someone remote from overseas you sound like a great “no bullshit” employer/company!
Re: Why is recruiting developers so difficult?
#174Earlier quoted context omitted.
There are ways of discovering if somebody can code without making them do fizzbuzz. This is a good process: https://www.youtube.com/watch?v=cfyWvJdsDRI
Quoted post unavailable.
Re: Why is recruiting developers so difficult?
#175Earlier quoted context omitted.
Tell us who you are and what your company is. You truly sound like a terrible employer based on your shocking responses. You came here to ask for feedback and then when you got it you didn't like it. You are clearly the issue of why you can't hire developers. I'd wish you good luck but I won't.
We're a terrible employer? Let me tell you what kind of employer we are. We pay top 1% of market. We work to have a low stress environment. We put life before work instead of work before life. We prioritize having the best benefits on the market, including platinum health care with $0 employee contribution and full mental health coverage for therapy and medication not covered through insurance. We don't overload our…
I see you went back through a lot of responses and edited them. Why is that?
Re: Why is recruiting developers so difficult?
#176Earlier quoted context omitted.
> If you do all of your two week sprint work in 20 minutes, you can enjoy the next two weeks off. Citation/sources wanted. That was my expectation with a 'salary' job; being paid to get the work done. Work is done under 40hr, congrats go home! Work takes longer than 40hr, oh well. In my experience though, in _every single_ company punishes efficiency and hard work, with more work. You're done in 20h? CONGRATS, you ge…
Yes, I/we do things significantly different than any other company I've worked for. Working fully remote makes it easier since you don't see people getting up from their desks or not coming into work. Our developers have no set hours, can work any hours they want, and are only expected to get the work assigned to them during a sprint done, no more, no less. I brought this style of work to our workplace and it's been…
Quality expectations make a lot of sense, but “on time” is famously hard in software. How do you decide whether the developer was slow or the deadline was unrealistic? And similarly, how do you protect developers from feeling that they have to throw out work-life balance to hit deadlines/sprints that turn out to be unrealistic?
Re: Why is recruiting developers so difficult?
#177Earlier quoted context omitted.
There are plenty of fish in the sea....
Tell us who you are and what your company is. You truly sound like a terrible employer based on your shocking responses. You came here to ask for feedback and then when you got it you didn't like it. You are clearly the issue of why you can't hire developers. I'd wish you good luck but I won't.
Re: Why is recruiting developers so difficult?
#178Earlier quoted context omitted.
> Sounds like we wouldn't want you anyways if you have such poor work ethic. Ouch. I knew I saw red flags in your original post. This seals the deal.
What red flags did you see? That we pay top of market? That we work to have a low stress environment? That we put life before work instead of work before life? That we prioritize having the best benefits on the market, including platinum health care with $0 employee contribution and full mental health coverage for therapy and medication not covered through insurance? That we don't overload our top performers by givin…
1. Mentioning firing in the very first post when talking about hiring.
2. Take home interview tests, showing you don't value your potential employee's time.
3. And this is an interesting one: accusing someone of having a poor work ethic when you don't know them and they didn't show any sign of it. This is a big red flag because it points to you equating disagreements with performance, which makes #1 even more of a red flag.
Re: Why is recruiting developers so difficult?
#1791) Because recruiters don't understand the subject material. 2) Because companies are hilariously risk adverse. I have over a decade experience in a consultancy environments (faster paced and more rigorous than a lot of other jobs, sorry not sorry). My work was independently driven and I provided input to the projects I was on at the highest levels. I've set IT and SWE policy for and introduced leading products at mo…
When was the last time you interviewed, and how do you feel about remote work? I interviewed a lot the last couple years, from the Midwest, and had more remote opportunities than I could handle. I'm not interviewing with FAANG though; almost entirely private companies, seed to E.
I wasn't hyper focused on FAANG. I did actually get a FAANG interview, didn't go anywhere. I mostly just don't get interviews.
Re: Why is recruiting developers so difficult?
#180Number one reason: You're not offering me enough good reasons to leave my current job. I don't think HR and software recruiting has really caught up to the reality that many developers by their mid-30's are sitting on a million+ in assets and good ones can rake in 200K+ easy. Further we usually find equilibrium with our roles wherever we are even if we have gripes with how things are because most devs are pragmatic p…
>>> many developers by their mid-30's are sitting on a million+ in assets and good ones can rake in 200K+ easy. What !!! Edit: I did return to tone down my reaction but I would be interested in any (evidence based) research on the pay scales in and out of SV. I understand it is only the very top tech (FAANG) that pay so highly and mostly though share options. It's not like that in Europe I am afraid. But even so, if…
I also made that much last year by working remotely for a Canadian company via a.team.
I know more examples of people working for Facebook in Germany and remotely for an Israeli company making over €300k.