Theory
Rejected before a human ever read it
Anvi applies for an internship at a top software company visiting Surat. Her code is genuinely solid, so she dashes off a resume line: 'Responsible for making a web development laboratory project.' Four hours later, an automated rejection lands. She is baffled: her code was flawless, so why did the application fail? The answer is that her resume had none of the clear structure, matching keywords, or concrete results it needed to get through the first screening, most of which is done by software before a person ever sees it.
Theory
Filling in the form the scanner can read
Think of a government form that gets fed through a scanner. Scribble outside the boxes or slap a sticker on it, and the scanner spits it back unread, no matter how good your answers are. Your resume is that form: it has to be laid out in the plain, expected way so the screening software can read it cleanly. Your cover letter is the short note you attach for the human on the other side, explaining, in your own words, why you fit this particular role.
Theory
The idea, plainly
Writing a strong resume and cover letter means shaping your documents to satisfy two readers: the Applicant Tracking System (ATS) software that filters applications, and the human who skims what survives. Instead of listing duties, a good tech resume uses the Google X-Y-Z formula: accomplished [X], as measured by [Y], by doing [Z]. That turns a vague task into a concrete, measured achievement that actually shows what you can do.
At a glance
Turning generic lines into specific, results-focused ones.
| Part of the application | Weak, passive version | Strong, specific version |
|---|---|---|
| A project on your resume | Helped my lab group build a database application. | Built a MySQL database that cut query time by 14% by adding proper indexing. |
| Your skills section | Familiar with various computer programs, Microsoft Word, and coding. | Languages: Java, C++, Python. Frameworks: React, Node.js. Tools: Git/GitHub, Docker. |
| Your cover letter opening | I am writing because I need a job and your company is reputable. | I have been following your cloud migration work; my experience tuning Java applications lines up directly with the Core Dev role. |
Follow along
Anvi's 3 steps to a sharper resume
- Keep the layout plain Anvi drops the multi-column design, graphics, icons, and fancy fonts, and uses a clean single-column layout the screening software can read top to bottom.
- Match the job's words She reads the job description and mirrors its terms, swapping her vague heading 'Coding Experience' for 'Software Engineering Projects'.
- Put numbers on her work She goes through her Semester 2 lab logs and applies the X-Y-Z formula, naming the real numbers: query speed, users, whatever she can measure.
Quiz
Anvi is editing the skills section of her resume. Which approach best gets her past the automated screening (ATS)?
- Grouping skills under clear, standard headings that match the job's wording, like 'Databases' and 'Developer Tools'.
- Showing her skills as colourful progress bars, stars, and percentage graphics.
- Listing every technical word she has ever heard to pile up as many keywords as possible.
Show the answer
Grouping skills under clear, standard headings that match the job's wording, like 'Databases' and 'Developer Tools'.
Screening software reads text, not pictures, so progress bars, stars, and charts often get lost or garble the parsing. Plain, standard skill headings that match the job posting are read cleanly every time.
Think first
Strategy check: no experience yet
As a Semester 2 student with no professional experience yet, what should be the main focus of your resume? Decide before you tap.
Show the answer
Lean on your academic projects, lab work, and any open-source contributions. Treat your major coursework like real work: describe the design choices, the database structure, and how the team worked, with real numbers wherever you can.
Watch out
Skip the flashy template
A common placement-exam mistake is using an over-designed template full of a headshot, a life motto, and soft-skill charts like 'Communication: 90%'. Recruiters spend about six seconds on a first scan; they want a clean, plain layout that shows your languages, frameworks, and projects instantly, not decoration to wade through.
Theory
Building on your first semester
Your first-semester module (BCA101) introduced the basics of a resume and standard formatting; this Semester 2 version pushes those basics into real, tailored practice. The polished projects and credentials you organise here are exactly what you will pour into your third-semester portfolio website (BCA206-02).
Summary
Key takeaways
- Your resume has to be laid out plainly so the screening software can read it.
- Your cover letter is the personal note that explains why you fit this specific role.
- Use the X-Y-Z formula to turn duties into measured achievements.
- Avoid multi-column graphics, progress bars, and icons that confuse the screening software.
- Memory hook: fill in the form the way the scanner expects, then add a personal note for the human.