[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-dvN-YZwCn2eFLrbvVA0ynFX_i7psMI85YaWu-rPnIag":3,"sanity-pkMJqqoeW-58rVxoJiX4EqmU-TuBW1FULPz-6MG0O5M":220},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":195},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"f83eb5f0-1237-487f-84d8-f7abf2318c39","2026-06-25T07:40:00.000Z",{"_type":10,"current":11},"slug","code-isnt-causing-your-production-failures",null,"Code isn’t the only thing causing your production failures",[15,21,27,33],{"_id":16,"publishedAt":17,"slug":18,"title":20},"eb5b66eb-9410-4329-83bb-22bbff39402a","2026-04-28T13:00:00.000Z",{"_type":10,"current":19},"turn-scattered-knowledge-into-trusted-intelligence","Turning scattered knowledge into trusted intelligence: Stack Internal 2026.3",{"_id":22,"publishedAt":23,"slug":24,"title":26},"369c2401-b62e-4a37-8ff8-bf603023ecad","2026-03-02T15:03:00.988Z",{"_type":10,"current":25},"what-s-new-at-stack-overflow-march-2026","What’s new at Stack Overflow: March 2026",{"_id":28,"publishedAt":29,"slug":30,"title":32},"5e9053a4-07ea-447c-91ea-29e0b6228537","2026-02-02T15:00:00.000Z",{"_type":10,"current":31},"what-s-new-at-stack-overflow-february-2026","What’s new at Stack Overflow: February 2026",{"_id":34,"publishedAt":35,"slug":36,"title":38},"a1b538eb-a8a6-46d0-80a1-ac70ec9bb935","2026-01-05T10:00:00.000-05:00",{"_type":10,"current":37},"what-s-new-at-stack-overflow-january-2026","What’s new at Stack Overflow: January 2026",{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":44,"author":45,"body":59,"comments":166,"dateUrl":167,"excerpt":168,"legacyBody":169,"product":12,"publishedAt":172,"slug":173,"sponsored":12,"tags":175,"title":194,"visible":166},"2023-05-25T09:37:01Z","wp-post-4321","07ZbrKPSUrjrV4wQ6fIGdA","blogPost","2023-07-13T14:54:45Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":54,"name":55,"role":56,"slug":57},"2023-05-23T16:27:18Z","wp-author-154","dgl3SCUzppW3U2LvConCK4","blogAuthor","2023-08-29T11:49:19Z",{"_type":53},"image","former","Joel Spolsky","Co-founder",{"current":58},"spolsky",[60,83,125],{"_key":61,"_type":62,"children":63,"markDefs":78,"style":82},"d9ebcad0ee3c","block",[64,69,74],{"_key":65,"_type":66,"marks":67,"text":68},"d9ebcad0ee3c0","span",[],"We're at that time of year where we go through everybody's salary and makes sure it's reasonable. We're up to about a dozen in-house software developers, and we'd been paying them based on ",{"_key":70,"_type":66,"marks":71,"text":73},"d9ebcad0ee3c1",[72],"72258e4753e5","a compensation system developed by our cousins at Fog Creek",{"_key":75,"_type":66,"marks":76,"text":77},"d9ebcad0ee3c2",[],", which is different enough from Stack Exchange that there was some chafing. So we sat down and thought out developer compensation from basic principles, and came up with what we feel is a pretty robust way to pay great people. Here were the core principles on which the system is built:",[79],{"_key":72,"_type":80,"href":81,"reference":12},"link","http://www.inc.com/magazine/20090401/how-hard-could-it-be-employees-negotiate-pay-raises.html?partner=fogcreek","normal",{"_key":84,"_type":62,"children":85,"markDefs":123,"style":124},"6206d827fa7d",[86,90,95,99,103,107,111,115,119],{"_key":87,"_type":66,"marks":88,"text":89},"6206d827fa7d0",[],"The development team at Stack Exchange is an amazing group of programmers who live up to our motto of “smart and get things done” every day. We want to offer them compensation that is fair, easily understood, transparent, and competitive. ",{"_key":91,"_type":66,"marks":92,"text":94},"6206d827fa7d1",[93],"em","Fair",{"_key":96,"_type":66,"marks":97,"text":98},"6206d827fa7d2",[]," means no games. Our compensation is not based on how well you negotiate or how often you ask for raises—it’s based on a repeatable predictable system. There’s no forced ranking, so other people don’t have to do badly for you to do well. We don’t have a range of possible salaries for every level, we have a single salary, so everything about the system is algorithmic. ",{"_key":100,"_type":66,"marks":101,"text":102},"6206d827fa7d3",[93],"Easily understood",{"_key":104,"_type":66,"marks":105,"text":106},"6206d827fa7d4",[]," means that any developer can figure out what their salary should be according to this system. They can see what they need to do to move up in their career. And different managers can figure out how to pay their team members and get consistent and fair results. ",{"_key":108,"_type":66,"marks":109,"text":110},"6206d827fa7d5",[93],"Transparent",{"_key":112,"_type":66,"marks":113,"text":114},"6206d827fa7d6",[]," reflects Stack Exchange’s core beliefs about running our business in the open, without secrets. It means that if a list of everyone’s salary suddenly appeared on Wikileaks, nobody would be surprised enough to be upset. Transparency is essential to insure fairness. ",{"_key":116,"_type":66,"marks":117,"text":118},"6206d827fa7d7",[93],"Competitive",{"_key":120,"_type":66,"marks":121,"text":122},"6206d827fa7d8",[]," means that you’re earning at least as much at Stack Exchange as you would earn elsewhere. It’s critical to being able to attract and retain the kind of developers we want working for us. If our compensation system isn’t competitive, we won’t be able to hire the people we want without giving them an “exceptional” salary, and exceptions defeat fairness.",[],"blockquote",{"_key":126,"_type":62,"children":127,"markDefs":159,"style":82},"d75f7de6cad4",[128,132,137,141,146,150,155],{"_key":129,"_type":66,"marks":130,"text":131},"d75f7de6cad40",[],"One important principle of Stack Exchange is that we do as much as we can publicly, and we try to leave public artifacts of all the work we do. In that spirit I've uploaded a complete copy of the current compensation plan so you can see what goes into compensation decisions at Stack Exchange. The only thing that is not public is the actual, final computation that determines each individual's paycheck, because we have to balance our own philosophy of openness against the individual developer's right to personal privacy. ",{"_key":133,"_type":66,"marks":134,"text":136},"d75f7de6cad41",[135],"bac70e4934e2","Stack Exchange Developer Compensation (PDF)",{"_key":138,"_type":66,"marks":139,"text":140},"d75f7de6cad42",[]," Are you looking for new work and new compensation? Find ",{"_key":142,"_type":66,"marks":143,"text":145},"d75f7de6cad43",[144],"678bcaf5a835","entry-level",{"_key":147,"_type":66,"marks":148,"text":149},"d75f7de6cad44",[]," to ",{"_key":151,"_type":66,"marks":152,"text":154},"d75f7de6cad45",[153],"47b254eaee67","senior opportunities",{"_key":156,"_type":66,"marks":157,"text":158},"d75f7de6cad46",[]," over at Stack Overflow Jobs.",[160,162,164],{"_key":135,"_type":80,"href":161,"reference":12},"http://stackoverflow.blog/wp-content/uploads/2017/02/Stack-Exchange-Developer-Compensation.pdf",{"_key":144,"_type":80,"href":163,"reference":12},"https://stackoverflow.com/jobs/junior-developer-jobs?utm_source=so-owned&utm_medium=blog&utm_campaign=dev-c4al&utm_content=c4al-link",{"_key":153,"_type":80,"href":165,"reference":12},"https://stackoverflow.com/jobs/senior-developer-jobs?utm_source=so-owned&utm_medium=blog&utm_campaign=dev-c4al&utm_content=c4al-link",true,"2011/07/14","",{"code":170,"language":171},"We're at that time of year where we go through everybody's salary and makes sure it's reasonable. We're up to about a dozen in-house software developers, and we'd been paying them based on \u003Ca href=\"http://www.inc.com/magazine/20090401/how-hard-could-it-be-employees-negotiate-pay-raises.html?partner=fogcreek\">a compensation system developed by our cousins at Fog Creek\u003C/a>, which is different enough from Stack Exchange that there was some chafing.\n\nSo we sat down and thought out developer compensation from basic principles, and came up with what we feel is a pretty robust way to pay great people. Here were the core principles on which the system is built:\n\n\u003Cblockquote>The development team at Stack Exchange is an amazing group of programmers who live up to our motto of “smart and get things done” every day.\n\nWe want to offer them compensation that is fair, easily understood, transparent, and competitive.\n\n\u003Cem>Fair\u003C/em> means no games. Our compensation is not based on how well you negotiate or how often you ask for raises—it’s based on a repeatable predictable system. There’s no forced ranking, so other people don’t have to do badly for you to do well. We don’t have a range of possible salaries for every level, we have a single salary, so everything about the system is algorithmic.\n\n\u003Cem>Easily understood\u003C/em> means that any developer can figure out what their salary should be according to this system. They can see what they need to do to move up in their career. And different managers can figure out how to pay their team members and get consistent and fair results.\n\n\u003Cem>Transparent\u003C/em> reflects Stack Exchange’s core beliefs about running our business in the open, without secrets. It means that if a list of everyone’s salary suddenly appeared on Wikileaks, nobody would be surprised enough to be upset. Transparency is essential to insure fairness.\n\n\u003Cem>Competitive\u003C/em> means that you’re earning at least as much at Stack Exchange as you would earn elsewhere. It’s critical to being able to attract and retain the kind of developers we want working for us. If our compensation system isn’t competitive, we won’t be able to hire the people we want without giving them an “exceptional” salary, and exceptions defeat fairness.\u003C/blockquote>\n\nOne important principle of Stack Exchange is that we do as much as we can publicly, and we try to leave public artifacts of all the work we do. In that spirit I've uploaded a complete copy of the current compensation plan so you can see what goes into compensation decisions at Stack Exchange. The only thing that is not public is the actual, final computation that determines each individual's paycheck, because we have to balance our own philosophy of openness against the individual developer's right to personal privacy.\n\n\u003Ca href=\"http://stackoverflow.blog/wp-content/uploads/2017/02/Stack-Exchange-Developer-Compensation.pdf\">Stack Exchange Developer Compensation (PDF)\u003C/a>\n\nAre you looking for new work and new compensation? Find \u003Ca href=\"https://stackoverflow.com/jobs/junior-developer-jobs?utm_source=so-owned&utm_medium=blog&utm_campaign=dev-c4al&utm_content=c4al-link\" target=\"_blank\" rel=\"noopener\">entry-level\u003C/a> to \u003Ca href=\"https://stackoverflow.com/jobs/senior-developer-jobs?utm_source=so-owned&utm_medium=blog&utm_campaign=dev-c4al&utm_content=c4al-link\" target=\"_blank\" rel=\"noopener\">senior opportunities\u003C/a> over at Stack Overflow Jobs.","html","2011-07-14T12:00:00.000Z",{"current":174},"how-much-should-you-pay-developers",[176,184,189],{"_createdAt":177,"_id":178,"_rev":179,"_type":180,"_updatedAt":177,"slug":181,"title":183},"2023-05-23T16:43:21Z","wp-tagcat-background","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":182},"background","Background",{"_createdAt":177,"_id":185,"_rev":179,"_type":180,"_updatedAt":177,"slug":186,"title":188},"wp-tagcat-company",{"current":187},"company","Company",{"_createdAt":177,"_id":190,"_rev":179,"_type":180,"_updatedAt":177,"slug":191,"title":193},"wp-tagcat-stackexchange",{"current":192},"stackexchange","Stackexchange","How much should you pay developers?",[196,202,208,214],{"_id":197,"publishedAt":198,"slug":199,"sponsored":12,"title":201},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":200},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":203,"publishedAt":204,"slug":205,"sponsored":12,"title":207},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":206},"your-ai-shipped-a-backend-that-boots-that-is-the-whole-problem","Your AI shipped a backend that boots. That is the whole problem.",{"_id":209,"publishedAt":210,"slug":211,"sponsored":12,"title":213},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":212},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"_id":215,"publishedAt":216,"slug":217,"sponsored":12,"title":219},"30b995f7-7cb9-4dd8-bf71-d0685940a32b","2026-06-19T14:00:00.000Z",{"_type":10,"current":218},"dispatches-from-o-reilly-from-capabilities-to-responsibilities","Dispatches from O'Reilly: From capabilities to responsibilities",{"data":221,"sourceMap":-1},{"count":222,"lastTimestamp":223},2,"2023-05-25T09:45:54Z"]