Critique this 8–9-module course for experienced devs moving to contracting

1 points by koehn 3 hours ago

I’ve been a software consultant for ~30 years. I’m shaping a course for experienced engineers (US SWE/DevOps/SRE, ~5–15 yrs) who want to move into contracting using an agency-first workflow: you qualify/price/deliver; agencies bring openings and handle MSAs/SOWs. Expected time: 2–4 hrs/week.

I’d love a sanity check from people who contract or place engineers: what’s missing, out of order, or unrealistic?

What students should build • A realistic target rate (with clear rate math) • A recruiter-ready profile and 10–15-minute qualification script • A simple “operate-like-a-business” setup (LLC/banking/insurance) • A pipeline plan that typically leads to interviews in ~6–12 weeks • Tactics to avoid scope/rate mismatches and keep agencies happy

Draft syllabus (9 modules)

Module 1: Introduction — What’s This All About? (Why you should/shouldn't go independent) Module 2: How Contracting Through an Agency Works Module 3: Finding Work & Working with Agencies Module 4: Setting Up Your Business & Life Infrastructure Module 5: Landing an Engagement Module 6: At the Engagement Module 7: Paperwork & Legal Basics Module 8: Building a Reputation & Staying Marketable Module 9: Long-Term Strategy

The course is designed to help people who want to go into the agency model get past the fear of the unknown (this was my biggest blocker for me before I went independent). By giving detailed instructions in a step-by-step structure, it helps engineers reap the benefits of contracting: higher pay, better hours, and a better lifestyle than working as an employee.

Specific questions • Which topics deserve more/less time? • Better ways to model rate, bench, and markup? • What do you look for in Right-to-Represent and MSA/SOW alignment? • Any “gotchas” you’d teach before the first engagement?

I’m not selling anything here—just looking for blunt feedback from other people who’ve done this.