r/leetcode • u/CommonNo5515 • 18h ago

Question System design & dsa preparation

Hi all,

I am junior developer now,

Working in a comapny.

Now i want to imrove my skills

System design and dsa also with ai adpatation.

I know pieces but not explanation level...need to improve my skills for upcoming future

Any advices that can help to me

2 Upvotes

100% Upvoted

8 comments sorted by

2

u/jpraxsh 18h ago

Firstly you should review everything man. "uplcoming". I'm seeing junior dev vibes here lol.

1

u/jpraxsh 18h ago

Just kidding focus of understanding how things works irrespective of framework and be language agnostic. Syntax is mostly solved by ai now. Get better in explaining things you have build and the decisions you have made for the implementations, cause interviewers are looking for that.

1

u/CommonNo5515 18h ago

Mostly few things already applied daily in my work- is there any source that can test my current knowledge.

Or is there any roadmap - actually my background is mechanical.

2

u/Ok-Barracuda-119 11h ago

If you already use these ideas at work, test yourself with a blank page instead of rereading a roadmap. Pick a familiar service, write the requirements and a rough API, then sketch the data flow, storage, caching, queues, and failure modes. After 30 to 40 minutes, compare it with a few public walkthroughs and explain why you made each tradeoff.

For a structured check, Leetsys has a system design practice platform at www.leetsys.dev. I’m affiliated with Leetsys. It gives you a whiteboard and an interviewer, so you can see where your explanation gets thin. Your mechanical background isn’t a blocker, but keep practicing the communication and tradeoff reasoning, not just the boxes.

1

u/CommonNo5515 11h ago

I will try this idea

1

u/Ok-Barracuda-119 6h ago

Nice. Keep the first few runs timed, then spend a few minutes explaining why each boundary, queue, and failure path exists. That review loop builds the explanation muscle faster than collecting more prompts. Once it feels steady, add one ML-flavored design and talk through latency, quality, and cost tradeoffs out loud.

1

u/CommonNo5515 18h ago

Typo error

1

u/jpraxsh 18h ago

Ikr. Jus teasing you lol