Company Secretary Resume Format, with 3 Full Samples

The format that works for company secretary resumes in India

Reverse chronological is the layout to use. Put the most recent secretarial role first, work backwards, and let the dates show. Functional resumes that group everything under Compliance Skills and drop the dates read as an attempt to hide a gap or a short tenure, and the promoters, CFOs and boards who hire company secretaries read a resume the way they read a compliance file, closely. Length is decided by evidence. One page holds everything a CS trainee and most company secretaries up to roughly six or seven years have to say. A listed-company CS with IPO, NCLT and SEBI-inspection work earns a second page. A page two padded with a list of every section of the Companies Act is a one-page resume in disguise. The qualification facts have to be visible immediately, because a company secretary is a statutory appointment and the first thing an employer confirms is membership. Put ACS or FCS, your ICSI membership status, and any LLB or LLM where they cannot be missed. Certificate of Practice, if you hold one, belongs here too. A strong governance record does not help if the reviewer cannot confirm you are a member in the first place. Four things belong nowhere on the resume: a photograph, date of birth, marital status and father's name. They survive from an older template. A board or a CFO screening a compliance officer is not looking for them, and every line they occupy is a line a filing record or a governance 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 role. The table below sets out the section order.

Naming the Companies Act is not the same as proving compliance

The most common company secretary resume failure is a skills line that recites Companies Act 2013, SEBI LODR, FEMA, RBI, Secretarial Standards, Corporate Governance, ROC, MCA21, SS-1, SS-2, PIT, LODR, IBC with no bullet anywhere that shows any of it applied to a real filing or a real board. A parser matches those terms, but a CFO or a partner reads the wall and assumes it is an exam syllabus, then goes looking for the one compliance area you can actually run. The fix is to let the experience prove the law. If you write SEBI LODR, a bullet should show the disclosures you filed or the listing obligation you managed. If you write FEMA, a bullet should name the FC-GPR or ODI filing you handled and that it met the RBI timeline. The listed sample lists SEBI LODR and PIT precisely because the bullets show exchange disclosures, an insider-trading code and clean inspections. The skills line and the work agree, which is what makes both believable. Name the specific forms and provisions you have worked with, because they signal the level you operate at. MGT-7 and AOC-4 are the base annual filings every CS handles. CHG-1, DPT-3, FC-GPR, a Section 204 secretarial audit, a Section 230 scheme, a SEBI PIT structured digital database, each of these tells a reviewer a different and more advanced kind of work. Precision here is the difference between a resume that reads as a trainee's and one that reads as a compliance officer's. Do not list a regulation you studied for the exam but never touched. If your only exposure to SEBI takeover regulations was a paper, do not claim takeover-code experience, because an interviewer who asks you to walk through an open-offer trigger will find the gap in a minute.

For every act and regulation on your skills line, ask: is there a bullet that shows me complying with it. If not, either add the bullet or cut the line. A wall of unproven statute helps the parser and hurts the interview.

Writing a summary a board or a CFO 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 company you run compliance for, how long you have been doing it, and the strongest governance outcome your work produced. Three or four lines, no adjectives a reference check cannot confirm. The old objective line, seeking a challenging position in a reputed organisation to utilise my knowledge of company law and secretarial practice, tells a reviewer nothing new. Replace it with a summary. An objective describes what you want, a summary describes what you have already done, and only one is evidence in a compliance function. Trainees and freshers often think they have nothing to summarise. Look at the fresher sample: it names ACS membership, the training length, and points at eight companies' filings accepted first time and a compliance calendar the office adopted. That is a genuine summary built from ICSI training. What it avoids is "a dedicated professional with sound knowledge of corporate laws", a phrase so common on CS resumes it now carries no information. A practical test: read your summary and ask whether any other ACS could paste it onto their resume unchanged. If they could, it describes the qualification, not you. Add the specific company, the specific filing record and the specific ownership until it stops being transferable.

Experience bullets: verb, filing or board action, consequence

Every strong bullet in the samples follows the same shape. It opens with an action verb, names the specific filing, meeting or compliance action you handled, and closes with what measurably resulted. The verb establishes that you did it. The filing or board action tells a reviewer whether the work fits their company. The number, or the clean outcome, does the persuading. Start with the outcome and work backwards. Company secretaries usually write the duty first, then leave it vague, which produces bullets like "handled ROC compliance and secretarial matters of the company". Instead ask what the compliance state was after your work: filings accepted without resubmission, no late-fee penalty, non-compliance closed, an inspection passed clean, a scheme sanctioned. Then write the sentence that ends in that fact. Compliance work has honest numbers and honest binary outcomes, so use both: number of companies, number of meetings a year, filings without penalty, inspection cycles with no adjudication, shareholders served, designated persons under a code. A clean record is itself a metric a board reads first. The mid and senior samples vary these across bullets, which reads as range. Where a number does not fit, give scope: how many companies in the group, how many committees, how large a shareholder base, how many years of accumulated non-compliance you cleared. "Closed two years of accumulated non-compliance in a subsidiary without a penalty proceeding" carries weight on its own. Allocate bullets by recency. Current role gets five or six, the previous one four, anything older two or three.

If a bullet would read identically on any other ACS resume, it is describing the qualification, not you. Rewrite it until it only fits the company and the filings you actually ran.

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

A company secretary's skills section has two audiences with opposite preferences. The parser wants literal terms it can match, Companies Act 2013, SEBI LODR, MCA21, secretarial standards. A human wants a short, organised list that signals what kind of compliance professional you are and at what level. Grouping satisfies both. Group by function rather than one long line. Statutory and ROC, corporate governance, securities and FEMA, and drafting and due diligence is a grouping that works for almost every CS. The exact headings matter less than the fact that structure exists. Write names the way the profession writes them: SEBI LODR not Sebi Lodr, MCA21 not MCA 21, SS-1 and SS-2 not SS1 SS2. 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 CS resumes are especially prone to reciting every regulation studied for the exam, LODR, PIT, SAST, ICDR, Buyback, Delisting, as separate skills when the candidate has worked only two of them. The list is a contract: every item is a question an interviewer can ask you to walk through. Do not include a proficiency bar. Star ratings invite an argument you cannot win, and nobody agrees what four stars in the Companies Act means. Let the experience prove the depth instead, and pitch the list to the target: a listed-company advertisement wants LODR and PIT, an unlisted group wants ROC and FEMA.

Transactions, audits and initiatives: what to include

For a trainee, the practical training assignments are the resume: filings you made, minutes you drafted, a secretarial audit you assisted, a compliance calendar you built. This is where a reviewer decides whether you can actually run compliance or only clear the ICSI exams. For an experienced CS, the standout items are the transactions and programmes that go beyond routine filing: an IPO, an NCLT scheme, a due diligence, a compliance system you implemented. The common failure is describing the activity instead of the outcome. "Handled a secretarial audit" tells a reviewer nothing, because it does not say what you found or fixed. Describe what you did, what it covered, and what changed. The secretarial-audit checklist in the fresher sample is a stronger entry than a vague audit line, because it names the standard mapped, the items tested and the gaps flagged. Pick work that shows range rather than three variations of the same filing. One routine-compliance line, one transaction or audit, and one governance improvement is a stronger set than three ROC-filing lines. For a senior CS, one well-described IPO or NCLT scheme is worth more than a paragraph of committee names. Be precise and honest about your role in a transaction. "Led the secretarial due-diligence workstream" is credible; claiming you led the whole acquisition when you drafted the share-transfer forms is the kind of overstatement a reference call from the deal counsel exposes immediately.

Where ICSI membership, LLB and certificates belong

For a company secretary the qualification is the profession, so ICSI membership sits high, not buried at the bottom. State clearly whether you are ACS (associate) or FCS (fellow), and where relevant your ICSI membership status, because this is a statutory appointment and an employer confirms membership before anything else. A trainee awaiting membership should say so honestly: passed the professional programme, membership under process. An LLB or LLM is a genuine differentiator for a CS, since so much of the role is drafting, due diligence and interpreting law, so name it with the institution and year. A Certificate of Practice, if you hold one and it is relevant to the role, belongs in the qualification block too. The underlying B.Com or graduation degree can sit lower once you are qualified. Percentage or division is worth keeping while you are a fresher and it is good, because early-career screening still uses it. Once you have run compliance for a group or a listed company, the degree marks matter far less than the filings and transactions you can point to, so let them recede. ICSI's certificate courses and specialised programmes, on FEMA, capital markets, insolvency, GST or forensic audit, sit below the core qualifications and are worth naming with the year when they match the target role. An insolvency-professional registration with IBBI, for example, is a real differentiator for a CS moving towards insolvency work, and irrelevant clutter for one who is not.

Getting through the applicant tracking system

Corporate employers, and almost every listed company and large group, run applications through an applicant tracking system before a human sees them. It reads your file, tries to break it into name, dates, employers, titles, membership 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 Corporate Journey, and Skills rather than My Expertise. No text inside images, because a scanned membership certificate reads as empty space. No critical information in the header or footer region, which some parsers drop, and for a CS the membership line especially must be in the body as plain text. Avoid text boxes and nested tables in the resume body. On wording, mirror the advertisement where it is honest. If the post says compliance officer, use compliance officer. If it names SEBI LODR or FEMA and you have done that work, write the term exactly. Spell out an acronym alongside itself at least once, for example "LODR (Listing Obligations and Disclosure Requirements)" and "ACS (Associate Company Secretary)", so both searches find you. Make sure ACS or FCS appears as plain text, because it is the single field a recruiter filters CS applications on hardest. Keyword stuffing does not work. A hidden block of every SEBI regulation 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, especially your membership and experience lines. 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 if your ACS or FCS line does not survive the copy, a recruiter's filter will not find you.

What gets company secretary 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 employers reviewing Indian company secretary resumes see most often, in rough order of how much damage each one does.

• Every SEBI regulation and every act from the syllabus recited as a skill, with no bullet showing any of it applied. An interviewer asks you to walk through one, and the gap shows.
• ACS or FCS membership status left unclear or buried, when it is the first thing an employer confirms for a statutory appointment.
• Duties copied from the appointment letter instead of outcomes. "Responsible for ROC compliance and secretarial matters" is the tell.
• No clean-record or numbers anywhere. Companies filed for, meetings a year, filings without penalty, inspections passed. Pick whichever is honest.
• "Sound knowledge of corporate laws" as the summary. Knowledge is assumed from the qualification; 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 governance result's space.
• Claiming listed-company or capital-markets work with no LODR, disclosure or inspection detail to back it, which a first interview exposes.
• Overstating a role in a transaction, which a reference call to deal counsel or the audit partner catches quickly.
• A generic objective line. Replace it with a summary that states company type, years and one governance result.
• Typos in the forms and regulations you claim, such as writing LODR as "LORD" or MGT-7 as "MGT7", which undoes an otherwise precise page.

Read your resume aloud once before sending it. Anything you would hesitate to defend to a board or an audit committee's face is a line to cut or rewrite.

Skills to put on a company secretary resume

Certifications worth listing as a company secretary

Keywords an ATS scans for in a company secretary 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.

• company secretary
• compliance officer
• ACS
• FCS
• ICSI
• companies act 2013
• ROC filings
• MCA21
• SEBI LODR
• corporate governance
• secretarial standards
• secretarial audit
• board meeting
• minutes and resolutions
• FEMA
• insider trading
• due diligence
• statutory registers
• annual return
• MGT-7

Company Secretary resume FAQ

Related resume examples and guides