Developers Are Leaving Jobs to Escape Bad Codebase - DZone Agile

Recently, Stepsize surveyed 200+ software engineers from different industries to learn how codebase health impacts engineer hiring and retention.

In this article, I’ll share some of the key stats from the survey, why investing in a codebase is crucial for businesses, and questions you can ask in the interview as an engineer to learn about the company’s codebase health.

Our Findings

• 82% believe that lack of proper development practices affects their job satisfaction.
• 62% consider code quality as an important factor when choosing a new job.
• 51%of engineers left or considered leaving a job because of technical debt.
• For 21% of engineers, excessive amounts of technical debt have been the number one reason for changing a job.
• Both junior and senior developers equally consider codebase health to be an important factor when choosing a new job.

Today, hiring and retaining developers is one of the biggest challenges for tech companies. And while recruiters, hiring managers, and leaders are focusing on attracting new tech talent, they might be ignoring one of the biggest reasons they are losing them in the first place: codebase health.

Technical Debt Leads to Employee Turnover

More than half of the engineers surveyed (51%) have left a company or considered leaving a company due to large amounts of technical debt, and 20% of engineers say that technical debt is the primary reason for them to leave the company.

As discovered in one of our previous reports, technical debt has a huge impact on developer team morale, causing frustration and hindering innovation.

Given how much it costs to hire new engineers, companies need to keep their staff turnover as low as possible. And the best way to do that is to carefully manage technical debt to maintain a healthy codebase.

What Engineers Care About When Looking for a New Role

Salary, technical challenges, and remote work opportunities are the three most important factors that engineers pay attention to during their interview process.

Compensation and workplace flexibility is at the top of the list for engineers when they’re looking for a new job. But 62% admit that they also consider code quality as an important factor.

Code health or code quality refers to the characteristics of the code, such as clean, consistent, easy to understand, and testable. Engineers often feel pressure to sacrifice code quality to meet deadlines and ship features fast, which leads to frustration and decreases team morale.

“Code quality definition is very unique for each engineering team and product. However, every engineer wants to write code that is scalable, performant, reliable, and most of all easy to maintain for future engineers,” says Shamma Pathan, senior software engineer at LinkedIn.

9 Questions to Ask to Gauge Codebase Health

Unlike salary and remote work opportunities, understanding the state of the codebase and software development practices can be challenging.

Engineers suggest asking the following questions during the interview process:

• What are the complexity metrics, defect metrics, and coding standards of the codebase?
• What does the workflow before deployment look like?
• Do all projects for each tech stack have consistent and identical CI/CD pipelines?
• How is refactoring built into your development process?
• What does the code review process look like?
• Do you dedicate time to fixing technical debt?
• How do you balance building new functionality and resolving technical debt?
• How much time does the team spend on refactoring?
• What processes are set up to ensure the company uses all the modern/latest stacks?

Job Satisfaction

When it comes to the job itself, 82% of Engineers admit that lack of proper development practices plays a crucial role in their job satisfaction.

“The mess slows developers down and sometimes even prevents them from doing their actual job. Technical debt can make it difficult to be proud of the work you’re doing, as a lot of time is lost dealing with annoying obstacles,” says Maarten Dalmijn, head of product at Rodeo.

The right way to fight technical debt is to talk about codebase-related issues across the whole company so that everyone can understand why it’s vital to manage it carefully.