Draft preview. This is a working mock — submissions don't go anywhere yet.
Host Problem Brief

Tell us about your project.

About 20 minutes of focused thinking. We'll read it within a week and follow up with a 30-minute sharpening call. Most fields are quick picks; a couple ask for real writing — those are the ones that matter most.

1 · About you

Just enough to follow up. We don't share contact info publicly without asking.

e.g., Executive Director, PI, Founder, Engineering Lead.
What kind of host are you?*
2 · Project at a glance

The single biggest predictor of a strong summer is a clear brief. Don't worry about polish — we'll sharpen it on the call.

Short and concrete. "Replace our donor CSV pipeline with a real database" beats "Data improvements."
Finish this sentence: "An intern who joins this project will…"
What's the problem, why it matters, who benefits, and what would shipped look like? 150–400 words is plenty. 0 words
2–3 observable things that would tell you the work is done. "Donors can be filtered by zip in under 200ms" beats "the system is faster."
What is explicitly out of scope this summer? This protects everyone — the most common cause of a rough summer is silent scope creep.
3 · Domain & data

This drives matching and tells us what guardrails the workspace needs.

Primary domain (pick all that apply)*
Data sensitivity*
e.g., data residency, IRB, BAA required, audit logging mandatory.
Will the intern work with real data or synthetic?
Repo visibility*
IP ownership*
NDA required before the intern starts?
4 · Tech stack

Skip anything that doesn't apply. "I'm not sure" is a perfectly valid answer for greenfield work.

Primary languages (pick all that apply)
e.g., Django, Next.js, FastAPI, React Native, Postgres, Snowflake, AWS Lambda. Comma-separated is fine.
Code maturity
Infra / hosting
5 · Time & duration

We design around the time you actually have, not the time you wish you had.

How much host time can you commit per week?*
Response time you can commit to for blockers*
Program length*
Preferred start window*
Grant report, conference, product launch, board meeting — anything that fixes when "done" has to be done.
6 · Location & arrangement
Work arrangement*
Equipment
7 · Compensation

We're direct with applicants about pay so the match is honest on both sides. Transparency here helps.

Compensation type*
e.g., $3,000 lump sum, or $20–25/hr. Even a rough range helps applicants self-select.
Who pays?
Especially relevant for hybrid/on-site roles. "None" is a fine answer.
8 · Intern profile you're hoping for

We use this for matching, not gatekeeping. "Willing to learn" is often the right answer.

Hard requirements only — things you can't teach in a summer.
Comfort with AI coding tools (Claude Code, Copilot, etc.)
Class year preference (pick any that fit)
Mentorship style
9 · Risk & publicity
Optional but high-value. Naming the failure modes early is the cheapest insurance you'll buy this summer.

Publicity & promotion. Two separate consents — your call on each.

Can we list this project publicly on the Orchid open-projects board before matching?*
After the project wraps, can Orchid feature this work in promotional materials?* Case studies, website, podcast, social, grant applications.
If yes to either above — what assets are okay to share?

When you submit, we'll read the brief within a week and email you to schedule a 30-minute sharpening call. Nothing is published or shared until you've reviewed and approved.

Back to host overview