If you are a 27-year-old IT services engineer with a 710 GMAT, three promotions, and a one-page resume you have rewritten eleven times, this post is for you. The uncomfortable truth about the ISB resume scan is that the first read is fast. A reviewer forms an impression of your file in well under two minutes, then decides whether to slow down. What follows is the four things that first pass actually looks for, and how to make sure your one-pager answers them.
What the ISB resume scan is really doing
ISB runs a holistic review, but holistic does not mean slow on the first pass. The official process says every verified application goes through a structured review of "academics, relevant test scores, professional experience, extracurricular activities, essays, awards and recognitions, and recommendations" to arrive at a final profile score. Your resume is where several of those inputs get read first and fastest.
The ninety-second framing is ours, not ISB's official language. It is how experienced reviewers actually behave when a round brings thousands of files. The reader is not grading prose. They are checking four things: where you come from, whether you are moving up, whether your work changed anything, and whether the whole page tells one coherent story. Miss those and the essays rarely get a generous read.
Scan point one: pedigree, read in three lines
Pedigree here means your undergraduate institution, your employers, and your test score, taken together. This is not snobbery. It is a fast proxy for selectivity you have already passed through. ISB states there is no minimum CGPA and no test cutoff, and that it evaluates your "institution, course selection, and performance trajectory" rather than grades alone. A tier-2 college with a rising trajectory is not a problem. A blank or buried education line is.
The fix is placement, not padding. Put institution, degree, graduation year, and one credible marker of academic standing on the same line. Do the same for each employer: company, function, city, dates. An Indian applicant from a lesser-known college often hides the college; the better move is to state it plainly and let progression and impact carry the weight.
Scan point two: progression, the line the eye follows down the page
The reviewer's eye runs down the left margin looking for movement. Analyst to senior analyst to team lead in four years reads as trajectory. Three parallel "Software Engineer" lines with no change in scope reads as tenure, not growth. With the PGP median student sitting at 26 with about four years of experience, drawn from a Class of 2026 of 826 students whose work experience runs from two to seventeen years, you are being read against a cohort that has almost all moved up at least once.
ISB's application asks you to log designation, employment type, duration, industry, and function for every role. Mirror that structure on the resume so the progression is legible in one glance. If you were promoted, say so on its own line with the date. If your title never changed but your scope tripled, quantify the scope, because the title alone will read flat.
Scan point three: impact, where most Indian resumes go quiet
This is where the IT services engineer usually loses the reviewer. The bullets describe responsibilities: "worked on," "was responsible for," "involved in." None of those tell the reader what changed because you were there. Impact is the number attached to the verb. Revenue moved, cost fell, a launch shipped, a team grew, a client was retained, a process got faster.
ISB says it looks for analytical thinking and leadership potential evident in "professional work" and "the impact that you seek to create." The resume is the first place that impact is either visible or absent. Convert three responsibility bullets into three outcome bullets with a metric each, even a modest one. "Reduced release-cycle defects 22 percent across a nine-person pod" beats "responsible for quality." If you cannot find a number, you have found the weak spot in your candidacy, not just your resume.
The common objection is that support and maintenance roles do not generate clean numbers. They usually do, once you look. Uptime you protected, tickets you cleared per sprint, an escalation rate you brought down, a client you kept from churning, onboarding time you shortened for new joiners. The metric does not have to be large or company-wide. It has to be real, attributable to you, and stated in a way a non-technical reviewer can grasp in one line. A modest, specific number is more persuasive than a grand claim with nothing behind it.
Scan point four: story arc, the thing that ties it together
The fourth read is holistic in the literal sense. Does the page point somewhere? A resume that shows a data engineer moving steadily toward product decisions, then applying to reposition into strategy, tells a story the career-goals essay can then complete. A resume that reads as a random walk forces the reader to do the connecting work, and reviewers under volume rarely do it for you.
You do not manufacture an arc; you surface the one already there. Order the extracurricular and awards lines to reinforce the direction, not to fill space. ISB explicitly invites awards "from any stage of your life" with context on why they mattered, so choose the two that support your arc and cut the rest. When the resume and the essays point the same way, the reviewer stops working to connect the dots and starts believing the story. That coherence, more than any single line, is what earns the slow, generous second read.
If you are an IT services engineer
Your risk is not pedigree; it is impact and differentiation inside a large applicant pool. Roughly half of each ISB class comes from engineering backgrounds, so the reviewer has seen your archetype many times in one sitting. Lead every role with an outcome metric, name the business context (client, revenue, users), and make one line show leadership outside pure code. Our deeper read on this profile lives in ISB for IT services engineers, and the pattern behind rejected strong-GMAT engineers is worth reading in why ISB rejects Indian engineers with perfect GMATs.
If you are a non-engineer or from a tier-2 college
Your risk is the opposite. Pedigree may not carry you on line one, so progression and impact have to do more work, faster. State the college plainly, then let a promotion line and a hard metric appear within the first third of the page. A CA, a doctor, or a humanities graduate should treat their non-standard path as the arc, not apologise for it. What a strong version of your file looks like is laid out in what a strong ISB profile looks like.
What this means for Indian applicants
The practical takeaway is to build the resume for the fast read first and the slow read second. Front-load institution and employer names, make progression legible down the left margin, attach a number to every claim of impact, and order the whole page so it points at one goal. ISB now asks for a specific one-page resume format inside the application, so use their template rather than a generic multi-page CV, a point echoed across applicant threads on the ISB one-pager.
If you want a second set of eyes before you submit, our profile evaluation and resume writing services are built around exactly these four scan points, and the full application context sits in our ISB PGP admissions guide.
Common questions applicants are asking
Does ISB require a specific resume format? Yes. The PGP application now includes a defined one-page resume component, and ISB's own admissions FAQ points applicants to the components inside the portal. Use the format the application gives you rather than a self-designed template, and keep it to a single page.
How long is the ISB resume read? There is no published figure, and any exact number you see is an estimate. The honest expectation is that the first pass is fast and the slow, full review comes only after your file clears that initial read. Write for both.
Should I list my CGPA if it is low? State it, in context. ISB says there is no minimum CGPA and that it reads your institution, course choice, and trajectory together. A low number with a rising trend and strong later performance is far better than a gap the reviewer has to wonder about.
How many bullets per role? Two to four, each an outcome with a metric where possible. Reserve the most space for your most recent and most senior role, since that is what the progression scan lands on last and remembers most.
Related reading
Sources verified 18 September 2026 against the Indian School of Business PGP eligibility pages and the Poets&Quants Class of 2026 profile. Next review: 1 January 2028. The ninety-second framing is Pegasus Global Consultants' characterisation of a first-pass review, not official ISB language.