Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Stack Overflow Developer Story: A New Technical Resume

blog.stackoverflow.com

Post reply on HN
Print view View original

81–90 of 147 posts

Re: The Stack Overflow Developer Story: A New Technical Resume

#81

Post by alain94040 »

ge96 wrote: post #78

I'm trying to get hired as a junior front end developer. Suck at writing resumes. This is my worst one so far. Also I've been applying but no responses, I have a defeatist mentality and also I think I do accept that I don't meet the requirements. http://m.imgur.com/a/oCdvU I have changed the format some as the bullets as titles doesn't make sense. Still I have to condense and overall my "achievements" are pretty basi…

That is a terrible resume :-(

Why would you start with negative sentences about your projects? "not complete". "at best what I have...". "decided to abandon".

The second page is much more promising. Instead of story-telling and editorializing "This was a basic job, and quick", focus on what techniques you used:

- started from a broken Bootstrap prototype - rewrote email sending using package xyz

etc. Show me that you know how to use a variety of technologies, packages and tools. Then I can judge whether I have a job for you.

Re: The Stack Overflow Developer Story: A New Technical Resume

#84

Post by pmiller2 »

user5994461 wrote: post #80
pmiller2 wrote: post #76

Earlier quoted context omitted.

Yeah. Can't do anything about my university or past companies. I do realize I have the equivalent of "I am totally open to leave my current company," because for the right offer, I would. Saying I'm "open to opportunities" means precisely that: offer me something that betters my current and future situation, and I might take it. If a company doesn't understand that, they're deluding themselves. I have no visibility i…

The university fades after a bit of experience (and regular switching to better companies :D). I try but I cannot understand your situation. I couldn't work without business and user metrics. That's the only thing changing from a job to another. Keywords: More technologies. More trendy job titles. [Don't know what's relevant to your past jobs. Can't help.]

What would be examples of trendy job titles? I can safely and ethically change my previous job title, as long as it doesn't imply I was an executive and accurately represents what I did. (They officially don't care about job titles. It's literally whatever you want as long as you don't claim to be an executive when you're not.)

Believe it or not, changing these job titles to what they are now actually got me far more attention than what I had before (which was just the "official" job title, which didn't necessarily reflect the things I was actually doing).

Re: The Stack Overflow Developer Story: A New Technical Resume

#85

Post by amorphid »

user5994461 wrote: post #64
throwawayosiu1 wrote: post #51

Earlier quoted context omitted.

Very recently, a close friend was looking for a job (as a junior dev - focused on web). After applying and getting rejected, we decided to try a different approach - he basically gave up and decided to the following: 1) added buzz keywords in his resume 2) hosted an instance of gitlab and took various open source projects (stuff that was not popular, but had enough polish), modified them and uploaded them. After a we…

> While he did get called out once, almost all engineers/non-tech hr didn't bother calling his bluff. I see plenty of GitHub profiles that are filled with forked/starred projects from other people, and nothing of substance. I don't bring it to the candidate because it is worthless and there are more interesting things to talk about. But that doesn't mean I didn't see it ;) Actually I have never once in my life see a…

I don't like this notion of having a "good" GitHub profile. GitHub started off as an easy place for me to dump code, no matter how crappy. Dumb ideas, samples from learning, incomplete experiments, whatevs.

Then I noticed that I had started censoring my code krapola. I was sepf conscious about the code I was making visible, as I didn't want to be judged. Then I decided that lame. Now I shamelessly put garbage on GitHub, too.

Coding poorly & having fun trumps curating a collection fancy schmancy artisinal repos. And I've also learned that my good code often lives at work, and never makes it to GitHub.

Re: The Stack Overflow Developer Story: A New Technical Resume

#86

Post by bduerst »

gamedna wrote: post #36

My recent job search lead me to the idea that the traditional resume is broken. Temporal view only gives recruiters and hiring managers the bullet points to qualify you in whatever bucket that they need. Instead of a traditional CV/Resume, I went with a single page narrative approach with a link to the temporal view on my LinkedIn profile. Initially there was some pushback as the recruiters were bellyaching over the…

I would take a step further and just make a 1-2 page project/product recommendation for their company based on the role that you're applying for.

It takes more time, but the last time I was job hunting, I did it with several startups and got interviews with all of them (no referral). The resume + cover letter converted much worse for the other companies I applied to at the time.

Re: The Stack Overflow Developer Story: A New Technical Resume

#87

Post by bduerst »

dhd415 wrote: post #26

It's an interesting idea, but I prefer to take my experience and tell a story that specifically targets the role for which I am applying. From that perspective, having a single "story" out there for all potential employers isn't optimal for me.

They should let you tag items on the timeline for different roles, so that you can quickly filter it for employers and send out.

Re: The Stack Overflow Developer Story: A New Technical Resume

#88

Post by BinaryIdiot »

fecak wrote: post #72
BinaryIdiot wrote: post #66

Earlier quoted context omitted.

> I hear too many people claiming "I have so much experience and accomplishments that I simply can't fit them all in under four pages". The problem there is just an inability to assess what is the most impressive or relevant experience. As someone who recently did some job hunting I will tell you that while I agree on an idealism level with your comment it's just simply not true in practice. I had many, many companie…

The 'in practice' part might have some non-human readers involved, but even an ATS scoring a resume isn't likely searching for a huge number of buzzwords that couldn't be contained in the average skills section - a list of maybe 3-4 lines of an entire page. I definitely agree on the benefit of sending a short resume direct to a human like those on a "Who's Hiring" post, but I don't think a human reader went through y…

> I don't think a human reader went through your entire 5 pages, and I'm pretty sure you could have achieved the same positive result with 1-2 pages if optimized properly. Maybe not though.

Possibly. I didn't take a ton of time testing different scenarios. And yeah most of the ones that rejected me were within minutes even applying late at night so I assumed an automated system.

I don't know if I've ever read my own 5 page resume all in one sitting, heh. I use it as more of a career / professional catalog of just about everything so I can pick and choose when I update / tweak my truncated resume depending on the employer.

Re: The Stack Overflow Developer Story: A New Technical Resume

#89

Post by dilemma »

gamedna wrote: post #36

My recent job search lead me to the idea that the traditional resume is broken. Temporal view only gives recruiters and hiring managers the bullet points to qualify you in whatever bucket that they need. Instead of a traditional CV/Resume, I went with a single page narrative approach with a link to the temporal view on my LinkedIn profile. Initially there was some pushback as the recruiters were bellyaching over the…

Looks like you made your CV your cover letter and your LinkedIn your CV.

The effect is that you used the mindspace otherwise occupied by the CV to tell your story - to brand yourself. There's only one you, but there's thousands of CVs indistinguishable from yours (and mine), so it makes sense that this worked better.

Re: The Stack Overflow Developer Story: A New Technical Resume

#90

Post by Nimitz14 »

ge96 wrote: post #78

I'm trying to get hired as a junior front end developer. Suck at writing resumes. This is my worst one so far. Also I've been applying but no responses, I have a defeatist mentality and also I think I do accept that I don't meet the requirements. http://m.imgur.com/a/oCdvU I have changed the format some as the bullets as titles doesn't make sense. Still I have to condense and overall my "achievements" are pretty basi…

In case you're not trolling, google for "example resumes".
Post reply on HN