> Markdown version of [/jobs/ext/4261624-technical-coach](https://www.wearedevelopers.com/jobs/ext/4261624-technical-coach). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# technical coach

- **Company:** CODEPATH, LLC
- **Location:** United States (Remote available)
- **Experience:** Experienced
- **Salary:** $110,000.0 - $124,500.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Code Review, DevOps, Machine Learning, Software Engineering, Claude, Basecamp
- **Published:** October 6, 2026
- **Apply:** https://startup.jobs/mentor-claude-corps-part-time-codepath-10303021

## About the Role

* 2 to 4 years of professional software engineering on a real team: long enough to have opinions about code, short enough to remember being the most junior engineer in the room
 * Real coaching or mentorship reps, formal or not: an intern you saw through a summer, a teammate you onboarded, a bootcamp you TA'd. We are hiring the instinct, not a management title
 * You can read a pull request you didn't write, in a stack you don't use every day, and give feedback that is specific and useful
 * You have shipped production work with AI-assisted development tools and can describe specifically how your workflow changed; you have to be ahead of the fellows on this curve
 * You are comfortable as a generalist coach: you find the answer or the right person quickly, and you trust partner experts to carry the depth you don't
 * Strong written communication; most of your feedback is asynchronous, read by people who don't speak your stack
 * Comfortable with remote, synchronous obligations across US time zones and about two evenings a month for cohort sessions and milestone reviews

Preferred

 * TA, bootcamp coach, fellowship mentor, or instructor experience in a cohort program, even informally
 * Experience at a small or scrappy organization where engineering meant translating business context into technical decisions
 * Comfort across at least two of: web full-stack, data/AI engineering, ML, infra/devops

## Description

Coach your pods

 * Carry roughly 10 pods (about 20 fellows across 8 to 12 host organizations) full-time from pre-Basecamp through final day, calibrating your time across the portfolio rather than sinking into one pod
 * Have first eyes on every fellow's pull request, and give structured written feedback on their real work (PRs, roadmap drafts, architecture proposals, QBR deliverables) at the cohort's pace, not your inbox's
 * Facilitate weekly 1:1s with all of the Fellows that report to you and document their progress, challenges, and successes using the tooling that Claude Corps operates on
 * Lead each fellow's Day 30/90/180/270 milestone review; you own the fellow-level synthesis and hand it up to your Sr. Manager of AI Practice, who owns the roll-up and the performance call

Deliver the curriculum in your pods

 * Deliver the just-in-time modules the curriculum team designs; author lane- or pod-specific content when they commission it, because you have seen the gap from closer in
 * Frame and debrief the cohort-wide all-hands your Sr. Manager of AI Practice runs, and the sessions where the curriculum team or a guest teaches your fellows directly
 * Co-lead the Basecamp practical assessment alongside Anthropic's instructors; it is your first calibration on each cohort

Keep the program honest

 * When the same problem shows up across three fellows, raise it to the right owner: the Claude Corps leadership team for program efficacy, the curriculum team for curriculum, partner experts for technical depth, host-org managers for a host issue, or your Sr. Manager of AI Practice for a delivery or performance issue
 * Be the first stop when a fellow's technical work is at risk; surface it to your Sr. Manager of AI Practice, who owns the escalation
 * Work AI-natively: Claude is core to your coaching loop for code review, pattern-spotting, and feedback at scale, and fellows should see you working the way they are being asked to work

Key Success Metrics

 * You have surfaced the top three cohort-wide technical patterns to your Sr. Manager of AI Practice and the curriculum team
 * 100% of host-org managers you've worked with in the last 30 days can produce one concrete example of your impact
 * Every Day 30 review is done and documented, handed up to your Sr. Manager of AI Practice, with a plan for any fellow whose work is at risk or ready for the next challenge