I'm of the opinion that if there needs to be some objective technical challenge to determine a baseline of competency (and there are very many, very strong arguments for that) then there need to be standards. I've encountered so many variables (no pun intended) in technical interviews that I've virtually stopped preparing. There's hardly any way to prepare when the field is so large and you never really know what you…
I interview a lot of people for frontend positions. I ask one two-sum question to see if they have some knowledge about data structures and simple algorithms. Then I ask them to build something trivial in React, which is what we use. If you can do those things, you're probably fine. The number of people who can't is truly shocking.
I don’t have time for coding challenges
51–60 of 243 posts
Re: I don’t have time for coding challenges
#52And nothing gives more open ended reasons than the coding test.
Re: I don’t have time for coding challenges
#53I agree that code challenges aren't ideal. But we've been struggling with parsing resumes and titles to identify the competency of developers. Our current coding challenge isn't super hard and based on the type of code you'd see in our product. It asks you to read a simple javascript function, explain it, and then implement new functionality that can built by refactoring the existing method. It's about 20 lines of co…
For advanced roles I'd suggest separating out the evaluation of coding ability from the evaluation of a particular language. Let the candidate pick their language when you want to test how well they can write new code, and then do a separate evaluation of how deep they are on the language and technical stack you are using.
That being said i'd be curious how you evaluate general software engineering ability (e.g. writing clean abstractions, decomposing monolithic methods, and general design). I feel most system design evaluations are a bit too high level or overly broad (e.g. design a library application or make a social network) and coding challenge are too low level.
Re: I don’t have time for coding challenges
#54I happen to prefer take-home challenges more than any of the alternatives. It’s much less stressful than any live assessment. And I have the time.
But I understand people that hate it. You evaluate the candidate how they think they are best evaluated. And I don’t think it is that much more trouble or time investment by the company.
Re: I don’t have time for coding challenges
#55Company 1:
1 hour HR interview
Coding task spend about 4 hours on it, at first i implemented basic but correct implementation, no OOD & design patters or anything fancy. They said i should redo it but with SOLID OOD and design patterns + unit tests, so i threw in the most convoluted code i could think of for a console app. That did the job and got to the next part.
3 hour technical interview, ~2 hours of HR talk & getting to know me, then a set of 5 algorithms tasks. I failed at some point, as i'm not fan of algorithms tasks and i don't have CS education, so my algorithms knowledge isn't strong.
Result : Not qualified enough no offer
Company 2:
1 hour HR interview
After which they sent me a task that would have taken me about 8-10 hours to do. I politely Declined.
Company 3: 1 HR interview 2 x 1hr technical interviews,
First technical interview : extend a very very simple code (2-3 classes) with couple of functionalities and write tests. All in all it took an hour and was pretty straightforward. With no hidden gotchas
Second technical interview : you are given task details, and have 20 minutes to come up with overall system design. after which we spend about 30 minutes going trough that and asking why i choose X or Y, or what if the requirements changed to X or Y.
then 1 hour final "culture fit" interview. Result: waiting for offer.
Company 4: 2 x 1 hour interviews with the CTO & CEO. Tech talk mostly, but no deep algo questions. What challenges I've had and how I've solved them. Result : waiting for offer.
Company 5: one 1 hour HR interview, and i have to do a 5 hours long fixed time (i.e. they sent tasks at 12:00 i have to be done by 5 and send results).
And i'm debating if i should do it at all.
I've had the most pleasant experience with companies 3 & 4. From their HR staff to their Interviewers.
About about me for context: I'm a backend/full stack engineer with about 10 years of experience. I've coded professionally in PHP, C# and JavaScript. I've led few interviews, but never used spend-a-day-doing-it code challenges.
Re: I don’t have time for coding challenges
#56I don't want to work with people who are good at bullshitting their way through interviews, but can't actually write code.
Re: I don’t have time for coding challenges
#57Earlier quoted context omitted.
That's why people do it, no doubt. Keep in mind, a lot of these questions are asked by vastly less desirable companies that ape the hiring practices of FAANG, even though they pay much less. And these companies complain bitterly about a shortage of good developers to hire. So... I'm all onboard with your statement, but I think you only said half of it. Nobody owes me a job, and if I don't like it, I'm free to not get…
Do only those companies complain about a shortage of candidates? Because in the tech centers I know, the market is just empty. Lots of large companies are competing for talent, and if you can't pay bank salaries, you're going to have a hard time. You make it sound like there's plenty of talent around but companies are being snobbish. That's not my experience at all in Germany.
Re: I don’t have time for coding challenges
#58I'm of the opinion that if there needs to be some objective technical challenge to determine a baseline of competency (and there are very many, very strong arguments for that) then there need to be standards. I've encountered so many variables (no pun intended) in technical interviews that I've virtually stopped preparing. There's hardly any way to prepare when the field is so large and you never really know what you…
I interview a lot of people for frontend positions. I ask one two-sum question to see if they have some knowledge about data structures and simple algorithms. Then I ask them to build something trivial in React, which is what we use. If you can do those things, you're probably fine. The number of people who can't is truly shocking.
Re: I don’t have time for coding challenges
#59Then, don't. I want to move from my 2000 USD a month (this is a good salary already) in a 3rd world country to a FAANG that pays 20k USD per month. I'm willing to go through any challenge because the reward is superb for me. Not to mention, without objective interview questions, an introverted non-native English speaker (who doesn't speak latin-germanic-based language) like me would fail most of these subjective ques…
It comes up with questions that are as simple as "Create a function that deduplicates an array of integers"
Re: I don’t have time for coding challenges
#60Then, don't. I want to move from my 2000 USD a month (this is a good salary already) in a 3rd world country to a FAANG that pays 20k USD per month. I'm willing to go through any challenge because the reward is superb for me. Not to mention, without objective interview questions, an introverted non-native English speaker (who doesn't speak latin-germanic-based language) like me would fail most of these subjective ques…
I don't know of any software company that would hire an introverted person who can't articulate themselves for 20k a month. This is how micro-service architected fully optimized solutions that solve the wrong problem happen. Do you really think the high value of a developer just comes from being able to pass coding challenges when there's millions of them out there?
1. Speaking perfect English, both fluently and without a heavy accent.
2. Talking about technical topics or other shibboleths with the same cultural affect an American would, as opposed to a foreigner. For example, many Indians will call a phone screen a "telephonic interview", and I've personally seen Americans react poorly to that.
I know lots of developers who are very well paid and very effective in their jobs, but they don't speak English as well as an American and would stumble at certain cultural nuances.