All companies appear to be grappling with their approach to diversity and inclusion in the organization. Many have appointed Chief Diversity Officers. However, when you appoint a Chief Anything Officer, you decline responsibility for that thing yourself. I’ve seen this in Quality, Excellence, you name it. When you name a Chief <something> Officer, you no […]
I started this series positing that respect is the cornerstone for how we might treat each other, to manage our interactions with success, especially in light of the #MeToo conversation. The series so far is: Organizations Are Not Families, Part 1. Why the metaphor of family-as-org demeans the people working there. Build Respect in Organizations,
You may think the #MeToo tag doesn’t have anything to do with product development. Not so fast. When people behave badly (more often it’s men than women, but it can be either), the people suffer. When the people suffer, the product suffers. It suffers in development and it suffers in release. The issue is this:
Yegor Bugayenko asked me to be a guest on his podcast to talk about Hiring Geeks That Fit. I gladly accepted and the podcast is now up: Shift-M/10. We spoke about many issues in hiring: Laundry list/shopping list problem in job descriptions Starting with a “test” or a phone screen (I need to write a post
I keep hearing about the “Skills gap.” There is no skills gap. There is a gap between what employers want to pay and what people are willing to work for. I read an article this morning that prompted this post: Talk of a skills gap in the labor market is ‘an incredible cop out’ Let
In The One Question You Should Ask About Every New Job, Grant says, Ask people to tell you a story about something that happened at their organization but wouldn’t elsewhere. There are four categories of stories: The human-ness of senior management (or not) Promotion opportunities for anyone How the organization fires/lays off The consequences for
I’m a big fan of auditions in an interview. (I have many posts about auditions in this blog.) However, some hiring managers and teams push interviewing and auditions too far. When you’ve had three interviews, and your interviewer asks you to solve a problem for them—again—is it a hiring issue, or are they asking you
I retweeted a link to Here’s a Thing: There’s No Correlation Between a College Degree and Coding Ability. I was a bit surprised by some of the reactions to that link. One colleague said, “I question whether people who wait until a college assignment to learn to code have the same obsessive interest in the topic.”
Have you seen Nick Korbel’s series about hiring techies? See On Hiring Techies. There are several posts: Evaluate Potential, Not Accomplishments. He’s talking about evaluating qualities, preferences, and non-technical skills. Coding Challenge: A pre-interview audition. The cool thing is that they then discuss the audition in the interview. The Team Interview. I dislike panel interviews.
If you are like many hiring managers I know, you don’t like to write job ads. You find them boring to write. When they are boring to write, many candidates find them boring to read. You don’t have to make your ads boring. Have you read Pradeep Soundararajan’s ad for his VP? Here is his