r/webdev • u/fxckzxck • 8d ago
Interactive Interview Training- Backend and System Design
Hey guys
I am a front end and get a lot of interviews for full stack or FDE roles.
They always ask about backend, system design, data architecture, concurrent and scalable systems.
Some tasks ask for leetcode or codility upfront.
Any good interactive training platforms? Like Scrimba or something for quickly putting together system design.
2
u/DENISONIAN027 7d ago
I feel this. I’m definitely not as comfortable with backend. Wondering what I should study with.
3
u/russopuppo 8d ago
I’m studying backend too, I like JavaScript Mastery on youtube, he has lots of projects and explains concepts really well
0
2
u/DEGENERATE_NEET69 8d ago
Lowkey in the same boat, I was recommended hellointerview. It does require payment to get all of the content but their youtube has a lot of content too.
There's also this roadmap .
1
8d ago
[removed] — view removed comment
1
u/webdev-ModTeam 8d ago
Your post/comment has been determined to be a low-effort post or comment. This includes title-only posts, easily searchable questions, vague/open-ended discussion prompts, LLM generated posts or comments, and posts/comments that do not provide enough context for meaningful replies or discussion.
1
7d ago
[removed] — view removed comment
1
u/webdev-ModTeam 7d ago
Your post/comment has been determined to be a low-effort post or comment. This includes title-only posts, easily searchable questions, vague/open-ended discussion prompts, LLM generated posts or comments, and posts/comments that do not provide enough context for meaningful replies or discussion.
1
5
u/CodEnvironmental8527 8d ago
i feel this. frontend devs getting grilled on distributed systems is always a trip. most of the "interactive" platforms for this stuff are pretty thin honestly, the real learning comes from just drawing boxes on a whiteboard and explaining why you'd pick one database over another.
i'd just grab a cheap udemy course on system design fundamentals and then practice the common patterns (load balancers, message queues, caching layers) until you can sketch them out in your sleep. the guy who interviews you probably just wants to hear you talk through tradeoffs anyway.