3 May, 2009

Skills that make a good developer

Posted by Bhavin Turakhia | (3) Comments

Joel Spolsky captures the essence of a good (read: recruitment material) developer in his succint mantra – “Smart and Gets Things Done“. My own personal part-plagiarised part-modified version has always been – “Smart, Takes Initiative, Gets things done, Paranoid about Perfection and is a Nice Person”. I believe Joel’s shorter version does not capture all these aspects – for instance being Nice and being Smart are mutually exclusive.

Both versions (mine and Joel’s), in their brevity, have a quotable-charm, but fail to provide a more detailed perspective. As a parallel effort, I wanted to list down, in micro-detail, a significantly more extensive document, of skills that I find good developers possess.

The current work-in-progress version of it has been put up at - What skills doth a good developer possess? within our Wiki. Granted that all developers at Directi do not possess all the skills listed. However the document serves as a “skills-to-acquire” list for our existing team, as well as a reference list for aspiring applicants. As someone who wants to join our organization, you should have several of these mastered, and be prepared to tackle the rest.

Excerpt from the document - What skills doth a good developer possess?

  • Algorithmic skills
    • Understand and dissect complex problems quickly
    • Understand trade-offs between space / time complexity
    • Come up with solutions with minimal space / time complexity
    • … <snip>
  • Data Structures
    • Basic Knowledge of data structures – Hashmaps, Binary tree, B-Tree, B+Tree, Linked Lists etc
    • Understanding of trade-offs between various data structures etc
    • … <snip>
  • RDBMS
  • Caching
  • Networking
  • … <snip>

For further details visit the complete document - What skills doth a good developer possess?

To apply for a tech position at Directi visit our Careers Portal

Category : 0-cosmos | Directi

24 Sep, 2008

Time and Resources Analysis of a Recruitment Exercise

Posted by Bhavin Turakhia | (1) Comments

I got around to thinking about the amount of effort that goes behind a recruitment exercise at Directi and I thought to pen down an article which details out a recruitment scenario and the effort / resources involved. The purpose to pen this down was to get an idea of the time, cost and people involvement per candidate. This in turn will enable us to -

  1. Set expectations in terms of targets of the number of interviews one can conduct per week
  2. Determine direct cost of an interview process
  3. Determine the opportunity cost of an interview process
  4. Improvise our recruitment process and make it more efficient

The article turned out to be a 1600+ word count multi-page article which I have posted on our Directi Wiki under the Recruitment University

Anyone involved in recruitment should read it. The article is available at – http://wiki.directi.com/x/TwDK

PS: If you wish to apply for a job at Directi, visit our careers portal at http://careers.directi.com

Category : Directi | Random Musings