Jonah Back

864 posts

Jonah Back banner
Jonah Back

Jonah Back

@jonahback

engineer and explorer

Los Gatos, CA Katılım Eylül 2009
362 Takip Edilen774 Takipçiler
Fahd Ananta
Fahd Ananta@fahdananta·
On this great Monday if you are not doing the best work of your life and just pushing around pixels as a designer, come join us at Opendoor What I can promise you: 1. Design every single inch of the user experience, not just styling the product 2. Maximal ownership. We are all stewards. We have 2 designers on our core product and you'll be the 3rd. 3. It will be intense, challenging, and very meaningful Details here: notion.so/We-seek-design…
English
6
15
94
9.1K
Jonah Back
Jonah Back@jonahback·
Excited to be a part of this journey with the Deeptrace team - killer team and killer product
andy lee@andys_lee

Excited to share that @deeptraceai has raised $5M to identify and fix every alert in production. This round is co-led by @felicis and @matrix, with participation from @ycombinator. As AI generates more of the world’s code, the real leverage shifts to systems that help engineers understand and run it in production. Deeptrace is that reliability layer. Today, teams like @opendoor, @mintlify, and @phantom use Deeptrace to automatically investigate every alert in production and proactively catch issues before they turn into incidents. If you’re looking to automate on-call and use agents to monitor prod, please reach out!

English
1
0
5
303
Jonah Back retweetledi
Austen Allred
Austen Allred@Austen·
The cruelest thing you can do to an engineer is require them to use AI to code and at the same time restrict them to using crappy models and tools. I understand why it happens but would be so frustrating.
Anish Moonka@AnishA_Moonka

Amazon had four Sev-1 outages (their highest severity level) in a single week. Internal memos say AI-assisted code changes were a contributing factor. The timeline here is wild. In October 2025, Amazon laid off 14,000 corporate employees. In January 2026, another 16,000. That’s about 30,000 people in five months, roughly 10% of the corporate workforce. CEO Andy Jassy said the cuts were about culture, not AI. During those same months, Amazon set a target: 80% of developers using AI coding tools at least once a week. They tracked adoption closely and blocked rival tools like OpenAI’s Codex. Even so, 30% of developers still hadn’t touched Amazon’s in-house tool Kiro by January. In December 2025, Kiro caused a 13-hour AWS outage. The AI tool had production-level permissions and decided the best fix for a bug was to delete and recreate an entire live environment. A second incident involved Amazon Q Developer, another AI tool. Amazon blamed both on “user error, not AI.” But quietly added mandatory peer review for all production access afterward. Then March 5: Amazon’s retail site went down for about six hours. Over 22,000 users reported checkout failures, missing prices, and app crashes. Amazon called it a “software code deployment” error. Five days later, SVP Dave Treadwell made the normally optional weekly engineering meeting mandatory. His memo acknowledged “GenAI tools supplementing or accelerating production change instructions, leading to unsafe practices.” These problems trace back to Q3 2025. Amazon’s own assessment: their GenAI safeguards “are not yet fully established.” The new rule: junior and mid-level engineers now need senior sign-off on any AI-assisted production changes. Treadwell also announced “controlled friction” for the most critical parts of the retail experience. For context, Google’s 2025 DORA report found 90% of developers use AI for coding but only 24% trust it “a lot.” An Uplevel study of 800 developers found Copilot users introduced 41% more bugs with no improvement in output. Amazon is finding out what those numbers look like at the scale of a $500 Billion revenue company, with 30,000 fewer people on staff to catch the mistakes.

English
32
23
593
53K
Jonah Back
Jonah Back@jonahback·
Sort of telling with buyback authorizations re: how companies think of their future. In a world where every pure SaaS company is at an all time high disruption risk, you’d think that money might be better spent on creating AI native experiences #AtomsNotBits
English
0
0
4
376
Jonah Back retweetledi
Paras Doshi
Paras Doshi@paras_doshi·
Most data teams are still building dashboards nobody looks at. We killed 1,400 of ours. Replaced them with a semantic layer you can talk to. Built custom AI tooling that replaced SaaS we were paying six figures a year for. Every person on this @Opendoor data team has unlimited tokens and AI agents running alongside them daily. Real estate is the largest asset class on earth and the transaction still feels like 1997. That's the data problem we wake up to. Pricing millions of homes. Optimizing tens of millions in ad spend. Building models that move real dollars, not slide decks. Our CEO's (@nejatian) mandate is "default to AI." Not a slogan. How we actually operate. Opendoor might be the most AI-native public company you haven't been paying attention to. Small team. Absurd talent density. Embedded across the entire C-suite. You touch pricing, marketing, product, sales, operations — all of it! We're hiring across Agentic Analytics Engineering and Data Science. Seattle or Toronto. If this is the kind of data team you've been looking for, stop scrolling and apply: Agentic Analytics Engineering: grnh.se/mqzo4ab46us Data Science: grnh.se/awisi8t36us
English
20
58
395
38.5K
Jonah Back retweetledi
Kaz Nejatian
Kaz Nejatian@nejatian·
Last shirt said "Faster." Sneak peek at what this one says. Limited drop at openarmy.com now powered by @shop. Don't miss Q4 Financial Open House tomorrow 2/19 at 2pm PT on X, Robinhood, and YouTube. investor.opendoor.com
English
80
79
669
115K
Jonah Back
Jonah Back@jonahback·
@maelan_sdmr Beyond time savings (which is definitely a secondary benefit), the main thing is iteration and learning speed. When things are fast and inexpensive you can change them often. When they are slow and expensive you don’t want to touch them.
English
0
1
2
123
Maëlan
Maëlan@maelan_sdmr·
@jonahback Incredible. -How much time do you estimate is saved? By a factor of 10? -Are mistakes fixed in the same way meaning they lead to the same final result, or is there a difference?
English
1
0
0
154
Jonah Back
Jonah Back@jonahback·
One of the most underrated things about AI driven automation. Mistakes are easy to fix. We had a bug in our assessment process yesterday. 3 months ago, that would’ve meant 2am pages, lot of overtime and delayed offers. Today we basically just hit ‘retry’ after a fix.
English
2
1
12
717
Jonah Back retweetledi
Jeff Escalante
Jeff Escalante@jescalan·
For anyone in a software engineering leadership/management position, this is the time to see if you can figure out how to shelve that responsibility for a while and return to being a full time IC. Software engineering has changed more in the last few months than it has in the previous decade. The skills, experience, and perspective that you built to get you to the leadership/management position you're in now are becoming irrelevant extremely rapidly. If you are not able to adapt right now, you are going to start becoming bad at your job very soon, if you have not already. You're trusted to lead because you built the skills and judgement over time direct the boat confidently. But the boat that you were driving has suddenly been replaced by a completely different boat which you have never worked on before, so it's time to shift down and re-build your expertise before taking the helm again. 🫡
English
27
17
294
31.7K
Jonah Back
Jonah Back@jonahback·
We’re doing a fun thing @Opendoor a lot more recently. Instead of beleaguering folks - esp founders - with typical tech interview loops, we’re just building in person together. 2 weeks of side by side crafting, focusing on delivering customer value.
English
13
13
226
21K
Jonah Back
Jonah Back@jonahback·
My F5 key is broken today from refreshing my “Sonnet 5” Google Search every 5 minutes
English
0
0
3
696
Yang Guo
Yang Guo@yang_guo·
Happening already - our internal tools are 2x more efficient, iterated on by impact hungry operators (who code and ship now) and engineers. Coding is commoditized but knowing wtf to build and having the agency to just do it is eternal. Lots of talkers, not enough walkers
Ian Tracey@ian_dot_so

x.com/i/article/2013…

English
4
7
103
26.7K
Jonah Back
Jonah Back@jonahback·
Related - we shipped a pretty meaningful change to how we work over the last few weeks. Many internal productivity asks around access, enablement etc all get served by agents with policy docs instead of people - enabling us to stay laser focused on enabling product velocity.
English
0
1
11
466
Jonah Back
Jonah Back@jonahback·
One of the most important decisions we continue to make day in and day out at @Opendoor is to bet on the partners that we think deserve to win in the ai-native landscape of tomorrow. Apps that enable agents > apps that are perfect for the needs of today
English
3
0
22
794
Jonah Back retweetledi
Branko
Branko@brankopetric00·
Client wanted multi-region active-active. I talked them out of it. Their situation: - 2,000 daily users, all in Western Europe - 99.9% uptime requirement - 18-month runway - 3 engineers total What they actually needed: - Single region with proper HA - Multi-AZ database with automated failover - CDN for static assets - Solid backup and restore tested monthly Cost difference: - Multi-region estimate: $23,000/month - Single region HA: $4,200/month They hit 99.95% uptime last year. Zero regrets. Not every problem needs a distributed systems solution. Sometimes the answer is just good fundamentals done well.
English
8
11
145
16.3K