About FirstShift
I built FirstShift after a summer job search that went nowhere. This is the story of the search, the build, and the ask behind it all.
Where it started
The search that went nowhere
Junior year at Delbarton, my parents said I needed a job. I did what they told me to do. I walked into six local businesses and asked in person. I filled out another ten applications online.
The answers sorted into three piles. Some said no. Some said come back closer to summer. Some said yes, let's get you on a training schedule.
I followed up on the maybes more than once. I still never got the job.
6
Walk-ins, asked in person and filled out an application
10
Online applications
0
Jobs offered
The realization
The requirement I couldn't meet
What stuck with me was not the rejection. It was the requirement I could not meet. Everywhere I went, some experience was the thing that separated a yes from a come-back-later. I did not have any, and there was no obvious way to get it without already being hired.
I figured that was not just my problem.
So I started designing a way for a teen to learn how a business actually works — a short, supervised session — without being on payroll. I did not want to walk back into those shops with an idea. I wanted a site they could click through.
The build
A first version that failed at home
That decision cost me time, and it was the right one, because the first build was not showable. Logins were the first wall. Teens and businesses both needed accounts, and those accounts needed to do different things.
Getting someone signed up was not the hard part. The hard part was what happened next. After signup, it was not clear where to go, what "approved" meant, or who was waiting on whom.
I stopped guessing and put my younger sister and my parents through the whole onboarding. I told them to write down every question they had while they did it. That list became the roadmap.
What family testing forced in
- Businesses needed room to set up a session their way, not a rigid form.
- Users needed to be told what was happening: notifications, reminders, cancellations, no-shows.
- People needed to preview a session before they created an account, because asking for a signup before they could see the thing was the same friction I had just hit as an applicant.
- I had to learn teen work rules well enough to build parent consent and a waiver flow, so a session stayed training and not unpaid work.
None of that was in the first version. Family testing is what forced it in. It also kept me from demoing a half-built site to owners who do not have time for a half-built site.
First Shift is the result
First Shift is the result of a search that failed, then a build that failed a smaller test at home, then the fixes those failures forced. The ask of a business is the thing I could not get someone to offer me: one short look inside, no commitment to hire.