Sorin’s comment got me thinking. How do you make the decision that a candidate’s technical skills aren’t worth the candidate’s lack of relationship, communication, listening, or some other soft skill? Esther was talking about collaborative teams, so someone who won’t or can’t collaborate is not going to work in your environment. But there are […]
There are two kinds of domain expertise: solution-space and problem-space. When a candidate understands the technical issues behind how your product solves the customers’ problems, that’s solution-space domain expertise. When a candidate intimately understands the problems your product is trying to solve, that’s problem-space domain expertise. One kind of domain expertise does not imply the
In Michael’s comment to When Candidates and Interviewers Disagree About “The Answer” he raised a critically important point: how much does the the candidate know about this issue and how hard will the candidate push to make sure that the interviewer hears his or her side of the issue? First, let’s separate the two issues
Since there’s a (temporary in my mind) glut of candidates, some hiring managers are asking for specific industry expertise, such as: consumer product, enterprise-wide application, or web-content expertise. Unfortunately, that’s shorthand for what I believe people are really looking for: a specific mindset that meets the cultural requirements of the product development process. Here’s an
Originally published in Computerworld. If yours is like many other organizations, your hiring freeze has lifted—a little. Maybe you have one or two open requisitions now, or maybe you think you’ll have one in a month or so. That’s great. Now it’s time to think about what kind of person you require in your group.
I’ve been working on an article for about a year now, trying to discuss how to decisions about which kinds of testers to hire when. The only good thing about working on an article that long is that I’m finally learning how to describe what I mean (I think). I’d like your feedback on these
Uh oh. I’m seeing laundry list job descriptions. You know, the kind of job description that so carefully bounds the job with so much technical tool skill, that no one could fit the job. If your job descriptions are laundry lists of tool skill, reconsider how you’re describing the job. I like to think about
How do you differentiate true designers and architects from other software developers? This may be the hardest question to answer, and the most necessary. A real designer or architect, someone who doesn’t just hack a bunch of software together, is worth more to your company than you can pay him/her. A real designer or architect
© 2002 Johanna Rothman. This article was originally published in Software Development, October 2002. When hiring personnel, subject domain expertise, industry experience and software skills, combined with corporate culture simpatico, make for a well-rounded worker. by Johanna Rothman Jim, a hiring manager in search of a developer, is talking to Jane, a human resources recruiter: