Find a posting that accepts the evidence you have
Kastle's employer-authored Software Engineer Intern posting on YC describes San Francisco work and accepts relevant coursework, personal projects and hackathons as experience. It names evaluations, quality checks and agent development among the tasks. A test harness you built could therefore be more relevant than a generic startup-interest pitch.
The page does not supply a pay amount or deadline. Ask about those terms rather than assuming that an accessible experience requirement also makes the role financially workable. The employer's promises about ownership and feedback are questions to verify in conversation.
Sources[1]
Turn improve activation into a finishable assignment
NACE's internship guidance calls for defined work, learning objectives and qualified supervision. Apply that to the project discussion. Improve activation is a goal; it does not tell you what to do on Monday or when the work is finished.
| Term | Concrete version |
|---|---|
| Deliverable | Map the setup flow and recommend one change in a two-page memo |
| Inputs | Approved product access and anonymized support categories |
| Timing | First draft after two weeks at the agreed weekly hours |
| Reviewer | The product manager checks the analysis and selects any test |
| Completion | Memo explains the problem, evidence, alternatives and proposed measure |
| Blocked inputs | Agree on a revised assignment; do not invent customer findings |
Sources[2]
Compare cash and time before discussing possible equity
These fictional offers cover 12 weeks. Assume all scheduled hours are worked and the stated cash is paid.
| Term | A | B |
|---|---|---|
| Pay | $25 per hour | $4,000 total stipend |
| Weekly hours | 20 | 30 |
| Total hours | 240 | 360 |
| Gross cash | $6,000 | $4,000 |
| Cash per scheduled hour | $25 | About $11.11 |
| Review | Named manager; weekly project review | Founder feedback when available |
| Other benefit | None stated | Equity may be discussed later |
What this comparison reveals
Ask about a paid need, not permission to do anything
When no suitable internship is posted, connect one piece of your actual work to a task the company appears to need. Keep the initial request narrow enough to answer. Do not volunteer for an undefined trial project before agreeing on the scope and terms.
Startup internship inquiry
Separate normal project uncertainty from missing basic terms
A startup may change the project. A manager can respond by defining a replacement assignment. That is different from leaving pay, hours or supervision unresolved. Ask for the written arrangement before accepting, including payment dates and how additional hours would be handled.
Also establish which equipment and expenses the company covers and what work you may discuss afterward. A useful project can be confidential; portfolio permission should not be assumed. Choose with those constraints visible rather than trying to value an unspecified future job or equity grant.