New Grad Jobs at Startups: A Practical 30-Day Search Plan

Finding new grad jobs at startups can be frustrating when every interesting posting seems to expect experience you do not have. You need a narrower target and evidence that you can finish useful work. This guide gives you a practical 30-day search plan for the US and Canada, including daily tasks, resume examples, and a tracking setup.

This article is general information, not legal advice. For work authorization questions, check the official sources below or consult your school's international student office, an immigration attorney, or a regulated Canadian immigration consultant or lawyer.

Why startup hiring is different for new grads

Do not assume a small startup has a campus recruiting calendar, a graduate cohort, or someone assigned to train you. Check whether the team hires junior employees individually and who would supervise you. Your search should work even without a university recruiting pipeline.

Y Combinator's first-engineer hiring guidance describes founders with limited recruiting time and an emphasis on personal networks. That is advice for early engineering hires, not a claim about every startup. It helps explain why submitting a resume may be only part of your search.

Give a founder or hiring manager something concrete to evaluate: a working feature, a useful analysis, or a clearly explained customer problem. YC's job-seeker guidance recommends specific contributions and examples such as product improvements, go-to-market plans, and sample code. You still need the role's essential skills; a clever demo does not replace them.

For international new grads, review the OPT and STEM OPT startup guide or the Canadian international-graduate jobs guide. As of November 2026, use the official USCIS OPT resource and IRCC PGWP resource to check your situation; conditions apply. Confirm your authorized start date and employer requirements with qualified guidance before promising availability.

Entry-level startup roles to search across eight functions

Pick one primary function and one adjacent function. Searching engineering, design, finance, and product simultaneously makes it harder to build convincing evidence. The table below suggests search terms and work samples, not verified current openings or guaranteed entry routes.

Read responsibilities before trusting “associate” or “founding” in a title. Look for a bounded task you could learn to own, with an experienced person available for feedback.

Turn coursework and projects into hiring evidence

Start with work you already have: a capstone, internship, campus job, research assignment, or volunteer project. Follow YC's what, how, and impact framework: explain the problem, your contribution, and the result. Our startup resume guide helps you organize that evidence.

Replace “completed a group project” with what you personally delivered. If the project never reached real users, say so. A tested prototype is useful evidence, but it is not a launched business or proof of revenue growth.

Illustrative resume bullets, with hypothetical numbers:

• Engineering: Built and deployed a campus-event signup tool using React and PostgreSQL; added 18 automated tests and documented setup for student-club maintainers.
• Business Analyst: Cleaned 2,400 rows in a public transit dataset using SQL; identified missing-value patterns and wrote a report explaining how they affected comparisons.
• Marketing: Created a student-club newsletter and signup page; recorded 46 registrations through tagged links across three sends and documented the measurement method.

Use your own verified numbers, not these examples. Counts of tests, records, or completed deliverables are legitimate when you can substantiate them. If you lack a credible metric, explain the output and a decision it informed instead.

For new work, build one small sample relevant to your target function. An engineer might automate CSV validation; an analyst might explain a public dataset; a marketer might draft an onboarding email sequence. Include the problem, artifact, your decisions, evidence of testing, and limitations. Use public or synthetic data, and never publish confidential internship work.

Find suitable jobs and set up a simple tracker

As of November 2026, YC Jobs lets you apply through one profile and allows founders to contact candidates. Startup Jobs provides experience, location, and workplace filters, including a 0–1 years experience option. Use these as discovery tools, then check the employer's career page before applying.

Search title variants such as “junior,” “new grad,” “analyst,” and “coordinator.” Limit results to locations where you can actually work. Treat “remote” as a prompt to check permitted countries and states, not permission to work from anywhere.

Unicorn Hunter emails a daily digest of startup jobs in the US and Canada, matched to your skills and interests by AI. If you use it, put relevant roles into the same tracker rather than keeping a separate inbox-only list. You still need to check each posting's experience requirements.

Create a spreadsheet with these columns:

Save the posting text because it may change. Add one row per role and deduplicate by employer URL. Log actions immediately so your weekly review reflects completed work, not intentions.

A 30-day new grad job search plan

The schedule below is a recommended workload, not hiring-market data or a promise of an offer. Every time budget and target is a planning suggestion. Aim for 35 suitable applications, 35 new outreach messages, 10 follow-ups, and one finished work sample; do not apply to unsuitable jobs just to reach the totals.

Week 1: Days 1–7, choose a target and prepare evidence

Daily budget: On days 1–5, reserve 120 minutes: 30 for research, 60 for evidence preparation, and 30 for applications, messages, or tracking. Reserve 60 minutes on day 6 and 30 on day 7. Targets: Five applications, five new messages, and a work sample with a defined scope.

• Day 1: Choose your primary and adjacent functions. Write down acceptable locations, earliest realistic start date, and work-arrangement limits.
• Day 2: Shortlist 15 employers or roles. Read their products and job descriptions; mark whether junior support is visible or needs clarification.
• Day 3: Rewrite your strongest project bullets. Scope one sample around a task that appears in your target postings.
• Day 4: Submit two tailored applications and send two relevant messages. Match your strongest evidence to each role's requirements.
• Day 5: Submit three applications and send three messages. Ask a former internship colleague or classmate for feedback on your sample.
• Day 6: Spend 60 minutes making the sample inspectable: a working demo, readable analysis, or campaign draft.
• Day 7: Spend 30 minutes reviewing the tracker. Remove poor-fit targets and choose next week's application queue.

Keep the project small enough to finish.

Week 2: Days 8–14, publish proof and build a routine

Daily budget: On days 8–12, use 120 minutes: 50 for applications, 20 for outreach, 40 for your sample, and 10 for tracking. Reserve 60 minutes on day 13 and 30 on day 14. Targets: Ten applications, ten new messages, and one published sample.

On each day from 8 through 12, submit two suitable applications and send two new messages. Give the sample work a daily focus: finish its core output on day 8, test it on day 9, document decisions on day 10, incorporate feedback on day 11, and publish on day 12.

On day 13, spend 60 minutes checking links, removing private data, and rehearsing a concise walkthrough. On day 14, spend 30 minutes reviewing responses and preparing the next queue. Fix broken evidence links before adding more applications.

Week 3: Days 15–21, follow up and practice explaining decisions

Daily budget: On days 15–19, use 120 minutes: 50 for applications, 20 for outreach and follow-ups, 40 for interview practice, and 10 for tracking. Reserve 60 minutes on day 20 and 30 on day 21. Targets: Ten applications, ten new messages, and five follow-ups.

On each day from 15 through 19, submit two applications, send two new messages, and follow up once on an older unanswered conversation. Skip a follow-up if the employer has given a timeline you should respect. Use the preparation block differently each day:

• Day 15: Rehearse your background and why this function interests you.
• Day 16: Explain your sample's hardest decision and an alternative you rejected.
• Day 17: Practice a role-specific task, such as SQL, debugging, or a design critique.
• Day 18: Run a mock conversation with a classmate or mentor.
• Day 19: Practice asking about supervision, onboarding, and team priorities.

On day 20, spend 60 minutes fixing the weakest answer or task from your mock. On day 21, spend 30 minutes reviewing which role types produced useful conversations. Do not interpret silence alone as a verdict on your ability.

Week 4: Days 22–30, refine the search and protect your time

Daily budget: On days 22–26, keep the same 120-minute split as week 3. Reserve 60 minutes on day 27, 30 on day 28, and 60 each on days 29–30. Targets: Ten applications, ten new messages, five follow-ups, and a clear next-cycle plan.

On each day from 22 through 26, submit two applications, send two new messages, and make one appropriate follow-up. Use each preparation block for an upcoming interview or a specific gap revealed by feedback. If an interview needs longer, reduce new applications rather than sacrifice preparation.

On day 27, compare active opportunities for supervision, work scope, location, and company stability. If none are active, use the hour to improve your target list. On day 28, reconcile your tracker and close stale entries.

On day 29, diagnose the bottleneck: weak fit, unclear evidence, unanswered outreach, or interview difficulty. On day 30, choose one change for the next cycle and schedule it. If you are balancing paid work or caregiving, halve the suggested volumes and preserve the same sequence.

Send outreach that connects your evidence to the job

Contact the hiring manager when you can identify them. A founder can be a sensible contact on a small team, but do not bypass instructions in the posting. Use a public professional contact channel, and avoid messaging several people at the same company simultaneously.

Illustrative outreach for a hypothetical startup with a published analyst role:

Subject: Analyst application and a CSV validation sample

Hi team,

I applied for your analyst role. Your posting mentions cleaning customer-import data, so I built a small CSV checker using synthetic records. It flags missing IDs and duplicate rows, with an explanation of the checks and limitations.

My capstone used SQL to investigate data-quality problems. The sample link is in my application, and I would be happy to explain the decisions behind it.

Would this background fit the analyst work your team needs?

Only mention a product feature or responsibility you actually verified. Change the evidence to match your real work; do not manufacture a company-specific project. The founder cold-email guide offers more help choosing a contact and writing the message.

Keep follow-ups brief; do not resend the project or demand an explanation for silence.

Check whether a startup can support your first job

An interview is also your chance to test the role. Ask who reviews your work, what onboarding involves, and what a successful first assignment looks like. Request an example of how the team helps someone who is stuck.

For a take-home, clarify expected effort, evaluation criteria, and whether the task uses synthetic or live company work. Do not let an open-ended assignment consume your entire search schedule. Ask whether a shorter exercise can demonstrate the same skills.

Before accepting, get the compensation and work arrangement in writing. Ask how the position is funded and what might change its scope. A broad title is less useful than a manager who can describe your responsibilities and provide feedback.

Next steps

1. Choose your primary function and locations today.
2. Create the tracker and add your first suitable roles.
3. Rewrite one existing project as evidence of useful work.
4. Schedule the first week's time blocks and start applying before the sample is perfect.