Earlier quoted context omitted.
While I agree with you that theres a few like that, you have forgotten about the candidates that genuinely don't want to spend their spare time grinding leetcode. I worked at facebook, when I started looking for a new job, I had to start grinding leetcode again to prepare for a new job. Take a step back and realise how ridiculous this is. Big companies that have prestiege and pay alot of money use it to eliminate fal…
If you can't readily demonstrate ability to write a simple function but insist on getting hired as a developer you are, by definition, overestimating your ability as software developer, because you can't code. If you need to grind to be able to write code you are doing something wrong. Like spending too much time at work copying code from stack exchange or relying on running your code to tell you if it is correct.
If software engineering is in demand, why is it so hard to get a job?
521–530 of 586 posts
Re: If software engineering is in demand, why is it so hard to get a job?
#522Re: If software engineering is in demand, why is it so hard to get a job?
#523Earlier quoted context omitted.
If you can't readily demonstrate ability to write a simple function but insist on getting hired as a developer you are, by definition, overestimating your ability as software developer, because you can't code. If you need to grind to be able to write code you are doing something wrong. Like spending too much time at work copying code from stack exchange or relying on running your code to tell you if it is correct.
Grinding leetcode != software engineering. That is my entire point, not sure why you're confused.
Never had to "grind" to get any software development job I wanted even though I am always expected to demonstrate my coding ability.
Actually, I wouldn't let myself be hired by a company that does not verify if their candidates can code. Too much of a drag working with people who can't pull their weight.
Re: If software engineering is in demand, why is it so hard to get a job?
#524We made the interview process very simple and traditional in our current organisation. 30 minute chat, judge whether the person can do the job or is a good fit, if yes then offer a year contract with 1-3 months of evaluation period. Changing a job is risky also from the candidate's perspective so if the person is pretending, the lies will catch up. Most of the scenario it has worked pretty well. Sometimes, people who…
Can I get a job? I've been on multiple stages of interviews, of which, some are 2+ hours of coding and even if it seems promising and that everyone's happy... I still end up getting looked over. Even programs like returnships that are specifically for people who've been out of the game for 1+ year, despite showing them that I can code and architect software... I'm still kept waiting and don't get in. I feeling pretty…
Re: If software engineering is in demand, why is it so hard to get a job?
#525We made the interview process very simple and traditional in our current organisation. 30 minute chat, judge whether the person can do the job or is a good fit, if yes then offer a year contract with 1-3 months of evaluation period. Changing a job is risky also from the candidate's perspective so if the person is pretending, the lies will catch up. Most of the scenario it has worked pretty well. Sometimes, people who…
If I remember right, Google found something similar too. Everyone knows Google makes the candidates jumps through a lot of hoops to evaluate them and hire the "best and the brightest". But an internal study showed that apart from the really top talent (the rare few), all that technical knowledge doesn't matter much in the long run: > "Google originally set its hiring algorithms to sort for computer science students w…
Politics never goes away unless you're the only employee, but the ratio of politics to technical ability that defines success changes drastically the smaller the company.
Re: If software engineering is in demand, why is it so hard to get a job?
#526I think a lot of this is because our profession does not have an accepted universal bar everyone can jump over to be considered ‘qualified’. Every technical interview feels like rolling the dice in proving I am a competent developer. Giving me 50 minutes in a high pressure situation in an environment i am unfamiliar with and people I just meet will never product my best results, and then add to the fact that I could…
>our profession does not have an accepted universal bar everyone can jump over to be considered ‘qualified’. They even do this crap to people with CS degrees. If a 4 year CS degree isn't enough, then people who do this have no idea what they are doing. I started in this field in 1997. The interviews were more old fashioned, a few tech questions, see if you were an oddball, then they'd get back to you. If you didn't w…
Re: If software engineering is in demand, why is it so hard to get a job?
#527We made the interview process very simple and traditional in our current organisation. 30 minute chat, judge whether the person can do the job or is a good fit, if yes then offer a year contract with 1-3 months of evaluation period. Changing a job is risky also from the candidate's perspective so if the person is pretending, the lies will catch up. Most of the scenario it has worked pretty well. Sometimes, people who…
Re: If software engineering is in demand, why is it so hard to get a job?
#528Earlier quoted context omitted.
I did an interview with Reddit - whom I hope sees this comment - and they not only provided zero information about the context of the tech interview in advance, or whether it would be one, but also the interview itself was like playing a random version of tech Jeopardy, but without the category columns, and very few of the questions had anything to do with the job I would be doing. I have over 20 years of programming…
I have a not dissimilar background and what you describe is exactly what caused me to throw up my hands and leave the tech world. It's just not worth the BS.
Re: If software engineering is in demand, why is it so hard to get a job?
#529Earlier quoted context omitted.
Grinding leetcode != software engineering. That is my entire point, not sure why you're confused.
Why do you assume it is I who are confused? Never had to "grind" to get any software development job I wanted even though I am always expected to demonstrate my coding ability. Actually, I wouldn't let myself be hired by a company that does not verify if their candidates can code. Too much of a drag working with people who can't pull their weight.
Good for you. Either you are quite gifted or you're not talking about interviews in FAANG or other similar companies like Doordash, Instacart etc. but rather other "easier" SF startups.
I think you seem to be assuming two things: 1. Most interview questions are intuitive and one should be able to organically come to an efficient solution within 40 mins without any prior practice. 2. Anyone who can't do that, is not worthy of being a software engineer
In my experience, both those assertions are false. If you look at the difficulty of questions companies are asking, I can assure you that no reasonable software engineer (unless they do competitive programming as a hobby) would be able to solve them. On the other hand, even a mediocre engineer who has been "grinding" on Leetcode will have a far better chance on solving them since they have seen them before. In short your prep of interview
At this point, it appears to me that the companies know that Leetcode exists and that their questions end up there and they still ask the questions marked as "hard" since most serious candidates would have already prepared for the "medium" ones.
Re: If software engineering is in demand, why is it so hard to get a job?
#530I think a lot of this is because our profession does not have an accepted universal bar everyone can jump over to be considered ‘qualified’. Every technical interview feels like rolling the dice in proving I am a competent developer. Giving me 50 minutes in a high pressure situation in an environment i am unfamiliar with and people I just meet will never product my best results, and then add to the fact that I could…
The first time I interviewed at Google I didn’t make it past the phone screen. I bombed a question about an appropriate length of a Bloom filter because I hadn’t recently been thinking about Bloom filters, and I was summarily rejected for onsites. The second time I interviewed I was asked a number of questions that I was perfectly “primed” to answer. Because those were in my brain’s cache, I was able to get through t…
I've never even heard of a Bloom filter, so I know how I would have done.