Resume audit: Meera Kashyap, Implementation Manager at Ledgerline
One page, six years, three real results buried under fourteen job-description bullets. Read against INSEAD, HBS and ISB admit resumes.
Verdict
CompetitiveCompetitive, under-sold
The career behind this page is admit-grade for INSEAD and ISB; the page itself gives away about a third of it to responsibility bullets and rupee units no foreign reader can size.
Generated on 10 October 2026 · AdcomLens · Confidential · 2,825 words
1. The ten-second read
Ten seconds in, a reader sees an NIT Warangal engineer, six years out, who left a 240,000-person IT services firm for a 420-person Series C payments company and was promoted to Implementation Manager in October 2025. Two numbers survive the fast pass: median go-live cut from 74 days to 41, and monthly payment mismatches cut from about 1,900 to 240 at Corvane. Both have a before and an after, both are hers, and both are the reason this page is worth fixing rather than rebuilding. Nothing else sticks. The page never says what she wants next: there is no product work visible, which is awkward for someone applying to switch into product management. It does not read as international; four years of daily calls with a claims team in Leeds appear as "participated in client calls". ₹6.2 crore and ₹1.1 crore mean nothing in Fontainebleau, Boston or Amsterdam. Everything under ADDITIONAL that involves other people stopped in 2022. The Focus 675 sits in Education without the 87th percentile quant beside it. Counts across the nineteen experience bullets: 5 state a result, 14 state a responsibility, 10 carry a figure.
2. Bullet audit
| Bullet (first six words) | Result or responsibility | Has a number | Fix |
|---|---|---|---|
| Manage a team of five implementation | Responsibility | Yes (5) | What the team now delivers per head versus before you took it. |
| Cut median time to go live | Result | Yes (74 to 41) | Keep. Strongest line on the page; move it to the top of the role. |
| Took 14 customers live in FY26 | Result | Yes (14, ₹6.2cr) | The FY25 comparison and the euro or dollar equivalent of the ACV. |
| Responsible for weekly status reporting to | Responsibility | No | Cut. Reporting upward is not an achievement. |
| Hired three of the five engineers | Responsibility | Yes (3 of 5) | What those hires went on to own, including the logistics accounts hire. |
| Run the weekly go-live review and | Responsibility | No | Merge into the team line; add what the allocation call changed. |
| Worked closely with product, sales and | Responsibility | No | Cut, or name one integration and what it won or saved. |
| Kept a ₹1.1 crore retail-chain account | Result | Yes (₹1.1cr, 9 days) | Keep. Convert the currency and say who asked you to step in. |
| Involved in building the multi-entity reconciliation | Responsibility | No | What you decided or specified, ship date, and who uses it now. |
| Wrote 22 integration guides now used | Mixed | Yes (22) | The effect: tickets per go-live, or new-engineer ramp time. |
| Handled escalations from enterprise and mid-market | Responsibility | No | Cut. "As and when required" tells a reader nothing. |
| Led a squad of four engineers | Responsibility | Yes (4) | Fold into the Corvane heading line; the checker bullet carries the role. |
| Built a checker that cut month-end | Result | Yes (1,900 to 240) | Keep. Add that nobody asked you to build it. |
| Participated in client calls and requirement-gathering | Responsibility | No | Call cadence, duration and whether you were the offshore point of contact. |
| Coordinated releases across the development, testing | Responsibility | No | Release count and defect or slippage change, or cut. |
| Responsible for development, testing and maintenance | Responsibility | No | Shrink to one line covering both early titles. |
| Handled production support on a rotating | Responsibility | No | Cut. |
| Trained 30 new joiners in the | Mixed | Yes (30) | What changed for them: ramp weeks, or how many you then supervised. |
| Received the Star Performer award twice | Recognition | Yes (2021, 2023) | Selection pool size; then move it onto the role line, not its own bullet. |
3. Rewrites
Before
1. Manage a team of five implementation engineers responsible for onboarding mid-market customers. 2. Involved in building the multi-entity reconciliation module with the product team. 3. Participated in client calls and requirement-gathering sessions with the insurer's claims operations team in Leeds.
After
1. Built the mid-market implementation team to five engineers, hiring three; one hire now owns Ledgerline's hardest logistics accounts, and the team closed [NEED: FY26 go-lives per engineer versus FY25]. 2. Specified [NEED: number] requirements for the multi-entity reconciliation module with product, shipped [NEED: month and year]; now live with [NEED: number] customers and cited in [NEED: deals won or churn avoided]. 3. Served as the offshore counterpart to a UK motor insurer's claims operations team in Leeds for [NEED: duration], on [NEED: calls per week] video calls, translating [NEED: what] into build decisions for a squad of four.
1. The original describes a reporting line; the rewrite shows she assembled the team and that one of her hires is now trusted with the worst accounts, which is the only proof a reader accepts that she can build people. 2. This is the single most important bullet on the page for a product switch and it currently says "involved in", so the rewrite forces her to name what she decided and what shipped. 3. Four years of daily contact with Leeds is her only cross-border asset and "participated in client calls" throws it away, so the rewrite states cadence, counterpart and what she actually converted into work.
4. Jargon and inflation
WatchThe SUMMARY paragraph: "results-driven", "strong skills in stakeholder management, problem solving and team leadership"
Not one word of it can be checked, and every claim in it is either proved by the bullets below or untrue. Adcom readers at INSEAD and HBS skip these paragraphs, so it costs four lines of the most valuable space on the page and buys nothing.
Mitigation required
Delete it. If a header line is wanted, write one factual line that only Meera can supply: the segment she runs, the number of customers live under her in FY26, and the euro or dollar value of that book.
Rupee units: ₹6.2 crore and ₹1.1 crore
Crore and lakh are not read outside South Asia, so a Fontainebleau or Boston reader cannot tell whether ₹6.2 crore is a rounding error or a real book of business. The two strongest commercial numbers on the page therefore land as noise for the readers she most needs to impress.
Mitigation required
Write the figure in rupees with the euro or dollar equivalent in brackets at a stated rate, for both the FY26 annual contract value and the retail-chain account she saved.
Credit-hedging verbs: "Involved in", "Worked closely with", "Participated in", "Coordinated", "Handled... as and when required"
Five bullets use a verb that deliberately avoids saying what she did, which reads as either junior work or borrowed credit. On a page that elsewhere proves she built a checker alone and rewrote a bank-integration playbook, the hedging makes the reader doubt the surrounding bullets too.
Mitigation required
For each of the five, write the single decision or artefact that was hers, or delete the bullet. Only she knows which requirement she wrote, which escalation she resolved and which release she unblocked.
"Responsible for weekly status reporting to the Director of Customer Solutions and the CTO"
This sounds like executive exposure and is in fact a calendar entry. Proximity to a CTO is not a result, and a reader who has seen thousands of these bullets will register it as padding in a role that already has genuine numbers.
Mitigation required
Cut it, or replace it with a decision the CTO or Director took because of something she brought them, with the date and the consequence.
Payments jargon: "settlement mapping", "multi-entity reconciliation", "bank-integration playbook", "go-live"
Half the admissions readers come from outside technology and none of them work in B2B payments. The reconciliation and settlement lines are where her hardest work sits, so losing the reader there costs her the evidence that supports a fintech product goal.
Mitigation required
Add three or four plain words inside each phrase, for example what the settlement mapping actually matched and why the retail chain was leaving. She should write it as she would explain it to her father, the retired bank branch manager.
"Team leadership" claimed in the summary while every result pre-dates the team
The three proof points are the checker (2023, before she managed anyone), the saved account (2025, as an individual contributor) and the go-live time cut (driven by a playbook she rewrote). A sharp reader will notice that nothing on the page shows output produced through other people, which matches the January 2026 feedback that she was rewriting her team's work.
Mitigation required
Add one bullet showing a result her engineers delivered without her hands on it, with the measure and the period since she stopped editing their plans. Only she can supply that number from FY26 and FY27 to date.
5. What to cut for recency and space
- Delete the SUMMARY paragraph. Four lines back, and nothing lost.
- Delete three pure-responsibility bullets outright: weekly status reporting, escalations "as and when required", and production support on a rotating basis.
- Merge the Implementation Manager team bullets (manage five, hired three, run the go-live review) into one leadership line, freeing two lines for the product and go-live evidence.
- Put one Ledgerline heading with two indented title lines and dates, and one Corvane heading with three indented title lines. Six separate headings for two employers wastes four lines and hides the two promotions.
- Compress Senior Engineer and Associate Engineer (Jul 2020 to Mar 2023) to two lines: one on the Java claims platform at scale, one on training 30 new joiners with the outcome added. Nothing from 2020 to 2022 deserves more.
- Move the Star Performer awards (2021, 2023) onto the Corvane role line as a bracketed tag rather than their own bullet.
- Cut the AWS Certified Cloud Practitioner (2022) and Certified Scrum Master (2023) certifications from the page. Neither tells an adcom anything about a product switch; both belong in the application form's qualifications field.
- Trim the skills line: Jira is not a skill. Keep the languages, which are genuinely four.
- Keep Code Saturdays despite ending in 2022; it is the only community item in the file, and it links to teaching rather than to payments. One line, with the number of students if she has it.
- Target roughly 60 percent of the page for Ledgerline (Jul 2024 to now) and the Corvane Module Lead year, which is what the last five years should take.
- Free space goes to one product-evidence bullet and one line of context for Ledgerline and for NIT Warangal, not to new responsibility bullets.
6. Education and extras
- Education entry
- Write: "B.Tech, Electronics and Communication Engineering, National Institute of Technology Warangal, India, 2016 to 2020" with one bracketed clause of context a foreign reader needs, for example national engineering institute, admission by the JEE national examination taken by [NEED: candidate numbers that year]. Put the GMAT on its own line under Education: "GMAT Focus Edition 675 (2026), Quant 87th percentile". Keep the words "Focus Edition" so no reader compares 675 with INSEAD's classic 710 average; on the classic scale the result reads around 720, which is at par for INSEAD and above ISB's 700.
- Degree grade
- Keep CGPA 8.2/10 and write the scale explicitly, since 8.2 means nothing without the /10. Six years of experience is well short of the ten-year point at which dropping a grade is sensible, and none of the three programme records in this file states a GPA or CGPA norm, so there is no basis for hiding it. Add any honours or rank the file does not yet record: [NEED: department rank, scholarships, or any academic award at NIT Warangal].
- Leadership and community
- One line for Code Saturdays, Pune, 2021 to 2022, with [NEED: number of students taught and sessions run]. Then add the leadership inside the employers that the page currently buries: hiring and reviewing five engineers at Ledgerline, and training 30 new joiners at Corvane. There is nothing she leads outside work today, which the page will show by the 2022 end date; the honest fix is to start something now with a date a reader can see, not to dress up the running.
- Skills and languages
- Group as Technical: Java, SQL, Python, API integration (drop Jira). Domain: [NEED: her own plain-English label for the payments work, for example bank integrations, settlement and reconciliation]. Languages: English (professional), Hindi, Kannada, Marathi, with [NEED: honest level for each of the three, fluent or conversational]. Do not claim any language the file does not state, and do not add a European language unless she starts one, in which case list it with the level and the date started.
- Interests
- One line, specific, no list of five: "Bengaluru 10K 2024 and 2025 ([NEED: finish time]); Carnatic violin to college level." Both are true, both are checkable, and the violin is the only line on the page that does not involve software.
7. Formatting checklist
| Check | Pass or fix |
|---|---|
| One page | Cannot tell from text: check it yourself. The cuts listed above should buy back roughly 10 to 12 lines, which is enough if it currently runs over. |
| One font family and consistent sizes | Cannot tell from text: check it yourself. |
| Even spacing and alignment | Cannot tell from text: check it yourself. |
| Place and dates for every role, dates not in bold | Partial pass in the text: every one of the five roles has a month and year range, and Bengaluru and Pune appear at employer level. Fix: dates sit on the title line, so make sure they are right-aligned and not bolder than the title. Cannot tell weight from text. |
| Headings that stand out from the text | Cannot tell from text: check it yourself. EXPERIENCE, EDUCATION and ADDITIONAL are present and correctly ordered. |
| The same pattern to the bottom of the page | Fix: the pattern breaks at Corvane, where Senior Engineer and Associate Engineer share one bullet block under two dateless-looking title lines while every other role has its own bullets. Decide one rule and hold it. |
| No photo or personal data schools do not ask for | Pass in the text: no photograph, no date of birth, no marital status, no father's name, no signed declaration, no CTC. This is the correct convention for INSEAD, HBS and ISB. Cannot tell whether the file itself carries an image: check it yourself, and do not add a phone-free header either, since [NEED: phone number with country code] and [NEED: LinkedIn URL] should both be on the contact line. |
8. Order of work
- Today: delete the SUMMARY paragraph, the three pure-responsibility bullets and the two certifications, and merge the six role headings into two employer blocks. This is pure subtraction and needs no new facts.
- Today: convert ₹6.2 crore and ₹1.1 crore into euros at a stated rate, and move the GMAT Focus 675 with its 87th percentile quant onto its own line under Education.
- This week: pull the missing figures from your own records, starting with the FY25 go-live count, the FY26 target, the ship date and adoption of the multi-entity reconciliation module, and the support-ticket effect of the 22 integration guides. Nothing gets written until the number exists.
- This week: write the one bullet the page lacks, a result your five engineers delivered without you editing their plans since January 2026, with the measure and the period.
- Before you send anything: check every figure against what your Ledgerline and Corvane recommenders will independently say. If your Director of Customer Solutions would not recognise the 74-to-41 framing or the ₹6.2 crore attribution, change the resume, not the recommender.
- Then fill the application work-history fields from scratch, not by pasting bullets. Those fields want scale and context: team size, reporting line, budget or target owned, customer count, region covered. Your no-P&L position is fine and should be stated plainly rather than dressed up.
- Target the INSEAD August 2027 intake November 2026 round with this page, since the September round has passed and your earliest start is August 2027. The January 2027 round is the fallback and HBS Round 2 in January 2027 is the same deadline week; ISB's next relevant entry is the April 2028 intake, which you apply to in autumn 2027.
- Last: re-read the finished page asking one question per bullet, what changed because of me. If a bullet cannot answer it, it should not be on a one-page record of results.
9. Next steps
- Run the subtraction pass today in Resume Optimiser: cut the summary, the three responsibility bullets and the certifications, then merge the role headings into two employer blocks.
- Collect the six missing figures listed in infoNeeded from your own FY25 and FY26 records before writing a single new bullet.
- Use Goals Credibility to test whether the rewritten product bullet actually supports a double switch into European fintech product management, because that is the weakest link in the whole file.
- Use Recommender Prep to check the 74-to-41 day claim, the ₹6.2 crore attribution and the retail-chain save against what your Ledgerline manager would say unprompted.
- Run Programme Fit Review on the INSEAD November 2026 round against the January 2027 round, given that a ten-month programme with no internship is the harder route for a function and industry switch.
10. Information that would sharpen this
- FY25 mid-market go-live count and the FY26 target, so the 14 go-lives can be stated against a baseline.
- Euro or dollar equivalent of ₹6.2 crore ACV and ₹1.1 crore account value, at a stated exchange rate.
- What Meera specifically decided or specified on the multi-entity reconciliation module, its ship date, and how many customers use it.
- Measured effect of the 22 integration guides: support tickets per go-live, or new-engineer ramp time, before and after.
- Cadence and duration of the Leeds client calls, and whether she was the named offshore point of contact for the UK motor insurer.
- A result delivered by her five engineers without her editing their work, with a measure, for the period since January 2026.
- Selection pool size for the Corvane Star Performer award (2021 and 2023).
- Number of students taught and sessions run at Code Saturdays, Pune.
- Any academic honour, rank or scholarship at NIT Warangal, and the JEE cohort size for context.
- Honest proficiency level for Hindi, Kannada and Marathi, and whether any European language study has started.
- Phone number with country code and LinkedIn profile URL for the contact line.
- Whether any product-adjacent responsibility has been taken on at Ledgerline since the March 2026 request to move into product.