Applying by email: the subject line, the body and the attachment that get read

Most applications today go through a careers portal, and email has become the exception. On HireSetu in late October 2026, one live listing used an email address as its apply link: ALTEN's walk-in drive for graduate engineer trainees in Bengaluru. Six more asked candidates to send a resume by email in the text of the listing, and all six were startups or small firms: YAL, Novalantis, Creoleap Technologies, New Street Technologies, xkey and Bellatrix Aerospace.

That pattern is useful. An email application usually lands with a founder, an engineering lead or a single recruiter who reads every message personally. There is no software ranking keywords, which helps you, and there is no structure forcing a busy reader through your details, which does not. What you write in the first two lines decides whether the attachment gets opened.

One email, line by line

A complete application email

Subject: Application: Junior Backend Developer, Python, 2026 B.Tech (Chennai). Hello Ms. Rao, I am applying for the Junior Backend Developer role posted on your careers page. I graduated in B.Tech Computer Science in 2026 and built an expense-splitting API in FastAPI with PostgreSQL, deployed on a free cloud tier, which handles about 200 requests a day from my hostel. The code is at github.com/yourname/splitwise-api. My resume is attached as a one-page PDF. I can join immediately and am happy to do a take-home task. Thank you, Arun Kumar, +91 phone number, linkedin.com/in/yourname

Why each part is there

• Subject with role, skill, year and city → The reader can sort or search for it later, and knows what the email is before opening it.
• Named greeting where you know the name → Shows you read the listing or the company page. Use "Hello" and the team name if you do not know who reads it.
• One sentence of proof, with a number → A specific thing you built beats a list of adjectives. The number makes it believable.
• A link to the work → Startups often look at the code before the resume.
• Availability and willingness to be tested → Answers the two practical questions a small team has, before they ask.
• Contact details in the signature → So nobody has to open the attachment to call you.

The attachment

Send one PDF, one page for a fresher, named so that it still makes sense in a downloads folder: Arun_Kumar_Backend_Resume_2026.pdf works and resume_final_v3.pdf does not. Do not send Word files that reflow on the reader's laptop, image scans of a printed resume, or a zip of certificates. If the listing asks for something specific, such as a portfolio link or a cover note, send exactly that and nothing extra.

Keep the email body short even if your resume is strong. The body's only job is to get the attachment opened. Three to five sentences is enough, and anything longer usually gets skimmed in exactly the places you most wanted read.

Writing to a company with no opening

Small companies often hire before they post anything, and a short email to the right person can arrive at exactly the right moment. The rules tighten: the reader did not ask for it, so every line has to earn its place. Name what the company makes, say in one sentence why you want to work on that specifically, show one piece of work that relates to it, and ask a small question that is easy to answer, such as whether they expect to hire juniors in the next few months.

Find the address from the company's own website or careers page, never from a list someone sells. Write to one person and skip every other address you can find, and send no more than one follow-up. A founder who replies "not now" to a good cold email often remembers the name when a role does open.

Following up, and keeping track

If you hear nothing in a week, one polite follow-up in the same thread is reasonable: a line restating the role and one new piece of information, such as a project you have since finished. If there is still no reply, move on. A third email rarely helps and can turn a maybe into a no.

A simple tracker for email applications

Company and role	Name, role title, where you found it
Sent to	The exact address, and the person if named
Date sent	And the subject line you used
Follow-up	Date of the one follow-up, if any
Reply	Date and what they asked for next

A spreadsheet with these five columns is enough. It stops double applications and missed replies.

Before pressing send, read the email on your phone. Most founders and recruiters will see it there first, and a subject line cut off after five words, or a paragraph that fills the whole screen, is exactly what they will see too.