91–100 of 223 posts
Charge a little to filter out people that clicked, but don't care. I'd pay.
Earlier quoted context omitted.
After the second interview I had an entire email written out that I was going to send to their lead, but honestly, given that the app that they asked me to develop prior to the interview was well done, detailed, commented and modern, complete with a PR flow that me and one of their devs went through via GitHub, I felt that if they were willing to pass due to me obviously locking up on a Skype + Google-Doc shared whit…
For those interviewers and candidates looking for a better solution than the "google doc shared whiteboard" - I suggest checking out a product I make: https://coderpad.io/ You can think of it as a much higher fidelity Stypi, Etherpad, Collabedit, etc, except that you can run the code in the browser as you write it . It really helps alleviate the choking sensation of being asked to write out an entire problem on a whi…
Earlier quoted context omitted.
After the second interview I had an entire email written out that I was going to send to their lead, but honestly, given that the app that they asked me to develop prior to the interview was well done, detailed, commented and modern, complete with a PR flow that me and one of their devs went through via GitHub, I felt that if they were willing to pass due to me obviously locking up on a Skype + Google-Doc shared whit…
"I felt that if they were willing to pass due to me obviously locking up on a Skype + Google-Doc shared whiteboard, and on the most basic of JavaScript skills (which were clearly elaborated upon within the project)" Or it could be a simple miscommunication, or they thought somebody else done the app given your performance on the interview. Reaching out and asking will cost you little compared to potential windfall.
Either way, I think you've nothing to lose by sending that mail/picking up the phone. Regardless of the doubts the interviewer may have in you post-interview they'll know that everybody is prone to a bad day every once in a while.
Good idea! It leapfrogs the scores of existing "code interview practice tools" that give you a problem and a text editor and do some auto-validation on your answer by providing a human element. Something like this seems like a more relevant kind of practice. How does the business model here work? Are interviewers paid? Are you planning on eventually expanding into recruiting?
hey, good question. right now, interviewers aren't paid, but that may change. re business model, ultimately, i'd like to have this platform be something companies can use to find candidates rather than relying on proxies like pedigree (or resume, for that matter!).
Earlier quoted context omitted.
That is awesome. I like; "That problem has been solved so I'd Google it". Your answer is faster.
-In elementary school when you were learning to do algebra did you say... Chill, he said 'so'. i think he was just saying he looked up the answer but that persons answer was faster
Dear software professional: if you have been rejected because of a coding interview, don't feel bad or discouraged. It has little to do with how smart you are. Unfortunately, this style of interviews is likely ineffective and leads to hiring people who look alike and have similar skills. Solving a problem with someone looking over your shoulder and forcing you to talk to explain what you are thinking is a skill that…
The interviews I had with the company I work for now were amazing; they asked me some basic questions to verify my resume wasn't completely BS, then asked me to discuss previous projects I'd worked on, asking questions about technical details on the way. ("Why did you use collection type X in stead of collection type Y?") This allowed them to learn about my real world experience without the risk of asking me about one specific type of problem I may not be familiar with.
This is a very promising idea. I always crack when it comes to algorithm type question. I am aware of some of the run of the mill ones like, write a palindrome detector, bubble sort. However, I still can't figure out the crazy hard ones like: In a pyramid of numbers, write an algorithm to find the path to the biggest sum. Write a method to produce pascal's triangle. Given a grid, where X = wall, O = space, write an a…
Earlier quoted context omitted.
For me, even worse than an in person interview is a remote coding interview over the phone. Usually some sort of screen sharing + phone call. I find it incredibly nerve wracking because it gives me that feeling of someone standing over my shoulder without me being able to fully interact with them or read their body language. When you sit down to hammer out a solution you have all the additional pressure of trying to…
Worse, you simply have no way of knowing what their evaluation criteria are. Maybe they want you to be slow and thorough (I've been nailed for not checking the exit status of print statements). OR maybe they want it quick and dirty, in which case you'll get nailed for "overengineering", or you just wont have time to do it the imaginary time frames they set for these tasks, if you go for any of the defensive practices…