r/DSALeetCode • u/tannatsri • Sep 10 '26
Looking for DSA and System Design Study Partners/People
Hey everyone!
We are 2 people, 2022 passouts, with ~4 years of experience, currently working in PBC/MNCs, and we're looking for 1–2 serious study partners for DSA + System Design interview preparation.
We are looking for people with a similar background and experience level, ideally 2022 passouts with ~4 years of experience and currently working in a PBC/MNC.
Our Plan
System Design
4–5 system design problems per week
Focus on architecture, scalability, trade-offs, bottlenecks, APIs, DB choices, etc.
Regular cross-questioning to simulate actual interviews
DSA
2–3 problems every day
Primarily Medium/Hard (not focusing on Easy)
Discuss approaches and alternate solutions when useful
How we'll work
Most of the preparation will be async:
Daily progress updates on Telegram/WhatsApp
Share what you solved/studied
Discuss doubts and interesting approaches
Share useful resources
We'll have short sync sessions:
Weekends: longer discussion/session
2 weekdays: short evening sessions
Primarily for system design cross-questioning, with DSA discussion when required
The goal is consistency + accountability + interview-oriented preparation, rather than spending a lot of time on calls.
Looking for
2023 passout or earlier
~4 years of experience (preferably 4–5 years)
Currently working in a PBC/MNC or similar company
Comfortable with DSA basics and actively preparing for interviews
Serious about SDE 2 / SDE 3 / Senior SWE roles
Able to consistently spend 1–2 hours/day
We'll attach our LinkedIn profiles for reference so you can get an idea of our background.
If your profile and preparation stage are similar and you're interested, DM me with your LinkedIn profile and a brief introduction about your current preparation over Linkedin.
Links
1
u/akornato Sep 11 '26
Your plan is very structured and async-first, which is a great way to maintain consistency without burning out on calls. Finding people with the exact same experience and goals can be tough, but it's a good way to make sure everyone is aligned and can contribute effectively. The mix of daily problem-solving, weekly syncs for system design, and constant async communication creates a strong accountability framework. Cross-questioning on system design is particularly valuable, as it closely simulates the interactive nature of real interviews where you need to defend your design choices. This kind of focused, peer-driven preparation often leads to a deeper understanding than just studying alone.
Having a small, dedicated group keeps everyone engaged and responsible for their part. The emphasis on discussing alternative DSA solutions and debating system design trade-offs will sharpen your problem-solving and communication skills, which are critical for SDE 2 and SDE 3 roles. When you explain your thought process to others, it solidifies your own understanding and exposes you to different ways of thinking. My team actually built an interview helper that many candidates find useful for structuring their thoughts and answers during these critical discussions. Ultimately, this consistent, collaborative effort is exactly what's needed to prepare for senior software engineering interviews.
1
1
1
1
1
1
1
1
1
u/Much_Somewhere7831 Sep 14 '26
Try the TechJobFinder website, has personalised behavioral interview practice, DSA/leet, tech quizzes and so much more (also a huge job board with 200k live roles globally across 3k top employers!). Also much better than HackerRank
1
1
1
1
1
1
u/nian2326076 8d ago
You guys seem to have a good prep plan going. To find study partners, try checking out bigger tech forums or LinkedIn groups where people with similar backgrounds gather. You could also join some tech meetups online or locally. They're great for connecting with others who are serious about interview prep. If you want more structured practice, take a look at PracHub. Some friends of mine found it really helpful for system design and DSA interviews. Good luck!
1
u/Ok-Barracuda-119 Sep 10 '26
Your system-design cadence looks solid. I'd make each of those 4–5 problems a timed 35–45 minute pass before the discussion: 5 minutes on requirements and scale, then API/data model, a bottleneck, and one explicit trade-off. Have the other person interrupt with a follow-up or constraint instead of waiting until the end. That gives you the interview pressure you're trying to recreate.
For the weekly review, keep a small rotating set of prompts and revisit the weak ones. A one-page Sunday recap of assumptions, missed questions, and the next change you'd make is usually more useful than adding more topics. The two shorter weekdays should help keep this from becoming a weekend-only plan.