First Job Guide for Freshers
Getting Your First Full-Time Job After College — Off-Campus Strategy
Most engineering graduates spend 6–18 months job hunting after college when they do not have an on-campus placement. The difference between a 3-month search and a 12-month search is almost entirely strategy — not luck. This guide covers the complete off-campus job search: profile building, where to apply, how to prepare for technical interviews, and how to evaluate your first offer.
Key facts you need to know
70% of tech jobs are never publicly listed
They are filled through referrals, internal transfers, and direct recruiter outreach. Applying on job boards alone misses the majority of opportunities.
Average job search for a fresh engineering graduate: 4–8 months
With a strong profile and active search, this reduces to 2–3 months. Without strategy, it extends to 12–18 months.
First 3 years of experience determine your 10-year trajectory
The skills, processes, and colleagues you encounter in your first 2–3 roles shape your technical identity more than education. First job selection matters beyond just the salary.
Action timeline
Pre-search (3–6 months before graduation)
Final year, first semester
- Complete all portfolio projects and deploy them publicly with clean READMEs
- Update LinkedIn: headline, about section, all experiences, skills, and project links
- Begin active LeetCode practice if targeting product companies
- Reach out to alumni from your college at target companies for referrals
- Attend company info sessions, tech meetups, and hackathons
Active search (graduation to offer)
Final semester or immediately after graduation
- Apply to 50–100 positions across tiers — do not be selective at the application stage
- Track every application in a spreadsheet: company, role, date applied, status, follow-up date
- Follow up on applications 7–10 days after applying if no response
- Do 2–3 mock interviews per week with peers or a mentor
- Negotiate salary — first offer is rarely the best offer; counter with a specific number backed by market data
Resume building — what matters and what does not
Professional Summary
Optional- 2 sentences maximum: your engineering focus and what you are looking for
- Make it role-specific — do not use the same summary for every application
Projects
Critical- Lead with your most technically complex project, not your most recent
- Include GitHub link and live URL for each project
- Quantify: "Handles 500+ concurrent users" beats "scalable architecture"
Internship/work experience
Critical- Even 1–2 month internships from college are valuable — include every professional work experience
- Describe your contribution specifically, not the company's product
- Include the tech stack used at the internship
Education
Important- Include your CGPA only if above 7.5 for most product companies
- List relevant coursework only if directly applicable and not obvious from your degree
Where to find and apply for positions
LinkedIn Jobs
Mid-to-large companies, international opportunitiesApply within 24 hours of posting. Set up daily job alerts. Message the recruiter directly after applying — many companies have recruiters checking LinkedIn even when the role is also on their portal.
Naukri.com
India-based companies, product and service companies bothUpdate your profile weekly — Naukri ranks active profiles higher in recruiter searches. Enable "Open to Work" and set your job preferences precisely.
Company career pages
Tier-1 product companies with specific new grad programsGoogle, Microsoft, Amazon, Flipkart, Swiggy, Zepto all have dedicated new graduate programs with their own application portals and timelines. Apply directly in addition to LinkedIn.
Referrals
Any company where you have a contactA referral from a current employee is the highest-conversion application channel — 5–10x better than a cold application. Message alumni, batch-mates, or LinkedIn connections who work at your target companies. Be specific about the role you want.
Interview process — round by round
Aptitude / Online Assessment
60–90 minutesWhat is assessed
- Verbal reasoning and reading comprehension
- Quantitative aptitude (percentages, ratios, time-speed-distance)
- Logical reasoning
- Basic coding (for technical roles)
Technical Interview
45–90 minutesWhat is assessed
- Data structures and algorithms (for software roles)
- Domain knowledge (your specialization)
- Project deep-dive
- Problem-solving approach
HR and offer discussion
30–45 minutesWhat is assessed
- Motivation for applying
- Career goals alignment
- Cultural fit
- Salary expectations
Skills to demonstrate — and how
Version control and collaboration
High importanceGitHub with consistent activity, proper commit messages, pull request descriptions on collaborative projects
Problem decomposition
High importanceDuring interviews: think out loud, break problems into subproblems, consider edge cases explicitly
Written communication
Medium importanceClean README files, well-structured emails to recruiters, LinkedIn posts about your projects
Networking — how to build relationships that open doors
- Alumni networks from your college are your highest-value resource. Reach out to batch-mates and seniors who are now 2–5 years into their careers — they remember being a fresher and are typically willing to refer.
- Attend tech meetups in your city (JavaScript meetups, AI/ML communities, DevOps meetups). After each talk, connect with 2–3 engineers. Most hiring happens through these informal networks.
- Create content about what you are learning: a tweet thread about a bug you debugged, a short post about how you built a feature. Technical content attracts inbound recruiter messages.
- Join the Discord/Slack communities for your target companies' technologies. Active participants get noticed.
Common mistakes — and how to avoid them
✕ Applying only to companies that are actively advertising
Fix: Many companies hire continuously but post jobs inconsistently. Reach out directly to hiring managers at your target companies even when there is no active listing. "I am a recent CS graduate interested in backend engineering roles at [Company]. Here is my profile [GitHub] — would love to connect." works more often than most people expect.
✕ Not negotiating the first offer
Fix: In India, only 15–20% of freshers negotiate their first offer — but most companies have 10–20% negotiation room. Research market rates on Glassdoor, LinkedIn Salary, and AmbitionBox. Counter with: "I was expecting ₹X–Y based on market rates for this role. Is there flexibility?" The worst outcome is "no" — which is the same as not asking.
✕ Accepting any offer quickly out of fear of not finding a better one
Fix: Your first job sets the reference point for future salary negotiations. Taking a significantly below-market first salary takes 2–3 job changes to correct. Unless you have a specific financial constraint requiring immediate income, allow yourself 2–4 weeks to evaluate multiple offers before deciding.
Frequently asked questions
Is it worth doing a Masters (MTech/MS) instead of getting a job directly?
For software engineering: an MS from a strong US university (CMU, Stanford, Georgia Tech) significantly accelerates career trajectory and opens US job market access. An MTech from a good IIT makes sense for research or academia tracks. For pure product development: 2 years of strong industry experience often beats an MTech in terms of skills and salary. Do not pursue an MTech purely as a backup plan — do it because you genuinely want to go deeper in a research area.
I have a 5.5 CGPA — should I hide it on my resume?
If the role has an explicit CGPA cutoff you do not meet, omitting CGPA may get you further in the process (and then you address it honestly when asked). For companies with no explicit cutoff, omitting CGPA focuses attention on your projects and skills. Never falsify or misstate your CGPA — this is grounds for offer rescission even years later.
Should I join a service company (TCS, Infosys, Wipro) if I cannot get a product company offer?
Service companies offer stability and structured onboarding but slow salary growth and less technical depth. If your goal is eventually a product company: 1–1.5 years at a service company is the maximum before the "service company trap" (hiring bias at product companies against service company profiles) kicks in. Use the time to build a portfolio and aggressively apply. If your goal is stable employment with government-level job security: service companies are a reasonable choice.
Practice internship interviews with a mentor who has hired engineers
The fastest way to crack a technical interview is mock interviews with someone who has been on the other side of the table — they know exactly what interviewers look for and what eliminates candidates.