[{"data":1,"prerenderedAt":285},["ShallowReactive",2],{"articles-list":3},[4,158],{"id":5,"title":6,"author":7,"body":8,"date":142,"description":143,"extension":144,"image":145,"imageAlt":145,"meta":146,"navigation":147,"ogImage":145,"path":148,"seo":149,"sitemap":150,"stem":151,"tags":152,"tldr":156,"__hash__":157},"articles\u002Farticles\u002Fstartup-didnt-pay-engineers-wrong.md","I Worked for a Startup That Didn't Pay Me. Here's What Engineers Keep Getting Wrong","Jon Wexler",{"type":9,"value":10,"toc":133},"minimark",[11,20,23,28,31,34,37,40,44,47,50,53,56,59,62,65,68,71,75,78,91,94,97,114,117,120,124,127,130],[12,13,14,15,19],"p",{},"I once worked for a startup called ",[16,17,18],"strong",{},"Soon Dating",".",[12,21,22],{},"They owed me around $56,000. I never got paid.",[24,25,27],"h2",{"id":26},"background","Background",[12,29,30],{},"This did not start as a bad situation. Like most early-stage opportunities, it began with energy and momentum. There was a real product vision, active development, and conversations about funding that made the future feel close.",[12,32,33],{},"There was also a contract. There were defined expectations. On paper, it looked legitimate. In practice, it felt like something worth committing to.",[12,35,36],{},"So I treated it like a job. I showed up, built what was needed, and trusted that the structure in place would hold.",[12,38,39],{},"That assumption turned out to be wrong.",[24,41,43],{"id":42},"lack-of-payment-and-legal-reality","Lack of payment and legal reality",[12,45,46],{},"The shift did not happen all at once.",[12,48,49],{},"Payments started slipping. An invoice would be delayed, then another. Each time there was a reasonable explanation. Funding was in progress. Money was expected soon. Something was processing.",[12,51,52],{},"Individually, none of these explanations felt alarming. Together, they formed a pattern that I did not act on early enough.",[12,54,55],{},"I kept working. Like most engineers, I optimized for progress. I assumed that continuing to deliver would help stabilize the situation or get things across the finish line.",[12,57,58],{},"Instead, the unpaid balance grew to a point where it could no longer be ignored.",[12,60,61],{},"At that stage, I explored legal options. The reality was sobering.",[12,63,64],{},"Even with a contract, enforcement depends on the company having money or assets. If a startup runs out of cash, there is often nothing meaningful to recover. Legal action becomes expensive, slow, and uncertain, especially across jurisdictions or without clear leverage.",[12,66,67],{},"The hard truth is this: a contract does not create money. It only gives you a claim to it if it exists.",[12,69,70],{},"By the time I fully internalized that, the situation was already set.",[24,72,74],{"id":73},"lessons-learned","Lessons learned",[12,76,77],{},"The biggest mistake was not that I worked with a startup. It was that I treated the engagement as if payment was guaranteed.",[79,80,81,85,88],"ul",{},[82,83,84],"li",{},"I let unpaid work accumulate beyond a reasonable threshold.",[82,86,87],{},"I relied on verbal assurances about funding instead of verifying them.",[82,89,90],{},"I continued delivering at full speed even as warning signs appeared.",[12,92,93],{},"None of this felt irresponsible in the moment. It felt collaborative and professional. In reality, it exposed me to risk that I was not actively managing.",[12,95,96],{},"What I would do differently is straightforward, but requires discipline.",[79,98,99,102,105,108,111],{},[82,100,101],{},"Keep unpaid balances small and enforce clear limits. If payments fall behind, pause work.",[82,103,104],{},"Structure payments in short intervals or require partial payment upfront.",[82,106,107],{},"Ask direct questions about runway and funding status, and take vague answers seriously.",[82,109,110],{},"Separate equity upside from cash compensation instead of blending the two.",[82,112,113],{},"Be willing to walk away early, before the situation compounds.",[12,115,116],{},"The mental shift matters most. When working with early-stage companies, you are not just contributing code. You are making a financial decision every time you continue without being paid.",[12,118,119],{},"If you do not manage that decision, it will be made for you.",[24,121,123],{"id":122},"bottom-line","Bottom line",[12,125,126],{},"Startups usually do not fail because they choose not to pay people. They fail because they run out of time and money.",[12,128,129],{},"When that happens, contracts offer limited protection.",[12,131,132],{},"Structure and discipline at the start of the engagement matter far more than anything you try to enforce at the end.",{"title":134,"searchDepth":135,"depth":136,"links":137},"",2,3,[138,139,140,141],{"id":26,"depth":135,"text":27},{"id":42,"depth":135,"text":43},{"id":73,"depth":135,"text":74},{"id":122,"depth":135,"text":123},"2026-04-27","Unpaid work at an early company taught me that contracts are not money, and that discipline and limits matter more than heroics. Lessons for engineers in volatile environments.","md",null,{},true,"\u002Farticles\u002Fstartup-didnt-pay-engineers-wrong",{"title":6,"description":143},{"loc":148},"articles\u002Fstartup-didnt-pay-engineers-wrong",[153,154,155],"career","startups","engineering","A startup owed me a large sum I never collected. The lesson is not to avoid startups, but to treat continuing without pay as a financial risk you manage, not a background detail.","_yyDdYIxCAOyWhnk4nA3sVP8ZisSuQkCHFHZosmLHy0",{"id":159,"title":160,"author":7,"body":161,"date":273,"description":274,"extension":144,"image":145,"imageAlt":145,"meta":275,"navigation":147,"ogImage":145,"path":276,"seo":277,"sitemap":278,"stem":279,"tags":280,"tldr":283,"__hash__":284},"articles\u002Farticles\u002Finvitation.md","An invitation: a little about me and this site",{"type":9,"value":162,"toc":265},[163,166,170,189,193,200,207,211,218,222,233,236,240,247,251],[12,164,165],{},"If you have landed on this page from a link, a search, or a friend, welcome. I built this site as a home for the things I care about professionally: how software gets designed, how teams ship, and how people learn. Below is a compact version of my path. If you want the full version later, the details still live in the usual places, but for now, here is the human version.",[24,167,169],{"id":168},"why-this-site-exists","Why this site exists",[12,171,172,173,178,179,183,184,188],{},"You should not have to dig through a PDF to get a feel for who someone is. Here you will find a ",[174,175,177],"a",{"href":176},"\u002Fportfolio","Portfolio"," take on how I think about work, a ",[174,180,182],{"href":181},"\u002Fbooks","Books"," page if you are curious about my writing, and a ",[174,185,187],{"href":186},"\u002Fcontact","Contact"," page if you want to get in touch. The goal is easy scanning: a few well structured pages instead of a wall of keywords.",[24,190,192],{"id":191},"big-teams-big-surfaces","Big teams, big surfaces",[12,194,195,196,199],{},"A lot of my energy has gone into work where mistakes are expensive and scale is real. At ",[16,197,198],{},"Bloomberg",", I helped build responsive web products used by millions of people every day, alongside work on data heavy legal analytics, ML for text and recommendations, and the day to day of shipping in a large engineering culture.",[12,201,202,203,206],{},"At ",[16,204,205],{},"Meta (Facebook)",", the problems shifted toward messaging, infrastructure, and very large user surfaces. I led or contributed to iOS, Android, and web initiatives, from messaging and queues to ML driven features that had to be safe, measured, and reliable for people all over the world. More recently I have also worked in the broader Meta ecosystem, including product direction around AI in Reality Labs, where constraints and tooling are still evolving fast.",[24,208,210],{"id":209},"mobile-product-and-startups","Mobile, product, and startups",[12,212,213,214,217],{},"Not everything has been a giant org chart. I have been a senior engineer on ",[16,215,216],{},"React Native"," and payment adjacent flows at a dating product startup, owned releases and push notification pipelines, and sat closer to the product and store submission cycle than a pure platform team sometimes does. That range matters to me. Shipping on a phone in someone’s hand teaches different lessons than shipping a dashboard in a browser.",[24,219,221],{"id":220},"teaching-writing-and-paying-it-forward","Teaching, writing, and paying it forward",[12,223,224,225,228,229,232],{},"I care about clarity for learners. I was ",[16,226,227],{},"Lead Developer and Academic Director"," at the New York Code and Design Academy, where I worked with a team, shaped Rails and Node curriculum, and taught in person. I have been an ",[16,230,231],{},"author with Manning"," on Node.js, with curriculum tied to university use, and I have written and spoken for a wider audience in other channels too.",[12,234,235],{},"I still think of \"engineer\" and \"educator\" as two parts of the same job: you only really know a topic when you can help someone else get unstuck.",[24,237,239],{"id":238},"the-independent-thread","The independent thread",[12,241,242,243,246],{},"For years I have also run my own small shop, ",[16,244,245],{},"Hacky Apps",", where I design and build for clients, coordinate contractors, and stay close to UI and product decisions. It keeps me honest about tradeoffs, timelines, and what \"done\" really means for a business, not just for a ticket.",[24,248,250],{"id":249},"if-you-want-to-go-deeper","If you want to go deeper",[12,252,253,254,257,258,261,262,264],{},"That is the short version. The longer story includes earlier teaching assistant work at ",[16,255,256],{},"Brandeis",", ",[16,259,260],{},"volunteer instruction"," for CodeNation and Re:Coded, a couple of degrees I am still proud of, and a lot of small team wins that do not fit a headline. When you are ready, wander over to the rest of the site, or just say hello through ",[174,263,187],{"href":186},". I am glad you are here.",{"title":134,"searchDepth":135,"depth":136,"links":266},[267,268,269,270,271,272],{"id":168,"depth":135,"text":169},{"id":191,"depth":135,"text":192},{"id":209,"depth":135,"text":210},{"id":220,"depth":135,"text":221},{"id":238,"depth":135,"text":239},{"id":249,"depth":135,"text":250},"2026-04-26","A warm hello if you are new here, plus a short tour of the work I do, based on the same path you would see on my full resume.",{},"\u002Farticles\u002Finvitation",{"title":160,"description":274},{"loc":276},"articles\u002Finvitation",[153,281,282],"web","node.js","This is a short tour of my career (Bloomberg, Meta, teaching, writing, and independent work) and an invite to explore the rest of the site, without replacing a full resume.","3hRDhG1Z-EayTNVzrBEyufRJeCsxjs77K9pKNsvxbpU",1777263960787]