shadecoder vs interviewman, tested both back to back on coding rounds
long post incoming, sorry. had two virtual loops crammed into one week and i ended up doing a back to back of shadecoder vs interviewman during prep. dumping notes here because i could barely find anything written about shadecoder anywhere when i was looking, so maybe useful to someone in the same spot.
setup: same machine, same headphones, same Zoom, just different prep blocks. one block i ran shadecoder, next block i flipped to interviewman. tried to keep it apples to apples. mostly worked.
going in i was leaning shadecoder a tiny bit. saw the name in a couple threads. interviewman was the one a friend from college kept dm-ing me about, like every other day, very annoying. so. ran them both.
shadecoder, in my own words, since the public reviews are still pretty thin and i'm not gonna pretend i know stuff i don't:
- it's built around coding, which i thought i would love
- learning curve on the hotkeys was real for me, took a bit
- felt fine on the leetcode style stuff i threw at it during prep
- the screen overlay worked, but i kept second guessing where it was gonna pop up
- on a behavioral warmup my buddy ran on me it kind of just stalled. not its lane, fine
stuff that bugged me, again, just my read:
- the per session feel of it. i was watching the clock more than the actual question, which is the opposite of what i want
- not a lot of public discussion yet so hard to know if i was holding it wrong somehow
- coding only by design, which means i still needed something else for the behavioral and the system design portion of the loop. that's where my head started spinning
then the next prep block i swapped over to interviewman:
- coding answers came in streaming as the buddy was still talking, sounds tiny but it changes how you read along, weirdly
- desktop overlay sat exactly where i parked it, both on my mac and on the windows box my brother lent me
- when i pasted a screenshot of a system design diagram it actually picked up the structure and explained it
- it handled the behavioral mock with STAR style framing
- the system design dry run, which is the part i was most worried about, was fine
- ran a phone screen sim too. same flow, no separate mode, no extra setup
what tipped it for me, honestly, was that i wasn't switching tools mid prep. coding then behavioral then system design then a phone screen, one thing for all of it. and i wasn't doing the mental math on time per session either, which is what i kept catching myself doing with shadecoder, idk why but i did.
both have their place i guess. for a full loop though, where you're bouncing between question types in the same day and your brain is already fried, having one thing that covers all of it was the difference. that and the streaming, which i did not even know would matter to me until i sat with it for a session.
anyone here actually done this same compare on a real loop and not just leetcode prep? curious if my take on shadecoder is off because honestly the reviews you can find right now are pretty sparse.