Build a resume, portfolio and application that actually get read.
A single, practical reference for writing resumes, cover letters and portfolios that pass ATS software, hold a recruiter's attention, and represent your work honestly — for freshers, experienced professionals, career switchers, freelancers, researchers and government job aspirants alike.
What a resume is actually for
A resume's only job is to get a real conversation started. It is not an autobiography, and it is not proof of effort — it is a targeted, skimmable case for why you, specifically, are worth 20 minutes of someone's time.
Every strong resume answers three silent questions a reader is asking, usually in this order: can you do the job, will you fit the team, and is there proof behind your claims? Everything on the page should serve one of those three questions. If a line doesn't, it's a candidate for deletion.
Resume vs. CV vs. Biodata
These three terms get used loosely, especially across Indian job portals and government application forms, but they are not the same document. Knowing which one an employer actually wants prevents an easy, avoidable rejection.
| Document | Typical length | Where it's used | Structure |
|---|---|---|---|
| Resume | 1–2 pages | Private sector roles worldwide — corporate, startup, MNC, and most freelance or remote hiring | Skimmable, achievement-first, tailored to each job posting |
| CV (academic/research) | 2 pages and up, no fixed cap | Academia, research fellowships, medical and scientific roles, and many PSU or government application forms that use "CV" to mean a full career record | Comprehensive and reverse-chronological; includes publications, grants, and full teaching or research history |
| Biodata | 1 page | Older South Asian convention; occasionally still requested on specific government or PSU forms | Personal details, education, and family background — largely replaced by the resume format in modern private-sector hiring |
In everyday conversation, especially in India, the UK, and much of Europe, "CV" is often used to mean exactly what this guide calls a resume. When a job listing just says "send your CV" without specifying an academic or research role, a standard 1–2 page resume is almost always the right document. When in doubt, match the format the employer's own application portal or template implies.
What recruiters are actually scanning for
Evidence over adjectives
"Hardworking" and "detail-oriented" are claims. "Reduced onboarding time from 9 days to 4" is evidence. Recruiters trust numbers, outcomes, and named tools far more than self-description.
Relevant keywords, in context
Both the ATS and the human skimming after it are pattern-matching your resume against the job description. The skills and tools mentioned in the posting need to appear naturally in your bullets — not just listed once at the bottom.
A readable career story
Gaps, lateral moves, and short stints aren't automatically disqualifying — unexplained ones are. A resume that lets the reader follow your logic reduces the chance they invent a worse explanation themselves.
Absence of red flags
Typos, inconsistent dates, unprofessional email addresses, and formatting that breaks on their system quietly signal carelessness — often before a single line of content is judged on merit.
Choosing the right resume format
The format is the skeleton your content hangs on. Picking the wrong one for your situation makes even strong experience look weaker than it is.
Chronological
Lists roles in reverse order, most recent first. The format recruiters and ATS software are most familiar with.
- Strong for: consistent work history, staying in the same field, experienced professionals
- Weak for: career switchers, visible employment gaps, first-time job seekers
Functional (skills-based)
Groups content by skill or theme instead of by job, pushing the timeline further down the page.
- Strong for: major career pivots, long gaps, returning professionals
- Weak for: ATS parsing (dates and titles are harder to extract) and recruiter trust — many read it as an attempt to hide something
Combination (hybrid)
Opens with a skills or summary block, then follows with a standard reverse-chronological work history.
- Strong for: most experienced professionals, career switchers with transferable skills, and anyone who wants strengths visible before job titles
- Weak for: nothing significant — the small extra effort to build it is almost always worth it
The anatomy of a resume, section by section
Not every section applies to every reader. Open the ones relevant to your situation — a fresher and a 15-year executive will use a different subset of this list.
Resume headline Optional but high-impact
A one-line label under your name that tells the reader what you are before they read anything else — especially useful on LinkedIn and portals where resumes are searched by keyword.
Example: Senior Backend Engineer · Distributed Systems · 6 Years · Java, Go, AWS
Resume summary 2–4 sentences, near the top
A short pitch that states your experience level, core specialty, and one standout result. Written in third person without pronouns, present tense for current focus.
Example: Financial analyst with 4 years in FP&A for D2C retail. Built a rolling forecast model that cut month-end close time by 30%. Strong in Excel modeling, SQL, and stakeholder reporting.
Best for candidates with at least 1–2 years of relevant experience.
Career objective Best for freshers & career switchers
States what you're aiming for and why you'd bring value, used when there isn't yet an experience track record to summarize. The most common resume-writing mistake here is writing what you want ("seeking a challenging role to grow my skills") instead of what you offer.
Weak: Seeking a challenging position where I can learn and grow.
Strong: Mechanical engineering graduate with hands-on CAD and thermal-analysis project experience, seeking an entry-level design role to apply simulation skills to real manufacturing problems.
Professional experience The core of most resumes
Reverse-chronological list of roles. Each bullet should follow a simple formula: action verb + what you did + measurable result. Avoid duty lists ("Responsible for managing a team") in favor of outcomes ("Led a 5-person team to ship the checkout redesign 3 weeks ahead of schedule").
Aim for 3–6 bullets per role, with more space given to recent and relevant positions and less to older or unrelated ones.
Achievements Optional standalone section
Worth breaking out separately when you have 2–4 results so strong they'd get buried inside a longer experience section — a patent, a major award, a record sales quarter, a published paper that drove hiring interest on its own.
Projects Essential for freshers, tech, design & research
For students, freshers, and career switchers without much paid experience, projects often carry more weight than the education section. Include the problem, your specific role, tools used, and outcome — and link to a live demo, repository, or write-up whenever possible.
Education
Degree, institution, graduation year, and location. Include GPA/percentile only if it's strong and recent (typically within 3 years of graduating) or explicitly requested. Coursework and academic projects belong here for freshers; they usually get dropped once you have 2+ years of work experience.
Skills Keep it tailored, not exhaustive
Split into logical groups (e.g., "Technical" and "Tools," or "Languages" and "Frameworks") rather than one long undifferentiated list. Match the exact terms used in the job description — an ATS matching "ML" against a posting that says "Machine Learning" may not connect the two.
Certifications
Include the certifying body and year. Prioritize certifications that are current, recognized in your industry, and relevant to the specific role — a long list of unrelated online-course certificates can dilute rather than strengthen a resume.
Awards
Academic honors, competition wins, or workplace recognitions. Include the awarding body and a one-line note on what it recognized if the name alone isn't self-explanatory.
Languages Relevant for government, hospitality & international roles
List spoken and written languages with an honest proficiency level (native, fluent, professional working proficiency, conversational). Particularly relevant for government exams and postings, hospitality, aviation, translation, and international or client-facing roles.
Volunteer experience
Valuable when it demonstrates relevant skills, leadership, or commitment — especially for freshers, career switchers, and anyone with a gap in paid employment. Treat it with the same bullet structure as professional experience.
Publications Academic & research CVs
Use standard citation format for your field. On a research or academic CV this section can run long; on an industry resume, list only the 2–3 most relevant or high-impact publications.
References Usually skip it
"References available upon request" is outdated and wastes a line — employers assume this by default. Only include actual reference contacts if an application explicitly asks for them.
How Applicant Tracking Systems actually read your resume
Most mid-size and large employers filter applications through an Applicant Tracking System before a person ever opens them. Research tracking Fortune 500 career pages has found an ATS in use at roughly 97–98% of those companies, and separate recruiter surveys put overall ATS or tech-assisted screening at around 75% of hiring teams — though adoption is lower among small businesses. Understanding what the software is actually doing removes most of the mystery.
What an ATS does — and doesn't do
An ATS is a database with a parser attached, not a judge of talent. When you apply, it extracts your text into structured fields (name, contact, job titles, dates, skills), stores it, and lets recruiters search, filter, and rank applicants against the fields they've defined for that role.
It rejects almost nothing outright by "quality." What it does do is fail to extract information from resumes it can't parse cleanly — which then shows up to a recruiter as a blank field, a missing skill, or a resume that never surfaces in a keyword search at all.
Formatting that breaks parsing
- Text inside tables, text boxes, or multi-column layouts — many parsers read left-to-right across columns and scramble the order
- Headers, footers, and text embedded inside images or icons
- Unusual section titles ("My Journey" instead of "Experience")
- Fancy Unicode bullets, symbols, or decorative fonts in place of standard characters
- Dates in inconsistent or non-standard formats
A single-column, standard-heading, plain-text-based resume gets parsed cleanly like this. Tables and columns often scramble the order above.
Keyword strategy that doesn't read as stuffing
ATS keyword matching and human readability aren't actually in conflict — a resume optimized correctly for one reads naturally to the other. The method:
- Pull the language from the job description itself. If it says "stakeholder management," use that exact phrase somewhere rather than only your synonym, "cross-functional communication."
- Spell out acronyms at least once. Write both "Search Engine Optimization (SEO)" and "SEO" so both forms are matchable.
- Place keywords in context, inside real bullets — not just in a dense skills list at the bottom, which some parsers weight less than skills demonstrated in experience.
- Never list a skill you can't discuss in an interview. Passing the ATS filter only to fail the human conversation it earned you is a worse outcome than not passing at all.
- Standard section headings (Experience, Education, Skills)
- Single column, left-to-right reading order
- .docx or a text-based PDF as the file format
- Standard bullet characters, not custom icons
- Skills or dates placed inside tables or text boxes
- Resume built as an image or infographic
- Headers/footers containing contact information only
- Multi-column "designer" templates from generic builders
Length, layout, fonts, and file format
Design choices on a resume aren't about looking impressive — they're about removing friction between your content and the reader's attention.
Length
- 0–10 years experience: one page
- 10+ years, or academic/research CV: two pages is acceptable; let content density decide, not a fixed rule
- Executive resumes: two pages is standard practice at senior and C-level
Fonts
- One font family, using weight (bold) and size for hierarchy — not multiple typefaces
- Safe choices: Calibri, Arial, Helvetica, Georgia, or a clean system serif/sans
- Body text no smaller than 10.5–11pt; name/headers can run larger
Colors
- Black text on white is always safe and prints reliably
- One restrained accent color for headings or a divider line is fine for most industries
- Creative fields (design, media, advertising) have more room for visual personality — corporate, government, legal, and finance generally reward restraint
Layout
- Single column, generous white space, consistent margins (0.5"–1")
- Left-aligned text; avoid full justification, which creates uneven word spacing
- Consistent formatting for every date, every heading, every bullet style throughout
File format
- .docx is the safest default for ATS parsing in most job-portal uploads
- Text-based PDF (not a scanned image) is safe for most modern systems and preserves formatting exactly — good when emailing directly to a person
- Follow the employer's stated preference on the application form over any general rule
File naming
- Use your name, not "Resume_Final_v3(2).docx"
- Format:
FirstName_LastName_Resume.pdf, or add the role for tailored versions:FirstName_LastName_Resume_ProductManager.pdf
Resume advice for your specific career stage
Generic advice fails here more than anywhere else. What helps a fresher can actively hurt an executive, and vice versa.
Freshers & students
- Lead with education and projects — experience section is optional if genuinely empty
- Internships, coursework projects, and college fest/committee leadership all count as real content
- Use a career objective, not a summary, until you have real work outcomes to summarize
Experienced professionals
- Lead with a summary and quantified achievements, not job duties
- Compress or drop roles older than 10–15 years unless directly relevant
- Show progression — titles, scope, and team size increasing over time
Career switchers
- Use the combination format so transferable skills lead before an "unrelated" job title does
- Name the transferable skill explicitly — don't assume the reader will connect the dots themselves
- A short "why I'm switching" line in the summary pre-empts the reader's biggest objection
Freelancers & consultants
- Structure gigs and clients like roles — client/project name, scope, outcome — instead of one vague "Freelance" line
- Group similar short projects together rather than listing each individually if there are many
- A linked portfolio matters more here than almost anywhere else — treat it as mandatory, not optional
Government job aspirants
- Follow the exact format specified by the application/notification — deviating can mean rejection regardless of content
- Include full personal and education details many private-sector resumes omit (father's/mother's name, category, exam roll numbers) only when explicitly requested on the form
- Double-check every date against certificates — government scrutiny is typically stricter than private-sector screening
International & remote applicants
- Check country norms: a photo, date of birth, and marital status are expected in some countries and considered inappropriate (even risky for the employer, under anti-discrimination law) in others, including the US
- State time zone and language proficiency explicitly for remote-first roles
- Note visa/work-authorization status only if the posting asks — don't volunteer it unprompted
Career gap / returning professionals
- A one-line, factual gap explanation is safer than leaving the reader to guess ("Caregiving leave, 2023–2024")
- List relevant learning, freelance work, or volunteering that continued during the gap
- Combination format again helps: skills first, timeline second
Entrepreneurs & founders
- Treat your own venture like a role: scope, team size, funding/revenue milestones, and what happened to it
- Be specific about your actual function (product, ops, fundraising) — "Founder" alone tells a recruiter little
- Address a closed or paused venture matter-of-factly; framing it as a learning experience reads better than omitting it
Executives
- Lead with strategic impact and organizational scale (P&L size, team size, market outcomes) over day-to-day tasks
- Two pages is standard; a one-page "career highlights" leadership brief can supplement it for board or executive-search contexts
- Board memberships, speaking engagements, and thought leadership belong here, not on an early-career resume
Quick reference: what changes by industry
Format and tone stay largely constant — what to lead with, what to prove, and what a portfolio should contain shift a lot by field. This table is a starting map; each industry has its own dedicated deep-dive guide linked at the bottom of this page.
| Industry | Lead with | Portfolio / proof expected | Common keywords to mirror |
|---|---|---|---|
| Software & IT | Shipped systems, scale, measurable performance gains | GitHub, live projects, technical writing | Languages, frameworks, cloud platforms, system design |
| Data Science / AI / ML | Models shipped to production, measurable business impact | GitHub, Kaggle, published notebooks, case studies | Python, model names, MLOps, specific metrics (AUC, F1) |
| UI/UX & Product Design | Design process and outcomes, not just visuals | Behance, Dribbble, or a portfolio site with 3–5 case studies | User research, wireframing, Figma, design systems |
| Graphic & Creative Design | Range and craft of visual work | Behance/Dribbble/Instagram with curated best work | Brand identity, typography, Adobe Creative Suite |
| Architecture | Built or academic projects with clear authorship | Visual portfolio (PDF or site) with drawings, renders, models | AutoCAD, Revit, sustainable design, project scale |
| Civil / Mechanical / Electrical Engineering | Projects delivered, standards compliance, safety record | Project sheets, CAD drawings, site documentation | Relevant codes/standards, CAD tools, project value/scale |
| Healthcare (Doctors, Nurses, Pharmacists) | Clinical experience, patient outcomes, specialization | Licenses, certifications listed prominently; publications for specialists | Clinical terms, licensure numbers, EMR systems |
| Teaching & Academia | Teaching philosophy, subjects, student outcomes | Academic CV with publications, conferences, teaching portfolio | Curriculum, pedagogy, subject specializations |
| Hospitality, Hotel Management & Aviation | Guest-facing metrics, service scope, languages spoken | Certifications (safety, service standards); rarely a visual portfolio | Guest satisfaction, service standards, multilingual |
| Banking, Finance & Accounting | Quantified financial impact, compliance, accuracy | Rarely a visual portfolio; certifications (CFA, CA, CPA) matter more | Financial modeling, reconciliation, audit, regulatory terms |
| Legal | Practice area, case/matter experience, bar admission | Publications, notable matters (where confidentiality allows) | Practice area terms, jurisdiction, litigation/transactional |
| Marketing & Digital Marketing | Campaign results, growth metrics, channels owned | Campaign case studies, analytics dashboards, portfolio site | SEO, CAC, ROAS, specific platforms (Meta Ads, Google Ads) |
| Sales & Business Development | Quota attainment, deal size, pipeline growth | Rarely required; references and numbers do the work | Quota, pipeline, closed-won, ACV/ARR |
| Human Resources | Process improvements, retention, hiring outcomes | Rarely visual; process documentation if requested | HRIS systems, retention rate, time-to-hire |
| Manufacturing & Supply Chain | Efficiency gains, cost reduction, safety record | Process documentation, certifications (Six Sigma, Lean) | Lean, Six Sigma, throughput, inventory turns |
| Media, Journalism & Content Writing | Published work, audience reach, beat expertise | Published clips, byline links, writing samples | Beat/topic areas, publication names, CMS tools |
| Government & Public Sector | Exact format compliance, tenure, postings held | Rarely a portfolio; certificates and mark sheets instead | Exact terminology from the official notification |
| Agriculture & Allied Sciences | Field experience, yield/efficiency outcomes, research | Field reports, research publications where applicable | Crop science terms, extension work, sustainability |
| NGO & Development Sector | Program scale, beneficiaries reached, grant management | Program reports, impact case studies | Program management, M&E, grant/donor terms |
The mistakes that quietly cost interviews
Most rejected resumes aren't rejected for one dramatic error — they lose the reader gradually, one small friction point at a time.
"Responsible for handling customer queries" describes a job description, not your performance in it.
"Resolved an average of 45 customer queries daily with a 96% satisfaction rating, reducing escalations by 20%."
A single unedited resume blasted at every posting ignores that different roles value different parts of the same experience.
Keep one master resume with everything, then trim and re-order it to match each specific job description before sending.
An email like coolgamer2004@ or a resume with no LinkedIn/portfolio link undercuts an otherwise strong document.
Use firstname.lastname@, a professional-looking free email address, and include LinkedIn and portfolio links where relevant.
Mixed date formats, uneven spacing, and three different bullet styles read as carelessness even when the content is strong.
Pick one date format, one bullet style, and one spacing rhythm, then apply them identically across every section.
Your strongest, most relevant qualification sitting on page 2 means many readers never see it at all.
Put your best, most job-relevant material in the top third of page one — summary, top skills, and strongest achievement.
A single typo in a resume with "detail-oriented" listed as a skill undermines the claim on sight.
Read it aloud, run a spell-check, and have one other person review it before you send it anywhere.
Bullet formulas and before/after examples
Templates you can adapt directly — swap in your own numbers, tools, and context.
The universal bullet formula
[Action verb] + [what you did / built / led] + [measurable result or scale]
Not every bullet will have a hard number — but aim for at least 60–70% of your bullets to include one.
"Built a full-stack expense tracker as a college project using React and Node.js, used by 40+ classmates during a semester-long trial."
"Redesigned the onboarding flow, cutting average setup time from 12 minutes to 4 and improving 30-day retention by 18%."
"Led a 9-person cross-functional team to launch a new product line that generated ₹2.3 crore in first-year revenue."
Strong action verbs by category
| Leadership | Building / Creating | Improving | Analyzing |
|---|---|---|---|
| Led, managed, directed, mentored, coordinated | Built, designed, launched, developed, engineered | Improved, streamlined, reduced, increased, optimized | Analyzed, evaluated, forecasted, audited, researched |
Cover letters, cold emails, and follow-ups
A cover letter's job is different from a resume's: it explains why this role, why this company, why now — context a resume can't hold on its own.
The structure that works
- Opening (1–2 sentences): the specific role, and one genuine, specific reason you want it — not "I am writing to apply for..."
- Body (2–3 sentences): one or two achievements mapped directly to what the job description asks for, not a restatement of your resume
- Closing (1–2 sentences): a clear, confident close — availability, enthusiasm, and a thank-you
Common mistakes
- Opening with "To Whom It May Concern" when the hiring manager's name is findable
- Repeating the resume line by line instead of adding context
- Making it about what you want ("this would be a great growth opportunity for me") instead of what you offer
- Running past one page — three to four short paragraphs is the ceiling
Dear [Hiring Manager's name],I'm applying for the [Job Title] role at [Company]. [One specific, genuine reason tied to the company or the work itself].In my current role at [Company], I [achievement directly relevant to their need, with a number]. I also [second relevant strength or result], which maps closely to [specific requirement from the posting].I'd welcome the chance to talk about how I can contribute to [team/goal]. Thank you for your time and consideration.[Your name]
Email & outreach templates
Copy, then personalize every bracketed section — a template that's obviously unedited is worse than no outreach at all.
Subject: [Your field] professional interested in [Company]'s [team/product] Hi [Name], I've been following [Company]'s work on [specific product/initiative] and wanted to reach out directly. I'm a [your role/title] with [X years/key skill], and I recently [relevant achievement]. I don't see an open posting that's an exact match, but I'd value 15 minutes to learn more about the team and share a bit about my background, in case something opens up. Resume attached for context. Thank you for considering it. [Your name] · [Portfolio/LinkedIn link]
Subject: Quick favor — referral for [Job Title] at [Company] Hi [Name], Hope you're doing well! I saw [Company] is hiring for a [Job Title] role, and I think it lines up closely with my background in [relevant area]. Would you be open to referring me, or introducing me to the hiring manager if that's easier? Happy to send my resume and a short summary you can forward along — just let me know what's useful. Really appreciate you considering it either way. [Your name]
Subject: Following up — [Job Title] application Hi [Name], I wanted to follow up on my application for the [Job Title] role, submitted on [date]. I remain very interested in the opportunity and in contributing to [specific team/project]. Happy to share any further information that would help with your decision. Thank you again for your time. [Your name]
Subject: [Your Name] — Interest in [Internship Title] Internship Dear [Name], I'm a [year/program] student at [college], currently looking for a [season] internship in [field]. [Company]'s work on [specific project/product] is exactly the kind of problem I'd like to contribute to. I've worked on [relevant class project/personal project] and am comfortable with [relevant tool/skill]. I've attached my resume and would welcome the chance to discuss how I could contribute to your team. Thank you for your time and consideration. [Your name]
Subject: Thank you — [Job Title] interview Hi [Name], Thank you for taking the time to speak with me today about the [Job Title] role. I enjoyed learning more about [specific thing discussed] and am even more excited about the opportunity to contribute to [team/goal]. Please let me know if there's any further information I can provide as you move forward with the process. Best, [Your name]
Hi [Name], I noticed you work on [team/area] at [Company] — I'm currently exploring roles in [field] and would really value your perspective. Would you be open to a brief chat sometime? Totally understand if you're busy — no pressure either way. Thanks for considering it!
Building a portfolio that proves your resume
A resume tells; a portfolio shows. For design, tech, writing, architecture, and freelance work especially, it's often the actual deciding factor after the resume gets you noticed.
What every portfolio needs, regardless of field
A clear intro
Who you are and what you do, in one sentence a stranger would understand.
3–5 strong pieces
Curated, not comprehensive. A weak 10th project dilutes a strong portfolio more than it adds to it.
Context per piece
The problem, your specific role, and the outcome — never just a finished image with no story.
An easy way to reach you
Contact details or a direct calendar/email link, not buried three clicks deep.
The case study structure (for design, product, tech & consulting)
| Section | What it covers |
|---|---|
| Problem | What situation or challenge existed before you got involved, and why it mattered |
| Your role | What you specifically did — critical on team projects, where credit can otherwise be ambiguous |
| Process | Key decisions and trade-offs, not a step-by-step diary — show judgment, not just activity |
| Outcome | What changed as a result — a metric where possible, honest qualitative impact where it isn't |
Where to host it, by field
| Field | Common platforms |
|---|---|
| Software engineering | GitHub (pinned repos with real READMEs), GitHub Pages, or a personal domain |
| Data science / ML | GitHub, Kaggle profile, a personal site with written case studies |
| UI/UX & product design | Behance, Dribbble, Adobe Portfolio, Figma community, or a personal site |
| Graphic & brand design | Behance, Dribbble, Instagram (curated, not a feed of everything) |
| Architecture & interior design | A PDF portfolio (still the industry standard for applications), plus Behance or a personal site |
| Writing & journalism | A simple personal site or Substack/Medium with linked, published bylines |
| Photography & film | A dedicated site (Format, Squarespace), Instagram as a secondary showcase |
| Product management | Notion page or personal site with 2–3 written case studies of shipped products |
| Consulting & business strategy | A PDF one-pager or Notion page with anonymized project summaries |
| Teaching & research | A personal or university-hosted academic page listing publications, syllabi, and teaching evaluations |
Don't have "real" projects yet? Build them.
Technical fields
- Rebuild a real product's core feature and write up the trade-offs you made
- Contribute to an open-source project and document your specific contribution
- Analyze a public dataset and publish the findings with your reasoning, not just the code
Design & creative fields
- Pick a brand or app you use and redesign one flow — explain what you'd change and why
- Offer a scoped, real project to a local business or nonprofit in exchange for a case study
- Enter a design brief/challenge from a community you're active in and document your process
Making sure the rest of your online presence agrees with your resume
Most recruiters search your name before or after reading your resume. What they find should reinforce it, not contradict it.
- Headline should say what you do, not just your job title — add your specialty or a one-line value statement
- About section can be longer and more conversational than a resume summary; it's where personality is allowed
- Keep job titles and dates consistent with your resume — mismatches are one of the first things recruiters cross-check
GitHub (technical roles)
- Pin your 4–6 strongest repositories, not everything you've ever pushed
- Write a real README for each pinned project: what it does, how to run it, what you learned
- A clean, active commit history on relevant projects matters more than raw follower count
Behance & Dribbble (design roles)
- Behance rewards full case studies; Dribbble favors polished single shots — use them for different purposes
- Custom cover images and consistent project naming make a profile look intentional rather than dumped
- Quality and curation beat volume — a tightly edited profile of 6 strong projects consistently outperforms 30 mixed ones
Professional bio / "About me"
- Third person for formal use (speaker bios, "About" pages); first person for LinkedIn and personal sites
- Structure: who you are + what you specialize in + one credibility marker + what you're focused on now
- Keep a short (1–2 sentence) and a long (short paragraph) version ready — different platforms need different lengths
Before you hit submit
Run through this once for every application — it takes under five minutes and catches most of the mistakes covered above.
0 / 10 complete
Frequently asked questions
How long should a resume actually be?
One page for most people with under 10 years of experience. Two pages become acceptable once you have a long enough track record that trimming to one page would mean cutting genuinely relevant material — that's usually somewhere past the 10-year mark, or for academic/research CVs and executive resumes.
Should I use a resume template from a website?
Only if it's a simple, single-column layout. Many visually striking templates from generic builder sites use multi-column layouts, graphics, or text boxes that parse poorly in an ATS. Simpler is safer — you can always show more personality on a linked portfolio.
Do I still need a cover letter if the application marks it optional?
Generally yes, if you have the time to write a genuine one. "Optional" filters out candidates unwilling to make the extra effort, which can work in your favor. A short, specific, non-generic cover letter costs little and rarely hurts.
What if I don't have any directly relevant experience?
Lead with transferable skills and projects instead of a thin experience section. Use the combination format, name the transferable skill explicitly rather than assuming the reader will infer it, and consider building a small relevant project specifically to fill the gap.
Should I include a photo on my resume?
It depends on the country and industry. Common and often expected in parts of Europe, Asia, and for some Indian government/PSU forms; generally discouraged in the US, UK, Canada, and Australia, where it can raise anti-discrimination concerns for the employer. When unsure, check the norm for the specific country and role.
How often should I update my resume?
After every significant achievement, not just when you're job hunting. Updating in the moment keeps details and numbers accurate — memory fades fast, and "roughly 20%" six months later is a weaker claim than a number you wrote down right away.
Is it okay to use AI tools to help write my resume?
Yes, for structure, phrasing, and tightening bullets — but every claim and number still needs to be true and something you can defend in an interview. AI is a strong editor and a poor source of your actual achievements; you're still the only source of truth for what you did.
What's the real difference between a resume and a CV?
A resume is short (1–2 pages) and tailored per application; a CV is comprehensive and grows over a career, used mainly in academia, research, and some government/PSU contexts. In casual conversation the two terms are often used interchangeably — check what the specific employer or form actually expects.
How do I explain a career gap without it hurting my chances?
State it factually in one line rather than leaving it unexplained — reviewers tend to assume worse than the truth when a gap is left silent. Mention anything relevant you did during the gap (learning, freelancing, caregiving, health) briefly and move on.
Go deeper on your specific situation
This guide is the hub for Abhyashsuchi's resume and portfolio coverage. Each topic below has (or will have) its own full-length, dedicated guide.
The Complete ATS Optimization Checklist
A line-by-line audit for making any resume ATS-safe.
Deep DiveIndustry-Specific Resume Guides
Full breakdowns for tech, healthcare, design, government, and more.
Deep DivePortfolio Examples By Field
Real-structure walkthroughs for design, tech, and creative portfolios.
Deep DiveCover Letter Examples That Worked
Annotated examples across entry-level to executive roles.
Deep DiveGovernment Job Resume Format Guide
Form-by-form guidance for Indian government and PSU applications.
Deep DiveLinkedIn Profile Optimization Guide
Turning your profile into an inbound opportunity magnet.
