Compensation & Benefits

Saying ‘Not Right Now’ Instead Of ‘No’ to Pay Raise Requests

A design intern was offered a full-time position, but asked for more money. The company decided to not cave in to the request, but instead laid out a series of goals for the intern to prove himself. After 6 months, the intern had met those goals and was given the pay raise he had asked for. The company also learned that their cutting-edge and fast-paced environment helps them attract and retain junior employees.

Hiring Rapidly and Time Efficiently

This article outlines the steps taken to rapidly hire engineers while maintaining quality. The author front-loaded the design, coordination, and preparation of the hiring funnel, set up hiring teams, and treated the hiring process as a product. Three metrics were used to measure success: percentage of hires from referrals, time taken to make a decision, and face-to-face interviews to hire ratio. The author also reduced the interviewing process to four hours and in one session. Lessons learned include the importance of treating the hiring process as a product, not letting quality fall to the wayside, and understanding that every hiring process is unique.

Turning a team around

When taking over a team of 60 engineers, the VP of Engineering noticed a lack of motivation and excellence. After observing interactions and having one-on-one conversations, it was determined that external factors such as a lack of purpose, goals, and challenges were causing the problem. To address this, modern tools were implemented, hiring practices were strengthened, job bands and compensation ranges were established, teams were reorganized, and the strongest people were put into influential positions. As a result, motivation and efficiency increased, and the team was better differentiated. Lessons learned include building relationships, ensuring a sense of purpose, challenging the team, and maximizing talent.

Convincing your executives to increase their hiring budget

This article discusses the challenge of hiring a full backend developer with at least five years of experience. The author had to convince their executives to increase the budget in order to hire a top-notch engineer, and they gathered data to demonstrate that a small budget would result in a loss for the company. They also compared their company's salary to the market price and found that they were offering much lower than the competition. After a month of convincing, the executives agreed to increase the budget, but the perfect candidate had already declined the offer. The author's advice is to bring a lot of data and present it in a way that executives will understand.

Creating and utilizing an engineering career path

A startup realized that their ad-hoc responses to career growth weren't enough and began researching career paths from other companies. After collecting a dozen paths, they created their own with six positions, four qualities per position, and one to three sentences per quality. They received feedback from their most experienced engineers and rolled out the path with a presentation. Lessons learned include understanding the problem, finding a starting point, avoiding "Not Invented Here," training managers and engineers, and working with HR.

How to manage the ego of a rockstar developer

A rockstar developer was exhibiting negative behavior in the team, such as not listening to other team members and being aggressive when defending his point of view. After investigating the root cause of his behavior, it was discovered that he felt unappreciated and needed to show everyone that he was the smartest person in the room. The manager took action by having a difficult conversation with him, praising him publicly and privately, and pushing for a reevaluation of his compensation. This simple solution was highly effective in fixing the problem.