AI Engineering Mentor (Claude Corps)

About the Role

Together with Anthropic, CodePath launched Claude Corps in June 2026, a national fellowship program with a $150 million commitment to place 1,000 AI-trained fellows at nonprofits across America. A fellowship is only as good as the engineer riding alongside the fellow when something breaks at midnight. As a CodePath Mentor, that engineer is you.

You are the full-time technical coach for a portfolio of roughly ten pods: about 20 fellows across 8-12 host organizations, from pre-Basecamp through the final day of the program. You are the coach that develops the fellow: you have first eyes on every pull request, you catch the patterns when something is off, and you proactively resolve any roadblocks that come up. The host org directs the fellow's day-to-day work, the curriculum team owns what they learn, and your Delivery Manager is the manager of record who holds the performance bar. Your job is to make each fellow better at the work.

The work is mostly written and asynchronous: code review on pull requests, feedback on roadmap drafts and quarterly business reviews, weekly office hours, and a few synchronous deep dives when something needs more than text. You will not be the deepest expert in the room for every fellow, and we are honest about that. You carry the throughline: you know your pods end to end, see patterns nobody else sees, and pull in deeper expertise the moment a single fellow needs it.

This role is built for engineers who would rather coach 20 engineers through real production work than ship one feature themselves. You are a few years further down the road than the fellows: enough professional reps to read code with judgment, a real coaching instinct, and the AI-native practice fellows are being trained to build.

Key Responsibilities

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 Delivery Manager, 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 Delivery Manager 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 Delivery Manager for a delivery or performance issue
• Be the first stop when a fellow's technical work is at risk; surface it to your Delivery Manager, 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 Delivery Manager 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 Delivery Manager, with a plan for any fellow whose work is at risk or ready for the next challenge

Qualifications

Required

• 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