Resume for B.Tech Freshers: Branch-Wise Templates, CGPA Tips & ATS Optimization (2026)

Your B.Tech Degree Alone Won't Get You Shortlisted. Your Resume Will.#

We analyzed 400+ resumes from B.Tech freshers across 30 colleges: VIT Vellore, SRM Chennai, Amity Noida, KIIT Bhubaneswar, DTU Delhi, NIT Trichy, IP University, Manipal, Chandigarh University, LPU. Here's the uncomfortable truth: over 70% of these resumes would score below 40 on any ATS system.

Not because the students lacked skills. Because nobody taught them how a B.Tech resume actually works.

The typical B.Tech student has 3-5 projects, at least one internship (even if it's a 1-month Internshala gig), a handful of certifications, and a CGPA they're either proud of or terrified of. That's plenty of material for a strong one-page resume. The problem is in the presentation.

Here's what we found in those 400 resumes:

• 62% started with a "Career Objective" that said absolutely nothing
• 45% listed skills they couldn't explain if asked
• 38% had formatting that ATS software couldn't parse (columns, tables, graphics, skill bars)
• 71% didn't tailor anything to the job description

We're going to fix all of this. Branch by branch. With actual templates you can use today.

"Career Objective" is Dead. Stop Writing It.#

We need to address this first because it's the single most common mistake on B.Tech resumes.

"Seeking a challenging position in a reputed organization where I can use my skills and grow professionally."

Every recruiter at every IT company (TCS, Infosys, Wipro, Cognizant, Accenture) has read some version of this sentence roughly 50,000 times. It tells them nothing. It wastes the most valuable real estate on your resume: the top 3 lines.

Replace it with a Professional Summary. Two to three lines that answer: Who are you? What can you do? What are you looking for?

B.Tech CSE example:

B.Tech Computer Science graduate (2026) from VIT Vellore with hands-on experience in Java, React.js, and cloud deployment. Built 4 projects including a real-time collaborative code editor. AWS Cloud Practitioner certified. Targeting Software Engineer roles at product-focused companies.

B.Tech Mechanical example:

B.Tech Mechanical Engineering graduate (2026) from NIT Trichy with strong foundation in CAD/CAM, thermal analysis, and manufacturing processes. Completed 3-month internship at Tata Motors analyzing drivetrain efficiency. CATIA V5 and ANSYS proficient. Seeking a design or manufacturing engineer role.

See the difference? Specific. Keyword-rich. Actually useful to the person reading it.

How to Present Your CGPA (Without Shooting Yourself in the Foot)#

This causes more anxiety than it should. Let's settle it with data.

According to NASSCOM hiring trend reports and our conversations with 30+ campus placement coordinators, here's how CGPA actually works in B.Tech hiring:

Above 8.0/10: Put it prominently. It's an asset. Some companies (Goldman Sachs, Google, Amazon) have soft cutoffs around 7.5-8.0 for campus hiring. A high CGPA signals consistency.

Between 7.0 and 8.0: Include it. This is perfectly fine for 90% of companies. TCS NQT requires 60% aggregate, Infosys requires 60%, most service companies are similar.

Between 6.0 and 7.0: Include it only if the company requires it on the application form. Otherwise, leave it out. Don't draw attention to something average. Let your projects speak louder.

Below 6.0: Do not put it on the resume. Period. If a company's application portal requires it, fill it there. But on the resume itself, focus entirely on projects, certifications, and skills. We've seen candidates with 5.8 CGPA get selected at startups because their GitHub had 3 solid projects. CGPA is one data point, not a verdict.

Percentage vs CGPA: Some universities use percentage, others CGPA. Use whatever your university officially uses. Do not convert unless the company specifically asks. "78%" and "7.8 CGPA" are not the same thing, and conversion formulas vary by university.

Format it like this:

B.Tech in Computer Science and Engineering
SRM Institute of Science and Technology, Chennai
Expected Graduation: June 2026 | CGPA: 8.2/10

If you're leaving out CGPA:

B.Tech in Computer Science and Engineering
SRM Institute of Science and Technology, Chennai
Expected Graduation: June 2026

Clean. No awkward gap that screams "I'm hiding something."

Branch-Wise Skills: What Actually Matters#

Here's where most B.Tech students mess up. They list every technology they've ever heard of. A CSE student writes "Machine Learning, Artificial Intelligence, Blockchain, IoT, Cloud Computing, Cybersecurity" and can't explain any of them in an interview. That's worse than listing nothing.

Rule: Only list skills you can confidently discuss for 5 minutes in an interview.

Computer Science (CSE / IT / CSE-AI / CSE-DS)

Programming Languages: Java, Python, C++, JavaScript
Web Development: React.js, Node.js, Express.js, HTML5, CSS3
Databases: MySQL, MongoDB, PostgreSQL
DevOps & Cloud: Git, GitHub, Docker, AWS (EC2, S3, Lambda)
Tools: VS Code, Postman, JIRA, Figma
Core CS: Data Structures, Algorithms, OOP, DBMS, Operating Systems

CSE students have it relatively straightforward. The market wants full-stack skills, DSA ability, and some cloud exposure. If you've solved 200+ problems on LeetCode, mention it. If you have a GitHub profile with pinned projects, link it.

Electronics & Communication (ECE)

Programming: C, C++, Python, Embedded C, MATLAB
Hardware & Design: VHDL, Verilog, Arduino, Raspberry Pi
Tools: MATLAB/Simulink, Cadence Virtuoso, LTSpice, Keil
Protocols: I2C, SPI, UART, MQTT, TCP/IP
Core: Digital Electronics, Signal Processing, VLSI Design, Communication Systems

ECE students often struggle because they think IT companies won't consider them. Wrong. Companies like TCS, Infosys, and Wipro hire ECE graduates for software roles all the time. But you need to show programming ability. If you've done projects involving embedded systems or IoT, those demonstrate both hardware understanding AND coding skills. That's a combination CSE students often lack.

Mechanical Engineering

Design Software: AutoCAD, SolidWorks, CATIA V5, Creo Parametric
Analysis Tools: ANSYS (Structural, Thermal, CFD), MATLAB
Manufacturing: CNC Programming, GD&T, Lean Manufacturing, Six Sigma
Programming: Python (for automation), MATLAB scripting
Core: Thermodynamics, Fluid Mechanics, Machine Design, Manufacturing Processes

For Mechanical engineers targeting core roles (Tata Motors, L&T, Mahindra, BHEL), design software proficiency is non-negotiable. But here's our contrarian take: if you're a Mechanical student who also knows Python and can automate CAD workflows, you become incredibly rare. That cross-functional skill is what gets you noticed.

Civil Engineering

Design Software: AutoCAD, Revit, STAAD Pro, ETABS
Analysis: MATLAB, SAP2000, GIS (QGIS/ArcGIS)
Standards: IS Codes, Green Building (IGBC/LEED basics)
Project Management: MS Project, Primavera P6
Core: Structural Analysis, Geotechnical Engineering, Transportation Engineering, Environmental Engineering

Civil engineers: list your site visit experience. Even if it was a 2-day college trip to a construction site, frame it as exposure. "Visited and documented structural progress of a 12-storey residential project, analyzing RCC framework and quality control checkpoints." That's real.

Full Resume Template #1: CSE Student with Projects#

ARJUN MEHTA
+91 98765 43210 | [email protected]
linkedin.com/in/arjunmehta | github.com/arjunmehta
Pune, Maharashtra

──────────────────────────────────────────────

PROFESSIONAL SUMMARY

B.Tech Computer Science student (2026) from VIT Pune with strong
foundation in Java, Python, and full-stack web development.
Built 4 projects including a real-time collaborative code editor
deployed on AWS. Solved 280+ problems on LeetCode. Targeting
Software Development Engineer roles.

──────────────────────────────────────────────

EDUCATION

B.Tech in Computer Science and Engineering
VIT Pune  - Vishwakarma Institute of Technology
Expected Graduation: June 2026 | CGPA: 8.4/10

Higher Secondary (12th), Science Stream
Maharashtra State Board  - 2022 | 89.6%

──────────────────────────────────────────────

TECHNICAL SKILLS

Languages: Java, Python, C++, JavaScript, TypeScript
Frontend: React.js, Next.js, Tailwind CSS, HTML5, CSS3
Backend: Node.js, Express.js, REST APIs, WebSocket
Databases: MySQL, MongoDB, Redis
DevOps: Git, GitHub Actions, Docker, AWS (EC2, S3, Lambda)
Tools: VS Code, Postman, Figma, JIRA

──────────────────────────────────────────────

PROJECTS

CodeCollab  - Real-Time Collaborative Code Editor
React.js, Node.js, Socket.IO, MongoDB, AWS EC2
• Built a real-time collaborative code editor supporting 5+
  simultaneous users with conflict-free editing using
  Operational Transformation algorithm
• Implemented syntax highlighting for 10 languages,
  live cursor tracking, and integrated chat
• Deployed on AWS EC2 with Nginx reverse proxy, handling
  200+ concurrent WebSocket connections in load testing

SmartSpend  - Personal Finance Tracker
React Native, Firebase, Chart.js, Razorpay API
• Developed a cross-platform mobile app for expense tracking
  with automated categorization using rule-based ML
• Integrated UPI payment detection via SMS parsing,
  auto-logging 90% of daily transactions
• Published on Google Play Store with 50+ downloads
  and 4.2-star rating in first month

JobMatch  - Resume-JD Matching Tool
Python, Flask, Scikit-learn, spaCy, PostgreSQL
• Built an NLP-based tool that extracts skills from resumes
  and job descriptions, calculating match percentage
• Achieved 85% accuracy in skill extraction using Named
  Entity Recognition with a custom-trained spaCy model
• Created REST API handling 500+ daily requests from
  a React frontend

──────────────────────────────────────────────

INTERNSHIP

Backend Developer Intern | TechStartup Pvt. Ltd., Bangalore
May 2025 – July 2025
• Developed 3 REST API endpoints for user authentication
  module, reducing login latency by 40%
• Wrote unit tests with 92% code coverage using Jest,
  reducing production bugs by 25%

──────────────────────────────────────────────

ACHIEVEMENTS & CERTIFICATIONS

• Solved 280+ problems on LeetCode (top 8% globally)
• AWS Cloud Practitioner Certified (2025)
• Runner-up, Smart India Hackathon 2025  - Built an
  AI-powered career counseling tool for rural students
• Completed "Machine Learning Specialization" on
  Coursera by Stanford University (2025)
• NPTEL Elite Certificate in Data Structures (Top 5%)

Full Resume Template #2: Non-CS Branch with Internship Focus#

SNEHA PATIL
+91 87654 32109 | [email protected]
linkedin.com/in/snehapatil
Nagpur, Maharashtra

──────────────────────────────────────────────

PROFESSIONAL SUMMARY

B.Tech Mechanical Engineering graduate (2026) from VNIT Nagpur
with specialization in CAD/CAM and thermal systems. Completed
a 3-month internship at Mahindra & Mahindra analyzing
vehicle thermal management systems. Proficient in SolidWorks,
ANSYS, and Python. Seeking a Design Engineer or CAE Analyst role.

──────────────────────────────────────────────

EDUCATION

B.Tech in Mechanical Engineering
Visvesvaraya National Institute of Technology (VNIT), Nagpur
Expected Graduation: June 2026 | CGPA: 8.1/10

Higher Secondary (12th), Science Stream
CBSE Board  - 2022 | 91.2%

──────────────────────────────────────────────

TECHNICAL SKILLS

Design: SolidWorks, CATIA V5, AutoCAD, Creo Parametric
Analysis: ANSYS Workbench (Structural + Thermal + CFD)
Programming: Python, MATLAB, C
Manufacturing: CNC Programming (G-code), GD&T, 3D Printing
Tools: MS Project, MS Excel (Advanced), LaTeX

──────────────────────────────────────────────

INTERNSHIP

Thermal Analysis Intern | Mahindra & Mahindra, Pune
May 2025 – August 2025
• Conducted thermal simulation of engine cooling system
  using ANSYS Fluent, identifying 3 hotspot regions
  exceeding design temperature by 12°C
• Proposed baffle redesign that improved coolant flow
  distribution by 18%, validated through CFD simulation
• Created 15+ SolidWorks assemblies for modified cooling
  duct geometry, reducing part count by 2 components
• Presented findings to a 10-member engineering team,
  with recommendations approved for prototype testing

──────────────────────────────────────────────

PROJECTS

Automated Sorting Machine | SolidWorks, Arduino, Sensors
• Designed and fabricated an automated sorting system
  using proximity sensors and servo motors, achieving
  95% sorting accuracy for 3 material types
• Created full assembly in SolidWorks with GD&T
  annotations and BOM (Bill of Materials)
• Reduced manual sorting time by 70% compared to
  existing process in college workshop

Solar Water Heater Optimization | ANSYS, MATLAB
• Performed CFD analysis of evacuated tube solar water
  heater, optimizing tube spacing to increase thermal
  efficiency by 14%
• Developed MATLAB script automating post-processing
  of ANSYS simulation data, reducing analysis time
  from 4 hours to 45 minutes

Wind Turbine Blade Analysis | CATIA V5, ANSYS
• Modeled NACA 4412 airfoil-based wind turbine blade
  in CATIA V5 and performed structural analysis in ANSYS
• Identified optimal blade angle (12°) for maximum lift-
  to-drag ratio through parametric study of 8 configurations

──────────────────────────────────────────────

ACHIEVEMENTS & CERTIFICATIONS

• First place, Mechanical Design Challenge at TechFest 2025,
  VNIT (out of 45 teams)
• NPTEL Elite Certificate in Finite Element Analysis (Top 5%)
• SolidWorks CSWA (Certified SolidWorks Associate)  - 2025
• Published research paper on "CFD Analysis of Heat Exchangers"
  in IJMTE (International Journal)  - 2025
• Volunteered as core member of SAE India Collegiate Club,
  organized a 2-day workshop attended by 200+ students

How to Present Projects (The Part Most B.Tech Students Get Wrong)#

For freshers, the Projects section IS your experience section. This is not an exaggeration. Recruiters at mass hiring companies like TCS (3.36 LPA), Infosys (3.6 LPA), Wipro (3.5 LPA), and Cognizant (4-4.5 LPA) tell us the same thing: "Show me you can build something."

Here's the formula that works:

Project Name | Tech Stack Used

• [Action verb] + [what you built] + [measurable outcome]

Three common mistakes to avoid:

Mistake 1: One-liner descriptions "Made a weather app" tells the recruiter nothing. Compare with: "Developed a weather forecasting application using React.js and OpenWeatherMap API, displaying real-time data for 200,000+ cities with 5-day forecast visualization."

Mistake 2: Listing tech stack without showing application "Used React, Node, MongoDB" is a list, not an achievement. Show what you built WITH those tools.

Mistake 3: No numbers Numbers make everything concrete. "Improved performance" vs "Improved page load time by 45% through lazy loading and image compression." The second version is memorable. The first is forgettable.

If you genuinely don't have numbers (and many college projects won't), approximate. "Designed for 100+ concurrent users" or "Processed 10,000+ records in dataset." These are design parameters, not lies.

B.Tech-Specific Sections Most Students Forget#

Relevant Coursework

If you're a B.Tech student applying for a role that's adjacent to your branch (say, an ECE student applying for a software role), add a "Relevant Coursework" section to bridge the gap.

Relevant Coursework: Data Structures & Algorithms, Object-Oriented
Programming, Database Management Systems, Computer Networks,
Operating Systems, Software Engineering

This tells the recruiter: "Yes, I'm ECE, but I studied these CS subjects too." It's particularly useful for TCS, Infosys, and other companies that hire across branches.

Publications and Research

If you've published a paper, even in a college journal, include it. Format it properly:

• "Comparative Analysis of Heat Transfer in Finned Tubes"
   - Published in International Journal of Mechanical
  Engineering, Vol. 12, Issue 3, 2025

For CSE students, even a technical blog post on Medium or GeeksforGeeks counts as published writing. Link it.

Competitive Coding Profile

If you have a meaningful coding profile, add it:

Competitive Programming:
• LeetCode: 300+ problems solved, Contest Rating 1650
• CodeChef: 3-star (max rating 1620)
• HackerRank: 5-star in Problem Solving, Java

This matters more than you think. A placement coordinator at KIIT Bhubaneswar told us: "When two students have similar CGPAs and projects, we look at their coding profiles. 200+ problems on LeetCode tells us they can handle the coding rounds."

ATS Optimization for B.Tech Resumes#

Here's a stat that should scare you: according to Harvard Business Review, roughly 75% of resumes are rejected by ATS before a human ever reads them. For campus placements at large companies, the ATS filter is even stricter because the volume is massive.

We tested 50 B.Tech resumes through 3 different ATS systems (Taleo, Workday, and a custom one used by an Indian IT company). Here's what killed scores:

1. Two-column layouts: ATS reads left-to-right, top-to-bottom. Two columns create garbled text
2. Skill bars and star ratings: ATS can't interpret "Python ★★★★☆" as "Advanced Python"
3. Headers and footers with contact info: many ATS systems skip document headers entirely
4. Images and logos: college logos, company logos, photo. All invisible to ATS
5. Fancy section titles: "My Technical Arsenal" instead of "Technical Skills." ATS looks for standard headings

The fix is simple: single-column, clean layout, standard headings, text-based PDF. That's it. (We go deep on this in our ATS resume format guide.)

Keyword matching is the other half of ATS. If the job description says "React.js", your resume should say "React.js", not "React" or "ReactJS." If it says "Machine Learning," don't just write "ML." Include both: "Machine Learning (ML)." ATS does exact string matching for many keywords.

Here's a trick we recommend to every B.Tech student: before applying, paste the job description and your resume into an ATS checker. See your score. Fix the gaps. Apply. This single step puts you ahead of most applicants.

What NOT to Put on a B.Tech Resume#

Some things we still see on B.Tech resumes that need to stop:

• Photo: not required for Indian IT hiring. Wastes space and can trigger unconscious bias
• Date of birth / Age: irrelevant
• Father's name: this is not a government form
• Permanent address: city and state is enough
• "I hereby declare that the above information is true": no. Just no. It's not an affidavit
• References: Available upon request. They'll ask if they want them
• Hobbies: Listening to music, playing cricket. Unless you played cricket at university level
• 10th marks: skip unless the company application form specifically requires it. Once you're a B.Tech graduate, nobody cares about 10th board results

We talked to an HR manager at an Indian IT company who told us (yes, directly): "When I see 'Father's Name' on a resume in 2026, I immediately assume the candidate copied an outdated template from the internet. It's not a dealbreaker, but it doesn't help."

Branch-Specific Job Application Strategy#

Here's something we feel strongly about: your branch does not limit you as much as you think.

LinkedIn Economic Graph data shows that 40%+ of Indian IT hires come from non-CS branches. ECE, EE, and even Mechanical graduates regularly get placed at TCS, Infosys, Wipro, and Cognizant in software roles. But your resume needs to bridge that gap explicitly.

If you're ECE/EE applying for software roles:

• Put coding projects first, hardware projects second
• Add a "Relevant Coursework" section with CS subjects
• Highlight any full-stack or web development work
• Mention coding profiles (LeetCode, HackerRank)

If you're Mechanical/Civil applying for IT roles:

• Lead with Python/MATLAB projects that show programming ability
• Emphasize automation: "Wrote Python script to automate [X]"
• Include any data analysis or visualization work
• Take a Coursera or NPTEL certification in programming to fill the gap

If you're Mechanical/Civil applying for core roles:

• Lead with design software proficiency (SolidWorks, AutoCAD, ANSYS, STAAD Pro)
• Highlight internships at manufacturing/construction companies
• Include relevant IS codes, standards, certifications
• Mention any published research or conference papers

Formatting Rules That Actually Matter#

We've reviewed enough resumes to have strong opinions here:

• One page. Always. No exceptions for freshers. If a B.Tech graduate with zero work experience has a two-page resume, something's wrong
• Font: Arial, Calibri, or Garamond. 10-11pt for body, 14pt for your name. Never use decorative fonts
• Margins: 0.5 to 0.75 inches on all sides. Tighter margins = more content, but don't go below 0.5
• File name: Arjun_Mehta_Resume.pdf, not resume (1).pdf or final_FINAL_v3.pdf
• File format: PDF only. DOCX can render differently on different systems. PDF preserves formatting
• Section order: Contact Info → Professional Summary → Education → Skills → Projects → Internship → Achievements

FAQ#

Should I make separate resumes for different companies?

Yes, and this is the single highest-impact thing you can do. A resume tailored to a TCS job description will score higher on their ATS than a generic resume. You don't need to rewrite the whole thing. Just adjust the Professional Summary keywords and reorder your projects to match each JD. Takes 15 minutes. Worth it every time.

My college is not well-known. Does that hurt my resume?

It can affect the initial filter at some companies. But here's what matters more: your projects, skills, and coding profiles. We've talked to hiring managers at startups who said they actively look for candidates from tier-2/3 colleges who have strong GitHub profiles, because it shows self-driven learning. Your college name matters less than what you did during college. (Though this is easier to say than to believe. We get it.)

I have a gap year. How do I address it?

Be honest but brief. If you took a gap year for GATE/CAT preparation, competitive exam prep, health reasons, or family circumstances, mention it in one line in your Education section or Professional Summary. "2022-23: Prepared for GATE (qualified, AIR 1850)." Gaps are far more common than you think, and recruiters understand. What they don't like is unexplained gaps that look like you're hiding something.

Should I include my GitHub and LinkedIn profiles?

Absolutely. For CSE/IT students, a GitHub profile with pinned projects is almost as important as the resume itself. For LinkedIn, make sure your profile matches your resume. Inconsistencies raise red flags. (Our LinkedIn profile optimization guide covers this in detail.)

B.Tech with arrears/backlogs: what do I do?

If you've cleared them, you don't need to mention backlogs on your resume at all. If the company's application form asks "Did you have any backlogs?" Answer honestly. On the resume itself, just list your current CGPA. Companies like TCS and Infosys allow candidates with cleared backlogs. Active backlogs are a different story. Most mass recruiters require all backlogs cleared before joining.

---

Sources & Further Reading#

• India Skills Report 2025 (Wheebox): employability data across Indian colleges
• NASSCOM: Indian IT industry hiring trends and skill requirements
• LinkedIn Economic Graph: hiring patterns across engineering branches
• Harvard Business Review: research on ATS rejection rates and resume screening
• TCS Careers: official hiring page, NQT requirements
• Infosys Careers: hiring criteria for freshers
• LeetCode: competitive programming for interview prep
• GeeksforGeeks: CS fundamentals and interview archives
• Coursera: certifications recognized by Indian recruiters
• NPTEL: free courses with certifications from IITs/IISc
• ATS resume format guide: deep dive into ATS-friendly formatting
• ATS score checker: test your resume before applying
• Resume for freshers with no experience: if you're still building your resume from scratch
• TCS interview questions for freshers 2026: what comes after the resume gets shortlisted
• Campus placement ki taiyari: Hindi guide to placement preparation

---

Your B.Tech degree opens the door. But your resume is what gets you through it.

We've seen students from VIT, SRM, Amity, and smaller private colleges get shortlisted at companies like TCS Digital (7+ LPA), Amazon, and Goldman Sachs, with the same projects and CGPA that their batchmates had. The difference was always the resume. How they presented their projects. How they matched keywords. How they formatted the document so ATS could actually read it.

Pick the template above that matches your branch. Fill it in. Run it through an ATS checker. Then apply. That's the playbook.