Guide 1 of 8
Write an internship CV
Recruiters spend under a minute on a first read, so keep it to one page and put your strongest proof near the top.
- Header: name, city, phone, a professional email, LinkedIn and GitHub or portfolio link.
- Summary (2 lines): what you study, what you build, what role you want. Example: "Third-year BSc CSIT student who builds web apps with React and Node. Looking for a frontend internship."
- Skills: grouped (Languages, Frameworks, Tools). List only what you can use in an interview.
- Projects: 2 to 4, each with one line on the problem, the stack and a result or link.
- Education: degree, college, expected graduation year.
- Extras: hackathons, CTFs, club roles, volunteering, certifications.
- Save as PDF named
Firstname-Lastname-CV.pdf. - Use action verbs: built, designed, reduced, led.
- No photo, date of birth or citizenship number unless the employer asks.
- Tailor the summary and project order to each role.
Members only · free
Read all 8 career guides
Two guides are open to everyone. Members get the full set, written for students in Nepal.
- Build a portfolio with no work experience
- Set up LinkedIn properly
- Write applications that get read
- Prepare for a hackathon or CTF
- Prepare for interviews
- Prepare scholarship documents early
Guide 2 of 8
Build a portfolio with no work experience
Your projects are your experience. Three finished, documented projects beat ten half-done ones.
- Solve a local problem: a bus route finder for your city, a college notice board, a Nepali-English vocabulary app.
- Write a README for each project: what it does, a screenshot, how to run it, what you learned.
- Deploy it: a live link is far more convincing than code alone. GitHub Pages, Cloudflare Pages and Vercel have free tiers.
- Show your process: short write-ups of a bug you fixed or a CTF you solved show how you think.
Guide 3 of 8
Set up LinkedIn properly
- Clear photo, and a headline that says what you do: "BIT student · Web developer · Open to internships".
- An About section of 3 to 5 lines in plain language.
- Projects and certifications added with links.
- Set "Open to work" for internships, visible to recruiters only if you prefer.
- Post once a week about something you built or learned.
Guide 4 of 8
Write applications that get read
Most applications fail on basics: missed instructions, generic text or a missing link.
- Read the whole call twice and list every required item.
- Answer the actual question in the first sentence of each response.
- Use one specific example per claim: "I led a team of 4 at a 24-hour hackathon" instead of "I am a team player".
- Submit 24 hours before the deadline. Portals slow down on the last day.
- Email follow-ups: short, polite, with the role name in the subject line.
Guide 5 of 8
Prepare for a hackathon or CTF
- Form a balanced team: someone who builds, someone who designs or presents, someone who knows the problem area.
- Set up before the clock starts: GitHub repo, a starter template, accounts for any APIs you plan to use.
- Scope small: one working feature with a clear demo beats five broken ones.
- For CTFs: split challenges by category, keep shared notes, and write up solutions afterwards.
- Practise the demo: 2 minutes on the problem, 2 on the demo, 1 on what's next.
Guide 6 of 8
Prepare for interviews
- Know your CV: be ready to explain every line and every project decision.
- Practise out loud: "Tell me about yourself" in 60 seconds, plus one story each for a challenge, a failure and teamwork.
- Technical rounds: practise problems on paper and explain your thinking as you go.
- Ask questions: about the team, the work you would do and how interns are supported.
- Online interviews: test your internet, camera and microphone 15 minutes early.
Guide 7 of 8
Spot fake opportunities
Real programmes publish their rules openly and never pressure you to pay quickly. Be careful when you see any of these:
- A fee to "reserve a seat", "process your selection" or "unlock your offer letter".
- No official website, or a website that copies a real organization's name with a slightly different address.
- Requests for citizenship copies, bank details, OTP codes or passwords at the application stage.
- Guaranteed jobs, guaranteed visas or prizes with no rules.
- Contact only through a personal phone number or a free email address.
When in doubt, search the organizer's official site yourself instead of using the link you were sent, and ask your college or SWABUD at info@swabud.tech.
Guide 8 of 8
Prepare scholarship documents early
Government scholarships often need documents that take weeks to collect. Start a folder now:
- Academic transcripts and certificates, attested by Nepal's Ministry of Foreign Affairs where required
- Passport, valid well beyond your intended study period
- English test scores, if required (check each programme's rules)
- Two or three referees who know your academic or work record
- Drafts of your personal statement, study plan and career plan
Apply only through the official website or embassy. Government scholarships do not need paid agents.