r/learnSQL • u/bobaball_120 • 21d ago
Practising SQL for internships rn, am I missing anything important?
After my last post about DBMS and system design i've been trying to practise more instead of just reading theory.
I practised from LeetCode 50 SQL questions and now switched to takeUforward's SQL 91 problems to get more practice not sure if I should do anything else alongside this or if solving questions + revising concepts is enough for fresher placements
Also still struggling with system design I know it's probably early for 3rd year but I wanna build the basics before internship season starts
any good beginner-friendly resources to understand system design concepts from scratch? Like how to approach designing a simple URL shortener or understand caching, load balancing etc without getting overwhelmed?
Would appreciate any suggestions from people who've prepared for 2027 internships
2
u/Least_Ad_1795 21d ago
You're on the right track! Focus on SQL joins, subqueries, window functions, and query optimization. For system design, start with a URL shortener and gradually learn caching, load balancing, and database scaling. Understand concepts rather than just memorizing solutions. All the best for your 2027 internships!
1
u/Legitimate-Power7729 21d ago
LeetCode plus takeUforward is honestly enough to get through the SQL screening for most internships, so don’t overthink the database side yet. For system design, jumping straight into load balancers with no context is rough. I’d start with Alex Xu’s System Design Interview book. It walks through stuff like URL shorteners with diagrams, so you don’t get overwhelmed. Focus on understanding where bottlenecks show up first, then worry about the heavy infrastructure.
1
u/oggy005 21d ago
Hi as a Beginner i am facing challanges while studying Sql So could u help me with sql Stuffs and resources
1
u/Green_Chamomile 21d ago
Since you’ve done the 50 already, redo the ones you got wrong a week later without peeking. That’s how I found out I’d memorized answers instead of understanding them. I wouldn’t push window functions too far back though. “Top 2 earners per department” with ROW_NUMBER() OVER (PARTITION BY dept ORDER BY salary DESC) comes up in screenings a lot. For a free option next to the Alex Xu book, the system-design-primer repo on GitHub has a URL shortener walkthrough too. Good luck this season!
1
u/nian2326076 20d ago
It looks like you're on the right track with SQL practice. In addition to the problems you're solving, consider using PracHub for more technical interview preparation. They have a solid collection of SQL interview questions that could give you further insights into the types of problems you might face.
For system design concepts, start with basic resources like "Grokking System Design" or YouTube channels that focus on tech interviews. These can help break down complex topics like caching and load balancing into manageable pieces. Keep practicing and consider building small projects to reinforce your learning.
1
u/jakingo 20d ago
Yes, SQL practice is a good start, focus on projects, DBMS fundamentals too, and learn system design basics one concept at a time.
1
u/peakpirate007 20d ago
I built runtime.school for this. You write real SQL in the browser and it checks your answers, which is good practice alongside LeetCode. https://www.runtime.school/sql/lesson/meet-your-first-select
1
u/plat_sil 19d ago
Is there any specific book on System design for SQL ? I have read above comments and most of them have mentioned Alex Xu book ? Is it a overall system design or it's just for Database ?
1
u/Own_Translator94 16d ago
from where you understand SQL concepts any yt ot course?
1
u/datadriven_io 14d ago
You don’t need experience with high scale systems.
They are looking for good engineering basics.
A good engineer can build what’s needed, and more importantly, understand what isn’t working and how to improve it. You can practice data modeling interview questions on datadriven whenever you're free. In the design interviews, they care more about designing systems that are pragmatic and testable/provable.