Biodata, resume or CV: which one is the employer actually asking for?

Three words, four documents, and a confusion that is not your fault

In India the words biodata, resume and CV are used loosely enough that none of them tells you what document is wanted. The same person can be asked for a biodata twice in one week and mean two entirely unrelated pages: a marriage broker asking for a biodata wants gotra, rashi and what your father does; a workshop supervisor asking for a biodata wants your qualifications, your date of birth and a signature at the bottom. Neither is being careless. The word genuinely carries both meanings, and which one is meant depends only on who said it.

It helps to stop arguing about definitions and look at what is physically printed on each page. A marriage biodata carries a photograph, personal details down to complexion and diet, religion, caste and gotra, rashi and nakshatra and whether you are manglik, then your family — your father’s occupation, your mother’s, your siblings — an About Me paragraph in your own voice, and a Partner Expectations block. A job biodata carries a photograph, father’s and mother’s name, date of birth, gender, marital status, nationality, languages known, permanent address, then education with marks and years, whatever work there is, and a signed declaration. A resume carries none of those personal rows at all: it opens with what you do and what you have delivered, and it never mentions your father, your date of birth or your marital status.

The distinction that matters most is the last one, because it is where people lose interviews without ever knowing why. If you are applying through a company’s careers portal or a job site, you want a resume, not a biodata — and PaperKit’s resume builder is where that one is made. Documents submitted that way are usually read by an applicant tracking system before a human sees them, and that software is looking for job titles, dates and skills in a shape it can parse. A tabular sheet that opens with your father’s name gives it nothing to work with, and personal details that a resume deliberately omits can quietly count against you at the screening stage in ways nobody will ever tell you about.

The reverse mistake is just as common and slightly more embarrassing. Sending a two-page achievement-led resume to a small firm that asked for a biodata, or to a school office that keeps a staff file, leaves the person on the other side hunting for a date of birth and a father’s name that are not there, and they will hand it back and ask you to fill in their own proforma. Neither document is better than the other. They are answers to different questions, and the only real skill is telling which question has been asked.

The same person, row by row, in each document

Rohit’s biodata has about nine kinds of information on it. Here is what each of the three documents does with the same nine — what it prints, what it leaves out, and why the omission is a decision rather than an oversight.

1. 01

   The photograph

   A passport photograph in the top corner, and whether the document is supposed to carry one at all.

   Both biodatas carry a photograph, and for the same practical reason: they are documents that get printed, handed across a counter and put in a file, and the photograph is how the page stays attached to the person. A marriage biodata’s photo is chosen carefully and is often the first thing looked at. A job biodata’s is a plain 35×45mm passport photograph, face square to the camera, on a light background — the same photo you would affix to a form.

   A resume is the odd one out, and Indian practice is genuinely split. A photograph is expected on resumes for airline cabin crew, hospitality, retail floor roles, modelling and some front-office jobs, and it is expected at many campus placements because the college proforma asks for it. For everything else — software, accounts, sales, analytics, most private-sector office work — the safer default is no photograph, because it takes up space that a result could occupy and because a photograph gives a screener a piece of information the shortlist has no business turning on. If the listing asks for one, attach it. If it does not, the space is better spent.

2. 02

   Father’s name and mother’s name

   The row that most reliably tells you which of the three documents you are holding.

   On Rohit’s biodata these are the first two rows: Shri Anil Deshmukh and Sau. Manisha Deshmukh, with the honorifics written out. On a marriage biodata they appear too, but with occupations attached — what the father does, what the mother does — because the family is part of what is being proposed. On a resume they do not appear at all, in any form, under any heading.

   That last point is worth stating flatly because it is the single most common defect in Indian resumes and it is almost never corrected. A parent’s name on a resume is information the employer cannot legally use and will not want to be seen holding, it occupies the top of the page where your strongest claim should be, and to a recruiter used to reading resumes it marks the document as a biodata that has been renamed. If a form later asks for your father’s name — and joining formalities almost always do — you give it then, on the form.

3. 03

   Date of birth, and the age it gives away

   A row that is compulsory on one document, conventional on another and quietly harmful on the third.

   A job biodata prints the date of birth — 14 August 2003, written out rather than in digits so that nobody has to guess whether 08/14 or 14/08 was meant. It is on the page because the forms this document feeds into ask for it: age limits are real in government-adjacent recruitment, apprenticeship schemes have upper age bounds, and a school or hospital office keeping a staff file needs it. Note that the age itself is not printed, only the date, because an age written on a document goes stale the moment the file is saved.

   A resume leaves it off. A recruiter reading a resume can work out roughly when you graduated from the years next to your qualifications, which is all they need, and a date of birth at the top of a resume invites a filter that has nothing to do with whether you can do the work. Leave it off unless a listing explicitly asks — and government notifications routinely do, which is exactly when the biodata is the right document anyway.

4. 04

   Marital status, gender and nationality

   Three rows that a job biodata prints as a matter of course and a resume has no place for.

   Rohit’s sheet says Unmarried, Male, Indian, one row each. On a job biodata these are ordinary and expected: they mirror the fields on the proforma the employer would otherwise hand you, and a page that omits them looks incomplete to the person filing it. On a marriage biodata the marital status row carries far more weight and is often more specific — unmarried, divorced, widowed — because it is the first thing a proposal is assessed on.

   On a resume, all three are noise. Nationality is assumed unless you are applying for a role that requires a work permit, in which case one line about your right to work in that country belongs at the bottom, not the top. Gender is visible from your name in most cases and irrelevant in all of them. Marital status is the one that does active harm, particularly for women applying in India, and there is no upside to volunteering it.

5. 05

   Languages known, and the permanent address

   Two rows that survive onto a resume, but in a different form and for a different reason.

   The biodata formula is the familiar one: Marathi, Hindi, English, with the bracket that says read, write, speak. It is written that way because employers who ask for a biodata often need a specific one of the three — a firm that needs Marathi correspondence written, not merely spoken, is asking a real question. Keep the bracket, and be honest inside it: read and write is a claim someone can test in ninety seconds.

   A resume keeps languages only when they are relevant to the work, and then usually as one line near the bottom rather than a headline row. The address is the sharper difference. A job biodata prints the full permanent address, house number included, because the document doubles as a record. A resume prints the city and state and stops there — Nashik, Maharashtra — because location on a resume exists to answer one question, which is whether you are where the job is, and a house number answers nothing while sitting in a file that gets forwarded.

6. 06

   Education, and what to do about the marks

   The one block all three documents carry, and the one where the difference is emphasis rather than presence.

   Rohit’s education runs newest first — B.Com with an aggregate of 68.4%, then HSC Commerce at 72.6%, then SSC at 81.2% — with the college, the board or university and the years for each. That is the job biodata convention, and the marks are expected, right down to the SSC line. A fresher’s biodata leads with this block because there is nothing stronger to lead with, and a screener at a small firm reads it as a proxy for whether you will be reliable at a desk.

   A resume gives the degree, the institution and the year of completion, and treats marks as optional. Give them where they are strong or where the listing asks for a cut-off — many firms do screen freshers on a percentage — and drop the school lines entirely once you have three or four years of work behind you, because they take space from something the employer actually asked about. The rule of thumb: the further you are from graduating, the more of this block disappears from a resume, while a job biodata keeps every line for as long as you use it.

   A marriage biodata compresses the whole thing into a single Qualification row — degree, institution, year — because the family reading it wants the level, not the transcript.

7. 07

   Work: posts held, against results delivered

   The block where the two documents stop being different arrangements of the same facts and start saying genuinely different things.

   A job biodata records posts held. Designation, organisation, dates, and one or two lines of what the work involved: on Rohit’s sheet, entering purchase and sales vouchers in Tally Prime for a wholesale grain firm, and matching the monthly GSTR-1 register against the cash book. It reads as a record of employment, which is what it is, and a supervisor scanning it is checking that you have done this kind of work before and are not exaggerating about it.

   A resume argues. The same six months become two or three bullets written as outcomes — what changed, by how much, for whom — chosen for this particular listing and ordered so the most relevant one is first. That is why a resume is rewritten for each application and a biodata is not: a biodata is a record and a record does not change, while a resume is a case and the case changes with the job.

   A marriage biodata has one Occupation row and one Organisation row, and adds one the others never carry — annual income — because that is a question the family will ask anyway and a biodata answers it before anyone has to.

8. 08

   The professional summary and the declaration: the two blocks that swap

   Each document opens and closes in a way the other one does not, and this is where the two are least interchangeable.

   A resume opens with a professional summary: two or three lines that say what you are, what you have done and what you are looking for, written so that a reader who gets no further still knows why you applied. A job biodata has nothing in that position — the top of the page is your name, a one-line subtitle and the personal details block. Rohit’s subtitle line, “B.Com (2025) · Applying for Accounts Assistant”, is as close as the document comes, and it is a label rather than an argument.

   At the other end, a job biodata closes with a declaration: that the information above is true to the best of your knowledge and belief, followed by the place, the date and your signature. That block is what turns a list into a statement, and a government-adjacent form will look for it. A resume has no declaration, and the Indian habit of adding one is a habit worth dropping — it spends three lines at the foot of the page saying something nobody doubted, on a document that is rarely printed and never signed.

9. 09

   The rows that belong only to a marriage biodata

   The clearest test of all: if the page has any of these on it, it is not a job document and must not be sent as one.

   Gotra. Rashi and nakshatra, with the charan. Whether you are manglik, and the gan and nadi that go with the nakshatra. Height, complexion, blood group and diet. Family type. Native place. An About Me paragraph written in the first person. A Partner Expectations block saying what you are looking for in a match. Not one of these has any business on a document going to an employer, and several of them — caste and gotra in particular — are information an employer should never be handed unasked.

   This matters because the two documents share a name and a shape, and a family that already prepared one has a finished page sitting on a phone. Sending it to a firm because it is the file that says “biodata” is a mistake people make every week. If yours has a rashi on it, it is the wrong document for the job, whatever the file is called.

Questions people actually ask