Application Execution: Volume, Quality, Cover Notes and Speed

The funnel maths in article 4 says you need many applications. The resume and referral articles say each application should be specific and careful. Students often feel stuck between these: either they send fifty one-click applications a day and hear nothing, or they spend two hours on each and manage four a week.

The answer is not one or the other. It is a routine that is careful where care pays off and fast where it does not.

• How to balance volume and quality across a sprint.
• How to batch applications, with a checklist that prevents silly mistakes.
• How to answer screening questions, including expected salary, honestly.
• When a cover note helps and how to write a short one.
• Safe ways to cut form-filling time, and where AI fits.

Give each application full care, about 15 to 20 minutes:

• Read the description in three layers (article 12).
• Choose the right resume version and make the five-minute tailoring pass.
• Answer every question carefully.
• Check for a possible referrer (article 19).
• Record everything in your tracker: channel, version, date.

This phase teaches you which roles, companies and resume versions get responses. Without it, speeding up just repeats your mistakes faster.

Once your resume versions are tested and your answers are written, each application should take 5 to 10 minutes:

• Pick the version that fits; adjust the summary line and project order only for high-priority roles.
• Reuse answers you have already written and checked.
• Keep careful work for your top 20 per cent of roles: referrals, a cold note, a full tailoring pass.

Applications done one at a time between other tasks take longer and contain more mistakes. Block focused time instead: for example, three 90-minute sessions a week, or a 45-minute session every weekday morning.

A session looks like this:

1. Pick (10 minutes): open your alerts and list, choose the roles for this session, newest first.
2. Check (5 minutes): eligibility, experience level, location, that the role is open on the company's own page.
3. Apply (most of the session): one role at a time, using the checklist below.
4. Log (5 minutes): tracker rows complete; next actions and dates set.

Run this for every application. It takes thirty seconds and catches most errors.

• The role is open on the company's own careers page, and I meet the stated eligibility.
• I am using the right resume version, saved as Firstname-Lastname-[Version].pdf.
• Every free-text answer names the right company and role.
• Screening answers are true (graduation date, location, notice period, work authorisation).
• Links in the form work (LinkedIn, GitHub, portfolio).
• I saved the job description text and the job ID.
• Tracker row complete: company, role, group, link, date, channel, version, next action.
• I checked whether someone could refer me (if yes, I paused to ask first where appropriate).

Application forms ask questions that can filter you automatically (article 11). Answer truthfully, every time.

Many forms ask for an expected salary, sometimes as a required number. As a fresher:

1. Research first. Look at salary data for the role, company size and city (article 40 covers sources), and any range the posting itself gives.
2. If the form allows text, a range based on research, or "open to the company's standard fresher compensation for this role", is reasonable.
3. If the form requires a number, enter a realistic figure from the middle of your researched range for that kind of company. A very high number can filter you out; a very low one can anchor an offer below market.
4. Write down what you entered in your tracker, so you are consistent later in HR conversations.

Many forms have an optional cover letter or "anything else?" box. A generic cover letter helps nobody; recruiters skim past "I am writing to express my keen interest". Write one only when:

• the company explicitly asks for it;
• you have a specific, checkable connection to their work (you used their API, contributed to their repository, built something in their domain); or
• the company is small enough that founders read applications.

When you do, keep it to about 150 words:

Your public API docs were the reason I built [project] on top of them: a tool that[one line] ([link]). Building it, I ran into [one specific thing], which is why the[role] on your [team] caught my eye.Relevant to the role: [one or two concrete points: a project result, a contribution].I'd like to learn [specific thing] from working with your team.I'm happy to walk through the project on a call.

Some applications ask "Why do you want to work here?" or "Describe a project you are proud of." Draft from your own research and notes (Module 7 builds a research notebook), then use AI to check and tighten:

Here is my draft answer to an application question: "[question]".Check it: (1) is every claim specific and checkable; (2) does it name the rightcompany and role; (3) is it under [limit] words; (4) does it sound like a personor a template? Point out problems and suggest edits using only my facts.Remove "passionate", "keen interest", "esteemed" and similar phrases.[draft]

You will see advice that applying on a particular weekday or hour gets more views. There is no good evidence for precise windows. What does help is applying soon after a role is posted (article 16) and not leaving a high-priority role for the weekend after you found it.

A sprint lasts weeks. Applying all evening, every evening, leads to burnout and careless mistakes. A sustainable plan, such as two or three applications on weekdays plus one batch at the weekend, reaches the numbers from article 4 without wrecking your preparation time. If rejections pile up on a day, stop applying for that day (article 44).

Deepa's sprint:

• Weeks 1 and 2 (calibration): 24 applications, about 18 minutes each, two resume versions, all tracked. Result: 4 screens, all from her "backend" version, and 3 of those from careers pages rather than one-click applications.
• Change: she drops the "full-stack" version, keeps the backend version as her base, and stops one-click applying.
• Weeks 3 to 6 (efficient quality): 3 sessions a week of about 90 minutes, about 8 minutes per application, roughly 10 applications per session. Her top 6 companies each get a referral attempt and a full tailoring pass.
• Screening answers: a saved document with her expected-salary range and the research behind it, her joining date and her relocation preferences, so every form says the same.

Her application rate tripled after week 2 without her screen rate dropping, because calibration came first.

• Speeding up before calibrating.
• Wrong company or role names in reused answers.
• Untrue screening answers to get past a filter.
• Generic cover letters that add nothing.
• Blindly trusting autofill.
• Applying all evening every evening and burning out.

• Next: The OA Landscape: Platforms, Formats, Proctoring and Rules prepares you for what your applications produce: assessment links.
• For cover letter and email templates, see How to Write a Cover Letter and Job Application Email That Gets Replies.
• For salary research, see How to Negotiate Your Salary in India Without Losing the Offer.