Backend Development Internship Interview Questions for Freshers (with Answers)
By K. Boopathikumar, CEO & Founder · 16 November 2026 · 8 min read
Backend interns are asked how data moves, how it is stored safely and what happens when many users arrive at once. The language matters less than understanding these ideas.
HTTP and APIs
- What happens when you type a URL and press Enter? DNS turns the name into an IP address, the browser opens a connection (with TLS for HTTPS), sends an HTTP request, the server runs code and returns a response that the browser renders.
- What makes an API RESTful? Resources named by URLs, standard methods (GET, POST, PUT, PATCH, DELETE), stateless requests and meaningful status codes.
- What is idempotency? Doing the same request twice has the same effect as once. GET, PUT and DELETE should be idempotent; for payments, an idempotency key stops double charges.
- How do you version an API? Put the version in the path (/v1/) or a header, and keep old versions working until clients move.
Databases
- What is an index? A data structure that lets the database find rows without scanning the whole table. It speeds up reads but slows writes slightly and uses space.
- What does ACID mean? Atomicity (all or nothing), Consistency (rules always hold), Isolation (transactions don't see each other's half-done work) and Durability (saved data survives a crash).
- What is normalisation? Organising tables so each fact is stored once, which avoids update mistakes. Sometimes you denormalise for read speed.
- When would you choose NoSQL? When data shape varies, you need very high write throughput or simple key-based access at scale. Choose SQL when relations and reporting matter.
Security and scale
- Authentication vs authorisation? Authentication checks who you are (login); authorisation checks what you may do (roles and permissions).
- How should passwords be stored? Never in plain text. Hash them with a slow algorithm such as bcrypt or Argon2, with a salt.
- What is caching and where do you use it? Keeping a copy of data that is slow to compute, for example in Redis. Cache read-heavy data and decide how and when it expires.
- Why use a message queue? To move slow work (emails, reports, image processing) out of the request, so users get a fast response and work is retried if it fails.
- What is rate limiting? Capping how many requests a client can make in a time window, to protect the service from abuse and overload.
How to answer well in the interview
- For design questions, start with requirements and data, then the API, then scaling.
- Mention logs and monitoring; real backends are judged by how fast problems are found.
- Use one project to show auth, validation and error handling done properly.
- Say the trade-off whenever you choose something, such as SQL or NoSQL.
Next steps
- Study the free Backend Development learning path and take its module quizzes for a free certificate.
- Follow the Backend Development skill track from basic to advanced.
- Do real, reviewed work in a Backend Development internship and keep every project in your own GitHub.