Professional Documents
Culture Documents
Structure
Structure
After lunch, youll probably have another 3 technical interviews, followed by an interview with someone non-technical. The non-technical person might be our general counsel, or our head of HR, or our head of corporate communications. They arent going to ass ess your coding skills. Instead, they are going to try and assess your fit with the culture in a more formal manner. It doesnt matter how strong you are technically if you wont fit our culture, we wont move forward. Whenever I can, I will interview yo u at the end of the day (Ill ask a bunch of logic questions, by the way.) (Side note: Id like to meet every candidate. I try to manage my calendar to spend about a third of my time on hiring and interviewing. But I often fail. Room for improvement, I suppose!) About 30 minutes after youve left, everyone who interviewed you will all get back together. Each person has submitted (in advance) feedback on their interview with you, including a score from 1 to 4. We go around the table, getting everyones score s, and, based on the average and the general feedback, decide to make an offer or not. You will get a call back that night with our decision. How does this process match our culture? First, we are data driven we score people in a standardized fashion but we move quickly youll hear the same day. We try to measure your horsepower by seeing you react to questions more than the beauty of your code. We will look at you in semi-social situations to see if youre going to thrive in our culture. We also have a high reject rate, many of whom are likely great employees. But startups must be exceptionally careful to avoid the false positives bad employees can poison an entire team and are hard to shed. Avoiding them in the first place is the win. And you as a candidate should be comfortable with the culture of the company you might join; you shouldnt take an offer from a company that doesnt show you their culture, or shows you a bad culture. You will spend several years there, you should choose wisely. Good hiring is in everyones best interest. More companies should think about their process, what it shows about them, and how it selects new employees.
Forbes
to them more," said one ex-Yahoo!. "I had one good conversation with [one Yahoo! executive] and one good one with [another executive] in [the last few years]. That's it. I know others tried to educate them on the issues. Nothing came of it. One group that Yahoo! executives were not shy about consulting in the last four years: the consultants. "There were way too many consultants and too many planning sessions. We needed more execution," said a former employee." Tolerating a Non-Performance Culture: Over time, it appears most employees stopped pushing for the changes they wanted to see. When they tried and it fell on deaf ears, they backed down. "I think a lot of people also knew they wouldn't get similar jobs elsewhere and decided to keep quiet." The tone got set from the top, and it trickled down to permeate the organization. Matrix Organizational Structure: One of the recommendations that Yahoo!'s consultants made a few years ago was to institute a so-called matrix organizational structure across the company. A matrix structure seeks to overcome the complexity of a large global organization by assigning multiple bosses to employees in different geographies working on similar product or functional tasks. In other words, you report up to two or more bosses -- a product or functional boss and a geographical boss. They create confusion about who is responsible for certain actions. The "shared" ownership of tasks and projects across multiple groups and bosses means that it's difficult to go back and assign blame for and learn from failures.