Ask HN: Writing cover letters for tech jobs
I really hate writing cover letters as I never know what to write or if anyone is even going to read them.
I see a lot of sites offering advice on how to write generic cover letters, but most all of them don’t seem appropriate (at least to me) for tech jobs - more for formal sales, business jobs. I'm interested to know what HN’ers with experience on either or both sides have to say by way of advice - What do you usually write/expect, is it even really a requirement?. Do you attach a separate document or just write an informal email. What tone do you take - formal, familiar. Do you summarize your skills experience or just include a link to Github etc.
129 comments
[ 0.24 ms ] story [ 208 ms ] threadNot that this is advice. I have no idea either and would like to hear what other folk do.
I had three or four standard cover letter templates I rotated through with a couple of places to add research I'd done about the company and why I would be a good fit for them. Often stuff based on what stack they use, who is on their team, etc.
I think applying to jobs directly is worse than networking and worse than working with a recruiter, in that order. If you do decide to go that route and write a cover letter, only include in it what is directly targeted to that company and the person reading it.
My advice is the opposite of another comment: Write one only if you have a "direct pass" that avoids the HR/recruiter filter. Recruiters don't seem to look at them, and HR folks usually don't know enough about the job to value them.
At the very least, a cover letter can't hurt, so write one for a position you're really interested in!
Try thinking about what could peak the curiosity of the reader and interest them in talking to you on the phone.
It’s also important to reference something from the company website / job offer in my opinion. I recently had to wade through a bunch of applications we got through Indeed and 100% of them had irrelevant generic cover letters / intro text that could apply to a startup or an enterprise at the same time. Spending your time on that instead of formatting your CV goes a long way.
Especially for entry level positions, a well-written cover letter is a much stronger positive signal than a bullet point style resume. Far too often the resume is a regurgitation of university class projects and career center templates.
Think of it like a pre-interview, but you get to choose the questions. Since most entry-level resumes look the same, this is your chance to explain why you stand out. (a passion for the industry, strong open-source contributions, etc)
If the position isn't entry level, my advice is the same. Use the opportunity to stand out and score the interview ( which is where the actual decisions will get made). At a small company, someone will read it.
That is interesting. We are seeking the best way to do something, but we are forgetting that people, the interviewers are all different, looking for arbitrarily (but defendable) different things..
Far as new grads. When I got my first job, I did list my class projects, but I focused more on the internships I had had (3 by that point), as well as my freelancing, and the work with open source 3d printers. If a new grad only has projects that would be a red flag.
I also see it as a filter on effort. If the applicant doesn’t care enough to make sure I know why they are a good fit, do they really care about the job?
In my experience, only checking off checkboxes rarely leads to the correct match.
Regarding cover letter advice, the main thing I would suggest is to try and demonstrate that you're aware of what the company does, and specifically interested in that position. Cover letters where you've just copy/pasted the name of the company and the position, then inserted a few relevant points, are painfully easy to spot. Far more effective is a letter that is really focused around your fit for that specific position. And, at least for me, it's a plus if you also clearly acknowledge anything that would be considered a weakness (lack of specific experience for instance,) and then make the case for why you would be a good choice regardless. Once again, this demonstrates you've thought about the company's specific needs and how you will address them.
Finally, be aware of who you're writing to. If possible, try to get a sense of the company culture before writing the letter, and tailor your style to fit. If you know the company you're applying to is small and/or relatively informal (and possibly even regardless), you can stand out from all the generic letters by allowing a bit of personality to come through.
"Your posting caught my eye because I've been a reader of How-To Geek for years. In fact, I discovered your site through the article you wrote about setting up a Raspberry Pi as an always-on downloading box. Thanks to that article, I've now got 3 Pis sitting around my apartment doing various jobs.
I'm currently a Technical Architect with doejo, a digital agency specializing in WordPress development and one of only 13 WordPress.com VIP partners worldwide. What that basically means is that we work on enterprise-scale WordPress. (See also a talk I gave at a local meetup detailing some important considerations for large WordPress sites https://www.youtube.com/watch?v=TB_e7yZ4MCM)
I wanted to reach out because the position that you and How-To Geek are in sounds like the position that Investor's Business Daily, one of our former clients, was in a couple years ago.
When we were brought on with IBD, they were deploying code to production late at night or on weekends because they were scared their deploys would break. There were pieces of the site that just plain didn't work. And there was technical debt all over the place that kept their developers from doing their jobs effectively.
I led the team that took WordPress and bent it to our will to produce one of the most custom digital publishing workflows I've ever seen. After migrating 100k+ pieces of legacy content and completing and documenting the new WordPress build, we handed it off to their internal development team and got to work on their DevOps situation. I helped their operations team architect and deploy staging environments so they didn't have to be scared of production deploys anymore. We helped them replace their out-of-date source control with Git and put in place processes that worked with them instead of processes they had to work around.
This whole re-launch and re-build resulted in a site that loaded 25% faster and brought in a ton more traffic. Couple that with the fact that they now trusted their developers and felt comfortable pushing changes to production in the middle of the day, and it was a win all around.
As far as tech stack, I exclusively use Nginx these days and I've never looked back. Javascript and jQuery are squarely in my wheelhouse. I know WordPress actions and filters like the back of my hand and I'm not afraid to use them or trace through someone else's use of them to get things back on track.
To sum up, I'm really impressed you've grown How-To Geek as far as you have while still deploying to production from your laptop. I think it's great that you see the challenges you have when it comes to infrastructure and technical debt. I'm excited by these challenges and look forward to taking them off your plate so you can get back to running and growing one of the best tech sites online today.
I would love to talk more about the position and answer any questions you may have for me.
(And yes, I won't pull punches when I see some particularly terrible code. I have a library of facepalm GIFs at the ready.)
Talk soon, Keanan"
If you are applying online to a big tech company, it almost always goes into an Applicant Tracking System (ATS). The ATS scans your resume and cover letter for keywords, and matches it with the keywords in the job description or specific keywords as asked my the hiring manager. (You can get through ATS just by copy-pasting the job description in your cover letter. Don't do it). Once you pass through the ATS filter, the recruiter don't seem to care much about the content of your cover letter, but it makes a huge difference when it goes to the hiring manager.
Apart from convincing why you are a perfect fit for the role, share interesting stuff about you like a link to your website (highly recommend this for new grads in tech roles), github profile, previous internship experiences and what excites you about this role.
PS - The most effective way to get a call is to network.(and avoid the whole ATS blackhole).
That said I've found cover letters to be pretty much a waste of my time so far.
+1 on the ATS. They are a waste of your time, generally. If you see an interesting position, try to find an "in" to the company via your network, 1st or 2nd order. See if you can reach the hiring manager directly. HR/ATS get in the way of that. They are supposed to be a service, but as often as not, they are a bottleneck of dubious value. Think of this as engineering your way around the bottlenecks.
+1 on writing a personalized cover letter for each application (e.g. resume submission). I spent quite a bit of time reading/listening to what people thought were good cover letters. What it comes down to is, be real, be yourself. Explain what excites you and how this position does this.
After I did all of this, I found myself a) applying to fewer positions (this was early this year), and b) getting a far higher response rate (60+%). This culminated in multiple interesting offers.
YMMV, but good cover letters help you stand out. Show you are a human being that they want on their team.
Example: Job ad says "we look for a proactive and self-reliant person" then my cover letter says "to successfully finish my PhD, being proactive and self-reliant was important". This technique works even better for the technical parts.
I'm not sure if it was worth the effort. In the german job market, employers are quite desperate these days. A friend sent out simple template letters and got interviews just as easily.
I always sent a PDF. If sent by email, I duplicated the cover letter in the email. My experience is that many had a print out at the interview and PDF works best to ensure a good print.
Many job ads will have a bulleted list of what they are looking for and responsibilities. Just copy-paste that list and then re-write the bullet points in a way that shows how you have that skill. EXP:
- Candidate must have 5 years experience with FooBar
- Candidate must have good knowledge of ZooCar
Turns into:
- Via my 5 years at class/volunteering/job at McEnroeCorp I used FooBar and made FooBarApp with it.
- I have used ZooCar for class/job/side-project and got-a-B/made-$$$-for-company/went-to-FGH-conference
Just go down the list and put in whatever you can.
ProTip for 'shyer' people: Don't worry if you only have 3 years and they need 5, apply anyway. Also, if you only have ~40% of the listed requirements, apply anyway. Hell, if you think the logo is kinda cool and you have an inkling that you can code and fog a mirro, apply anyway.
If my letter didn't succeed in addressing at least 3/4 of the bullet-points in the text file, I would scrap the application.
1. Who am I, short description of career so far.
2. Why I think hiring me would be good for your company. This is essentially a sales pitch, based on prior research on the company I'm applying for.
It is also what I like to see when being on the other side. It helps filtering out people that have an actual interest vs the ones that send mass mails, and also it already gives a first personal impression about a candidate.
Attach the cover letter as a separate document. If you can, get the email of the hiring manager and let them know that you've applied through the standard HR interface. Tone should always be professional and cordial. If you can craft this cover letter well enough you will stand out from others who don't customize their cover letters. Do your research on the company and find where your strengths can play to their business objectives and communicate why you are the one they should choose (then you can link to GitHub projects accordingly). Good luck.
The tone doesn't matter that much, but I would avoid the extremes of very informal or very formal. It should be the first thing that I read, so if you're applying by email it should be the body of the email.
A cover letter is an opportunity for you to tell me why you're interested in this job/company specifically and to highlight things that might not be readily apparent by reading your resume. Some of the best cover letters call out specific achievements that are relevant to the job you're applying for, or preemptively address concerns that someone reading only your resume might have. Even just including enough information to show that you did some research on the job/company before applying already puts you above most cover letters. A generic cover letter makes me wonder if you're just applying to every job ad.
Cover letters have helped me get jobs in the past, and have led me to get interviews (and to interview people).
It doesn’t have to be long, in fact, it really shouldn’t be. But if you’re up for writing a well phrased comment on HN, you should be up for writing a well phrased explanation of why you’re a good fit for the role.
For professional jobs, the pattern is as follows:
1. Locate professionals at the company you would like to work at.
2. Email them through a friend if that is possible, and if not, cold email them and say you are interested in learning more about XYZ company. Ask if they can grab a coffee or do a quick call.
3. During the coffee, ask them good questions to learn more and if you think you would still be interested, ask them if they have any advice on how to apply.
4. Do their advice, which typically means giving them just your resume and having them insert you in to the HR recruiting process.
Any other strategy is a gigantic waste of time.
Sounds like you value networking but I wouldn't call other strategies a waste of time. I got a lot of jobs in my career by simply writing a cover letter and directly applying.
OTOH, in smaller and more close-knit communities of employers (for a completely random example, "architecture firms based in Des Moines", or "health-focused startups in SF"), where there's a relatively small group of smallish companies with a lot of cross-pollination between employees, this might be an effective strategy.
It probably feels better than dropping a resume in some online drop box, because you are personally taking action rather than sitting around and waiting for callbacks that are probably not going to call back, but just because something feels better doesn't mean it's more effective.
FWIW, I myself and plenty of other people I know have gotten really good jobs at big tech companies simply by making sure that any company of interest has a copy of one's resume in their vast database of resumes. It doesn't take any time at all to do that, so no time wasted, and it's one more way in which a potential employer can find it. Even it's just an additional 5% chance to get hired, that's a 5% chance that didn't exist before and doesn't cost time or money.
Ultimately the only advice I can give anyone is to consider all avenues. Nothing's a gigantic waste of time if you're unemployed or unhappy at your current job. If you know people at the company, great. If there's someplace you can send in a resume or even apply for a specific position, great. If you have a non-stalkery means of making contact with people at the company (maybe going to meet ups or relevant conferences or whatever), also great. None of these approaches are mutually exclusive and most complement one another.
I got the job I'm out now (since 2011) and applied in a traditional sense. I was also in a foreign country at the time. It was painless and quick. Hardly a waste of time.
Also, if this is such an established pattern for professional jobs, why even bother having proper channels for applications? Are online applications just a honeypot to blacklist me from actually getting hired?
As an aside, it may seem unfair to the less socially outgoing that others don’t use an existing process that might be in place. Take dating for instance - just because a girl is on a dating site doesn’t mean that the dating site is the only way to ask her out on a date. Finding a job is similar to dating in some ways.
Two key takeaways (in my opinion):
- If you care about the job, do a little bit of research about the company. What does the job posting focus on and how do you align with that? What's their engineering stack and when have you worked with those technologies? This isn't "required" (i.e. you can certainly find jobs by mass-sending the same generic intro) but investing a little time in finding out about the company goes a long way towards telling them that they should take the time to find out about you in return. I also think this helps with the question of tone -- you probably won't go wrong matching the tone of the job posting itself.
- Make it easy for them to see if they want to hire you. Include your resume and make it easy to read (a short, well-formatted PDF is great). Include a direct link to your GitHub/portfolio/etc. If you don't have any public work, just say so and give them a Cliff's notes instead -- "Most of my recent GitHub contributions are private, but for the past six months I've lead a team of four developers in developing a new widget using React, Redux, and ES6, which I see is a close match to your tech stack."
Speaking as someone that has interviewed a lot of senior level engineers in the last 2 years. The fastest way to get a black mark is to hand me an 6 page resume. Frankly as a lead, with 10 resumes on my desk.. most of whom don't have the right skill set. The last thing you want to do is make me hunt to see if you can do the job. Cover letters in the rare case I got them, I didn't read at all. If your resume interests me I'll look at your linkedin.
That said, I am a senior / lead android dev. So I don't exactly hurt on the job front.. I have noticed the smaller the company the more they want you to know about them. Especially start ups (the more obscure and small the higher the expectation)
That's an interesting hack. And I suppose if I discovered an applicant was trying to game the system in this way, my distaste would be outweighed by my admiration.
I don't particularly care about tone, though. I'm looking to see if the applicants can string thoughts together, and if they understand what sort of position they're applying for.
I always write very short cover letters that say who I am and what are my interests (e.g: ML, Distributed systems) Then I write why I think I would be a great fit for this position (e.g: I worked on something very similar)
Now say that you get past this round and that your application gets picked up by someone in HR or the Hiring Manager. They have a pile of others they need to look at as well. What would they prefer to read? This is a bit subjective: some would like you to not waste their time - keep it short and sweet. Others would like to read a love letter.
So, what do you do? I'd say keep it short and sweet for most jobs that you apply to. Two, maybe three paragraphs with two to four sentences each with the last paragraph being an invitation to read the resume and get in touch with you for a meeting. One in ten.. maybe one in twenty jobs get a love letter. It has to be a job that you feel strongly about. But even the love letter - don't waste words - edit it well.
Good luck!
As a person hiring, I would ignore them. I only care does the candidate have the minimum skill set to be worth taking time to phone screen. I'll find out everything else I think is relevant then.
It seems very useful in some fields which require the skills a cover letter shows off and could substitute for a screen or casual interview.
In many technical fields however, requesting cover letters usually suggests to me a lower quality in their hiring process. This undoubtedly bleeds over to my perception of the management, namely more into checking boxes than results.