Field guide
Workout plan for software engineers
The complete weekly plan — exact days, exercises, sets, reps, and progression rules — for developers who sit all day and need something they can actually put on the calendar.
The weekly plan
Run Monday, Wednesday, Friday (or any three non-consecutive days). Progress each lift when you hit the top of the rep range across all sets with clean form — add 2.5 to 5 lb and climb again.
Monday — Full body, squat emphasis
- — Back squat or goblet squat — 4 sets × 5–8 reps
- — Bench press or dumbbell press — 3 sets × 8–10 reps
- — Chest-supported row — 3 sets × 10–12 reps
- — Romanian deadlift — 3 sets × 10–12 reps
- — Dead bug — 3 sets × 8 reps each side
Primary lower-body push day. Squat is the main lift — prioritize form and load. Keep the session to 45–50 minutes.
Wednesday — Full body, hinge emphasis
- — Trap-bar or conventional deadlift — 3 sets × 4–6 reps
- — Overhead press — 3 sets × 8–10 reps
- — Lat pulldown or assisted pull-up — 3 sets × 8–12 reps
- — Split squat — 3 sets × 8–10 reps each leg
- — Face pull — 3 sets × 15 reps
Primary hip hinge day. Deadlift first when you are freshest. Face pull at the end — do not skip it, it addresses the rounded-shoulder pattern from desk work.
Friday — Full body, upper emphasis
- — Incline dumbbell press — 3 sets × 8–10 reps
- — Cable row or machine row — 3 sets × 10–12 reps
- — Leg press or front squat — 3 sets × 10–12 reps
- — Hip thrust or glute bridge — 3 sets × 12–15 reps
- — Farmer's carry — 3 sets × 30 meters
Upper emphasis and posterior chain. Hip thrust targets glute activation that sitting suppresses. Farmer's carry builds trunk stability under load — one of the best exercises for desk workers that most programs skip.
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 hypertrophy than once per week, as established by Schoenfeld et al. Three full-body days hits every major muscle group roughly twice, which is the threshold the evidence supports. 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 do I do today?" question matters.
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.
Common questions
- What is the complete workout plan for software engineers?
- A three-day full-body plan: Monday (squat emphasis), Wednesday (hinge emphasis), Friday (upper emphasis). Each session is 45 to 50 minutes, covers every major muscle group, and progresses by adding load when you hit the top of the rep range. Run it for at least eight weeks before evaluating.
- How many sets and reps should software engineers do?
- For compound lifts (squat, deadlift, press): 3 to 4 sets of 4 to 8 reps. For accessory work (rows, lat pulldowns, Romanian deadlifts): 3 sets of 8 to 12 reps. For carries and isolation: 3 sets of 12 to 15 or distance-based. When you reach the top of the range across all sets, add weight.
- Why full-body instead of push-pull-legs for a 3-day plan?
- At three training days per week, a push-pull-legs split hits each muscle only once per week. Research shows training a muscle at least twice per week produces better muscle growth than once per week. Full-body training on three days hits every muscle roughly twice per week — the better choice for a three-day constraint.
- How do I stay consistent when work gets in the way?
- Use two sessions as your floor: one squat-and-press day, one hinge-and-pull day, each 30 minutes. When a sprint blows up, the floor keeps the habit alive. Schedule sessions at a fixed time — morning training has the highest completion rate for remote workers because the calendar cannot steal it.
- What do I eat to support this plan?
- Target 0.7 to 1 gram of protein per pound of bodyweight daily. Protein at every meal is the most important default. If fat loss is also the goal, add a moderate calorie deficit of 300 to 500 calories below maintenance, but protect protein first — cutting calories without protecting protein erodes the muscle this plan is building.
- Not sure which routine style fits your 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.
References
- Schoenfeld BJ, Ogborn D, Krieger JW. Effects of Resistance Training Frequency on Measures of Muscle Hypertrophy: A Systematic Review and Meta-Analysis. Sports Medicine. 2016. https://pubmed.ncbi.nlm.nih.gov/27102172/
- Schoenfeld BJ, Ogborn D, Krieger JW. Dose-response relationship between weekly resistance training volume and increases in muscle mass: A systematic review and meta-analysis. Journal of Sports Sciences. 2017. https://pubmed.ncbi.nlm.nih.gov/27433992/
- Huber P, et al. The impact of working from home on sedentary behaviour and physical activity compared to onsite work in the working population: a systematic review and meta-analysis. BMC Public Health. 2024. https://pmc.ncbi.nlm.nih.gov/articles/PMC12621373/
Want the plan adjusted to your sprint?
Not sure whether full-body, push-pull-legs, or upper-lower fits your schedule? Read the best gym routine guide for software engineers — it compares routine types by available days and schedule stability before giving you the exact program.
For the broader context on desk-worker programming — posture framing, hip and thoracic mobility through lifting, and posterior chain emphasis — see the desk-worker strength guide. Or the software engineer coaching page for 1:1 coaching. Coaching is application-based.
Coaching fit
Want this built around your real week?
Use the guide as a baseline. If your schedule, food, or consistency keeps breaking the plan, Kris can map the training and nutrition to the week you actually live.
Apply for 1:1 coachingWeekly training insights
One email a week on training, recomposition, and building the body you actually want. No spam. Unsubscribe anytime.
Keep going
Related guides
Proof and next steps