Declaration in Resume: Needed or Outdated?

The declaration line — "I hereby declare that the above information is true to the best of my knowledge" — sits at the bottom of countless resumes, copied from a template that was old a decade ago. Freshers keep it because they have always seen it, not because anyone asked for it. So here is the straight answer: for modern IT and software roles it is optional and largely outdated, and in almost every case that space is better spent on something that actually helps you get shortlisted.

This guide gives you the clear rule, the few genuine exceptions, and what to do with the space instead.

The short answer

Drop the declaration for most software and IT applications. Recruiters do not expect it, do not read it, and do not think less of a resume that omits it — if anything, a clean modern resume without one reads as more current. The declaration adds no information a hiring manager needs. Your resume already implies that its contents are true; a formulaic sentence restating that changes nothing.

Why it became outdated

The declaration is a holdover from an era of paper resumes and formal application conventions, where a signed statement felt procedurally necessary. Modern hiring runs through job portals, ATS databases and quick recruiter scans. In that flow, a closing declaration is noise. Recruiters spend their seconds on your summary, skills and projects — never on the declaration. Keeping it does not hurt you much, but it almost always displaces something that would help.

The genuine exceptions

There are real cases where you should keep it:

KEEP the declaration when:
- A specific job posting or employer explicitly asks for one
- Applying via government / PSU / defence forms that require it
- Regional or academic convention in your context still expects it
- A formal, non-IT sector where it remains standard practice

In these cases, include it — but keep it to a single clean line. The exception is about compliance with a specific requirement, not about resume quality.

The correct format, if you need one

When a declaration is genuinely required, minimal is correct:

BLOATED (wastes 4-5 lines)
DECLARATION
I hereby solemnly declare that all the information furnished
above is true, complete and correct to the best of my knowledge
and belief. I bear the responsibility for the correctness of the
above-mentioned particulars.

Place: Hyderabad
Date:  16/07/2026
                                        (Signature)
                                         Ravi Kumar

CLEAN (1-2 lines)
I declare that the information above is true to the best of my
knowledge.                              16/07/2026 - Ravi Kumar

The clean version satisfies any real requirement without eating a quarter of the page. Place it at the very bottom, after education and certifications.

What to put in that space instead

The real value of this question is what the freed-up space can hold. For a fresher especially, every line should earn shortlisting. Better uses:

INSTEAD OF a declaration, add:
- One more strong project bullet with stack + outcome
- A relevant certification (e.g. Java Full Stack - CodeBegun)
- Two or three more defensible skills
- A GitHub or portfolio link if not already prominent
- A concise achievement (hackathon, contribution, award)

On a one-page fresher resume — which is what you should have, per the one-page vs two-page guide — those lines are precious. A project bullet that proves you can build something does far more work than a sentence swearing your resume is honest.

Declaration versus other outdated blocks

The declaration usually travels with other stale elements. If you are removing it, clear the rest of the same era at the same time:

ALSO drop (usually outdated for IT freshers):
- "References available on request" (assumed)
- A vague career objective ("seeking a challenging role...")
- Full postal address (city is enough)
- Marital status, father's name, nationality (unless legally required)
- Hobbies that add nothing relevant

Removing these is not just tidying — it modernizes the whole document and frees space for evidence. The fresher resume format guide shows the current, lean structure to aim for.

Does it affect the ATS?

The declaration is harmless to parsing — it is just text at the bottom. The cost is never the ATS; it is the opportunity cost of the space and the slightly dated impression on a human reader. So this is a judgment call about relevance and modernity, not a technical formatting rule like single-column layout.

Common mistakes

- Keeping a 4-5 line declaration with a signature block by default
- Adding it "just to be safe" on a modern IT resume
- Letting it push a project or skill off a one-page resume
- Pairing it with other stale blocks (references, objective, personal details)
- Omitting it when a specific form actually required it

Your declaration checklist

[ ] Modern IT/software role, no explicit request? -> omit it
[ ] Specific form/employer requires it? -> keep ONE clean line
[ ] Freed space reused for a project, cert, skills or links
[ ] Other outdated blocks removed at the same time
[ ] Resume stays one page (fresher) and lean

The declaration is a small decision, but it is a useful test of whether you are building a modern, evidence-first resume or copying an old template out of habit. Spend the freed space on proof of what you can build. If your projects section is thin and you are unsure what to put there instead, a structured program that builds real, reviewed projects gives you material worth the space — and a free CodeBegun counselling session can help you plan the path.