The 60-second answer
At 1 to 2 years, experience leads and academics shrink. Replace the fresher objective with a 2 to 3 line professional summary, put quantified work experience at the top, and move projects below it. Show impact with numbers (tickets resolved, features shipped, time saved), keep it one page, and if you are switching to a product company, lead with engineering depth and your strongest project. You are now selling what you have delivered, not what you studied.
The resume that got you your first job will hold you back on your first switch. Recruiters and hiring managers now expect evidence of impact, not potential. This guide covers exactly what changes after the fresher stage, how to quantify work from an IT-services or support role, and how to position yourself if you are aiming for a product company.
What changes after a fresher resume
| Element | Fresher | 1 to 2 years |
|---|---|---|
| Opening | Objective | 2 to 3 line professional summary |
| Top section | Education / Projects | Work experience (quantified) |
| Projects | Centrepiece | Supporting, below experience |
| 10th / 12th marks | Included | Usually dropped |
| Emphasis | Potential | Delivered impact |
The structure at 1 to 2 years
- Header: name, phone, email, city, LinkedIn, GitHub. Note your notice period if actively switching.
- Summary: 2 to 3 lines, your experience, core stack, and target role.
- Experience: your role(s) with 3 to 5 quantified bullets each. This is the heart of the resume now.
- Projects: 1 to 2 of your strongest, especially work outside your day job.
- Skills: grouped and current, matched to the roles you want.
- Education & certifications: degree, CGPA if strong, relevant certs.
Our makes the summary-first, experience-led layout easy, and the format guide helps you pick the right structure.
How to show impact from a services job
Services and support work is quantifiable if you look for the numbers:
Weak
Worked on bug fixes and support tickets.
Stronger
Resolved ~40 production tickets/month against a 24-hour SLA (98% met); automated a recurring data-fix script that cut manual effort ~6 hours/week for the team.
Look for volume, SLA/quality, time saved, defects reduced, and the scale of what you touched. See how to quantify achievements for 50+ examples.
Where your numbers come from
"Quantify everything" is easy to say and hard to do at your first job. Here is where the numbers actually hide, by the kind of work you do:
| If you do | Look for numbers in |
|---|---|
| Support / production | Tickets or incidents per month, SLA % met, mean time to resolve, uptime, escalations avoided |
| Development | Features or modules shipped, defects reduced, latency or load-time gains, test coverage added, release frequency |
| QA / testing | Test cases written or automated, regression time cut, bugs caught pre-release, coverage % |
| Data / reporting | Reports automated, hours saved per week, records or data volume handled, accuracy improvements |
You rarely have perfect metrics at 1 to 2 years, and that is fine. A careful estimate ("~40 tickets/month", "saved ~5 hours/week") is credible as long as you can explain how you got there.
A worked before-and-after
Here is a full experience block for a services engineer, rewritten from responsibility-speak into delivered impact.
Summary
Software Engineer with 2 years at an IT-services firm, building and supporting Java/Spring microservices for a retail-banking client. Delivered features across 3 modules, cut a recurring defect class by 60%, and automated a release step that saved the team ~5 hours a week. Targeting a backend role in a product team.
Before
- Worked on development and bug fixing for the client project.
- Attended daily standups and followed the process.
- Was part of the release team.
After
- Built 6 REST endpoints in the payments module (Java, Spring Boot), serving ~50k transactions/day in production.
- Cut a recurring validation-defect class by 60% by adding input checks and 30+ unit tests.
- Automated the pre-release smoke check in Python, removing ~5 hours of manual QA per release.
Same job, same two years. The "after" version just names what was built, how much, and to what effect, and that is the entire difference between a fresher-shaped resume and a switch-ready one.
Positioning for a switch to product
If you are moving from services to a product company, the resume should read like an engineer's, not a ticket-closer's. Lead your summary with your strongest engineering work, surface a substantial project (ideally outside your day job), show DSA and system exposure, and tailor your skills to the target stack. Add your coding-profile links. Pair this with a referral (see the referral templates) for the best shot.
5 mistakes to avoid
- Keeping a fresher objective. Switch to a professional summary.
- Listing responsibilities, not results. Quantify every bullet you can.
- Leading with academics. Experience goes on top now.
- A stale skills line. Update it to the stack you actually use and target.
- Spilling to two pages. One page. Cut the weakest content first.
Frequently asked questions
How is a 1 to 2 year experience resume different from a fresher one?+
Experience leads, not academics. You swap the fresher objective for a 2 to 3 line professional summary, put your work experience at the top with quantified bullets, and move projects below it. Coursework and long skill dumps shrink; measurable impact grows. The resume now argues "here is what I have delivered", not "here is what I studied".
Should I still show my 10th and 12th marks after 1 to 2 years?+
Usually you can drop them. Keep your graduation and, if strong, your CGPA. Some Indian IT-services roles still ask for 10th and 12th, so keep them handy, but on the resume itself, prioritise experience over school marks once you have real work to show.
Should a 1 to 2 year resume be one page or two?+
Still one page. At 1 to 2 years you do not have enough to justify two, and a tight one-page resume reads as focused. Cut older or weaker content before you spill onto a second page.
How do I show impact from a services or support job?+
Quantify. Tickets or incidents resolved, modules or features delivered, defects reduced, SLA or uptime met, automation that saved time, the size of the team or system you worked on. Even "automated a weekly report, saving ~4 hours a week" beats a list of responsibilities.
Should I use an objective or a summary?+
A summary. At this stage an objective ("seeking a challenging role") reads as junior. Use a 2 to 3 line professional summary that states your experience, your core stack, and what you are targeting, for example "Software Engineer with 2 years in Java/Spring microservices, seeking a backend role in a product team".
How do I position for a switch from services to a product company?+
Emphasise engineering depth: your strongest project, DSA and system exposure, and measurable impact rather than process. Tailor the skills line to the target stack, add coding-profile links, and lead with the work that looks most like product engineering. A referral plus this positioning goes a long way.
My company or client name is not well known. Does that hurt?+
Not much. Recruiters care more about what you built and the stack you used than the brand on your payslip. Name the client domain (banking, healthcare, retail) and the technology, and let the quantified work carry it. If the client is under NDA, describe the domain generically, for example "a large retail-banking client", and focus the bullets on your contribution.
Should I put my notice period on the resume?+
If you are actively switching, yes, a short line helps. Add "Notice period: 30 days" (or your actual number) to the header or summary, because many Indian recruiters filter on it early. Keep it small; it is a detail, not a headline. If you are on a buyout or can negotiate, you can note that in the conversation rather than on the page.
How many bullets should each role have?+
Three to five for your current or most recent role, two to three for anything older. Every bullet should earn its place with a result or a number. If a bullet just restates a responsibility ("attended standups", "followed the process"), cut it, that space is better spent on something you delivered.
Rebuild your resume for the switch
Free to start, no sign-up. A summary-first, experience-led, ATS-tested layout that shows what you have delivered.