\n\nGet yours today at \u003Ca href=\"http://s.tk/story\">s.tk/story\u003C/a>. It only takes a few minutes, and you do NOT want some other joker snapping up the good URLs. Take it from me, \u003Ca href=\"https://www.youtube.com/watch?v=DLzxrzFCyOs\">stackoverflow/story/J@yH@n10n\u003C/a>.\n\n\u003Ch2>Technology has evolved. Tech resumes? Not so much.\u003C/h2>\n\nThe resume was invented by Da Vinci in the 15th century. It mostly served as a letter of introduction for traveling lords… and it hasn’t changed much since. What do you see when you scan the bold stuff on a resume? Employers, job titles, schools, and degrees. And a lot of small bullets. Plus maybe an other-stuff-intended-to-round-me-out-as-an-actual-human section at the bottom.\n\n\u003Cblockquote>In the roughly \u003Cem>five centuries\u003C/em> since resumes were created to help nobility vouch for roadbound gentry, they’ve stayed mostly optimized for one thing: conveying the importance of your pedigree.\u003C/blockquote>\n\nThe emphasis is all on the seniority of your titles and how impressive your companies or schools have been. Which is a great way for \u003Cem>some\u003C/em> developers to put their best foot forward. Have a Masters in CS from Yalemouth? Cool! That’s one good signal. But it ain't the only one. Heck, even \u003Cem>politicians\u003C/em> know that fancy schools are only one of many ways to signal potential:\n\n\u003Cblockquote>“It turns out it doesn’t matter where you learned code, it just matters how good you are at writing code.” — \u003Ca href=\"https://www.wired.com/2015/03/techhire-initiative/\">President Barack Obama\u003C/a>\u003C/blockquote>\n\n\u003Ch2>Show, don’t just tell.\u003C/h2>\n\nDevelopers, fundamentally, are \u003Cem>makers\u003C/em>. Like designers… or architects… or jugglers! You wouldn’t hire any of them based on a list of titles or places they’d worked. (\"Oh, a \u003Cem>Senior\u003C/em> Associate Juggler? Get her! I bet she can do those flaming sticks and stuff!\") So why hire a developer that way? Makers' skills are conveyed by \u003Cem>showing\u003C/em>, not telling. Portfolios. Blueprints. This \u003Ca href=\"https://vimeo.com/71300481\">awesome juggling video\u003C/a>.\n\n\u003Ch3>Be more than bullets: Your best work, front and center.\u003C/h3>\n\nThe Developer Story lets you share what you've worked on by linking to actual features you’ve worked on, blog posts, or public code. Those things shouldn’t be \u003Cem>described\u003C/em> in the second clause of a tiny bullet, or relegated to the “Other interests” section of a resume, to sit unassumingly next to your second-place trophy in intramural tetherball.\n\nThe Developer Story puts the work you’re most proud of where it belongs: at the grownup table, right alongside your roles or schools.\n\n\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/5jcMz.png\" alt=\"Which of these better tells the real story?\" />\n\n\u003Cstrong>No reputation points? No problem.\u003C/strong> Posting answers or contributing to \u003Ca href=\"http://stackoverflow.com/documentation\">Documentation\u003C/a> is one way to build up public artifacts of your coding experience, but it’s not the only way. Your Developer Story lets you show off whatever you work on. So you’ll look good, no matter how much rep you have on Stack Overflow.\n\n\u003Ch3>Find a job you'll love, on your terms.\u003C/h3>\n\nIf you’re ready for your next challenge, the Developer Story makes it easy to learn about jobs that fit \u003Cem>your\u003C/em> personal criteria. And since \u003Ca href=\"https://stackoverflow.com/jobs/back-end-developer-jobs?utm_source=so-owned&utm_medium=blog&utm_campaign=dev-c4al&utm_content=c4al-link\" target=\"_blank\" rel=\"noopener\">developers\u003C/a> are in demand, we know it’s not about finding a job — it’s about finding the \u003Cem>right\u003C/em> job. The same way Stack Overflow Q&A put the right answer right on top, when you fill out your profile, \u003Ca href=\"https://stackoverflow.com/jobs?utm_source=so-owned&utm_medium=blog&utm_campaign=dev-c4al&utm_content=c4al-link\" target=\"_blank\" rel=\"noopener\">Stack Overflow Jobs\u003C/a> shows you roles that match the technology or projects you want to work on. (Even if they’re not what you’re using today.) And we \u003Cem>always\u003C/em> put the developer in control. No spam, no BS. (Did you know that Stack Overflow Jobs actually penalizes blind messaging by employers?)\n\n\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/i8Y3H.png\" alt=\"\" />\n\nAnd it's 100% backwards-compatible with those crusty old resumes - it \u003Cem>can\u003C/em> still highlight fancy schools and fancy titles, and anything else you'd include on a traditional resume. So if you're like me, and \u003Cem>still\u003C/em> just a little proud that you got off the waitlist and eked your way into a school above your intellectual weight class, you can still show off your alma mater off with pride.\n\n\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/0VEqO.png\" alt=\"\" />\n\n\u003Cstrong>But don’t employers just want role, schools, and keywords?\u003C/strong>\nNope. It turns out that they’ve just accepted that that’s all that they can generally get from a resume, leaving them stuck using “seven vs. eight years of JavaScript experience” to determine whom to interview. The employers we’ve shared it with \u003Cem>love\u003C/em> the way the Developer Story gives them real, tangible ways to understand what a candidate has actually worked on.\n\n\u003Ch3>It's not just for developers who are job hunting.\u003C/h3>\n\n\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/iI5fD.png\" alt=\"\" />\n\n\u003Cstrong>Happy at your current gig, but open-minded?\u003C/strong> According to our \u003Ca href=\"http://stackoverflow.com/research/developer-survey-2016\">2016 developer survey,\u003C/a> 63% of developers aren't actively looking, but \u003Cem>are\u003C/em> open to learning about new opportunities to level up. If you’re enjoying where you are, but open to finding that perfect new challenge, the Developer Story can help you keep an eye on what’s out there, and we’ll only send you the best opportunities that match your goals.\n\n\u003Cstrong>\u003Cem>Completely\u003C/em> not interested in jobs, but proud of what you’ve made?\u003C/strong> Listen, I get it. I \u003Ca href=\"https://twitter.com/JayHanlon/status/775721682661216256\">\u003Cem>never\u003C/em> want to leave my job\u003C/a>. The Developer Story is for you, too. Like most people who make things, devs often like to share what they’ve built. So it’s designed so you can use it as your own “coding central,\" even if you’re not job hunting. Just create a Developer Story, but set your job preference to “Not Interested.” You can share the features you’ve worked on, Github repos, blog posts, or even books you’d recommend. It’s your story. Tell it your way.\n\n\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/2RVAi.png\" alt=\"\" />\n\n\u003Ch3>Once your Developer Story is beautiful, let’s work on your wardrobe.\u003C/h3>\n\nWe think one of the best ways to inspire other devs is by sharing some of the awesome stuff their peers are building. Or by showing a curious twelve year old what someone else who loves breaking machines can grow up to be.\n\nSo, for the next two weeks, if you tweet a link to your developer story, and include the #mydevstory hashtag, we’ll enter in you in a contest to win one of two hundred gen-u-ine Stack Overflow tees (50 mens and 50 women shirts each week.) And don’t forget the link to your Developer Story - we need it to contact you if you win.\n\n\u003Ca href=\"http://stackoverflow.com/users/story/join\">Take a minute to start your story now.\u003C/a>\n\n\u003Cem>(We hope you’ll indulge our use of Rear Admiral Hopper’s incredible biography as a case study for the images in this post. You should not take this to mean that the Rear Admiral endorses Stack Overflow in any way. You can, however, take it to mean that we endorse her. Wholeheartedly.)\u003C/em>\n\n\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/b9CbL.png\" alt=\"Grace Hopper\" />\n\nThanks to Abby T. Mars, Elaine Wang, Kaitlin Pike, Kit Carrau, Rachel Maleady, Taryn Pratt, and Tim Post for helping to improve this post.","html","2016-10-11T12:00:00.000Z",{"current":534},"bye-bye-bullets-the-stack-overflow-developer-story-is-the-new-technical-resume",[536,544,549],{"_createdAt":537,"_id":538,"_rev":539,"_type":540,"_updatedAt":537,"slug":541,"title":543},"2023-05-23T16:43:21Z","wp-tagcat-announcements","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":542},"announcements","Announcements",{"_createdAt":537,"_id":545,"_rev":539,"_type":540,"_updatedAt":537,"slug":546,"title":548},"wp-tagcat-company",{"current":547},"company","Company",{"_createdAt":537,"_id":550,"_rev":539,"_type":540,"_updatedAt":537,"slug":551,"title":553},"wp-tagcat-stackoverflow",{"current":552},"stackoverflow","Stackoverflow","Bye Bye, Bullets: The Stack Overflow Developer Story is the New Technical Resume",[556,562,568,570],{"_id":557,"publishedAt":558,"slug":559,"sponsored":12,"title":561},"1b0bdf8c-5558-4631-80ca-40cb8e54b571","2025-08-21T14:00:25.054Z",{"_type":10,"current":560},"research-roadmap-update-august-2025","Research roadmap update, August 2025",{"_id":563,"publishedAt":564,"slug":565,"sponsored":12,"title":567},"5ff6f77f-c459-4080-b0fa-4091583af1ac","2025-08-20T14:00:00.000Z",{"_type":10,"current":566},"documents-the-architect-s-programming-language","Documents: The architect’s programming language",{"_id":16,"publishedAt":17,"slug":569,"sponsored":12,"title":20},{"_type":10,"current":19},{"_id":571,"publishedAt":572,"slug":573,"sponsored":12,"title":575},"f0807820-02d7-4fc5-845f-3d76514b81c0","2025-08-11T16:00:00.000Z",{"_type":10,"current":574},"renewing-chat-on-stack-overflow","Renewing Chat on Stack Overflow ",{"count":577,"lastTimestamp":578},3,"2023-05-25T09:45:54Z",["Reactive",580],{"$sarticleModal":528},["Set"],["ShallowReactive",583],{"sanity-URHeXJ_3Ix-nMdClg54U7ugHKHF4OebSuvaYz-adY80":-1,"sanity-comment-wp-post-5278-1755878840188":-1},"/2016/10/11/bye-bye-bullets-the-stack-overflow-developer-story-is-the-new-technical-resume/"]