In this guide
- This is the plan, not the comparison
- Why this plan is built the way it is
- How to progress the plan
- Nutrition and walking: the other two components
This is the plan, not the comparison
A workout plan for software engineers has to start with the job. You sit for long blocks, your brain is the main tool, and the day can vanish into debugging, meetings, code review, or a production incident.
This post gives you the complete weekly plan: exact days, exercises, sets, reps, and progression rules. If you are still deciding which routine style works for your schedule — full body versus push-pull-legs versus upper-lower — read the routine decision guide first, then come back here once you have made the call.
The goal here is not to explain theory. The goal is to give you something you can put on your calendar Monday.
Why this plan is built the way it is
Three full-body days per week is the default for software engineers for three reasons. First, frequency: training each muscle twice per week produces better muscle growth than once per week. Three full-body days hits every major muscle group roughly twice. A push-pull-legs split with only three training days hits each muscle once per week — the wrong choice if you are only training three times.
Second, resilience: when a sprint blows up and Wednesday gets nuked by an on-call incident, a full-body plan still works if you shift to Monday and Thursday. Two full-body sessions covers everything once. A body-part split with the same disruption misses entire muscle groups for the week.
Third, execution simplicity: each session is the same shape — one big lower-body compound, one push, one pull, one hinge or second lower movement, one core or carry. You know exactly what the session structure is before you walk in. For developers who already make hundreds of decisions per day, removing the “what am I doing today?” decision makes the plan easier to execute.
How to progress the plan
Progressive overload is the mechanism. Without it, you are exercising, not training. The rule is simple: when you reach the top of the rep range across all sets with clean form, add weight the next session and climb the range again.
For big compound lifts (squat, deadlift, press): add 5 pounds when you hit the top of the range across all work sets. For accessory work (rows, lat pulldowns, Romanian deadlifts): add 2.5 to 5 pounds. For bodyweight or cable work (face pulls, carries): add a rep or increase resistance when the current load becomes easy.
One rule that matters more than any other: do not change exercises until the current selection stops producing gains. Developers often treat programming like a system-design problem and rebuild it before the current version has data. Run this plan for eight weeks minimum.
By week four, every major lift should be moving. By week eight, the squat, deadlift, and press should be meaningfully heavier than week one. If they are not, the issue is almost always nutrition or sleep — not the program.
Track your lifts. A plain text file, a spreadsheet, or a phone notes app works. You need the previous session's numbers to know what to do next session. Without a log, you are guessing.
Nutrition and walking: the other two components
The plan above covers the training. But the training only works if nutrition and daily movement are handled.
For nutrition: protein at every meal is the single most important default. Most men doing this plan should target 0.7 to 1 gram of protein per pound of bodyweight per day. That is the range that supports muscle building and hunger control without requiring obsessive tracking.
If you are also trying to lose fat, create a moderate calorie deficit — 300 to 500 calories below maintenance — but protect protein first. Cutting calories without protecting protein erodes the muscle the lifting is building.
For daily movement: a coding day is a sedentary day by default. Pair the plan above with a walk before work and a walk after the laptop closes. Those two anchors add 20 to 30 minutes of daily movement and create psychological boundaries that separate work from rest. On non-training days, add a midday walk as well. If you have a walking pad, use it during calls and shallow admin blocks at 1 to 1.5 mph.
If you work from home, the kitchen also needs structure. Remote workers accumulate up to 110 more minutes of sitting per day than office workers and tend to snack more because the kitchen is always nearby. Batch-prepare proteins, keep water at the desk, and set a rule about eating during work hours. The training plan and the lifestyle structure have to work together.
The fallback week
Every developer has a week where the plan breaks. Production incident on Monday. On-call rotation. A release that runs until midnight. These weeks are not failure — they are part of the job. The plan needs a fallback.
Two sessions is the floor: one squat-and-press day, one hinge-and-pull day. Each takes 30 minutes. Everything gets hit once instead of twice. It is not optimal and it does not need to be. It keeps the habit alive and keeps the main lifts moving, which is what protects months of progress from one bad week.
The goal is not to optimize every week. The goal is to not quit. A floor of two sessions per week, reliably executed across 12 months, produces far more progress than an aggressive six-day plan that collapses after the first on-call rotation.
When coaching helps
If you keep researching, restarting, and redesigning the plan, the problem is not lack of information. It is lack of constraint.
A coach chooses the plan, reviews execution, adjusts the next week, and removes the optimization loop that technical people get stuck in. For a software engineer, that outside judgment keeps the planning from becoming the activity instead of the training.
Not sure which routine style is right for your specific schedule? The best gym routine guide for software engineers compares full-body, push-pull-legs, and upper-lower splits by schedule constraints — read that first if you are still deciding.
What the desk-work evidence can tell you
A workout plan for a software engineer cannot treat desk work as an afterthought. You spend long hours seated in front of screens, and your day is defined by intellectual focus and variable work pressures. The studies below do not test this specific three-day lifting program. They do provide direct evidence on sitting patterns, back pain, and how office workers navigate physical activity alongside demanding work.
Bontrup and colleagues (2019) evaluated sitting habits and back pain in 64 call-centre employees, recording sitting behaviour across 400 hours with a textile pressure mat alongside questionnaires evaluating acute and chronic low back pain (PMID 31422243). In their sample, 75 percent of the workers reported some level of acute or chronic back pain. Workers with chronic low back pain showed a possible trend toward more static sitting compared to pain-free coworkers, though the comparison did not reach a reliable difference on a t-test. The authors also observed a stronger association between sitting behaviour and chronic low back pain than with acute pain or disability, noting this may plausibly reflect greater awareness of pain-free sitting positions among people dealing with chronic symptoms. The researchers noted that relationships between sedentary lifestyles, sitting habits, and low back pain remain controversial. For an engineer, this highlights that while sitting all day is a reality of the profession, static posture alone has not been proven to directly cause back pain. Changing position, breaking up long seated stretches with short walks, and completing regular lifting sessions provide sensible physical variety throughout the week.
Landais and colleagues (2022) conducted a qualitative study examining office workers' perspectives on physical activity and sedentary behaviour (PMID 35354447). The researchers identified six core themes: 1) workers held specific beliefs about the health effects of physical activity, but their understanding of sedentary behaviour was superficial; 2) along with health as a value, participants prioritized other values, including social and work-related commitments; 3) motivation to participate in physical activity stemmed primarily from valuing health, driven by wanting positive short- and mid-term outcomes as well as avoiding negative long-term outcomes; 4) attitudes toward inactivity and sitting were diverse and shaped by individual values and prior experiences; 5) perceived barriers depended on both internal and external factors; and 6) supporting factors relied on support and information within the social and physical environment. Landais and colleagues concluded that interventions could be improved by educating workers on the health risks of prolonged sitting and highlighting short- and mid-term advantages of physical activity—including mental health benefits—while aligning movement with workers' existing values and shaping the work environment to support breaks from sitting.
For software engineers, those findings mirror common workplace realities. You might value your health and still see a production deployment, code review deadline, or architecture design take priority over an evening workout. Relying strictly on raw motivation when internal fatigue or external workload escalates is an unreliable strategy. Creating supportive external conditions—such as keeping your gym gear prepared, scheduling lifting sessions as protected calendar appointments, and arranging your workspace for easy movement—removes friction so training aligns with daily engineering demands.
Bailey (2021) published a narrative review assessing the prevalence, health implications, and interventions surrounding workplace sedentary behaviour (PMID 33710270). Bailey reported that office workers are highly sedentary, which increases their risk of health issues, but noted that workplace strategies operating at individual, organisational, and environmental levels can successfully reduce sitting time. Multicomponent interventions combining these levels may be the most effective for lowering sitting duration. However, Bailey emphasized an area of controversy: the actual effects of sedentary workplace interventions on health outcomes remain inconsistent, likely because of a shortage of randomized controlled trials adequately powered to measure changes in health outcomes. Determining long-term health and cost-effectiveness remains an active research need.
This distinction is valuable for anyone setting expectations around workplace fitness. A standing desk, walking treadmill, or posture reminder can help reduce continuous sitting time, but current research does not show that desk adjustments alone guarantee specific health outcomes. A structured lifting program provides the progressive training stimulus that desk accessories cannot deliver. Pairing three weekly full-body sessions with practical movement anchors during work hours gives you a realistic, sustainable baseline.
Honest limits
These studies examine sedentary office workers and call-centre employees; they do not test software engineers specifically, nor do they evaluate this exact three-day full-body lifting schedule. Bontrup and colleagues (2019, PMID 31422243) observed associations between sitting behaviour and back pain across 64 participants, but their observational data cannot establish that static sitting causes pain, and the observed trend toward static sitting in chronic pain sufferers was not a reliable difference. Landais and colleagues (2022, PMID 35354447) used a qualitative design capturing self-reported worker perspectives, which clarifies behavioural barriers and competing values but does not quantify physical performance or physiological adaptation. Bailey (2021, PMID 33710270) pointed out that while workplace interventions reduce sitting, evidence for changes in health outcomes remains inconsistent and lacks large powered randomized trials. Use this research to inform sensible movement habits around your work schedule, not as a guarantee that any exercise plan or ergonomic setup will eliminate pain or produce specific health outcomes.
More questions
Which routine style fits a software engineer's schedule?
Read the best gym routine guide for software engineers. It compares full-body, push-pull-legs, and upper-lower splits by available training days, schedule stability, and goal. Come back to this plan once you have made the call.