Having previously worked at a place where it took minimum 3 months to hire someone (but often 6-12), I'd be amazed if Canonical actually ever gets to hire their first choices. What happened was this: By the time the first pick hires had been cleared, they had gotten another job. Same with second pick. Maybe even third, too. Most people don't have the luxury or will to just sit and twiddle their thumbs for months and…
Having done a lot of interviews for my company, I also agree. If your whole process takes more than 3 weeks, you are losing people to competitors. Candidates aren't going to wait 3 months and delaying all the other offers they are receiving, that's not going to work unless you are working in a FAANG maybe and the prestige of your company can make this work.
Canonical’s recruitment process is long and complex
211–220 of 460 posts
Re: Canonical’s recruitment process is long and complex
#212Earlier quoted context omitted.
C'mon, it was a casual joke and no harm done. Also punching someone weaker is a simple act, but taking on someone stronger requires courage. Does it fit the somewhat quirky (but by far not unusual) interview process? Yes Is it a sign of a moral flaw? No
Unless, of course, you work for that government. Kind of the same one that put people on the Moon, made the atomic bomb, invented the internet, and other things less extraordinary than repackaging Debian ;-) I have talked to him a couple times while working for Canonical and, while I knew his reputation of being a very Steve Jobs person, he was never an asshole with me. And the CEO was a real sweetheart. I'd think tw…
Re: Canonical’s recruitment process is long and complex
#213Earlier quoted context omitted.
Having done a lot of interviews for my company, I also agree. If your whole process takes more than 3 weeks, you are losing people to competitors. Candidates aren't going to wait 3 months and delaying all the other offers they are receiving, that's not going to work unless you are working in a FAANG maybe and the prestige of your company can make this work.
My current job was less than a week between my application and signing the final offer. Day 1: I send in an application. Day 2: My future manager writes back "Hey, do you have any work examples in obscure language I used for 10 minutes in my EE classes ?". I respond "No, nobody has work examples in obscure language ." Later that day, same manager emails me again, asking the same question, in slightly different words.…
Re: Canonical’s recruitment process is long and complex
#214(A bit off-topic, but to give another example of where convoluted hiring processes get you to...) Last year, I did 8 interviews (including 4 technical assessments and quizzes) to get an offer from AMD (in Germany) as a software engineer. For completeness, they reached out to me. I wasn't really looking at the time. When I got the offer, salary+bonus was less than what I had at the time (a lot less now) living in a si…
Re: Canonical’s recruitment process is long and complex
#215(A bit off-topic, but to give another example of where convoluted hiring processes get you to...) Last year, I did 8 interviews (including 4 technical assessments and quizzes) to get an offer from AMD (in Germany) as a software engineer. For completeness, they reached out to me. I wasn't really looking at the time. When I got the offer, salary+bonus was less than what I had at the time (a lot less now) living in a si…
Hardware companies simply don't pay as much as software companies in industry. I don't fully understand the reasons, because hardware is often more difficult to deal with than software. That said, I have found that there has been a rash of companies / recruiters reaching out to relatively senior people making offers that wouldn't have been acceptable a decade ago, much less in 2023. I recently had one reach out to me…
My theory is it comes down to the margins on software vs hardware products. If you look at software, in a certain sense, your unit margins are infinite - your variable costs are nothing(well, besides the literal bandwidth) to copy a piece of code and sell it to a second customer. With hardware, for every unit of your product, you have raw material cost, mfg, transport, etc. At scale, there's less $ to go around.
Re: Canonical’s recruitment process is long and complex
#216My mail contained 43 separate questions.
43. I am not joking, I just went and counted them. Each of which probably wanted a sentence to paragraph answer. Some could be more.
As Blaise Pascal said: If I had more time, I would have written a shorter letter. https://quoteinvestigator.com/2012/04/28/shorter-letter/
Write a shorter letter Canonical. You told me so much about you in one step. You can't write a short letter, or you don't care.
Re: Canonical’s recruitment process is long and complex
#217Having previously worked at a place where it took minimum 3 months to hire someone (but often 6-12), I'd be amazed if Canonical actually ever gets to hire their first choices. What happened was this: By the time the first pick hires had been cleared, they had gotten another job. Same with second pick. Maybe even third, too. Most people don't have the luxury or will to just sit and twiddle their thumbs for months and…
Well.. have you met their CEO?
The truth is once companies have a certain size and revenue, their software developers don't matter really that much. Yes it can be hell to work there, everyone is overworked, things are low quality, etc. As long as the checks keep coming in ( and they will ) there is really no critical problem to be addressed.
Now the funny part: once the alarm bells go off and they try to change course... not happens, the "ship" is unresponsive and in most cases it will sink. But depending on the size of the company that will take years and maybe even decades.
So the best skill everyone needs to have (I wish really technical introverted software developers had this more ) is: Develop "street smarts" and tell these people to go fuck themselves and shove their "hiring process" up their asses.
Re: Canonical’s recruitment process is long and complex
#218Earlier quoted context omitted.
Having done a lot of interviews for my company, I also agree. If your whole process takes more than 3 weeks, you are losing people to competitors. Candidates aren't going to wait 3 months and delaying all the other offers they are receiving, that's not going to work unless you are working in a FAANG maybe and the prestige of your company can make this work.
My current job was less than a week between my application and signing the final offer. Day 1: I send in an application. Day 2: My future manager writes back "Hey, do you have any work examples in obscure language I used for 10 minutes in my EE classes ?". I respond "No, nobody has work examples in obscure language ." Later that day, same manager emails me again, asking the same question, in slightly different words.…
Or was the manager just interested in trivia?
Re: Canonical’s recruitment process is long and complex
#219Having previously worked at a place where it took minimum 3 months to hire someone (but often 6-12), I'd be amazed if Canonical actually ever gets to hire their first choices. What happened was this: By the time the first pick hires had been cleared, they had gotten another job. Same with second pick. Maybe even third, too. Most people don't have the luxury or will to just sit and twiddle their thumbs for months and…
I am not sure I would stay motivated in another context.
Re: Canonical’s recruitment process is long and complex
#220Earlier quoted context omitted.
> interviewed me while having dinner (on his end) Wtf? Couldn’t he have done that at a more convenient time?
Doesn't seem that odd? I imagine he has a pretty busy schedule.