Librarian Resume Format, with 3 Full Samples

The format that works for librarian resumes in India

Reverse chronological is the layout to use. Put the most recent library post first, work backwards, and let the dates show. Functional resumes that group everything under Skills and drop the dates read as an attempt to hide a gap or a short tenure, and academic selection committees, who read carefully, treat them that way. Length is decided by evidence. One page holds everything a fresher and most professionals up to roughly six or seven years have to say. A deputy or university librarian with a real publication record, accreditation work and department leadership earns a second page, and sometimes a short list of publications on it. A page two padded with a hobbies paragraph is a one-page resume in disguise. For an academic post, the eligibility facts have to be visible fast, because a committee screens against UGC norms before it reads your achievements. Put your qualifying degree, UGC NET or SET status, and any PhD where they cannot be missed. A brilliant repository project does not help if the reviewer cannot confirm you clear the eligibility bar. Four things belong nowhere on the resume: a photograph, date of birth, marital status and father's name. They survive from an older template that circulated through placement cells. A school or university library committee is not screening for them, and every line they occupy is a line a project or a result could have used. Send a PDF unless the posting asks for DOCX, keep to a single column, and name the file with your own name and the post. The table below sets out the section order.

Naming Koha is not the same as proving you ran it

The most common librarian resume failure is a skills line that reads Koha, SOUL 2.0, LibSys, DSpace, Greenstone, KOHA, DDC, UDC, CC, MARC21, RDA, AACR2 with no bullet anywhere that shows any of it in use. A parser matches those terms, but a human reviewer reads the wall and assumes it is a course syllabus copied onto a resume, then goes looking for the one system you can actually administer. The fix is to let the experience prove the tools. If you write Koha, a bullet should say what you did in it, catalogued a number of titles, migrated a catalogue, set circulation rules, ran the reports. If you write DSpace, a bullet should describe the repository you built or maintained and how big it grew. The assistant sample lists Koha administration and DSpace precisely because the bullets show a migration, a stock reconciliation and a repository. The skills line and the work agree, which is what makes both believable. Be specific about the classification scheme and cataloguing standard you actually use, because it signals the kind of library you come from. Dewey Decimal is standard in most Indian school and college libraries, UDC and Colon Classification appear in some universities and research libraries, and MARC21 with RDA or AACR2 is the metadata layer. Naming the right one for the target library tells a committee you will fit their practice, not that you memorised every scheme for an exam. Do not list a system you touched once in a lab class as a core skill. If your only Koha exposure was a demo, say Koha (familiar) or leave it off, because an interviewer who asks you to add a MARC field on a screen share will find out in a minute.

For every system on your skills line, ask: is there a bullet that proves I ran it. If not, either add the bullet or move it to a familiar-with line. A wall of unproven library software helps the parser and hurts the interview.

Writing a summary a selection committee actually reads

The block under your name is the part you can be reasonably sure gets read, so it should carry three facts: what kind of library you run, how long you have been running it, and the strongest thing that happened because of your work. Three or four lines, no adjectives a reference check cannot confirm. The old objective line, seeking a challenging position in a reputed institution to utilise my library science knowledge, tells a committee nothing it did not already assume. Replace it with a summary. An objective describes what you want, a summary describes what you have already done, and only one is evidence. Freshers often think they have nothing to summarise. Look at the fresher sample: it names the type of library, the internship length, and points at a real cataloguing backlog cleared and a borrowing lift. That is a genuine summary built from a BLIS, one internship and hands-on Koha work. What it avoids is "passionate about books and knowledge", a phrase so common on library resumes it now carries no information. A love of reading is assumed; a catalogue you cleaned is not. A practical test: read your summary and ask whether a classmate with the same BLIS could paste it onto their resume unchanged. If they could, it describes the degree, not you. Add the specific library, the specific number and the specific ownership until it stops being transferable.

Experience bullets: verb, collection, consequence

Every strong bullet in the samples follows the same shape. It opens with an action verb, names the specific collection, system or service you handled, and closes with what measurably changed. The verb establishes that you did it. The collection or system tells a reviewer whether the work fits their library. The number does the persuading. Start with the outcome and work backwards. Librarians usually write the duty first, then struggle to attach a number, which produces bullets like "handled cataloguing and circulation work in the library". Instead ask what was different after you did it: a backlog was cleared, misshelving dropped, e-resource usage rose, stock reconciled, turnaround shortened. Then write the sentence that ends in that fact. Library work has plenty of honest numbers, so use them: titles catalogued, size of the collection, membership served, borrowing or footfall change, e-resource usage, stock accuracy, query turnaround, backlog cleared. The assistant sample varies the metric across bullets, which reads as range rather than one trick repeated. Where a number does not exist, give scope: how many volumes, how many users, how many branches, how long a migration took. "Migrated a 60,000 record catalogue to Koha over four months with no lending downtime" carries weight without inventing a percentage. Allocate bullets by recency. Current post gets five or six, the previous one four, anything older two or three.

If a bullet would read identically on any BLIS holder's resume, it is describing the qualification, not you. Rewrite it until it only fits the library you actually ran.

The skills section: grouped, honest, and short enough to defend

A librarian's skills section has two audiences with opposite preferences. The parser wants literal terms it can match, Koha and DDC and MARC21 and DSpace. A human wants a short, organised list that signals what kind of library professional you are. Grouping satisfies both. Group by function rather than one long line. Cataloguing and classification, library systems, digital and e-resources, and reader services is a grouping that works for almost every academic librarian. The exact headings matter less than the fact that structure exists. Write names the way the field writes them: Koha not KOHA, DSpace not Dspace, MARC21 not Marc, INFLIBNET not Inflibnet. A parser matches on strings. Twelve to sixteen skills is the working range. Below eight the section looks thin. Above twenty it stops being a signal, and library resumes are especially prone to listing every classification scheme and every ILS taught in the course, DDC, UDC, CC, LC, Koha, SOUL, LibSys, WINISIS, as though breadth of exposure were depth of use. The list is a contract: every item is a question you have agreed to answer. Do not include a proficiency bar. Star ratings invite an argument you cannot win, and nobody agrees on what four stars in cataloguing means. Let the experience prove the depth instead.

Projects, digitisation and initiatives: what to include

For a fresher, project and internship work is the resume. A catalogue clean-up, a reading programme, a digitisation task or a stock verification you ran during a BLIS internship is where a reviewer decides whether you can actually run a library or only pass exams about it. For an experienced professional these move below experience and become the initiatives that set you apart: a repository you founded, a discovery system you set up, an information-literacy programme you started. The common failure is describing the activity instead of the result. "Did a project on digital library" tells a reviewer nothing, because hundreds of BLIS resumes carry that exact line. Describe what you built, who used it, and what was genuinely useful. The Koha clean-up in the fresher sample is a stronger entry than a vague digital-library project, because it names a real backlog, a real standard and a documented convention the next person could follow. Pick work that shows range rather than three variations of the same task. One cataloguing or classification job, one digital or digitisation piece, and one reader-facing initiative is a stronger set than three cataloguing lines. Two well-described initiatives beat five listed by name. If you built a repository or a digital collection that is publicly accessible, say so in plain text. A committee that opens it and finds a real, searchable collection reads it as a work sample, which is worth more than any adjective.

Where education, UGC NET and certifications belong

Education goes near the top for a fresher, who has nothing stronger to lead with, and lower for anyone with real posts behind them, though for library work the qualifying degree stays prominent because eligibility is checked hard. BLIS or MLIS, institution, years. A PhD, where you have one, is a headline fact for university posts and belongs high. For academic library roles, UGC NET or SET is not a nice-to-have, it is the eligibility gate for assistant librarian and above, so it should be impossible to miss, sitting with education or in your eligibility line. Leaving it buried at the bottom, or omitting the year, makes a committee hunt for the one fact that decides whether they can shortlist you at all. Percentage or class is worth keeping while you are a fresher and it is good, because campus and early-career screening still filters on it. Once you have run a library for a few years, the degree class matters less than the collections you have handled, so let it recede. Certifications and short courses sit below education. Workshops on Koha administration, DSpace, RDA or research data management are worth naming with the issuing body and year, because they show you keep current in a field where the systems change. For senior roles, a short, real publications list, chapters, journal papers, conference presentations, adds weight, but only if it is genuine. An inflated or padded list is easy for an academic panel to check, and it costs more than it gains.

Getting through the applicant tracking system

Many Indian institutions, and almost every large one that recruits online, run applications through an applicant tracking system or a portal parser before a human sees them. It reads your file, tries to break it into name, dates, employers, titles, qualifications and skills, and stores the result so a recruiter can search. Almost every ATS problem is a parsing problem, and parsing problems come from layout, not wording. The layout rules are short. One column. Standard section headings, so use Work Experience rather than My Library Journey, and Skills rather than My Toolkit. No text inside images, because a photo of your certificate reads as empty space. No critical information in the header or footer region, which some parsers drop. Avoid text boxes and nested tables in the resume body. On wording, mirror the language of the advertisement where it is honest. If the post says assistant librarian, use assistant librarian, not just librarian. If it names Koha or INFLIBNET, and you have used them, write them exactly. Spell out an acronym alongside itself at least once, for example "UGC NET (National Eligibility Test)", so both searches find you. For academic posts, make sure your UGC NET status, qualifying degree and any PhD appear as plain text, because these are the fields a committee filters on hardest. Keyword stuffing does not work. A hidden block of every classification scheme in white text is found quickly, and the outcome is worse than being filtered. Write real bullets that naturally contain the right terms. Save as PDF from a tool that embeds real text, then open the file and confirm you can select and copy a sentence. If you cannot select the text, neither can the parser.

Test your own file before you send it. Copy the text out of the PDF into a plain text editor. Whatever you can read there is roughly what the parser sees, and anything scrambled, especially your UGC NET line, is a real risk.

What gets librarian resumes rejected

Most rejections at the resume stage are not close calls. They come from a small set of recurring problems, and all of them are fixable in an afternoon. The list below covers what committees reviewing Indian librarian resumes see most often, in rough order of how much damage each one does.

• Every classification scheme and every ILS from the course listed as a skill, with no bullet proving any of it. Breadth of exposure is not depth of use.
• The UGC NET or SET status buried at the bottom or left off, for a post where it is the eligibility gate.
• Duties copied from the appointment order instead of what you achieved. "Responsible for cataloguing and circulation" is the tell.
• No numbers anywhere. Titles catalogued, users served, borrowing change, stock accuracy, e-resource usage. Pick whichever is honest.
• "Passionate about books and reading" as the summary. A love of reading is assumed, not evidence; state what you have run.
• A photo, date of birth, marital status or father's name. None of it belongs on the resume and it takes a result's space.
• No mention of any digital or e-resource work, on a resume for a modern library that runs on Koha, DSpace and consortium databases.
• A generic objective line. Replace it with a summary that states library type, years and one result.
• Inflated titles or a padded publications list that a background check or an academic panel can catch in minutes.
• Typos in the systems you claim to run, such as writing Koha as "Kova" or DSpace as "D-Space", which undoes an otherwise careful page.

Read your resume aloud once before sending it. Anything you would be uneasy defending to an interview panel's face is a line to cut or rewrite.

Skills to put on a librarian resume

Certifications worth listing as a librarian

Keywords an ATS scans for in a librarian resume

These are the literal terms a parser matches against the job description. Use the ones that are true of you, in the sentences where you did the work, not as a list at the bottom.

• librarian
• assistant librarian
• library and information science
• BLIS
• MLIS
• cataloguing
• classification
• DDC
• MARC21
• koha
• OPAC
• DSpace
• institutional repository
• INFLIBNET
• e-resources
• circulation
• collection development
• UGC NET
• stock verification
• reference service

Librarian resume FAQ

Related resume examples and guides