Who


Book Description

In this instant New York Times Bestseller, Geoff Smart and Randy Street provide a simple, practical, and effective solution to what The Economist calls “the single biggest problem in business today”: unsuccessful hiring. The average hiring mistake costs a company $1.5 million or more a year and countless wasted hours. This statistic becomes even more startling when you consider that the typical hiring success rate of managers is only 50 percent. The silver lining is that “who” problems are easily preventable. Based on more than 1,300 hours of interviews with more than 20 billionaires and 300 CEOs, Who presents Smart and Street’s A Method for Hiring. Refined through the largest research study of its kind ever undertaken, the A Method stresses fundamental elements that anyone can implement–and it has a 90 percent success rate. Whether you’re a member of a board of directors looking for a new CEO, the owner of a small business searching for the right people to make your company grow, or a parent in need of a new babysitter, it’s all about Who. Inside you’ll learn how to • avoid common “voodoo hiring” methods • define the outcomes you seek • generate a flow of A Players to your team–by implementing the #1 tactic used by successful businesspeople • ask the right interview questions to dramatically improve your ability to quickly distinguish an A Player from a B or C candidate • attract the person you want to hire, by emphasizing the points the candidate cares about most In business, you are who you hire. In Who, Geoff Smart and Randy Street offer simple, easy-to-follow steps that will put the right people in place for optimal success.




Interviewing & Hiring Software Performance Test Professionals


Book Description

I have been asked for years, where do you find high value software performance professionals. Most people, when they think of a software performance professional, immediately think of a tester. It is worthwhile to stop and consider what is the desired outcome of that effort. The answer will often determine the type of individual you need to solicit on the open market: An architect, an engineer, or a tester.This book is targeted at those who need to recruit, to interview, and to objectively evaluate the capabilities of different classes of performance professionals even if you do not have a mature performance testing team that can evaluate the candidate.You will gain insight into the foundational skills shared by high value performance professionals & how to interview for these skills.This book will save you from at least one bad hire.-James Pulley







System Design Interview - An Insider's Guide


Book Description

The system design interview is considered to be the most complex and most difficult technical job interview by many. Those questions are intimidating, but don't worry. It's just that nobody has taken the time to prepare you systematically. We take the time. We go slow. We draw lots of diagrams and use lots of examples. You'll learn step-by-step, one question at a time.Don't miss out.What's inside?- An insider's take on what interviewers really look for and why.- A 4-step framework for solving any system design interview question.- 16 real system design interview questions with detailed solutions.- 188 diagrams to visually explain how different systems work.




The Holloway Guide to Technical Recruiting and Hiring


Book Description

Learn how the best teams hire software engineers and fill technical roles. The Holloway Guide to Technical Recruiting and Hiring is the authoritative guide to growing software engineering teams effectively, written by and for hiring managers, recruiters, interviewers, and candidates. Hiring is rated as one of the biggest obstacles to growth by most CEOs. Hiring managers, recruiters, and interviewers all wrestle with how to source candidates, interview fairly and effectively, and ultimately motivate the right candidates to accept offers. Yet the process is costly, frustrating, and often stressful or unfair to candidates. Anyone who cares about building effective software teams will return to this book again and again. Inside, you'll find know-how from some of the most insightful and experienced leaders and practitioners—senior engineers, recruiters, entrepreneurs, and hiring managers—who’ve built teams from early-stage startups to thousand-person engineering organizations. The lead author of this guide, Ozzie Osman, previously led product engineering at Quora and teams at Google, and built (and sold) his own startup. Additional contributors include Aditya Agarwal, former CTO of Dropbox; Jennifer Kim, former head of diversity at Lever; veteran recruiters and startup founders Jose Guardado (founder of Build Talent and former Y Combinator) and Aline Lerner (CEO of Interviewing.io); and over a dozen others. Recruiting and hiring can be done well, in a way that has a positive impact on companies, employees, and every candidate. With the right foundations and practice, teams and candidates can approach a stressful and difficult process with knowledge and confidence. Ask your employer if you can expense this book—it's one of the highest-leverage investments they can make in your team.




Smart and Gets Things Done


Book Description

A "good" programmer can outproduce five, ten, and sometimes more run-of-the-mill programmers. The secret to success for any software company then is to hire the good programmers. But how to do that? In Joel on Hiring, Joel Spolsky draws from his experience both at Microsoft and running his own successful software company based in New York City. He writes humorously, but seriously about his methods for sorting resumes, for finding great candidates, and for interviewing, in person and by phone. Joel’s methods are not complex, but they do get to the heart of the matter: how to recognize a great developer when you see one.




The Minimum You Need to Know about Logic to Work in IT


Book Description

This book is part of aaThe Minimum You Need to Knowaa family of books by Logikal Solutions. As the family expands they will cover an increasing variety of topics. This book is designed to be used as a text book for classes in logic from high school to college level. It should be one of the first courses you have on IT and this should be one of the first books you read when starting in IT. Not only does this book cover flow charting and pseudocode, it teaches the reader to think before they start mapping out the logic to solve a problem. The author of this book is an industry veteran with nearly 20 years in the field. It has been his experience that recent graduates, from any country, are nearly useless at problem solving. If they cannot point, click, and drag, they cannot solve the problem. This book is an attempt to teach them how to solve the problem. An instructoraas guide is available for schools looking to make this book the basis of coursework.




Automated Software Testing


Book Description

A guide to the various tools, techniques, and methods available for automated testing of software under development. Using case studies of successful industry implementations, the book describes incorporation of automated testing into the development process. In particular, the authors focus on the Automated Test Lifecycle Methodology, a structured process for designing and executing testing that parallels the Rapid Application Development methodology commonly used. Annotation copyrighted by Book News, Inc., Portland, OR







Building Mobile Apps at Scale


Book Description

While there is a lot of appreciation for backend and distributed systems challenges, there tends to be less empathy for why mobile development is hard when done at scale. This book collects challenges engineers face when building iOS and Android apps at scale, and common ways to tackle these. By scale, we mean having numbers of users in the millions and being built by large engineering teams. For mobile engineers, this book is a blueprint for modern app engineering approaches. For non-mobile engineers and managers, it is a resource with which to build empathy and appreciation for the complexity of world-class mobile engineering. The book covers iOS and Android mobile app challenges on these dimensions: Challenges due to the unique nature of mobile applications compared to the web, and to the backend. App complexity challenges. How do you deal with increasingly complicated navigation patterns? What about non-deterministic event combinations? How do you localize across several languages, and how do you scale your automated and manual tests? Challenges due to large engineering teams. The larger the mobile team, the more challenging it becomes to ensure a consistent architecture. If your company builds multiple apps, how do you balance not rewriting everything from scratch while moving at a fast pace, over waiting on "centralized" teams? Cross-platform approaches. The tooling to build mobile apps keeps changing. New languages, frameworks, and approaches that all promise to address the pain points of mobile engineering keep appearing. But which approach should you choose? Flutter, React Native, Cordova? Native apps? Reuse business logic written in Kotlin, C#, C++ or other languages? What engineering approaches do "world-class" mobile engineering teams choose in non-functional aspects like code quality, compliance, privacy, compliance, or with experimentation, performance, or app size?