In Hiring for an Agile Team: Who Do You Need?, I asked you to consider the kinds of people you were looking for. Yes, you might need developers or testers or BAs or writers. And, I suggested you think about T-shaped people, those folks who could do whatever it takes to move a feature forward. […]
This is the start of a 5-part series: Hiring for an agile team. Let’s assume you are trying to hire for your agile team. Let’s assume you are in a location where you have candidates to recruit, that there are people looking for jobs in your area. I’ll cover how to hire feature teams elsewhere
Have you read The STEM Crisis Is a Myth? It’s a fascinating article. Bob actually has data, as opposed to my anecdotal evidence, now and dating back to my article from 2001, Crisis? What Crisis? A Contrarian Perspective. (For those of you who don’t know the four letter acronym, STEM is Science, Technology, Engineering, and
I read Latest figures increase digital skills gap fears as marketers struggle to fill jobs. (Tip of the hat to John Sumser.) What’s the problem? What kinds of people are hiring managers looking for? “companies seek the ‘all-in-one’ marketing and technologically capable employee” Well, that’s the problem of too many essential skills. Look, it’s great
Have you read this New York Times article, In Head-Hunting, Big Data May Not Be Such a Big Deal? It’s an interview with Laszlo Bock, senior vice president of people operations at Google. There are several points that are critical for you to read: We looked at tens of thousands of interviews, and everyone who
I’m at the SHRM conference in Chicago this week, courtesy of Dice.com. I blog for them, and am working on an agile recruiting series. Watch for it, in the coming weeks. I read this piece, The War for STEM Talent is a Lie. I agree. Until we do all of these things: Hire the people
Did you read The Jobless Trap? In it, Paul Krugman asserts we are creating an underclass of long-term unemployed. This is what really stood out for me: This could happen because their work skills atrophy, but a more likely reason is that potential employers assume that something must be wrong with people who can’t find
If you have not gathered data about your hiring activities, consider doing so. I find it useful to see how well I’m doing. This is especially important if you can’t find people and you want to know why. For data about recruiting and selection, look at your different recruiting strategies, and for each strategy, record:
There’s a great article that George Dinwiddie pointed me to, If There’s a Gap, Blame It on the Employer. It’s a nice companion piece to John Sumser’s entire series, Skills Gap: The Series. Here’s what this means for people in technology: Hire based on how well people fit into your team. Yes, this is cultural
John Sumser is writing a series of articles about the hiring paradox on HR Examiner. Read the first one, The Hiring Paradox (Skills Gap 1). The gist is this: It takes more time to hire when you have more alternatives. And, boy oh boy, do employers have more alternatives right now. What I found fascinating