Live data from Hacker News

The Stack Overflow Developer Story: A New Technical Resume

blog.stackoverflow.com

141–147 of 147 posts

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

#141

Earlier quoted context omitted.

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…

Software Engineer, Data Engineer, Systems Engineer, Software Architect...

There are endless variations referring to close jobs.

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

#142
post #54
post #47

StackOverflow as a company may have grown a little too quickly; I wonder how much $$ they make from this and whether they should just focus on their core which is community and maintaining a decent community rather than these marketing-led stunts.

These aren't mutually exclusive goals. We have people dedicated to growing and maintaining the community (on Stack Overflow, as well as the other sites in the Stack Exchange network), people who work on large feature areas (e.g. Documentation), yet more people who are focused on the Jobs and hiring/recruiting experience for developers, etc.

I'm more curious to know how these affect the profits of StackOverflow and what gets more bang for the buck or if random ideas are being tried out seeing which one sticks.

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

#143
post #138
post #137

Earlier quoted context omitted.

I wonder if you would think that about my github profile. I don't have any JS, but I have forked a few C and C++ repos to make minor changes and hold them until upstream accepted them. I don't think I have deleted any of them. Then I have a few experiments answering questions I wanted answered. It is not particularly hard to determine if fork n` fix is the reason for the repo. A search for the name of a project will…

Sure, but these ones are definitely box-ticking exercises, I guess some "thought leader" on LinkedIn said all the best companies only hire people with Github, and off the masses went. There are loads of placeholder "tech blogs" too.

If a company is asking for code from a person then not checking the code, doesn't that indicate something is really wrong with the company?

Why would someone with real skill and therefore a real profile work there? Let all the fakers go work at shitty companies.

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

#144
post #143
post #138

Earlier quoted context omitted.

Sure, but these ones are definitely box-ticking exercises, I guess some "thought leader" on LinkedIn said all the best companies only hire people with Github, and off the masses went. There are loads of placeholder "tech blogs" too.

If a company is asking for code from a person then not checking the code, doesn't that indicate something is really wrong with the company? Why would someone with real skill and therefore a real profile work there? Let all the fakers go work at shitty companies.

All it's actually done is made Github no longer a signal that would make you pick a CV out of the pile.

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

#145
post #134

Earlier quoted context omitted.

Although I'm not intending to derail the thread, I'm curious what resources or techniques would you recommend to get better at this?

If you're writing your own resume, I'd maybe sit down every six months to a year and think about things you accomplished, and write then down (problem solved, how it was solved, data if possible, impact, etc.). At some point you'll have a list of accomplishments, and you can select the more impressive of them to put on the resume. (As an aside - this also helps with career stagnation. If you're having a hard time dec…

Neat, thanks it's very much appreciated. I did some digging and except from re-posted articles and CV builders it seems like there are not many tools to help with this. Which surprises me a bit given that I'd think many struggle to be effective in something I consider crucial to be successful in your chosen field.

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

#146
post #60

Earlier quoted context omitted.

As I've gotten older my resumes have gotten shorter. The shortest resume is just your last name "Zuckerberg" or "Snowden". If you've achieved something impressive (sold a company, started a well known web framework, fixed some large horrible government or organizational process) it speaks for itself and the rest of it is just making sure you aren't a conartist, which an interview can easily handle.

>As I've gotten older my resumes have gotten shorter. That's refreshing to hear. 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. Many people do get emotionally attached to the work they've done. I've worked with people transitioning…

So true.

Some years ago, I changed my career from Linux System Engineer to Web Developer (Rails and JS). I know that the fact that I was building HA clusters some back then has 0 relevance with the job I am doing now, but it is hard for me to just delete this from my résumé, to leave more room to explain what I am doing now.

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

#147
post #118

Earlier quoted context omitted.

if I was recruiter, math knowledge would make the difference, it helps even unconsciously for problem solving, logic reasoning, algorithms

math... helps even unconsciously for problem solving, logic reasoning, algorithms What makes you think this? Anything aside from intuition?

at least one point that helps math minds is that a lot of math notions are present in programming languages
Post reply on HN