Emily·12h agoSystem Design Interview: How Do You Keep One Slow Dependency From Taking Down Your API?A practical way to budget time, bound retries, and keep optional work from blocking the core request.
Emily·23h agoBackend Interview Question: Why Does Loading 20 Orders Run 21 Queries?A practical way to spot hidden database calls, fix the read path, and check what the fix costs.
Emily·1d agoYour Python Script Works on 1,000 Rows. Then the Real CSV Arrives.How to process files that outgrow memory and explain your approach in an interview.A response icon1A response icon1
Emily·2d agoAmazon Interview Prep: What Happened After You Lost the Argument?How to explain disagreement, trade-offs, and what you did after the team chose a different direction.A response icon1A response icon1
Emily·2d agoDoorDash’s Coding Interview Lets You Use AI. Here’s My 60-Minute Practice Plan.One small project, a running clock, and a way to show that you understand the code your assistant helped you write.
Emily·3d agoTop 10 Software Engineer Interview Questions I’m Practising This NovemberMy November 2026 shortlist, with the examples, traps and follow-ups that make each question worth your time.
Emily·4d agoI Don’t Trust an AI Fix Until I Can Make the Bug Come BackA missing ticket, a misleading green test, and a repeatable way to check what your coding agent actually repaired.
Emily·5d agoSalesforce Interview Question: The Customer Paid. Why Isn’t Their Coffee Being Made?One oat latte, a missing payment confirmation, and a system-design walkthrough that follows the order all the way to the counter.
Emily·5d ago3 Real Outages I’d Study Before My Next System Design InterviewWhat AWS, Cloudflare and GitHub can teach you about failures that clean architecture diagrams leave out.
Emily·6d agoLeetCode 735 Looks Easy Until the First Collision Isn’t the LastOne tiny chain reaction, a tempting wrong solution, and the O(n) reasoning worth taking into your next interview.