Claude Code Intern

Claude Code Intern: Pax Distribution

We automate our own operations with Claude Code. Not "we use AI." We write skills, wire up MCP servers, run subagent fan-outs, and ship workflows that touch real money — purchase orders, ad spend, brand relationships.

You'd be building those workflows. Small company, no layers, your work goes live the week you write it.

Before you apply, you should already know:

What goes in CLAUDE.md and why it beats prompting the same thing every session

The difference between a skill, a subagent, and a slash command, and when each is the wrong tool
- How to write a SKILL.md that fires on the right trigger and doesn't fire on the wrong one
- How to connect an MCP server, and what to do when the tool call comes back empty
- Why you'd route a fan-out to Haiku instead of Opus
- How to keep a 40-file export out of your context window
- If you had to look up more than one of those, this isn't the role yet. Come back after you've built something real with it.

The screen: Send us a link to a Claude Code project you built, the actual .claude/ directory, not a screenshot of a chat. We'll read your skill files. If your CLAUDE.md is three lines of "be helpful," we'll know.

What we don't want: Someone who's watched the videos. Someone who thinks "prompt engineer" is a job title. Someone who needs a ticket written before they'll touch anything.

What you get: A messy, real operation with a hundred processes that should be automated and aren't.