Hiring a person for your team is the single most important decision you can make. It has long-lasting impact, whether you are the manager or a team member. Would you like to learn to hire great people? Not sure how? You need this book. Great geeks are not the same as skill-based staff. You need to analyze your culture, determine your problems, define the essentials you need in a candidate, and then you’re off and running. Great geeks adapt their knowledge to your context. One developer or technical manager is not interchangeable with another. Hiring Geeks That Fit takes the guesswork and cost out of hiring.

This is the digital version of the printed book (Copyright © 2004). Proven Methods for Attracting, Interviewing, and Hiring Technical Workers Good technical people are the foundation on which successful high technology organizations are built. Establishing a good process for hiring such workers is essential. Unfortunately, the generic methods so often used for hiring skill-based staff, who can apply standardized methods to almost any situation, are of little use to those charged with the task of hiring technical people. Unlike skill-based workers, technical people typically do not have access to cookie-cutter solutions to their problems. They need to adapt to any situation that arises, using their knowledge in new and creative ways to solve the problem at hand. As a result, one developer, tester, or technical manager is not interchangeable with another. This makes hiring technical people one of the most critical and difficult processes a technical manager can undertake. Hiring the Best Knowledge Workers, Techies & Nerds: The Secrets & Science of Hiring Technical People takes the guesswork out of hiring and diminishes the risk of costly hiring mistakes. With the aid of step-by-step descriptions and detailed examples, you'll learn how to write a concise, targeted job description source candidates develop ads for mixed media review résumés quickly to determine Yes, No, or Maybe candidates develop intelligent, nondiscriminatory, interview techniques create fool-proof phone-screens check references with a view to reading between the lines extend an offer that will attract a win-win acceptance or tender a gentle-but-decisive rejection and more An effective hiring process is crucial to saving an organization the costs and consequences of a bad hiring decision. Not only is a bad hire costly in terms of recruiting expenses and the time spent hiring, it can also bog down or derail projects that may already be running late. You, your team, and your organization will live with the long-term consequences of your hiring decision. Investing time in developing a hiring strategy will shorten your decision time and the ramp-up time needed for each new hire. Technical leaders, project and program managers, and anyone putting together a team of technical workers will greatly benefit from this book.

The Geek Gap is thoroughly original, virtually unique, of paramount importance and, on top of ALL that, a 'great read.' Bill Pfleging and Minda Zetlin deserve a giant 'Hats off' for this wonderful piece of work. --Tom PetersBusiness managers (suits) and technology professionals (geeks) have become warring camps in too many companies. While both groups have no trouble following the lingo of their own specialties, when they have to communicate with each other, neither side fully understands-or wants to understand-the other. And that's a big problem in an increasingly technology-dependent business environment where success depends on the smooth integration of both business savvy and technological expertise.Bill Pfleging-a respected computer and Web consultant-and Minda Zetlin-a veteran business writer-explore, in this insightful, witty, and very instructive book, the culture clash that pervades nearly every business-technology interaction. The Geek Gap provides members of both camps a practical guide to working together effectively. Using many real-world examples, the authors vividly illustrate the consequences in time, money, careers, and even lives when these separate cultures fail to communicate. By far the most serious example was the Challenger space shuttle disaster, which was likely the direct result of an internal clash and lack of communication between NASA's managers and engineers.The authors provide practical solutions for building trust between business and computer professionals. The book is filled with tips aimed at geeks and suits to help each group understand the other, communicate in what amounts to a foreign language, and get what they need to do their jobs effectively. The authors profile companies and individual executives who have successfully bridged the gap by conducting events that bring the two groups together, switching jobs from one area to the other, creating whole new careers as go-betweens, and much, much more.This is the first book to directly address issues of communication and understanding between business and technology people. The Geek Gap-in identifying this problem and providing numerous practical and workable solutions-is an indispensable guide for all.Bill Pfleging (Woodstock, NY) is a computer and Web consultant who writes a regular technology column for the Woodstock Times. With computer experience going back to the early 1970s at IBM, he has also worked for Tripod.com and Lycos Network.Minda Zetlin (Woodstock, NY) is a longtime business writer whose work has appeared in Crain's New York Business, Success!, Management Review, and other publications. She is also the author of Telecommuting for Dummies and co-author of The ASJA Guide to Freelance Writing.

Distributed agile teams have a terrible reputation. They don’t deliver “on time,” and too often, they don’t deliver what the customer needs. However, most agile teams, have at least one remote team member. And, agile approaches are here to stay. Don’t blindly apply agile practices designed for collocated teams. Instead, learn to use three mindset shifts and the agile and lean principles to create your successful distributed agile team. Use the tips and traps to help your team succeed. Leave the chaos of virtual teams behind. See how to help your distributed team succeed.

In the course of their 20+-year engineering careers, authors Brian Fitzpatrick and Ben Collins-Sussman have picked up a treasure trove of wisdom and anecdotes about how successful teams work together. Their conclusion? Even among people who have spent decades learning the technical side of their jobs, most haven’t really focused on the human component. Learning to collaborate is just as important to success. If you invest in the "soft skills" of your job, you can have a much greater impact for the same amount of effort. The authors share their insights on how to lead a team effectively, navigate an organization, and build a healthy relationship with the users of your software. This is valuable information from two respected software engineers whose popular series of talks—including "Working with Poisonous People"—has attracted hundreds of thousands of followers.

Are you a technical person, such as a software developer, tester, writer, or project manager? You know that a job search is tough. You have to network, online and in person. You have to customize your resume for each job, so you can showcase your talent. You have to look for a culture that fits you. How do you start? Treat your job hunt like the project it is. Use agile and lean project management approaches that allow you to create a visual system. You'll increase your productivity, track your progress, evaluate your work, gain feedback, and throw out what doesn't work while building on your successes. Learn from your past career to optimize for your next step. Full of tips, stories, and humor, you'll apply practical techniques to take control of the most important project you'll ever work on: find your next best job.

It’s been said that software is eating the planet. The modern economy—the world itself—relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it’s ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it’s an emboldening, specific vision of what software development looks like in the world of developer hegemony—one where developers band together into partner firms of “efficiencers,” finally able to command the pay, respect, and freedom that’s earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that’s rightfully yours. It’s time for developer hegemony.