Skip to main content

DevIntersection 2014 – Interviewing developers

At the moment I’m in Las Vegas attending DevIntersection. Next to all the technical sessions, there was a whole track dedicated to leadership.

InterviewInProgress

One of the sessions in the Leadership track was ‘Interviewing Developers’ by Billy Hollis. Here are some of the notes I made during the session:

  • Keep a professional attitude.
    • You are here to find the perfect match for your team not to get new friends.
    • Don’t try to become friends with the candidate. If you hire him (or her) you get time enough to get acquainted.
  • It’s a good idea to ask the candidate to send some code up front. This should not be a whole project but just some files the developer can share.
    • Unfortunately some developers work on proprietary projects and cannot provide any code.
  • Do a review of the application letter.
    • Chances are high that the candidate did write this letter himself, which could not be the case for his CV.
    • Don’t be merciful on spelling mistakes!
  • Do a full analysis of the CV.
    • Especially look at the project length and the time they stayed at the same customer(longer is better)
  • Listen to your first impression.
    • But don’t listen too much. :-)
  • Keep a neutral tone and posture during the interview.
    • People try to read your body language and change their answer accordingly.
  • Be aware for defensiveness
    • Development is a trial-and-error process. Making mistakes is part of our job. Look how the candidate handles mistakes and can learn from them.
  • Don’t make too much notes during the interview.
    • It distracts the candidate.
  • Ask open ended questions.
  • Avoid telephone interviews.
    • If it is not possible to see the candidate in person, use Skype(or a similar tool).
  • An interview should not take too long(not more than one hour).
    • After one hour, nature kicks in and the candidate will probably need to use the bathroom :-)

Billy also gave a whole list of sample questions which he asked not to share. So I will not add them here. If you want to know these questions, apply for a job at my company ;-)

Remark: Billy mentioned that he will probably create a Pluralsight course based on this talk, so watch out for it…

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more