How developers detect quacks when hiring other developers

Back when I was a full time freelancer, I would get two or three requests for design work. Mostly from referrals. I often got too busy and had to to help get the work done. The other day I heard a non dev doing an interview with a developer and I thought, wow, they just are not asking the right questions. So here you go, this is what I ask as a developer to my colleague  to detect if they are full of Bologna. The basic premise, if it walks like a duck quacks like a duck it is a duck!

  1. WHAT IS THE MOST SUCCESSFUL SITE THEY HAVE WORKED ON

    Remember that your developer is responsible for your success. They should take into account your budget and specs and make it happen. Bad developers will no successful sites in their portfolio because they are not subscribed to their clients success. By successful I mean a money making businesses. Just having a site is not enough. It actually must be successful business. Losers beget losers. Winner beget winners. Don’t hire a loser.

  2. DO THEY TALK ABOUT HOW GOOD THEY ARE?

    Good developers talk about cool projects and favorite websites. They talk about what is hot and what is not. If run into a dev that  blabs about how good they are then run. Any developer who feels they need to convince you of their greatness has issues. Like, insecurity over crappy skills issues.

  3. ARE THEY AVAILABLE REGULARLY AT THE SAME TIME EVERY DAY

    Professionals are available and online. They need to be reachable and responsible. If devs are flaky about meetings and availability, their code will be flaky too. Code always reflects a developer's personality.

  4. THE SPEED IN WHICH THEY PROVIDE THEIR REFERENCES

    If a developer does not have references ready to go, or at least be able to deliver you references in less than 30 minutes then run. Professional developers that rock have tons and tons of happy customers that will vouch for them at the drop of a hat. If they need day or so to conjure some buddies to give you a reference, then run!

  5. ASK WHAT KIND OF PLANNING PROCESS THEY DO

    ALL professional developers will go through a planning phase. If they ask you for an email of specs and start pounding keys, tell them your mom got sick and you need your money back. 100% the better the dev, the better they plan

  6. ASK WHAT ARE THEIR TOP FAVOURITE PROJECTS REGARDING YOUR TECHNOLOGIES

    There are so many hacks that learn a little php and just start building sites. Remember that the development  universe is filled with really cool projects. Things like buttons that change colour and fade away. Ways to push messages onto a page. Or scrolling pagers in ajax. There are literally thousands of these things out there. All professional devs research and try these things out. They should have several that they love and follow. They should know what is on the cutting edge. Things like 3d css. If they don’t they suck.

Related Stories

Leave a comment

Alternatively

This will only be used to quickly provide signup information and will not allow us to post to your account or appear on your timeline.