Pramp - Live Coding Interview Practice. Roundcube Webmail 1.2.1 :: Welcome to Roundcube Webmail 1.2.1. Why Hiring is So Hard in Tech – JavaScript Scene – Medium. This problem is easy to spot on many coder resumes: Quick jumps from one job to the next with ever-more-impressive company names and job titles. Interviewing These don’t work: Puzzles and riddlesWhiteboard code testsBig O notation quizzesDetailed quizzes about the mystery corners of the language These work great (in order of value): Pair program with candidate on an actual issue from your ticket queue (let the candidate drive)Code samples / OSS contributionsPAID Sample project assignment (err on the side of paying fairly — say $100+/hour for estimated completion time — if the problem should require 2 hours to complete, offer $200)Review past work / portfolioRead candidate blog, publications, watch candidate talksAsk candidate for input on a real problem you’re currently working onAsk specific questions about software problems and solutions from candidate’s resume Startups are miserable at interviewing candidates.
None of those strategies work. Assessing Employee Performance – JavaScript Scene – Medium. Talk to your employees frequently, but assess their performance annually in order to give their contributions time to produce value. The more experience your employee has, the longer you should allow for their contributions to be assessed. Why? Your best employees may take days or weeks to contribute code to your application, and that’s OK. They’re making long term investments that will significantly impact your company’s bottom line. They’re making the decisions that will spell the difference between $1 million dollars per year in profit, or $10 million dollars per year in profit. If you use in-house software to make money (why else would you hire developers?) For example, I once stopped contributing any code to an app for a whole week in order to conduct a usability study.
I discovered our shopping cart abandonment rate was much higher than expected. I then brought inexperienced users into the office and asked them to browse our products and use our shopping cart. Troy Hunt: Offshoring roulette: lessons from outsourcing to India, China and the Philippines. I've had this blog post in one form or another of draft for several years now. I hesitated to complete it, in part because at the best of times cultural observations can easily be misinterpreted and also in part because of the role I had in working with many outsourcing vendors across Asia. Whilst the former hesitation has in no way changed, the latter has and I think it's a genuinely interesting topic worth sharing, particularly before my outsourcing memories fade too far.
One thing before I begin: these are opinions based on personal observations. I'll qualify them wherever possible and articulate my experiences as far as I can but they remain just that - my experiences. I'll also be as culturally sensitive as I can but ultimately I'm still going to comment on cultural traits. It'll resonate with some people and it will upset others but I hope that amongst all that, there's some genuinely valuable insights. Who am I to talk about offshoring / outsourcing / other cultures? Why outsource? The One Method I’ve Used to Eliminate Bad Tech Hires - Mattermark.
Let’s be real. Interviews are a terrible way to hire tech candidates. Not only do you not get a real sense of the candidate, they often weed out good candidates in favor of bad ones. In this fantastic article on Medium by Eric Elliott, he talks about many of the techniques that work and don’t work for interviewing engineers. In regards to what works the best, I found that these 2 ideas work the best when combined. PAID Sample project assignment (err on the side of paying fairly — say $100+/hour for estimated completion time — if the problem should require 2 hours to complete, offer $200)Bring the candidate in and discuss the solution. Let the candidate talk about their design decisions, challenge them as you would any team member and let them provide their reasoning.
Paying candidates to work on a simple project and then discussing it with our team has almost single handedly eliminated any bad hiring decisions. Here’s why paying candidates to solve problems works For the Employer In Summary.