Professions & remote work
IT CV Format in Nepal
An IT CV in Nepal is read twice: once by software (an applicant tracking system or a keyword search) and once by a human who has fifty more to read. The same page must survive both — machine-scannable structure, and bullets a person actually believes. This guide shows how to do both, with a complete example.
Updated 17 July 2026
Quick answer
An IT CV for jobs in Nepal or remote work is one page with: a dedicated Skills section listing your languages, frameworks, and tools in the exact terms a recruiter searches for; experience and project bullets that state what you built and what changed (performance, users, errors) rather than duties; links to a working GitHub or portfolio; and a single-column, table-free layout that an ATS can parse.
Key takeaways
- An IT CV is read twice — by software, then by a human with fifty more to read — and the same page must survive both.
- Group the stack so it scans in five seconds (Languages / Frameworks / Tools), strongest first, in the posting's exact terms where honestly true.
- Add the outcome to every bullet: "rebuilt the page in React, cutting load from ~6s to under 2s" — not "worked on the website".
- No experience? Projects ARE experience: name, what it does, stack, the hardest part you solved, and a working link (deployed beats repo, repo beats nothing).
- Fifteen technologies at six months each reads as none at all — list only what you can defend in an interview.
Build this CV in the editor.
Start building →Make the stack scannable — and honest
The Skills section is what both the ATS and the recruiter's first glance land on. Group it so it reads in five seconds:
A skills section that scans
Languages: JavaScript/TypeScript, Python, SQL
Frameworks: React, Next.js, Node.js/Express, Django
Tools: Git/GitHub, Docker, PostgreSQL, Linux, Figma
Use the exact terms from the job posting where they honestly apply — an ATS matching "React" will not credit "modern JS frameworks". And keep the list to what you can defend in an interview: a stack of fifteen technologies at six months' experience each reads as none at all.
Tip: Order each line by strength, strongest first. Recruiters assume the first item is your main tool — don't let a framework you touched once lead the line.
Project bullets: what you built, and what changed
The difference between a duties CV and an impact CV is one edit per bullet — add the outcome:
✗ Duties (says nothing)
• Worked on the company website using React.
• Fixed bugs and added features.
• Involved in database management.
✓ Impact (says everything)
• Rebuilt the order-tracking page in React, cutting page load from ~6s to under 2s.
• Closed 40+ reported bugs over six months; wrote regression tests so they stayed closed.
• Redesigned the product tables in PostgreSQL, removing duplicate records across 3 systems.
Numbers make bullets believable, but only honest ones — an interviewer will ask how you measured it. Where you have no number, name the concrete thing instead: the feature, the system, the user group.
No experience yet? Projects are experience
For freshers and career-switchers, a Projects section carries the CV. Treat each project exactly like a job:
- Name it, one line on what it does, and the stack in brackets — "Bus-ticket booking app (Next.js, PostgreSQL)".
- One or two bullets on the hardest part you solved — auth, payments, offline mode — not a feature list.
- A working link: deployed beats repo, repo beats nothing. A dead link is worse than no link.
- College projects count if you can explain every line; tutorial clones count only if you extended them meaningfully.
Tip: Choosing what to learn or aiming at foreign clients? Remote work from Nepal covers which skills remote employers actually hire for and how to build proof of work; free certificates worth a CV line lists verified-free starting credentials like freeCodeCamp.
Keep the layout ATS-safe
All the ATS-friendly CV rules apply here with full force: single column, no tables or text boxes, no icons for section headings, standard section names (Experience, Projects, Skills, Education), and a PDF export. The International ATS template in the builder is built for exactly this.
One page. For an IT CV in Nepal with under ~8 years' experience, a second page signals padding, not seniority.
A complete junior-developer CV example
Example — junior developer, one year plus projects
ANISH GURUNG
Frontend Developer
Lalitpur · 98XXXXXXXX · anish.gurung@email.com
github.com/anishg · anishg.com.np
SUMMARY
Frontend developer with 1 year at a Kathmandu software company and three
deployed personal projects. Strong in React/TypeScript; comfortable owning
a feature from design to release.
SKILLS
Languages: JavaScript/TypeScript, Python, SQL
Frameworks: React, Next.js, Node.js/Express
Tools: Git/GitHub, Docker, PostgreSQL, Figma
EXPERIENCE
Junior Frontend Developer — [company], Kathmandu (2025–present)
• Built the customer dashboard's reporting screens in React; used by ~200
daily users.
• Cut the main bundle size by a third by splitting routes and lazy-loading
charts.
PROJECTS
Room-rent tracker (Next.js, PostgreSQL) — rent and utility split for shared
flats; 60+ signups. Solved: monthly recurring bills and partial payments.
EDUCATION
BSc Computer Science — [college] (2024)
Frequently asked questions
- Should I link my GitHub or portfolio?
- Yes — in the contact block, as a plain readable URL. But audit it first: pin your best repos, add READMEs that say what each project is, and remove or archive abandoned ones. A recruiter who clicks through to sixty forks and no original work leaves worse-impressed than if there were no link.
- How do I show freelance or upwork-style work?
- As real experience: "Freelance Web Developer (2023–present)" with bullets on the two or three strongest delivered projects — what you built, for what kind of client, and the outcome. Anonymous clients are fine ("an Australian logistics startup"); invented ones are not.
- Do certificates (Udemy, Coursera) belong on an IT CV?
- One line each at most, below Education — and only where they support a skill the CV already shows in a project. A certificate for a stack that appears nowhere else on the page raises questions instead of answering them.
- Same CV for local companies and remote jobs?
- The content, yes; the framing, no. For remote roles, follow the remote-job CV guide: everything in clean English, results stated in terms a foreign reader can verify, and time-zone/communication signals added. For local IT companies, the same page works as-is.