How to Write a Job Description for Freshers

A fresher reading your job description is asking three questions: can I do this, what will I learn, and what will I earn? Most JDs answer none of them clearly. They list ten "requirements", ask for "1-2 years of experience" for an entry-level role, and hide the salary. The result is either very few applicants or hundreds of irrelevant ones. This guide shows how to write a JD that pulls in the right freshers and filters out the wrong ones without extra screening effort.

The structure that works

Keep a fixed order so candidates can scan it in under a minute:

Title that matches what people search for, plus level: "Junior Data Analyst (Fresher)", not "Data Ninja".
Two-line summary of the team and why the role exists.
What you will do: four to six concrete responsibilities.
Must-have: three to five genuine requirements.
Nice-to-have: skills that help but will not rule someone out.
What you will learn: tools, mentoring, exposure.
Pay and terms: CTC or stipend, location, work mode, start date, duration for internships.
How to apply and what happens next: steps and a rough timeline.

If you want a ready shell, use the internship job description template or generate a draft with the JD generator, then edit it with the rules below.

Write responsibilities as real tasks

"Assist the team with various tasks" tells a fresher nothing. Describe the work at the level of a normal week: "Write test cases for new features and log bugs", "Call 30-40 inbound leads a day and update the CRM", "Prepare the weekly sales report in Excel". Concrete tasks help candidates self-select, which saves you screening time. They also make interviews easier, because you can test exactly those tasks. A useful test: if a current team member read the list, would they recognise their own week? If not, rewrite it. Add a line about who the fresher will work with day to day, since mentoring is one of the main things entry-level candidates look for when comparing offers.

Separate must-have from nice-to-have

This is where most fresher JDs go wrong. Every item you list as required removes applicants, and freshers tend to take lists literally. Be strict about what is truly required on day one.

Role	Must-have (example)	Nice-to-have (example)
Fresher software developer	One programming language well, basic data structures, Git	A framework such as React or Spring, cloud basics
Data analyst fresher	Excel formulas and pivots, basic SQL	Power BI or Tableau, Python
Marketing intern	Clear written English or the relevant regional language, social media familiarity	Canva, basic SEO, an existing blog or page
Sales fresher	Comfort with calls and field visits, local language	Two-wheeler and licence, CRM familiarity

For more role-specific wording, see our ready JDs for a software intern, marketing intern, sales intern, data science intern and HR intern.

Drop "experience required" from fresher roles

Asking for "1-2 years of experience" in a fresher role is the most common contradiction in Indian job posts. It confuses candidates and discourages the very people you want. If you need some exposure, ask for evidence instead: "at least one project, internship or freelance assignment in this area". That lets final-year students, recent graduates and self-taught candidates qualify on what they have done rather than on time served. Similarly, be careful with rigid cut-offs like a minimum percentage unless the role truly needs it; they filter on college marks, not ability.

Be open about pay

State the stipend or the CTC range. For freshers, pay is often the deciding factor between two similar offers, and a hidden salary leads to late-stage drop-outs when expectations do not match. A range such as "₹3.0-3.6 LPA depending on skills" is enough. If there is a variable component, say how it is calculated. For interns, state the monthly stipend and payment date; the stipend calculator helps you pick a figure, and our post on stipend benchmarks by role gives indicative ranges.

Use inclusive, plain wording

Avoid gendered or age wording ("young and dynamic", "he will"). Describe the work, not the person.
Avoid jargon and internal team names a student will not know.
Do not ask for a specific college or "tier-1 only" unless you have a real reason; talent is spread widely, as our tier-2 city hiring page explains.
Mention flexibility you genuinely offer: remote days, exam leave, part-time options. If the role can be done from anywhere, say so; it widens your pool considerably, as the work-from-home intern page explains.
Keep sentences short. Many candidates read JDs on their phones.

A JD skeleton you can copy

Title: Junior [Role] (Fresher) or [Role] Intern, [City or Remote]
About the role: [Team] at [Company] is hiring a fresher to [main outcome]. You will work with [mentor role] on [what they will build or handle].
What you will do: four to six weekly tasks, written as actions.
Must-have: three to five items, each testable in an interview or task.
Nice-to-have: two to four items.
You will learn: tools, processes, mentoring, customer exposure.
Pay and terms: ₹[stipend]/month or ₹[x-y] LPA; [location]; [work mode]; start [date]; [duration].
Process: application, short task, one or two interviews, offer within [n] days.

Two examples of the skeleton filled in: for a web role, see the web development intern JD; for a client-facing role, the business development intern JD. Notice how both describe weekly tasks rather than personality traits, and how each must-have maps to something you can check in a short task.

Before you publish: a quick checklist

Does the title match what a candidate would type into search?
Can every must-have be checked in the interview or task?
Is pay stated as a number or range?
Is location and work mode unambiguous?
Is there any "experience required" line left in a fresher role?
Have you added one or two screening questions tied to the must-haves?

When it passes, post the job for free or post an internship; our guide on posting a job for free covers the posting itself. Once applications arrive, move on to screening fresher resumes. If you are hiring many freshers at once, the fresher hiring checklist and the fresher hiring page are good companions.

Frequently asked questions

How long should a fresher job description be?

Aim for something a candidate can read on a phone in about a minute: a short summary, four to six responsibilities, three to five must-haves, a few nice-to-haves, pay, location and the process. Length matters less than clarity.

Should I mention salary in a fresher job description?

Yes. Stating a stipend or CTC range attracts candidates whose expectations match and reduces late-stage drop-outs. A range is fine if the final figure depends on skills.

Is it wrong to ask freshers for experience?

Asking for years of experience in a fresher role is contradictory and discourages good applicants. Ask for evidence instead, such as a project, internship or freelance assignment relevant to the role.

Can I use an AI tool to write my JD?

A generator is useful for a first draft, but always edit it: replace generic lines with your real weekly tasks, cut the must-have list down to what is truly required, and add the actual pay and location.

More hiring guides

Ready to hire? Tell us what you need on Hire Talent, post a job for free, or browse more employer templates and checklists.

How to Write a Job Description for Freshers That Attracts the Right Applicants