Getting started · 6 min read
How to land your first internship with no experience
Every student starts with an empty "Experience" section. Recruiters hiring interns know that. What they look for instead is evidence that you can learn quickly and finish things. You can build that evidence in a few weeks.
1. Build two or three projects that solve a real problem
One finished, deployed project beats five tutorial clones. Pick something you or people around you actually need: a timetable planner for your college, an expense splitter for your hostel, a dashboard built on public data from data.gov.in. Put the code on GitHub with a clear README (what it does, a screenshot, how to run it) and deploy it so a recruiter can click and try it in ten seconds.
2. Get one "proof of work" line from outside your college
A hackathon, a merged open-source pull request, or a rated contest profile tells a recruiter that someone else has already checked your work. Beginner-friendly places to start: weekend hackathons, weekly coding contests, and programs like Hacktoberfest and GirlScript Summer of Code.
3. Apply consistently, not all at once
Students often send 50 applications in one weekend, hear nothing, and give up. A better rhythm is 10–15 tailored applications a week, tracked in one place. On ORBNET you can filter for roles in India, remote roles or startups, and save everything to your dashboard so you know what you've applied to and when to follow up.
4. Know the hiring calendar
Large companies usually open summer internship applications months in advance, sometimes in the previous autumn, and close them once they've found enough candidates. Startups hire year-round and often move from application to offer in a week or two. So apply early for big names, and keep a steady stream of startup applications going all year.
5. Don't ignore non-tech roles
Operations, product, design, marketing, content and data-analysis internships are often less crowded than software roles and teach skills that transfer anywhere. If you're from a non-CS branch, these are a great door into the industry.
The goal of your first internship isn't the perfect company. It's a real manager who can vouch for you. That reference makes the second internship far easier.
Resume · 6 min read
The one-page resume that gets past ATS filters
Most companies run applications through an Applicant Tracking System (ATS) before a human sees them, and when a recruiter does look, they often skim for only a few seconds. Your resume has two jobs: be readable by software, and be scannable by a busy human.
Format: boring is good
- One page, single column. Skip photos, skill-level bars, icons and text boxes; parsers often scramble them.
- Use standard headings: Education, Projects, Experience, Skills, Achievements.
- Pick a clean font (Calibri, Arial, Inter, Garamond) at 10–11 pt, with consistent date formats and margins.
- Export as PDF unless the company asks for something else, and name it properly:
Firstname-Lastname-Resume.pdf.
Order for students
Header (name, phone, professional email, LinkedIn, GitHub or portfolio) → Education → Projects → Experience (if any) → Skills → Achievements. For most students, projects are the strongest section, so put them high.
Write bullets with this formula
Action verb + what you built + how + result. Numbers make it real.
WeakWorked on a website for college fest using React.
StrongBuilt the registration site for our college fest in React and Firebase; handled 1,200+ sign-ups and cut the organisers' manual work from 3 days to 3 hours.
Tailor it, honestly
Read the job description and mirror its important keywords where they're true for you. If it says "SQL" and "dashboards" and you built one in Power BI, say exactly that. Never list a skill you couldn't discuss for five minutes in an interview; that's the first thing interviewers probe.
Final checklist
- Fits on one page, with no spelling mistakes (read it aloud once)
- Every project has a link to the code or a live demo
- At least half your bullets include a number or a concrete result
- Your email address is professional (not a nickname)
- The file is a PDF with your name in the file name
Safety · 4 min read
How to spot a fake internship in 60 seconds
Fake internships and job offers target students because they're eager and less likely to know the warning signs. Almost every scam shows at least one of these red flags.
Red flags
- They ask you to pay. Registration fees, "training fees", a refundable "security deposit", or paying for your own certificate. Genuine employers pay you, never the other way round.
- An offer with no real interview. "You're selected!" after a two-minute chat or a form submission.
- Personal email or chat-only contact. Recruiters using Gmail or Yahoo addresses, or talking only on WhatsApp or Telegram.
- Pressure and urgency. "Only 2 seats left, pay within an hour."
- Too good to be true. High pay for simple "typing", "data entry" or "like and review" tasks.
- Sensitive details too early. Asking for bank details, Aadhaar, PAN, or an OTP before any official offer letter.
How to verify in a minute
- Find the role on the company's official careers page. Every role on ORBNET links to one.
- Check the sender's email domain matches the company's website exactly (watch for look-alikes such as
g00gle-careers.com).
- Search the company on LinkedIn: do real employees work there?
- For Indian companies, look up the registered company on the Ministry of Corporate Affairs portal.
- Search "company name + scam" or "+ fraud" and read what others have reported.
If something already went wrong
Stop all contact and payments, call your bank immediately if you shared card or account details, and report it on India's National Cyber Crime Reporting Portal or the cyber-fraud helpline 1930. The sooner you report, the better the chance of stopping the money. And if someone used ORBNET's name, please tell us.
Outreach · 5 min read
Cold emails and LinkedIn messages that get replies
Many internships, especially at startups, are filled before they're ever posted. A short, specific message to the right person can get you an interview without competing in a pile of thousands of applications.
Who to message
At startups (under ~100 people), write to a founder or the head of the team you want to join. At larger companies, an engineering or team manager or an alumnus from your college usually beats a generic HR inbox. Find them on the company's website, LinkedIn, or their engineering blog.
A five-line template
Subject: Built [thing related to their product]: internship?
Hi [Name],
I'm [Name], a [year] [branch] student at [college]. I've been using [product] and built [small, relevant project] that [result]. Here's the link: [link].
I'd love to intern with your [team] this [season]. I'm strong in [2 skills], and happy to do a short task to show how I work.
Would you be open to a 10-minute chat this week?
Thanks,
[Name] · [LinkedIn] · [GitHub]
What makes it work
- Specific beats generic. Mention their product, a recent launch, or a blog post. Mass messages are easy to spot and easy to ignore.
- Show, don't tell. One link to something you built is worth more than a paragraph of adjectives.
- Make the ask small. "A 10-minute chat" is easy to say yes to; "please give me an internship" isn't.
- Keep it short. If it doesn't fit on a phone screen, cut it.
Follow up once or twice
No reply after 4–5 working days? Send one polite follow-up in the same thread ("Bumping this in case it got buried, happy to share more details"). Then move on. Silence usually means busy, not rejected.
Interviews · 6 min read
Getting through your internship interview
Internship interviews test three things: can you do the basics, can you explain your own work, and would people enjoy working with you? Prepare for each one deliberately.
Before the interview
- Re-read the job description and write down the three skills it emphasises most.
- Use the product. Have one thing you like about it and one idea to improve it.
- Revise every project on your resume. Expect "Why did you choose this database?" and "What would you do differently?"
Technical rounds (software roles)
- Be comfortable with the fundamentals: arrays, strings, hashing, two pointers, sorting and binary search, recursion, linked lists, stacks and queues, trees, and basic graphs (BFS/DFS).
- Think out loud. Interviewers are judging your approach as much as the final code.
- Clarify the problem first, start with a simple solution, then improve it. State the time and space complexity.
- Test your code with an edge case (empty input, one element, duplicates) before saying "done".
Behavioural questions: use STAR
For "Tell me about a time you…" questions, answer with Situation, Task, Action, Result in about 90 seconds. Prepare three stories in advance (a challenge you solved, a conflict in a team, something you learned fast) and adapt them to the question.
Questions to ask them
- "What would a great first month look like for an intern on this team?"
- "What did the last intern work on?"
- "How does the team review code or give feedback?"
After
Send a two-line thank-you email within a day, mentioning something specific you discussed. It's rare enough that people remember it.
Ready to put this into practice? Browse live internships or fresher jobs.