Come do work that compounds.

High-judgment early-career people who want to operate, not observe.

If your instinct when you see a broken process is to quietly fix it — and then write the SOP so the next person doesn't hit the same wall — the Pod is for you.

We are not screening for prestige signals. Name-brand logos, GPA, polished LinkedIn branding — these may help at the margin, but they are weak substitutes for the one trait we value most: reducing executive load without creating hidden cleanup work.

High-signal traits

• Judgment — you can tell what matters from what's loud
• Speed without sloppiness
• Respect for confidentiality (non-negotiable)
• Analytical honesty — you show your assumptions and flag what you don't know
• Taste in synthesis — you compress without flattening
• Follow-through — you close loops, not just open them
• The ability to improve a system, not merely complete a task

Secondary, still valued

• Writing quality
• Spreadsheet logic and numerical sanity checks
• Coding or low-code fluency
• Founder empathy — you can read a pitch and spot the wobble
• The ability to see when a tactical question is really a proxy for a strategic one

We are allergic to fluff. Fellows leave with stronger pattern recognition, tighter written communication, real artifacts, and a better understanding of how value is actually created.

Explorer → Fellow → Advanced Fellow → Operator Candidate.

Advancement is evidence-based. We do not elevate people because they stayed around. Advancement requires repeated proof that the person can handle more trust, more ambiguity, and higher-consequence work without becoming a supervision sinkhole.

Explorer  ·  1–3 weeks

A short proving period. Small, scoped, low-risk tasks that reveal core habits: follow-through, responsiveness, research quality, formatting discipline. Promotion signal: delivers on time with clean formatting and honest uncertainty.

Fellow  ·  8–16 weeks

The core program stage. Real scoped workstreams, routine review, and a weekly rhythm of prioritization + deliverable + retrospective. Promotion signal: can ship decision-useful output with moderate supervision.

Advanced Fellow  ·  12–24+ weeks

Higher-trust assignments that involve synthesis, systems design, or founder-facing support. You start mentoring peers informally. Promotion signal: reduces executive load and produces low-revision output.

Operator Candidate  ·  as earned

Internal designation for fellows strong enough to be considered for paid contractor or embedded operator roles inside Noygear portfolio companies. Tested on ownership under ambiguity, not just execution.

Six live workstreams. No speaker series. No shadow HR program.

Every assignment is real work that would otherwise be done by the studio or a portfolio company. Fellows rotate across the workstreams that match their strengths and the Pod's current needs.

01 — Venture research

Market maps, competitor grids, thematic memos, company profiles, sourcing lists, thesis testing.

02 — Diligence & decision support

Interview prep, reference questions, red-flag summaries, product teardowns, data room indexing, cap table and scenario analysis.

03 — Operating systems & family-office workflows

KPI dashboards, Notion and Airtable schemas, GTD pipelines, inbox automation, SOP creation, governance trackers.

04 — AI & automation builds

Internal tools, prompt libraries, document pipelines, model-based tagging, data ingestion and synthesis systems.

05 — Founder & ecosystem support

Briefing packets, call memos, partner maps, ecosystem research, product requirements, architecture notes, software development.

06 — Grant & non-dilutive capital support

Landscape research, calendar tracking, application drafting, evidence collection, post-award process systems.

Lean, high-trust, feedback-dense.

The default pod is four to six active fellows per reviewer. Trust compounds when the group is small enough that the lead actually remembers each fellow's strengths, revision patterns, and risk profile.

Operating cadence

• Daily (async): acknowledge blockers, update status, respond to critical questions
• Weekly: Monday prioritization note · midweek checkpoint · Thursday deliverable · weekly pod review
• Monthly: governance review — who is rising, who is stalled, what systems are breaking
• Quarterly: bonus pool review, alumni review, program redesign

Deliverable standard

Every deliverable answers five questions cleanly:

• What problem is being solved
• What the fellow did
• What assumptions were used
• What the recommended next step is
• What remains uncertain

Formatting matters because clean formatting is a proxy for structured thinking. A build without a handoff note is not a finished build — it is an IOU disguised as output.

Curiosity. Integrity. Hard work.

Behavior that reflects these values is rewarded early and often, because it lifts everyone. Transgressions are not tolerated, because they can hurt the studio and the Pod irreversibly.

Integrity is evaluated explicitly. Fabricated citations, hallucinated references, hidden collaboration, and résumé inflation are disqualifying. We watch how candidates handle uncertainty, and whether they admit what they do not know.

Confidentiality is non-negotiable. Everything you see inside the Pod stays inside the Pod.

A short but real selection process.

At minimum: application form, work sample, one interview focused on background and communication capacity, and one practical exercise testing problem-solving and judgment.

Selection exercises are real Pod work

• A short market memo
• A company breakdown
• A cap-table clean-up
• A diligence outline
• A workflow-mapping exercise
• A founder-email draft
• A lightweight automation prompt

What we are evaluating: judgment under ambiguity, written clarity, follow-through, and the habit of making things better rather than just completing them.

Highly scripted. Nothing left to osmosis.

Day 0

Legal docs, tool access, security setup, communication norms, role clarity.

Days 1–3

Orientation to the studio's operating principles, current workstreams, deliverable standards, and active priorities.

Days 3–7

First scoped task, first review, first quality baseline established.

Days 8–14

Second task, first retrospective, initial scorecard.

Every fellow receives a one-page onboarding brief that answers six questions: what matters here, what good looks like, what bad looks like, how to ask for help, where work lives, and how approval actually happens. Access is granted to do the work well — plus enough context to avoid hallucinating relevance.