Why startups are relying on "running" a program rather interviewer judgement on collabedit? Expectation of writing a bug free running code in 30 mins seems too much to ask..
I'm not hiring you to write psuedocode
Code that cannot run is useless
If interviewers expect code than thinking process, you may as well cheat by having one tab open and search the web or leetcode. Coding question was never intended for optimal solution in given time or running a bug free code. Rather it is a tool to evaluate thought process, communication skills, knowledge, testing strategy and other tech skills. Today's interview turned into who practiced more competition as many brain dead leetcode worshiper interviewers have not even thought about why he is asking a coding question and for what and how he can be fooled by cheating.
It's good that only startups are doing that..no big ones...
When they ask u to code on coderpad they tend to give you easier question like string or simple dfs/bfs. Trust me it’s better than having to solve a DP question and not able to come up with the equation till the end😂
Nope.. I always prefer solving DP problem rather writing not so logical but lengthy code in 45 mins..
It’s just that the bar is so high nowadays so this is what they expect. Go to a competitive programming website and you will see college/high school kids who can code max flow/ segment tree/complex dp in 5 minutes bug free.
Coderpad is for pre-screening. We would tailor a set coding questions that were original enough that it'd be hard to "google the answer" fast enough, and so that the total test time was reasonable. With 1h, for a few coding puzzles and some general questions, we would expect an average candidate to at least finish all the coding, with a few mistakes. I remember that when I did the same set of questions as an interviewee, I went through all of them flawlessly in less than 20min (and I'm not some coding competition wiz, just an experienced professional software developer). But I always disabled the compiler in coderpad, because I would consider that a few typos aside, you should know if your code will compile just by looking at it, I certainly can and wouldn't hire someone who can't. So that's part of the interview too. Afterwards, in more substantial interviews, that's where the harder and more open-ended questions are asked and where we care not at all about compilable code and look more at people's thought process, attitude, problem solving skills and approach, and breadth of background. And if you are a coding competition guru, you will be sniffed out pretty quickly at that stage and you won't get far. Long story short, I would expect most decent programmers to have a pretty easy time through those coderpad questions. If you think it is too much to ask, maybe you just have to become better. After all, that's the point, we want to hire the best. If an interview process seems too hard, you might simply not be as close to the top as you might think.
I find coderpad exercises easier, since I get to work on a problem iteratively and test as I go. the trick is to not wait until you’re finished and hit run
Weak