Why is recruiting developers so difficult?
151–160 of 233 posts
Re: Why is recruiting developers so difficult?
#152Earlier quoted context omitted.
It's literally an elite salary. It makes no sense to imply you're living a frugal, simple life if you need an elite salary to do it.
I wasn't the one who said I was living a frugal life.
Re: Why is recruiting developers so difficult?
#153Because you make it a complete nightmare. I'd rather wait in line at the DMV all day than go through a typical 6hr tech interview. Hire me based on my resume and a phone call, give me a task, and if it's good enough keep me. Problem solved.
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.
Re: Why is recruiting developers so difficult?
#154Earlier quoted context omitted.
That skill has nothing specifically to do with Go. Most languages have some "ParseInt" function or so. And of all the languages I use for daily work I could not 100% tell you what that function is exactly called. By doing that you are wasting a potentially good developper because they didn't happen to remember some languages exact syntax. It's also just straight up insulting. If someone worked for x years in a relate…
Converting ints to strings isn't a 'skill'. It's a simple task to see if they are well versed enough in Go to get started. And no the question isn't 'convert a number to a string', it's a small function tasked with doing something along those lines. I don't get why you feel that's insulting. If I were applying for a job speaking French, was asked to translate a simple sentence, and couldn't...I wouldn't expect to be…
Just hire a few people part time and the one(s) that can deliver offer full time roles.
Re: Why is recruiting developers so difficult?
#155Earlier quoted context omitted.
I'm from Canada. I make ~$100k/yr at the moment. It's considered a top 10% salary. I am content. Top 1% here is ~$200k/yr. It's a lot of money, but not a lot of money is needed frankly for the average Canadian. I don't think I'll ever reach $200k/yr+, so the $100k/yr I'm at I'm thankful for. Mind you, I'm not including housing. Housing in Vancouver in Toronto require I make more than $200k/yr which further solidifies…
The problem with housing in Toronto and Vancouver is that like many other commonwealth countries, Canada isn't particularly strict about shady foreign money entering the country and driving up asset prices (in fact, it seems they welcome it). This is similar to why London real estate is off the charts expensive for the people who live there... this still happens in the US, but it seems like a smaller deal relative to…
The silver lining here is remote work. Both Vancouver and Toronto are in dire need of a physical brain drain. Allow remote workers to work from across Canada. The demand for in-city workers will lower and home prices will fall
Re: Why is recruiting developers so difficult?
#156Earlier quoted context omitted.
No worries.
Your tone speaks dividends about how you view programmers. Often when you ask why something is hard then you’re the problem, not them. Edit: FYI. The OP changed their initial reply from the condescending combative response to that below.
Re: Why is recruiting developers so difficult?
#157Earlier quoted context omitted.
No worries. Sounds like we wouldn't want you anyways if you have such poor work ethic.
There are plenty of fish in the sea....
Re: Why is recruiting developers so difficult?
#158Earlier quoted context omitted.
No worries.
Your tone speaks dividends about how you view programmers. Often when you ask why something is hard then you’re the problem, not them. Edit: FYI. The OP changed their initial reply from the condescending combative response to that below.
Re: Why is recruiting developers so difficult?
#159Earlier quoted context omitted.
So if I asked you to do to a 1-2 hour coding task, you'd only do it if I were on a zoom call with you while you did it?
Yup! The interviewer can see my thought process. I can also evaluate my peers and ask questions about the work. The interviewer can also see how easy or cumbersome it is to set up the environment and code in the allotted time. Win-win.
Re: Why is recruiting developers so difficult?
#160Earlier quoted context omitted.
I've never been asked to do a take home interview assignment, but I actually have the opposite attitude. I would much rather spend a few hours putting together that I feel good about than spend 10x the time cramming interview prep.
Or, you know, you don't cram for the interview and just do as well as you can and let them evaluate on that. If you give me a meaningless take-home assignment, I have to actually write working code for it that looks good. If there's a trivial problem in an in-person interview, I can often "blah blah blah" through the more rote parts unless they really ask for details. There's no wiggle room on a take-home. The code y…
Sure, depends how much you want the job and what your general approach is. If it's a competitive job then you want to optimize for the interviews. Last time I interviewed, the potential impact on my income and net worth over the next decade was significant, so I took it pretty seriously.