Junior Software Engineer Interview Guide: Essential Questions, Answers and Definitions
- Andrian
- May 27
- 9 min read
Are you preparing for your first software engineering interview? Whether you're fresh out of college or transitioning into tech, this guide covers everything: the most commonly asked questions, clear answers, and all the key definitions interviewers love to test.
PART 1: CORE COMPUTER SCIENCE CONCEPTS
1. What is an algorithm?
An algorithm is a step-by-step set of instructions used to solve a problem or perform a computation. It has a defined input and output, is unambiguous, and terminates in a finite number of steps.
Example: A sorting algorithm takes an unsorted list as input and returns a sorted list.
Definition — Algorithm: A finite sequence of well-defined instructions used to solve a class of problems.
2. What is a data structure?
A data structure is a way of organizing, storing, and managing data so it can be accessed and modified efficiently.
Array: An ordered collection of elements accessible by index.
Linked List: Nodes where each points to the next.
Stack: Last In First Out (LIFO).
Queue: First In First Out (FIFO).
Hash Table: Key-value pairs for fast lookup.
Tree: A hierarchical structure with a root and child nodes.
Graph: Nodes (vertices) connected by edges.
3. What is Big O Notation?
Big O notation describes the performance or complexity of an algorithm — specifically how runtime or space requirements grow as input size increases.
O(1) — Constant: Always takes the same time regardless of input.
O(log n) — Logarithmic: Halves the problem each step (e.g. binary search).
O(n) — Linear: Grows proportionally with input size.
O(n log n) — Log-linear: Typical of efficient sorting algorithms (e.g. merge sort).
O(n²) — Quadratic: Common in nested loops.
O(2ⁿ) — Exponential: Very slow, typical of brute-force recursion.
4. What is Object-Oriented Programming (OOP)?
OOP is a programming paradigm based on objects that combine data (attributes) and behavior (methods). The four pillars are:
Encapsulation: Hiding internal state; all interaction happens through defined methods.
Abstraction: Exposing only relevant information and hiding complexity.
Inheritance: A class can inherit properties and methods from another class.
Polymorphism: The same interface can be used for different types (e.g. method overriding).
5. What is the difference between a class and an object?
A class is a blueprint or template that defines properties and behaviors. An object is an instance of that class — a concrete realization of the blueprint.
Example: Car is a class. Your specific red Toyota Corolla is an object.
6. What is recursion?
Recursion is when a function calls itself as part of its own definition. Every recursive function needs a base case (to stop) and a recursive case (which moves toward the base case).
Example: Factorial of n = n × (n-1)!
Definition — Stack Overflow: When recursion goes too deep and exceeds the call stack memory limit.
Definition — Call Stack: A data structure that records active function calls; each call adds a frame, each return removes one.
7. What is the difference between compiled and interpreted languages?
Compiled (C, C++, Go): Source code is translated entirely to machine code before execution. Faster at runtime.
Interpreted (Python, JavaScript): Code is executed line-by-line at runtime. More flexible and easier to debug.
Hybrid (Java, C#): Compiled to bytecode, then run on a virtual machine (JVM / .NET).
8. What is garbage collection?
Garbage collection is an automatic memory management process where the runtime identifies and frees memory that is no longer in use — preventing memory leaks. Languages like Java, Python, and JavaScript use garbage collectors.
Definition — Memory Leak: When a program fails to release memory it no longer needs, causing memory usage to grow over time.
PART 2: VERSION CONTROL AND GIT
9. What is Git?
Git is a distributed version control system where every developer has a full copy of the repository history. It enables collaboration, tracks changes, and allows rolling back to any previous state.
Key commands: git init, git clone, git add, git commit, git push, git pull, git branch, git merge, git rebase.
10. What is the difference between git merge and git rebase?
Merge: Combines two branches and preserves the full history with a merge commit.
Rebase: Moves or replays commits from one branch onto another, creating a cleaner, linear history.
11. What is a pull request (PR)?
A pull request is a request to merge code from one branch into another. It triggers code review, discussion, and automated tests before the merge is accepted.
Definition — Branch: An independent line of development (default is usually 'main' or 'master').
Definition — Commit: A snapshot of changes saved to the repository.
Definition — Merge Conflict: When two branches change the same part of a file differently; must be resolved manually.
PART 3: WEB DEVELOPMENT FUNDAMENTALS
12. What is the difference between HTML, CSS, and JavaScript?
HTML: Defines the structure and content of a web page.
CSS: Controls the visual presentation — layout, colors, fonts.
JavaScript: Adds interactivity and dynamic behavior to the page.
13. What is the DOM?
The Document Object Model (DOM) is a programming interface for HTML documents. It represents the page as a tree of nodes that JavaScript can manipulate to dynamically change content, structure, and style.
14. What is the difference between GET and POST HTTP methods?
GET: Retrieves data from a server; parameters are in the URL; should have no side effects.
POST: Sends data to the server in the request body, typically to create or update a resource.
Other HTTP methods: PUT (replace resource), PATCH (partial update), DELETE (remove resource).
15. What is REST?
REST (Representational State Transfer) is an architectural style for designing networked APIs. RESTful APIs use HTTP methods and treat everything as a resource identified by a URL.
Key principles: Statelessness, client-server separation, uniform interface, cacheability.
16. What is JSON?
JSON (JavaScript Object Notation) is a lightweight, human-readable data interchange format. It uses key-value pairs and arrays. Example: { "name": "Alice", "age": 25, "skills": ["JavaScript", "Python"] }
17. What is an API?
An API (Application Programming Interface) is a set of rules that allows one software application to communicate with another. It defines the requests you can make, the data formats, and the conventions to follow.
PART 4: DATABASES
18. What is the difference between SQL and NoSQL?
SQL (Relational): Data stored in tables with predefined schemas. Uses structured query language. Examples: MySQL, PostgreSQL, SQLite.
NoSQL (Non-relational): Flexible schemas. Types: document (MongoDB), key-value (Redis), column-family (Cassandra), graph (Neo4j).
Use SQL when data is structured and relationships matter. Use NoSQL for flexibility, unstructured data, or massive scale.
19. What is a primary key?
A primary key uniquely identifies each record in a table. It must be unique and cannot be NULL.
20. What is a foreign key?
A foreign key is a field in one table that references the primary key of another table, establishing a relationship between them.
21. What is normalization?
Normalization organizes a database to reduce redundancy and improve data integrity by dividing large tables into smaller, related ones.
1NF: Eliminate repeating groups.
2NF: Eliminate partial dependencies.
3NF: Eliminate transitive dependencies.
22. What is an index?
An index is a data structure that speeds up data retrieval at the cost of additional storage and slightly slower writes. Think of it like a book index — instead of scanning every page, you jump directly to the right one.
PART 5: PROGRAMMING CONCEPTS AND PATTERNS
23. What is the difference between synchronous and asynchronous programming?
Synchronous: Code executes line-by-line; each operation blocks until it completes.
Asynchronous: Operations can run in the background; the program continues without waiting. Used heavily in I/O, network requests, and event-driven systems.
24. What is a callback function?
A callback is a function passed as an argument to another function, to be executed later — typically after an asynchronous operation completes.
25. What is a Promise?
A Promise is an object that represents the eventual completion or failure of an asynchronous operation. It has three states: pending, fulfilled, and rejected.
26. What are SOLID principles?
S — Single Responsibility: A class should have only one reason to change.
O — Open/Closed: Open for extension, closed for modification.
L — Liskov Substitution: Subclasses should be substitutable for their parent class.
I — Interface Segregation: Don't force classes to implement interfaces they don't use.
D — Dependency Inversion: Depend on abstractions, not concrete implementations.
27. What is a design pattern?
A design pattern is a reusable solution to a commonly occurring problem in software design.
Singleton: Only one instance of a class exists.
Factory: Create objects without specifying the exact class.
Observer: Notify multiple objects when state changes.
MVC (Model-View-Controller): Separates data, UI, and business logic.
PART 6: TESTING
28. What is unit testing?
Unit testing tests individual functions or components in isolation to verify they work correctly.
29. What is the difference between unit, integration, and end-to-end testing?
Unit: Tests a single function in isolation.
Integration: Tests how multiple components work together.
End-to-End (E2E): Simulates a real user flow through the entire application (e.g. Cypress, Selenium).
30. What is TDD?
Test-Driven Development (TDD) is a practice where you write tests before writing the code. The cycle: Red (test fails) → Green (write code to pass) → Refactor (improve the code).
Definition — Mock/Stub: A fake object used in testing to simulate behavior of real dependencies without actually calling them.
PART 7: BEHAVIORAL AND SITUATIONAL QUESTIONS
31. Tell me about yourself.
Keep it concise and relevant: your background, what you've built, why you're excited about software engineering, and what you're looking for. Aim for 60–90 seconds.
32. What is your biggest weakness?
Be honest and growth-oriented. Name a real weakness and immediately follow with what you're actively doing to improve it. Avoid clichés like 'I work too hard.'
33. Describe a challenging project you worked on.
Use the STAR method: Situation (context), Task (your responsibility), Action (what you did), Result (outcome). Focus on your personal contribution and what you learned.
34. How do you handle a bug you can't figure out?
Show a methodical approach: reproduce it reliably, isolate the problem, check documentation and Stack Overflow, use a debugger or add logging, and ask a colleague if still stuck. Show you don't panic.
35. How do you stay current with technology?
Mention dev blogs, podcasts, GitHub trending, documentation, side projects, online courses, and communities like dev.to, Hacker News, or Discord servers.
PART 8: ESSENTIAL DEFINITIONS GLOSSARY
IDE (Integrated Development Environment): Software for writing, testing, and debugging code (e.g. VS Code, IntelliJ).
CLI (Command Line Interface): A text-based interface to interact with a computer.
Framework: A pre-built structure for building applications (e.g. React, Django, Spring).
Library: A collection of reusable functions/modules (e.g. Lodash, NumPy).
Dependency: External code a project relies on.
Package Manager: A tool to install and manage dependencies (npm, pip, Maven).
Container: A lightweight, standalone executable package of software (e.g. Docker).
CI/CD: Automating the build, test, and deployment pipeline.
Agile: An iterative development methodology focused on collaboration and adaptability.
Scrum: An Agile framework using time-boxed sprints, daily standups, and retrospectives.
MVP (Minimum Viable Product): The simplest version of a product that can be released to gather feedback.
Refactoring: Improving code structure without changing its external behavior.
Technical Debt: The cost of shortcuts taken during development that must be fixed later.
Deployment: The process of releasing code to a production environment.
Latency: The delay between a request and its response.
Throughput: The number of requests a system can handle per unit of time.
Scalability: A system's ability to handle increased load by adding resources.
Load Balancer: Distributes incoming traffic across multiple servers.
Cache: Temporary storage of frequently accessed data for faster retrieval.
Authentication: Verifying who someone is (login).
Authorization: Verifying what someone is allowed to do (permissions).
Encryption: Transforming data into an unreadable format to protect it (e.g. AES, RSA).
Hashing: A one-way function that maps data to a fixed-size value (e.g. bcrypt for passwords).
SSL/TLS: Protocols for encrypting data in transit (HTTPS).
Race Condition: A bug where behavior depends on the relative timing of concurrent events.
Deadlock: Two or more processes waiting on each other indefinitely, resulting in a standstill.
ORM (Object-Relational Mapping): Interacting with databases using object-oriented code (e.g. Hibernate, Sequelize).
Middleware: Software that acts as a bridge in a request/response cycle.
Webhook: An HTTP callback triggered by a specific event in one system to notify another.
Environment Variable: A variable set outside code to configure application behavior (e.g. API keys).
Repository: A central location where code is stored and managed.
Open Source: Software with freely available source code.
Microservices: An architecture where an app is split into small, independent services.
Monolith: A single, unified application where all components are interconnected.
Thread: The smallest unit of execution within a process.
Concurrency: Multiple tasks making progress at the same time (not necessarily simultaneously).
Parallelism: Multiple tasks literally running at the same time on multiple CPU cores.
Singleton Pattern: A design pattern ensuring only one instance of a class exists.
FINAL TIPS FOR YOUR INTERVIEW
1. Practice coding without your IDE — whiteboard or shared online editors feel very different.
2. Think out loud — interviewers care as much about your thought process as the final answer.
3. Ask clarifying questions before solving — it shows you think like a professional engineer.
4. Know your resume deeply — be ready to go into detail on anything you listed.
5. Prepare questions for the interviewer — ask about the tech stack, code review process, or team structure.
6. Stay calm on hard questions — acknowledge what you don't know, then reason through it logically.
Good luck — you've got this! 🚀
Comments