It doesn’t matter what kind of paper your resume is printed on. It does matter how your resume looks to potential employers. Here’s a little checklist to make sure you’re presenting yourself in the best light: Is your experience in reverse chronological order? It’s too hard to quickly read a resume in any other way.
You’re hiring someone. You don’t want to waste your time in the interview. So, if you want to ask good interview questions, ask people about how they’ve worked in the past. People repeat perceived successful behaviors (whether those behaviors were successful or not). Behavior-description questions elicit the candidate’s story of how they worked in the
I seem to have a vision theme happening this week 🙂 How many kinds of review do you perform on your project’s work products? Especially with software projects, it makes sense to review interim work products, so you have some idea about how good the final product could be. Sometimes when I ask project
Once you’ve worked for 10 years or more, it’s worthwhile creating a one-paragraph summary of your experience. It’s not easy to create that paragraph, and it’s necessary, so that you can grab and retain the hiring manager’s attention. So what’s a one-paragraph summary? Here are some: A proven track record of improving business processes through
I was working on a newsletter article about how to see your project’s progress, and got stuck. It’s easier to see project progress on a project with a tangible deliverable; it’s much harder for software or a service project. So, I took a break and read Esther Derby’s blog entry, Start Seeing Software from
Sometimes, it’s not clear that you should fund or staff a project. If you’re not sure how to discriminate between alternative projects, here are four questions to ask: What’s the strategic reason behind this project? (Does the strategic reason behind the project change the importance of the project?) How does this project fit into
“Just go network. You’ll find the people (or the job) you’re looking for.” Yeah. Right. Wouldn’t it be nice if it were that easy? If you’re like most technical managers (or technical people looking for a job), networking is not one of your innate skills. Here are some suggestions to help you network: Attend local
You know you’re supposed to keep your resume to two pages. But you’ve been working for 20+ years, and you have lots of great experience. Instead of pages and pages of the chronological resume, think about the kinds of things you’ve done in your work. Have you rescued projects? Have you facilitated strategic planning? Have
I’m facilitating a roundtable, Test Management 101, on Stickyminds, and someone just posted a question about how to measure testers to show return on investment: measuring the number of defects they find. Ouch. When you measure developers on the number of lines of code, or testers on the number of defects, or carpenters on
Fred Brooks, in his classic, “The Mythical Man-Month,” talks about a chief programmer team (chief programmer, and programmers of lesser hierarchy until you get to the peon). The chief programmer team works when one person can keep all the details about the product in their head. If you use several hierarchical teams of chief