Developer Burnout Dataset 7000

By shrijeetverma13 · April 19, 2026

This dataset models developer work patterns, stress levels, and burnout risk based on lifestyle and productivity factors. It captures realistic…

The analysis successfully generated both a pie chart and a bar chart showing the distribution of burnout levels across all developers. These visualizations break down how developers are spread across the Low, Medium, and High burnout categories, with each segment clearly labeled with counts and percentages.

The analysis produced a bar chart showing average stress levels across different age groups (20-24, 25-29, 30-34, 35-39, and 40-44). The visualization uses a color scale from green to red to highlight relative stress intensity, with error bars indicating variability within each group.

The analysis produced a stacked bar chart showing how burnout levels are distributed across four experience ranges: 0-3 years, 4-7 years, 8-12 years, and 13-19 years. The visualization makes it easy to compare the proportion of High, Medium, and Low burnout across each group.

Based on 1,782 high-burnout developers, the average profile shows significantly more work hours, less sleep, higher caffeine consumption, and slightly less exercise compared to the overall developer population. The bar chart and data table generated make it easy to compare high-burnout developers against all developers across all four metrics.

Two line charts were generated showing how meetings per day relate to commits and bugs across burnout levels. The overall correlation between meetings and both commits (0.017) and bugs (0.015) is essentially zero, meaning meetings have almost no impact on daily output. Interestingly, bugs per day tend to decrease slightly as meetings increase, regardless of burnout level.

The analysis explored how sleep hours relate to stress levels across different burnout groups. Two data tables were generated summarizing the relationship between sleep duration, stress levels, and burnout categories. These tables break down the patterns for each burnout segment (Low, Medium, High), allowing you to compare how sleep and stress interact across groups.

About 16.09% of developers — that's 1,126 out of 7,000 — work more than 10 hours daily while sleeping less than 6 hours. A pie chart has been generated to visually illustrate this breakdown between this high-stress group and the rest of the developer population.

There is a weak but consistent positive relationship between caffeine intake and both stress level and burnout. As daily caffeine consumption increases from 0 to 7 cups, average stress rises from 46.8 to 60.4, and the proportion of people with high burnout more than doubles from 16.5% to 35.8%. The Pearson correlation of 0.20 confirms the trend is real but modest — caffeine alone doesn't strongly predict stress or burnout. Two charts were generated: a box plot showing stress level distributions across caffeine intake levels, and a grouped bar chart showing burnout level percentages by caffeine intake.

Yes, developers who exercise more do tend to have lower stress and burnout levels, though the relationship is modest rather than dramatic. Analyzing 7,000 developers, those exercising just 0–0.5 hours/day had an average stress score of 57.0 and burnout score of 2.13, compared to 50.8 stress and 1.95 burnout for those exercising 1.5–2 hours/day. Two charts and supporting data tables were generated to visualize these patterns.

High-commit developers are actually LESS likely to experience high burnout, but the difference is negligible. Developers in the highest commit quartile have a 24.9% high burnout rate compared to 25.7% for the lowest commit group — only a 0.8 percentage point difference. This suggests commit frequency has virtually no meaningful relationship with burnout levels.

The analysis successfully identified how work hours, sleep, caffeine intake, screen time, and exercise correlate with stress levels. Two visualizations were generated: a horizontal bar chart showing the Pearson correlation coefficients for each factor (with red bars indicating positive correlations and blue bars indicating negative ones), and a scatter plot highlighting the strongest correlating factor against stress level, color-coded by burnout level with a trend line.

Among 1,593 low-burnout developers, the most common combination is sleeping 8-9 hours paired with 1.5-2.0 hours of exercise, shared by 131 developers. A heatmap visualization has been generated showing the full distribution of sleep and exercise hour combinations across this group.

Yes, developers with higher bugs per day clearly show elevated stress and burnout levels. The data reveals a moderate-to-strong positive correlation (0.492) between bugs per day and stress levels. Two charts were generated showing average stress by bug group and burnout distribution across bug groups, making the trend easy to visualize.

No, younger developers aged 20-25 with low experience (≤3 years) are NOT at higher burnout risk compared to their peers. The data shows nearly identical burnout rates and stress levels between the two groups.

The analysis segmented developers into 4 distinct workload profiles using K-Means clustering on three key dimensions: daily work hours, meetings per day, and commits per day. Two data tables were generated summarizing these profiles and their characteristics.