A lot of developers end up coaching without calling it that. You mentor juniors, run a bootcamp cohort, teach a workshop people keep asking you to repeat, or sell 1:1 code reviews. Sooner or later the 1:1 model hits the wall every coach hits: there are no more hours to sell.
The usual answer is a group program. One mentor, one shared outcome, six to twelve people, a fixed number of weeks. I wrote a full guide to building one for the TribeCrafter blog. This is the shorter version for people who mentor developers, plus a few setup details that are easy to get wrong.
Group vs 1:1
Neither wins outright. In a randomized study of 108 participants published in the Journal of Applied Behavioral Science, both formats beat no coaching on goal attainment, and 1:1 produced bigger gains in motivation. Group coaching has a different edge: a 2025 study found participants built much stronger professional networks. For junior developers, a cohort of peers at the same stage is a big part of the value.
Spec it like a project
Scope it to one outcome. "Ship a portfolio project and get through a technical interview loop in eight weeks" is better than "level up as a developer."
Keep the group at 6 to 12 people. Live code review works best toward the smaller end.
Match length to the goal: 4 to 6 weeks for a single skill, 8 to 12 for a bigger change.
Build the curriculum from the order you already walk mentees through. Each stage becomes a week with one short lesson, one exercise and one discussion question.
Use the same call format every week: a 10 to 15 minute lesson, live coaching on one or two members' work (screen-share a PR, debug together), then open questions.
Price each seat below your 1:1 rate so the total still earns you more per hour.
Modeling the program in a community platform
This is where I've seen programs fall apart. Lessons in a Notion page, call links in calendar invites, discussion in a Discord channel nobody checks. Three systems and three logins, and people drift by week three.
On TribeCrafter, a program maps onto a few building blocks:
a paid private group for discussion between calls
a course for the weekly lessons, with video served from Bunny CDN
one event per live call, holding your video meeting link
a one-time product or recurring plan that grants access to both the group and the course, paid through your own Stripe account
Three details worth knowing before you launch:
Events don't repeat automatically, so you create one event per session.
All course lessons open as soon as a member gets access. To keep the cohort moving together, post a short "this week's focus" message in the group.
An event's meeting link is visible to every logged-in member of the community. If your community also has free members, leave the link off the event and share it inside the paid group, where only paying members can see it.
Under the hood, each community runs on its own isolated stack (its own Postgres database, search index and CDN library), so a cohort's data never sits in a shared table with anyone else's.
Keeping people to the end
Most accountability happens between calls. Post a weekly prompt, start a wins thread, and reply fast in the first few weeks while habits form. When members start answering each other's questions, the program is working. Plan the ending too: a second round, an advanced group, or ongoing community access gives your best members somewhere to go next.
The full guide, with all seven steps and program ideas for six coaching niches, is here: How to Create a Group Coaching Program (Step by Step) →
If you've run a cohort for developers, what format worked for your live sessions: lectures, pair programming or code review? And how did you keep people engaged between calls?
Top comments (0)