How Do I Write My Resume After an IT Layoff in India?

Being laid off from an IT services or product company is common, and recruiters in India know it. What they look for on the resume is not a reason. They look for clear dates, a believable story and recent proof that you can do the job they are hiring for.

This guide covers resume presentation only. It does not advise on notice pay, severance, resignation letters or your rights under your contract. For those questions, read your own documents and speak to HR or a qualified adviser.

The short answer

• Last role: keep your official title, employer name and dates exactly as your relieving or experience letter shows them.
• End date: use your last working day or the relieving date on your letter. Do not stretch it to cover the months since.
• The gap: if it is a few months, you can leave it as it is. If it is longer, add one short dated line saying what you did.
• Contract or freelance work: list it as its own entry, with the client type, dates and what you delivered.
• The reason you left: optional on the resume. Answer honestly when a form or interviewer asks.

Your last role: dates and title as they are

Your last role is still your strongest evidence. The layoff does not erase the work.

Write the entry as you would if you had resigned for a better offer: official designation, employer, location, and month and year of joining and leaving. Then three to five bullets on what you owned and what changed because of your work.

Two things matter more after a layoff than usual:

• Consistency with your documents. Employers in India often verify employment through relieving letters, experience letters and background checks. Your resume dates should match what those documents will show. Our Naukri profile vs resume article explains how to keep one factual record across every surface.
• Your actual title. If your team called you "tech lead" but your letter says "Senior Software Engineer", keep the official title. Describe the lead work in your bullets instead.

Notice period, garden leave and your last working day

Layoffs in Indian IT happen in different ways. Some people serve a notice period. Some are asked to stop working at once and are paid for the notice period instead. Some stay on the payroll for a while without working, which people often call garden leave. Some receive a severance amount after exit.

For the resume, the rule is simple. Your end date is the date your employer's documents give as your last day of employment. That is usually the last working day or relieving date. It is not the date a severance or notice payment ends, unless your letter says so. If you are unsure which date your letter will show, ask HR before you update your resume. Do not guess.

If you are still in a notice period or on garden leave, "Present" is accurate while you are employed. When your relieving date is fixed, you can say so in one line, for example: "Available from 1 November 2026." The CTC and notice period guide covers when that line helps. How you describe your notice period is your choice. Keep it true.

The gap since you left

A gap of a few months after a layoff needs no explanation on the page. Recruiters see month-and-year dates and understand that a job search takes time.

A longer gap is easier to read with one dated line. Keep it factual and short. For example:

• "Career break, Mar 2026 – present: job search after role elimination; completed AWS Solutions Architect Associate (Jun 2026)."
• "Family responsibilities, Jan – Jul 2026."

Do not turn the gap into an invented job or a list of every course you started. One or two relevant items are enough. If the break has run long, the return-to-work resume guide goes further.

Contract or freelance work in between

Short contracts and freelance work count. List them as a normal entry, not hidden inside the gap line.

• Name the arrangement honestly: "Freelance", "Contract via" and the agency name or "Consultant". If a staffing firm paid you, that firm is usually the employer on paper. Say so, and name the client only if your agreement allows it.
• Give real dates, even if the work lasted six weeks.
• Show what you delivered: a migration finished, a feature shipped, a dashboard the client still uses.

Do not blend a contract into your previous employer's dates to make one long, unbroken job. It will not match your records.

Illustrative example: one entry, before and after

This is a fictional example for teaching. Nandini is a backend developer with six years of experience. Her role was eliminated in a restructuring. Her last working day was 14 March 2026. She then did a two-month freelance contract.

Before

Senior Software Engineer, Product Company, Bengaluru · Jul 2022 – Present

• Worked on payment services
• Laid off in March 2026 due to restructuring, not performance related

After

Senior Software Engineer, Product Company, Bengaluru · Jul 2022 – Mar 2026

• Owned the refunds service (Java, Spring Boot, Kafka) handling merchant refunds across three payment methods
• Cut failed-refund retries by redesigning the idempotency checks; on-call pages for the service fell in the following quarter
• Mentored two junior engineers through their first production releases

Freelance Backend Developer · May 2026 – Jun 2026

• Built a webhook retry service for a small e-commerce client in Node.js; handed over with runbooks

What changed: the end date now matches her documents. The "Present" that was no longer true is gone. The defensive line about performance is off the resume and saved for the interview, where she can say it in her own words. The contract has its own dates. Every bullet shows a result, and no figure is invented.

Reframe for the next role

After a layoff you may aim at a slightly different role. The facts stay the same. What changes is which facts come first.

• Rewrite the summary for the target role. Two lines: role, years of experience, and the two or three skills that job post asks for.
• Reorder bullets. Lead with the work closest to the new role. A services engineer moving to a product company can lead with ownership and technical decisions; our service to product company article shows how.
• Refresh the skills list. Keep only what you can discuss in an interview. Add anything you genuinely learned during the gap.
• Make one version per type of role, not one per company.

What not to hide

A resume can leave things out. It cannot state things that are untrue. After a layoff, the common mistakes are:

• Keeping "Present" after your last working day.
• Moving your end date forward to cover the gap.
• Claiming a promotion or title you did not formally receive.
• Listing freelance work that did not happen, or a client you cannot name if asked.
• Stating a notice period or joining date you cannot actually meet.

Each can surface in a background check or interview. One wrong date raises doubts about the whole page.

A checklist before you send it

• Title, employer and dates match your relieving or experience letter.
• The last role ends on your last working day, not "Present", unless you are still employed.
• Any gap longer than a few months has one short, factual dated line.
• Contract or freelance work has its own entry and real dates.
• Your summary names the role you are applying for now.
• Your Naukri and LinkedIn dates match the resume.
• The reason for leaving is ready for the interview, in one calm sentence.

If you have an older resume file, you can import it into the Guul builder and update the dates and bullets there rather than retyping everything. Before you send each version, Guul's resume checker explains each finding in plain words, and you can tailor a copy to a specific job description. Neither can promise a call. What they help with is a clean, accurate page.

Then send it. Keep your records consistent, and give each application a version aimed at that role.