First Circuit

Searching for a first job without work experience

By First Circuit Editorial · · 3 min read

"Entry level, 2–3 years of experience required" is one of the most discouraging lines a graduating student can read. It is also less final than it looks. This guide covers what counts as experience, how to read requirements, and how first-job searches differ from internship searches.

Internships and first jobs are different searches

InternshipFirst job
TimingOften recruited months ahead, tied to a summer or semesterYear-round; timing varies by employer
What the employer is buyingPotential and a trial periodSomeone who can do a defined job soon
Where they're postedCampus boards, program pagesEmployer career pages, general boards, referrals
Typical labelsIntern, co-op, summer analyst, fellowAssociate, coordinator, assistant, analyst I, new grad

Some first-job openings close soon after they appear, so as a practical habit, check your target employers often and apply promptly when a good role opens.

What counts as experience

Employers hire for skills and reliability. Paid work in your field is the most obvious proof, but it is not the only kind. Make an inventory before you write anything:

  • Coursework with real output: a capstone, a lab, a research paper, a case competition, a studio critique.
  • Part-time jobs of any kind. Retail, food service, tutoring and campus jobs show you can turn up, handle customers, manage time and handle money or records.
  • Volunteering and clubs, especially where you were responsible for something: a budget, an event, a schedule, a newsletter.
  • Independent projects: a small website, a dataset you cleaned and analyzed, a series of illustrations, a podcast.

For each item, write one sentence about what you did and one about the result. "Scheduled 14 tutors across three shifts each week" says more than "strong organizational skills." NACE's career-readiness competencies, such as communication, teamwork and professionalism, are a handy checklist for spotting what an item demonstrates.

Required versus preferred

Sort each line of a posting into three groups. Required: what the posting says you must have, such as a degree, license, schedule or work authorization. Preferred: what it labels as preferred, a plus or nice to have. Unclear: anything the posting doesn't label either way.

  • Never quietly treat a required item as optional. If you don't meet it, skip the role or ask the recruiter before applying.
  • If an item is unclear, ask the recruiter or hiring contact how strictly it applies, or read it as required.
  • For preferred items, apply if you meet the requirements and can show some of them.

Coursework, part-time jobs and volunteering can show the skills a posting describes, but they aren't automatically the same as professional experience. If a role requires "two years of professional experience," describe what you've done accurately and let the employer decide, or ask first.

Skip roles that are clearly senior: managing a team, owning a budget, or titles like senior, lead or manager. Applying to these mostly wastes your time.

Be honest in applications. Do not claim a degree, certification or level of skill you do not have. Requirements like licenses or work authorization are real filters, not suggestions.

Build a target list

A target list is a set of thirty or so employers you would be glad to work for, grouped so you can see where you are spreading your effort. A simple version has three groups:

  1. Reach: well-known organizations with structured new-grad programs. Apply, but don't rely on them.
  2. Fit: mid-sized employers in your field and region, where your coursework and projects line up closely with the work.
  3. Local and overlooked: small firms, hospitals, school districts, manufacturers, nonprofits and local government. They hire graduates too and may get less attention from students.

Check each employer's own careers page once a week. When a relevant role opens, you'll already know the organization well enough to write a specific application.

Make your applications specific

For each application, choose the two pieces of evidence that match the posting best and lead with them, in your resume summary or the first lines of an email. Keep a short master document of your accomplishments so tailoring takes ten minutes, not an hour.

If you're invited to interview, prepare a short story for each piece of evidence: the situation, what you did, and what happened. Interviewers for first jobs often care more about how you think through a problem than about the exact tools you used.

Keep it sustainable

First-job searches can take months, and responses are uneven. Set weekly goals you control, such as applications sent, follow-ups done or one new project milestone, rather than outcomes you don't. People you meet during the search can point you to roles you wouldn't find otherwise, so keep talking to people in your field even when it feels slow.

Sources and further reading

Practice the interviewTry a sample mock interview with Sloane and see the feedback that improves an answer.