CS Fundamentals Guide | Resources by Shumbul Arifa

🧠 CS Fundamentals

The core computer science every fresher interview digs into: Operating Systems, Databases, Networks, and OOP. You do not need a whole semester, you need the right topics, explained simply.

🎯 Interview-focused 📚 4 core subjects 🌱 Plain-English

How to use this guide

Do not try to master everything. For each subject below you get: why it matters, the focus topics (the ones that actually get asked), and a few sample questions with short answers so you know the depth expected. Read actively: after each topic, try to explain it out loud in one or two sentences. If you can teach it, you know it.

Operating Systems (OS)

Why it matters: interviewers test whether you understand how programs really run, share resources, and avoid stepping on each other.

Focus on these topics:

Process vs thread
CPU scheduling (FCFS, SJF, Round Robin)
Deadlock (4 conditions, prevention)
Process synchronization, mutex vs semaphore
Virtual memory & paging
Context switching

Q: Difference between a process and a thread?

A process is an independent running program with its own memory; a thread is a lighter unit inside a process that shares that memory. Threads are cheaper to create and communicate, but a crash in one can affect others in the same process.

Q: What is a deadlock and how do you prevent it?

A deadlock is when processes wait on each other forever. It needs four conditions at once (mutual exclusion, hold-and-wait, no preemption, circular wait). Break any one, for example by acquiring locks in a fixed order, and you prevent it.

📚 Want the full theory with analogies and quizzes? See the Operating Systems Deep Dive.

Databases (DBMS)

Why it matters: almost every app stores data, so interviewers check that you can model it, query it, and keep it consistent.

Focus on these topics:

SQL queries & joins
Normalization (1NF, 2NF, 3NF)
Keys (primary, foreign, candidate)
ACID properties & transactions
Indexing (why it speeds reads)
SQL vs NoSQL, when to use each

Q: What is normalization and why do it?

Normalization organizes tables to reduce duplicate data and avoid update anomalies. You split data into related tables (up to 3NF for most apps) so each fact lives in exactly one place, keeping data consistent.

Q: Explain ACID.

Atomicity (all or nothing), Consistency (valid state to valid state), Isolation (transactions do not corrupt each other), Durability (once committed, it stays). Together they keep transactions reliable, like a bank transfer never losing money midway.

Want hands-on SQL practice? See the SQL & Databases guide. For the full theory with quizzes, see the DBMS Deep Dive.

Computer Networks (CN)

Why it matters: every web app talks over a network, so interviewers check you understand what happens when you type a URL and hit enter.

Focus on these topics:

OSI & TCP/IP models
TCP vs UDP
HTTP / HTTPS & status codes
DNS (how names become IPs)
What happens when you visit a URL
IP addressing basics

Q: TCP vs UDP?

TCP is reliable and ordered, it confirms delivery (used for web pages, email). UDP is fast but does not guarantee delivery or order (used for live video, games, calls) where speed beats perfection.

Q: What happens when you type a URL and press enter?

The browser resolves the domain to an IP via DNS, opens a TCP connection (and a TLS handshake for HTTPS), sends an HTTP request, the server responds with HTML, and the browser renders it, fetching CSS, JS, and images as needed.

📚 Full theory with quizzes: the Computer Networks Deep Dive. See it live with the Networking Toolkit.

Object-Oriented Programming (OOP)

Why it matters: most codebases are object-oriented, so interviewers check you can design clean, reusable code, not just make it work.

Focus on these topics:

The 4 pillars (below)
Class vs object
Overloading vs overriding
Abstract class vs interface
Composition vs inheritance
SOLID principles (at a high level)

Q: What are the four pillars of OOP?

Encapsulation (bundle data with the methods that use it, hide internals), Abstraction (expose what, hide how), Inheritance (reuse via parent-child classes), and Polymorphism (one interface, many behaviors, e.g. overriding a method).

Q: Overloading vs overriding?

Overloading = same method name, different parameters, in the same class (compile-time). Overriding = a subclass redefines a parent method with the same signature (run-time). Overload for convenience, override for polymorphism.

📚 Full theory with quizzes: the OOP Deep Dive.

What to prioritize

Short on time? Here is a rough priority order based on how often each shows up in fresher interviews.

SubjectInterview frequencyMust-know topics
OOPVery high4 pillars, overloading vs overriding, abstract vs interface
DBMSVery highJoins, normalization, ACID, indexing
OSHighProcess vs thread, deadlock, scheduling, synchronization
NetworksMedium to highTCP vs UDP, HTTP, DNS, URL walkthrough

Free places to learn

What to do next

Pair these fundamentals with problem-solving and interview practice:

🌱 Why this guide exists

Many freshers grind DSA but freeze when asked "what is a deadlock?" or "explain normalization." These core subjects come up in almost every entry-level interview, especially at service companies and product firms alike. This guide gives you the high-value topics per subject, plus the questions that actually get asked. Want a topic explained your way? Tap ✦ Ask AI.