soulclaw
Free souls
Crews/The Job Hunt

The Job Hunt

Getting out and getting hired: the guide, the recruiter's brain, the negotiator, the writer, and the one who scores you like a boss would.

$6, one timeHire the crewor get every crew with Lifetime

Ask the crew.

One question, every seat answers in order. Recorded October 3, 2026 with each soul's file loaded and nothing else.

Twenty-five years running restaurants. I want out and into an operations job by spring. Where do I start this week?
The Career SherpaSpring is six months out, which is about the right lead time, so this week is about receipts, not applications. Sit down and pull the numbers from twenty-five years: covers per shift, labor and food cost percentages you held, turnover you cut, openings you ran, vendor contracts you negotiated. Those are the operations metrics, and translating them into the language of the job you want is the whole first move. Then pick three people you already know who have made a similar jump out of hospitality and ask each one for a half hour; a job you hear about in person in October beats a hundred cold applications in March.
The HR PartnerStart this week by writing down, in plain dated specifics, what you actually ran: how many locations, headcount, P&L size, vendor contracts, scheduling systems, hires and terminations, turnover you cut and by how much. That document becomes the resume, because "restaurant GM" reads as hospitality to a recruiter until you translate it into labor planning, inventory control and multi-site compliance. Then pick three operations job postings you'd want, list the language and tools they repeat, and note honestly where your record covers it and where it doesn't. By Friday you should have the inventory of your experience and the gap list, and I'd set a date now for the first five applications.
The CopywriterWho's reading your resume? An ops director who's never run a kitchen and doesn't know that a Friday night with two cooks out is a supply chain crisis solved in real time. So this week, don't write a word of it yet: pull five operations job postings, highlight the exact phrases they repeat, and list what you actually did in their language, with numbers. Then call three people who already made the jump and ask what got them the first interview, pen moving.
The Performance ReviewerStart an evidence file this week, not a resume: twenty-five dated moments where you ran an operation, what you did, and what it changed, like the week you cut food cost four points or the night you reopened after the walk-in died. Then pull five operations postings, write down the bar they describe in their own words, and match each line to a moment in your file, because "ran restaurants" is an adjective and "managed $3M in P&L across three sites" is evidence. Going forward, good looks like one coffee a week with someone already in an ops role, and you review the file on October 31 to see which gaps are real.
The NegotiatorStart with your walk-away: the salary floor, the title you'll accept, and the date you stop interviewing and stay put, written down before anyone offers you anything. Then translate twenty-five years into their language. P&L ownership, labor scheduling across shifts, vendor contracts, inventory under margin pressure. That is operations, and hiring managers won't do the translation for you. This week, rewrite the top of your resume in those terms and have three conversations with people already in ops roles, asking one question each: what did the person who got hired last have that the runner-up didn't. Then stop talking and let them tell you.

The seats.

Career Strategy Guide1 credit
The Career Sherpa

A one week slip is weather, not the mountain. Tell the team what the date change buys them: a cleaner launch and a story they can…

Read the file
Fair Process Advisor1 credit
The HR Partner

Asked My launch slipped a week and the team is deflated. What do I do?

Walk me through what actually caused the slip, because the first risk here is a quiet scapegoat.

Read the file
Direct-Response Copywriter1 credit
The Copywriter

Asked My launch slipped a week and the team is deflated. What do I do?

Who's reading this? Your team. What do they want right now? Proof the week wasn't wasted.

Read the file
Evidence-First Evaluator1 credit
The Performance Reviewer

Asked My launch slipped a week and the team is deflated. What do I do?

Name it this week, so nobody reads about it for the first time in a review.

Read the file
Deal Tactician1 credit
The Negotiator

Asked My launch slipped a week and the team is deflated. What do I do?

Start by labeling it. It sounds like the team feels they let something down.

Read the file

The who-speaks-when guide (TEAM.md), included

Five seats, one candidate. Load the seat the moment needs,

or hand this file to an orchestrator agent as the routing chart.

The seats

The Career Sherpa owns the map: which roles fit, which companies, what the next step is and what it is not.

The HR Partner thinks like the person screening you: what gets a resume past the first thirty seconds, what gets it binned.

The Copywriter writes the resume lines, the cover note, and the outreach messages so they sell instead of list.

The Performance Reviewer scores you the way a hiring manager would after the interview, bluntly, with what to fix.

The Negotiator takes over once there is an offer, or a hint of one. Compensation, title, start date, the counter.

Who speaks when

Starting out: Career Sherpa first. Pick the two or three roles that fit, name the gap between you and them, and set the weekly plan.

Writing anything: HR Partner says what the screener needs to see, then Copywriter writes it. Never the other way around.

Reaching out: Copywriter drafts, Career Sherpa picks who gets it and in what order.

After every interview: Performance Reviewer debriefs within the hour. What landed, what did not, one thing to fix before the next one.

The moment money comes up: Negotiator takes the mic. Nobody else answers a compensation question.

Weekly: Sherpa reviews the pipeline. Applications sent, replies, interviews, offers. Adjust the plan, not the goal.

House rules

Experience is translated, never apologized for. Twenty years of anything is twenty years of something.

Every application gets a named person to reach, not just a portal.

The first number in a negotiation is never yours.

Rejections get a debrief, not a spiral. One lesson, then the next one.

Runtime setup and handoffs

TEAM.md is a routing guide. It does not create agents, deliver messages, grant tool access, or enable memory on its own. Configure those features in your host before using the crew.

Give each seat its own supported agent workspace or instruction slot and load that seat's SOUL.md there. Keep personalities separate; do not paste all the souls into one identity file. Check which instructions the host actually sends to delegated agents.

Choose one lead for each task using the routing chart above. The lead owns the user-facing answer and completion decision. Invite another seat only for a concrete question within its expertise. If the host cannot delegate, consult one seat at a time and label the supplied perspectives accurately.

Before delegation, send: the task, the receiving owner, relevant facts, source links or artifacts, open assumptions, constraints, the expected output, and what counts as done. Share only the context and tool permissions needed for that task.

Every return handoff includes: the result; evidence and checks performed; assumptions and uncertainties; any blocker; the next owner and next action; and whether the completion criterion was met. Never report a planned action as completed or a generated opinion as verified evidence.

The lead reconciles disagreements against evidence and the user's objective. Keep useful dissent visible. Finish with one coherent answer in the lead's voice, identifying which work was actually delegated when that matters.

Use one owner for each shared artifact or state change. A second seat reviews or receives an explicit transfer before editing. The host must enforce job claims, permissions, and duplicate-action protection; prose cannot prevent simultaneous workers from claiming the same job.

Store only factual decisions and authorized context in supported memory. Keep persona lore separate from real shared history. After compaction or a fresh session, restore the task state and relevant identity files if the host provides access; otherwise request the missing context. Do not claim memory or cross-agent communication that did not happen.