10 ms·
What I Learnt From Reviewing 22 CVs
- cheez 6y agoThe author says he would ignore a nice looking resume for c++ developers but not frontend developers. This is only because he's consciously aware of it. When I used to look for jobs, I was one of the only to use LaTeX and it was most definitely a point of discussion when I was called in. Sadly the LaTeX resume templates now look like something out of MS Word. So whether or not you're a frontend Dev, every non cringy thing you can do to stand out is important.
- Ragib_Zaman 6y agoI used to use a LaTeX resume until a recruiter told me their ATS couldn't scan it properly :(
- marcinzm 6y ago>And although I’m not particularly a big fan of LinkedIn, I always quite like it when I see people who are at the early stages of their career making connections with everyone they met at last night’s Meetup. To me this shows people who are more concerned about networking than learning. I want co-workers who are passionate about technology and not about how to hack their careers. edit: More broadly the best engineers I've worked with had horrible social profiles because they were concerned about making things and learning rather than social credits.
- bluedino 6y ago>> To me this shows people who are more concerned about networking than learning. I've always thought of a conference as something to plant the seeds of ideas in your head. There isn't a lot of detail and you might be one of 100 other people in the room so you can't really ask about details. Following up with the speaker or other attendees after the fact is where the benefits are. I don't mind a developer that says "I'm not sure how to do that, but _____ said they did something similar, let's give them a call."
- jcims 6y agoLurking the ten minute post-talk scrum at the front of the room is the best part of conferences for me. 'Ah damn, they are running into the exact same issue we are'...trade some ideas and contact info.
- zigzaggy 6y agoI agree that priorities are important. But these things aren’t mutually exclusive, right? I was equal parts networker and learner in my early career and it definitely paid off. I remember being accused of being “too social” at times. And I’m sure I overdid it now and then (as we do in our youth). But my personal network has been very valuable over time, especially in the tough times. And I’ve come through for them too. I’m not saying “it’s not what you know, but who.” I am saying it’s what you know AND who.
- marcinzm 6y agoThat's the distinction between being good for you and being good for your co-workers/company. When I'm hiring someone I care about them being good for co-workers and the company.
- zigzaggy 6y agoI guess we can agree to disagree, because in my opinion people who are connected to a group, and participate in the "give and take" that goes with it, bring additional value to the job. I don't see how that wouldn't be good for co-workers and the company. Maybe I should clarify that these aren't things I would do on the job. I engaged with co-workers through volunteer work, at those goofy socials at the Chamber (which I refuse to do now), going out for lunch or drinks with folks I met in the halls, etc. Either way, to me work isn't just going in, punching a clock, and cranking out canooter valves and cagibilt rings. As a program manager, I've always had an appreciation for the relationships and motivations of others. I do the canooter valve thing too, but I always enjoyed the brainstorming sessions and mind maps, and solving problems and making deals happen. I dunno, networking is part of the job if you ask me.
- Insanity 6y agoFWIW, recently I had to interview a fair number of candidates and screen their CVs. The point made about having a github profile definitely resonates with me. With the small caveat that if it was empty, I considered it silly to put something on your CV that you're not using. For frontend developers some kind of portfolio also stands out, and many did seem to have some. I know it's bias and many good developers don't have side projects. It's just my "gut reaction" towards the CVs.
- throwaway98797 6y agoIdentifies bias. Changes nothing. Snarky comment aside, that’s the challenge that even if you see a flawed thinking in yourself it’s hard to change your bias. We give ourselves a pass too often. Maybe we shouldn’t be so forgiving.
- corytheboyd 6y agoYeah, it’s something I catch myself doing all the time too, confirming a bias I have but then just moving on anyway. As if confirming the bias somehow made it okay to just have it.
- Insanity 6y agoIn the moment itself I manage to move away from the bias - but a lot of times it probably happens subconsciously. It's tricky to overcome, not sure if it is even possible to overcome it entirely.
- bb123 6y ago> I want to be with people that are sharing links to things they’ve read, people who are trying out new technologies and languages, people who have weekend projects, or who are contributing bug fixes back to open source projects. I hate this culture in software engineering. There are many excellent engineers out there who work to live, rather than live to work. Why do we have this expectation that programmers want to spend every waking second coding something? I'd hire someone who appears to have balance in their life with other interests and hobbies besides computers (all other things being equal).
- abalaji 6y agoIt’s more fun to work with people who enjoy work rather than people who work to enjoy. At least that’s my 2 cents
- bb123 6y agoI enjoy my work, but it is just that - work. I give my work 100% in good humour when I am working, but I think the expectation that I'm going to go home and do more of the same on my own time is unfair and unhealthy. No other profession expects this.
- reallydontask 6y ago> No other profession expects this. I don't think this is the case (anecdotal evidence from friends and family in varied professions) I think the problem is that there seems to be an expectation of knowledge of the exact technologies. I have to say that lately I have seen a lot more: X or equivalent but this might be related to devops engineer job adverts where maybe they've realised that the tools are similar enough that you can get up to speed quickly enough between them ...
- vsareto 6y agoI don't know why people would enjoy work with all of the process stuff we impose on development.
- beardedwizard 6y agoAll of the biases present in the article are why I avoid reading CVs (leaving it to recruiters) and focus on an interview process that demonstrates whether you have what we need.
- bryanrasmussen 6y agothe thing that I found interesting about it is he's a developer who was told to look over CVs, and these are the feelings he noticed himself having after looking over 22 of them. Given that makes me wonder what it's like for HR looking over CVs, gotta be worse I figure, and if I wouldn't have the same reaction - I mean sure, I don't believe you need a LinkedIn account, GitHub account etc. but if I see a bunch of resumes and one doesn't have it will I be able to see that point as inessential or will it make me cautious. We all like to talk a good game about how we would handle hiring, but maybe we wouldn't handle it as well as we hope.
- secondaryditto 6y agoRecently worked with someone who... gotta say, it was a bit strange after a while. We're all remote, but he had no picture of himself, ever. Now... granted - there may actually be some visual reason - some disfigurement, for example - that the person is self-conscious of (hadn't originally thought of it). However - we had no social media profile at all for this person. No pics of the person, alone or with friends. We had no programming profile - no bitbucket/github/etc. I did find, later, a couple of public bug fixes from 2014 (this was in 2020) attached to this person, but no pic or any other work to tie it to. The person was no more than a voice on a phone/webex. It was just a strange experience, because the rest of the team - probably another 6 people or so - all had some degree of personal whatever - picture, blog, repo, camera during Webex for facial expressions. Over time, it was just... odd. Then ... off. The person was recently let got from the project, but had communicated some weird stuff to me in private, which was troubling (moreso to have been told in the first place, because then I have to make a decision how to act on it). I completely agree that we don't have to live online 24/7, people should have separation between work/life, we shouldn't judge people just based on a GitHub profile, and private life can (and should) be private. But taken to an extreme, where you end up just working with a faceless voice... had its drawbacks.
- Clubber 6y agoHonestly with what we know now, people who have a heavy social media profile and claim to know about computers would be concerning to me.
- mrkwse 6y agoDid that person have any sort of avatar (cartoon etc.)? I've known a couple of people who have been reluctant to use photographs of themselves as avatars and I've later on found out that they've come out as trans. For those who are closeted (or perhaps haven't processed their dysphoria) it can be problematic (and I realise that in physical offices nobody can avoid being seen, but save the bathroom or perhaps lifts, one isn't usually confronted with the sight of oneself (and online profiles tend to be visible for the user))
- DanBC 6y ago> but he had no picture of himself, ever. Now... granted - there may actually be some visual reason - some disfigurement, for example - that the person is self-conscious of (hadn't originally thought of it). > However - we had no social media profile at all for this person. No pics of the person, alone or with friends. People who are fleeing domestic abuse or controlling parents may have very locked down social media profiles, and may even be using different names for different parts of their life.
- caiobegotti 6y ago> I want to be with people [...] who have weekend projects, or who are contributing bug fixes back to open source projects. These are two sides of the same problem. I happened to be in both kind of shoes in the past but this is why hiring is fucked up in tech, I believe. This sentence implies someone is expected to work more than they are paid for if they want to be recognized at something. That's ridiculous. The brightest and most talented engineers I ever worked with in the last 20 years had families with kids (I don't, for the record) and were many years in their careers already, who got offline during the weekend enjoying dinners, doing whatever non-tech stuff and posting only personal content online, sharing it with non-work friends. If you want me to contribute with bug fixes to OSS while I am doing something else of personal value or have neat weekend projects to post on HN then pay me to do so or at least have the decency of not expectating my own life to revolve around what you think it should. These... "projects"... take time and, deities forbid it, I'm doomed in screenings if I don't share the same passion for engineering projects on late weekend nights as you because you are biased? Hiring folks, through tech managers' perspectives, talk about freedom but they expect others to exercise their own liberty in accordance to what the company think is best, it seems. Bullshit.
- raghava 6y agoNobody every asks "so, how many sales gigs do you do on the sides, during weekends?" or "oh, how many teams do you lead/mentors, during the weekends?" All this BS "weekend-extra-open-source-labour-tax" must be borne by the members opting for tech streams. The innate, simple truth is that all that "weekend extra effort" is a way to see if the person can take up more work off hours without so much of a complaint and not demand overtime pay - in the name of "passion". Passion is overrated. There are many who play the passion card, while trying to showcase their role-playing fantasies in a very skewed way. Hiring based on such appearances is at best just a gamble. There are many such "social profiles" which are either crafted for befooling the spectators, or inane content which just about passes the "100 for effort! value, best left unsaid!" types.
- musicale 6y ago> Passion is overrated "Passionate employees" seems to be code for "compliant human robots willing to sacrifice their personal lives, health and sanity for the company's bottom line, and to work extensive overtime without compensation while we recruit their cheaper replacements."
- MattGaiser 6y agoResumes are a marketing document with a heavy focus on signalling, simply because you can’t stuff much in there.
- zwieback 6y agoWow, all the emotion in the comments, what's going on? I thought it was a pretty balanced observation and clearly a personal opinion, not a "39 ways to find the perfect candidate" type of post.
- ahartmetz 6y ago"A public Git account" - that is not really a well-defined concept. Did you mean GitHub? Open source software exists outside of GitHub. If we want to be pedantic, even outside of Git.
- wazzaps 6y agoA static site hosting a git server with your projects could be considered a "Git account" of sorts
- jiveturkey 6y agojust another knowitallogist
- DavidVoid 6y ago> One final thing has just occurred to me…I didn’t consider the qualifications of anyone, which I imagine is down to the role that the CVs were for. You’d certainly be interested in degrees and PhDs if you were hiring a data scientist or someone to write an operating system; in these spaces theory is a major element. But for fast-moving technologies like front-end development, you can probably tell everything about a person from their experience. This feels like a prime example of why applying for programming jobs as a new-grad is so frustrating. You spend five years getting an MSE degree and then the recruiters just ignore your application because you don't have any previous work experience. edit: Parts of this blog post also reminded me of this awful tweet from a senior recruiter at Blizzard [1]. "I've asked this in interviews at Blizzard for 30 years: What do you program at home? Many answer they don't have time. Wrong. Program at home. Every day. If you don't have that passion, programming is not really for you. Write small games. Do game jams. #gamejobs" The "you're not a real/good programmer unless you program as a hobby" sentiment really needs to die. [1] https://i.redd.it/jgiy4rw2ug751.png https://i.redd.it/jgiy4rw2ug751.png
- mixmastamyk 6y ago> This feels like a prime example of why applying for programming jobs as a new-grad is so frustrating. Or how when you've a decade or two of experience and self-directed learning but no fancy degree. Apply to any coveted job and resume is in the first group sent straight to the trash. It's as if we have no idea how to hire developers. ;-)
- musicale 6y ago> It's as if we have no idea how to hire developers. ;-) Indeed.
- NKosmatos 6y agoThis: >typos really jump out at you when you are looking at a lot of CVs I've seen a couple of CVs professionally and I've helped a few friends with theirs and it really leaves me with a bad taste when I see spelling/typo mistakes. Perhaps it's my OCD with symmetry and order :-)
- corytheboyd 6y agoGlad to see others bringing up concerns about the obsession with extracurricular learning in the industry. It’s pressure on people to do work at home, cleverly worded to not sound like a requirement. Yes, in depth learning takes a lot of time and is needed to become a better engineer, but that qualifies as WORK which should be compensated for, just like how delivering features is work. Throughout my career I have actively encouraged teammates to slow down and really understand problem domains, because the industry default they tend to be used to is to rush to completion. All that being said, you just have to play the game a little bit too if you want to maximize your hireability. Find some dumb errors in doc sites for popular projects to check off the “OSS contributor” box. Have code in your GitHub account be public, hell just go fork some projects and never do anything with them, better than nothing and takes zero time. Add tasteful color and styling to your resume, etc. Feels superficial, it is! But in a competitive market it’s worth it and all of the above is mostly one-off work, not a “code is my lifestyle” transformation. Be honest if asked about it though, don’t lie about being a Rails core contributor because you forked Rails.
- raghava 6y agoImagine, biases like "good formatting => better; no typos => better; social profiles => better;" etc being put within an AI/ML based resume parser, with an intent to mimic human behaviour of sourcing a resume out of a bundle of resumes, and scoring against a job description. Now, what might go wrong, when - more such biases creep in to the models, thanks to groupthink, multiple developers/groups and their biases - such systems end up gating the applicants before a human view is cast on the resume This is happening now, at scale. And only a very few in the industry seem to be really tuned about such dangerous bias perpetuation engines.
- klondike_klive 6y ago>an important criteria In a section of the article about typos, this is annoying to see.
- sharadov 6y agoPeople don't always use their real names on their stack overflow and github acccounts, I certainly don't.
- thoraway1010 6y ago22 CV's. Anyone doing hiring would love if their life only involved 22 cv's. I'd interview half of them :) If you hire regularly at least in some fields, the total flood of cv's is a bit crazy (obviously something is scraping and auto or one click submitting them).
- blizkreeg 6y agoWe know that having people vouch for you goes a much longer way than self-reported accomplishments on a resume. I keep wondering why isn't there a platform where your specific accomplishments in a job are validated by your former co-workers? Effectively, a peer-validated resume. Not LI style testimonials but more specific like say "yes, Jack worked on this feature and did a great job!"
- munchbunny 6y agoIt’s because such a system will be gamed by the networkers, not the most competent. The people who are vouched for most will be the people who are most shameless about asking.
- vincent-manis 6y agoI'm retired now, so thankfully don't have to look at CVs any more. I was a university/college instructor, so over the years I reviewed many, many CVs of applicants for computer science teaching positions. Some comments on the blog post and the other comments here. a) If I saw a CV with a picture, I'd call up HR and ask why they let the picture through. Pictures, and even names, give information that can be (and has been) used to discriminate on racial and gender grounds, among others. I always wanted to hire the best candidate, based on track record. Pictures provide no useful information here. b) When I got the CVs, I'd look primarily at what they say the applicant has done, rather than formal qualifications. CVs then went into 3 piles: worth interviewing, worth interviewing if nobody in the previous group pans out, not worth interviewing. I would tend to give each CV about 1 minute of attention in doing this, because in my experience the interview tells you a lot more than the CV. A CV is primarily for getting one's foot in the door, and announcing interest in the position. My alltime favorite CV was one I reviewed for hiring a successor when I was leaving a university teaching position. The job posting specified “Masters or PhD in computer science required”. The applicant's CV detailed some very low-level education in a field completely distant from computer science. The cover letter said “I recognize that I may not have all the background needed for this position. If so, could you please tell me where I could get it.”
- musicale 6y ago> There were other technologies that were similarly indicative, such as mention of ‘microservices I will never mention microservices on my CV. Except maybe as an anti-pattern that I can assist with avoiding.