Firecode (@firecodeio) header
Firecode (@firecodeio) profile picture

Official X for Firecode. Coding Interview Prep - Done Right. See what the hype is about at https://teapawt.net/t.co/ATzwG2aScM

San Francisco, CA
Joined April 2015
Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)Photo by Firecode (@firecodeio)
Coding interview tip: say the brute force out loud first. The interviewer isn't grading whether you jump straight to O(n). They're watching you get from O(n²) to O(n) and say why. Brute force, its cost, the bottleneck, the fix. Four sentences, and you've shown them how you think.
46
Replying to @coryalthoff
All the doomers who said software engineering is dead have been wrong so far, let’s be optimistic and try to enjoy the evolution of the role and our day-to-day work!
10
Replying to @jonsegov
Agree. Though it won’t be called CS anymore.
3
Replying to @enjojoyy
I’d go a step further and say developer was never really a durable role to begin with. Software engineer, sure. That’s two very different sets of skills. Both write code, but only the latter builds durable engineering systems
6
Replying to @Muskanm_1227
12 days to go 🔥 the prefix-parity trick from that one comes back a lot: Subarray Sums Divisible by K is the same idea with remainders mod k instead of odd/even
4
Replying to @vaishnavidotdev
heap week continues 🔥 Smallest Range is the sneaky one: same k-way min-heap as Merge K, but you also track the running max. every pop gives a candidate range [heap min, max], and you stop when one list runs out
3
Design WhatsApp, in one picture. 200M open sockets across 600 chat servers. Now Arjun's phone is offline when Priya's message lands. Where does it wait, and how does it find him later? (One inbox row per device.)
1
39
Replying to @AnanyaGupta____
113 days is serious consistency 🔥 one thing worth adding to revision days: re-solve a problem from ~3 weeks ago without looking. if it comes back in 10 min, it's actually yours
6
Replying to @I_Am_Kajal_Sing
nice pick. you only need the parity of the prefix sum: a subarray is odd exactly when its two prefixes have different parity. count evens and odds as you go (start evens at 1 for the empty prefix) and it's one pass, O(1) space
4
Replying to @badlogicgames
system design was always the round you couldn't pass by pattern-matching. nice to know it holds for models too 😅
8
Replying to @meenia_aman
nice! the bit interviewers love in tic tac toe LLD: check a win in O(1) with row/col/diagonal counters (+1 for X, -1 for O) instead of scanning the board every move
10
Replying to @vaishnavidotdev
a full heap day 🔥 two heaps for the median, a size-k min-heap for kth largest. the "why MIN-heap for the LARGEST" one trips everyone up the first time
13
Replying to @buildwithpb
real codebase rounds are great until the "real codebase" is a 40-file repo you get 45 minutes with and the first 30 go to finding where main() is 😅
22
Replying to @Prathkum
the follow-up is where it gets good: "agent 3 just rewrote agent 1's tests so they pass. what do you do?"
11
Less LeetCode. More job offers. Firecode is 50% off for life until Nov 30. Practice the patterns, and Firecode brings each one back right before you'd forget it, so it's still there on interview day.
1
37
"No resume. No LeetCode. Just the pager." The most honest technical interview anyone's written: the take-home is 3 AM and the test cases are prod 😅
9
Replying to @buildwithpb
Same design, honestly: one long bill in, one short code out. Mom's version has a 100% cache hit rate on "who left the router on" 😂
2
Replying to @buildwithpb
Half agree 😄 Memorized patterns prove nothing. But the moment good interviewers actually score is "it passes 9 cases and fails on empty input, why?" That's a prod bug in miniature. The good rounds were always debugging in disguise; the bad ones were trivia.
8