Stack Overflow Jobs

» see stackoverflow.com/jobs as it lived, on the wayback machine

~ the goodbye ~

stack overflow careers launched on october 7 2009 with a joel spolsky blog post that explained the whole business model in one paragraph. the q&a site was free for users while paid job listings would pay the bills. developers could optionally tie their public stack overflow profile to a private cv so they were findable by signal rather than by keyword. for an industry that had spent ten years filtering candidates on whether their resume mentioned "agile" three times, that was a genuinely different idea.

it relaunched as careers 2.0 later, then was rebranded to stack overflow jobs in the late 2010s. developer story arrived as the resume-replacement layer that let candidates assemble a timeline out of repos and answers rather than bullet points. the integration with the main site was real. on a good answer page in 2016 you might get a small embedded recruiter card from a company hiring for that exact tag, which sounds annoying but was less annoying than linkedin recruiter spam.

prosus acquired stack overflow for $1.8 billion in august 2021. on january 19 2022 the company posted a blog announcing that jobs and developer story would both be discontinued by march 31, with the salary calculator going at the same time. the official line from the ceo was that talent acquisition was not a space where stack overflow had a strong competitive advantage. translated: the job board was not earning enough to defend against indeed or linkedin, and prosus wanted the company refocused on knowledge products instead.

i was a working engineer through this whole arc. stack overflow itself was a daily-use site. the jobs section was a place i looked at maybe twice a year when curious about market rates or remote roles. the developer story thing felt like a good idea that nobody around me actually used as their primary cv. when the march 31 shutdown landed it was a non-event for most working engineers, which was the problem.

~ the chronicle ~

~ how it landed ~

the original 2009 careers product was a paid-only place to sign up. developers paid $29 to list a cv, which was meant to filter out spammers. that gating disappeared by careers 2.0. the integration deepened in the 2010s as stack overflow added company pages and tag-based job alerts with a real ats integration on the employer side. for a window around 2014-2018 it was the editor-and-language-specific job board that some developer audiences actually preferred over indeed.

the candidate-side product was tied to the developer story timeline. you put your github profile and your work history in one place, set a "open to opportunities" flag with quiet privacy controls, and recruiters could search you by tag affinity. it was not a perfect product but it was the closest thing the industry had to a github-native cv.

~ why it died ~

indeed and linkedin both spent the 2010s building bigger funnels with bigger ad budgets and a more capable sales motion. y combinator's work-at-a-startup pulled in the founder-network top end of the market. stack overflow jobs was sandwiched in the middle with a smaller catalog and a smaller sales team. the per-listing pricing was high enough that mid-tier companies preferred posting somewhere else first.

prosus wanted cleaner numbers on the post-acquisition books. talent acquisition is a sales-heavy business with a separate team, and shutting it freed the company to push stack overflow for teams, which was the actual growth product. the jobs sunset took eight weeks from announcement to deletion.

~ what got buried with it ~

developer story died alongside it. a small population of working engineers had assembled what they considered their canonical resume on that timeline, with git commit graphs and stack overflow reputation tied in. the export tool worked but the linked-resume format had no destination, so most of those timelines just stopped being updated. you could still link your stack overflow profile in a regular linkedin cv, but the integrated story view was gone.

the salary calculator was the other quiet loss. it used aggregate compensation data from the annual developer survey and was the closest thing to honest mid-career salary signal for a lot of regions, especially the ones glassdoor never had enough data for. levels.fyi covered the high end but for non-bigco roles the stack overflow numbers were what people actually quoted.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »