SRM Students: Full Stack Web Development Internship Interview Questions to Practise

The best way to prepare for a full stack web development internship interview is to practise out loud across four areas: frontend, backend, database and system basics. Score each answer against a fixed rubric so you can see which area is weakest. This guide gives you 40 questions, a 0 to 4 scoring scale, a worked example and a two-week practice plan.

How to use this question set

Internship interviews for full stack roles are usually short, often 20 to 40 minutes. Interviewers rarely expect production experience from a student. They want to see whether you understand how a request travels from a browser to a server and a database and back, and whether you can explain your own project code without bluffing.

This guide is an independent resource for students of SRM Institute of Science and Technology. It is not issued by, endorsed by or connected with the institution. Question formats differ between companies, so treat the set below as practice material, not a prediction of any specific interview.

Work through it in this order:

1. Read a question and answer it aloud in 60 to 90 seconds without notes.
2. Write down what you said, or record it on your phone.
3. Score it using the rubric in the next section.
4. Look up the gaps, then re-answer the question two days later.

The scoring rubric

Use the same 0 to 4 scale for every question. It rewards accuracy and clear reasoning rather than memorised definitions.

Each section has 10 questions, so each section is scored out of 40. Add the four sections for a total out of 160.

Section 1: Frontend questions

Frontend questions test the browser fundamentals first and your framework second. If you use React, Angular or Vue, expect questions on both.

1. What happens, step by step, between typing a URL and seeing a rendered page?
2. Explain the CSS box model. What does box-sizing: border-box change?
3. What is the difference between flexbox and grid? When would you pick each?
4. Explain var, let and const, including scope and hoisting.
5. What is a closure in JavaScript? Give a practical use.
6. How do promises and async/await relate? How do you handle a failed fetch call?
7. What is event delegation, and why is it useful for long lists?
8. In your framework of choice, how does state differ from props? What causes a re-render?
9. How would you make a page accessible to a keyboard-only user? Name at least three practices.
10. A page loads slowly on a mobile connection. List what you would check first.

What a strong frontend answer includes

• Question 1: DNS lookup, TCP/TLS connection, HTTP request, HTML parsing, building the DOM and CSSOM, then layout and paint.
• Question 6: the idea that fetch does not reject on HTTP 4xx or 5xx status codes, so you check response.ok.
• Question 9: semantic HTML elements, visible focus styles, labels tied to inputs, meaningful alt text.
• Question 10: image size and format, bundle size, unused JavaScript, caching, and render-blocking resources.

Section 2: Backend questions

Backend questions look for an understanding of HTTP, structure and security. Use the language you actually built with, such as Node.js with Express, Java Spring or Python Django or Flask.

1. Name the main HTTP methods. Which are idempotent, and why does it matter?
2. What do status codes 200, 201, 400, 401, 403, 404 and 500 mean? Give one case for each.
3. Explain the difference between authentication and authorisation.
4. How does token-based authentication (for example JWT) differ from session cookies? What are the risks of each?
5. How should you store user passwords? Explain why plain hashing alone is not enough without salting and a slow algorithm.
6. What is middleware? Describe one you have written or used.
7. How would you design a REST API for a to-do app? List routes and methods.
8. What is CORS, and why does the browser enforce it?
9. How do you validate input on the server even when the frontend already validates it?
10. What is the difference between synchronous and asynchronous handling on a server? Why does blocking code hurt a Node.js server?

What a strong backend answer includes

• Question 1: GET, PUT and DELETE are idempotent; POST usually is not. Retried requests must not create duplicates.
• Question 5: bcrypt, scrypt or Argon2 with per-user salts, and never storing or logging raw passwords.
• Question 8: it is a browser rule about cross-origin reads, controlled by response headers from the server. It does not protect the server from other clients.
• Question 9: reject unexpected types, lengths and formats; use parameterised queries; never trust client data.

Section 3: Database questions

Most student projects use either MySQL or PostgreSQL, or MongoDB. Be ready to defend the choice you made.

1. What is the difference between SQL and NoSQL databases? Why did you pick one for your project?
2. Explain primary key, foreign key and unique constraint.
3. Describe the types of JOIN. When would a LEFT JOIN return a NULL?
4. What is normalisation? Take a table with repeated customer details in every order row and fix it.
5. What is an index? What does it speed up, and what does it cost?
6. What does ACID stand for? Give an example where a transaction is necessary.
7. What is SQL injection, and how do parameterised queries prevent it?
8. Write a query to find the second highest salary in an employees table.
9. In MongoDB, when would you embed documents and when would you reference them?
10. Your query is slow on a table with a million rows. How do you investigate it?

What a strong database answer includes

• Question 5: faster reads on indexed columns, slower writes and extra storage.
• Question 6: a money transfer where debit and credit must both succeed or both roll back.
• Question 10: read the query plan (EXPLAIN), check for missing indexes, and avoid selecting more columns or rows than needed.

Section 4: System basics questions

System questions show whether you can zoom out. At internship level they are conversational, not whiteboard architecture drills.

1. Explain client-server architecture using an app you have built.
2. What is the difference between HTTP and HTTPS? What does TLS provide?
3. What is Git branching? How do you resolve a merge conflict?
4. What are environment variables, and why should secrets never be committed to a repository?
5. What is caching? Name two places in a web app where it can happen.
6. Explain horizontal and vertical scaling in plain language.
7. What is the difference between a monolith and microservices? Why might a small team avoid microservices?
8. How would you deploy a simple full stack app so others can use it? Name the pieces you would need.
9. What kinds of tests would you write for a login feature?
10. Describe a bug you debugged. How did you find the cause?

What a strong system answer includes

• Question 4: a .env file excluded through .gitignore, and rotating any key that leaks.
• Question 7: honest trade-offs, since microservices add network failures, deployment overhead and debugging cost.
• Question 10: a specific story, with the symptom, your hypothesis, the check you ran and the fix.

Worked example: full stack internship interview questions (illustrative)

The following is an illustrative answer and scoring exercise, not a record of a real interview.

Question: “How does your login feature keep user passwords safe?”

Weak answer (score 1): “We use JWT and the password is encrypted in the database.”

This names a term and uses the wrong word. Encryption is reversible; stored passwords should be hashed. The answer also mixes up tokens with password storage.

Better answer (score 4):

“On registration, the server receives the password over HTTPS, hashes it with bcrypt using a per-user salt and a cost factor, and stores only the hash. On login, I compare the submitted password to the stored hash using bcrypt’s compare function. If it matches, the server issues a short-lived JWT. A limitation in my project is that I did not add rate limiting, so someone could try many passwords. With more time I would add that and account lockout.”

A sketch of the registration code you might describe is below, labelled illustrative and not executed here:

// Illustrative sketch only
app.post("/register", async (req, res) => {
  const { email, password } = req.body;
  if (!email || password.length < 8) {
    return res.status(400).json({ error: "Invalid input" });
  }
  const hash = await bcrypt.hash(password, 12);
  await db.query(
    "INSERT INTO users (email, password_hash) VALUES ($1, $2)",
    [email, hash]
  );
  res.status(201).json({ message: "Registered" });
});

Notice what earns the 4: the order of events, the correct terminology, a parameterised query, a status code choice and an honest limitation. Interviewers often respond well to a candidate who names their own gaps.

Likely follow-ups to practise

• Why 12 for the cost factor? What happens if it is too low or too high?
• Where do you store the JWT on the client, and what are the risks?
• How would a “forgot password” flow work safely?

Project walkthrough scorecard

Almost every internship interview includes “tell me about a project you built”. Score yours with this table, using 0 to 4 per row.

A total of 20 or more out of 24 means your walkthrough is in good shape. Below 12, rewrite your explanation before attempting a mock interview.

A two-week practice plan

Mistakes that cost marks

• Memorising definitions. Follow-up questions expose this quickly. Always attach an example.
• Listing technologies you barely used. If your resume says Docker, expect a Docker question.
• Silence instead of reasoning. Say what you do know, state your assumption and work forward.
• Claiming team work as your own. Be exact about your part.
• Skipping error handling. Mention what happens when the network fails or input is invalid.

Getting hands-on practice

If you need a structured way to build something you can talk about, the free two-week online internship at CareerSwami offers 26 tracks, including a free offer letter and a free completion certificate after successful completion. Whatever you choose, what matters in an interview is what you built and can explain.

SRM and the Full Stack interview prep: what the regulations say about internships

Students preparing for full stack internship interviews at SRM Institute of Science and Technology should know that the university’s internship rules sit in programme-level regulations, not in one university-wide policy. The B.Tech/M.Tech (Integrated) Regulations 2021 describe SRMIST as a deemed university based at Kattankulathur and were approved by the Academic Council in March 2022. The institute also runs several campuses, so check which document applies to your campus and batch.

Under Regulation R 2.7, a Semester Internship can be done in industry, a research centre or specialised labs for 12 to 15 weeks in the eighth semester. The department’s Project Review Committee or Panel must approve it, and the student needs a faculty mentor, periodic reviews and a report assessed by examiners appointed by the head of department. A short external web development internship is therefore different from this credit-bearing route. The same regulation bars students continuing to M.Tech (Integrated) from taking the Semester Internship.

The Regulations 2021 B.Tech CSE curriculum lists 21CSP403L Internship (5 credits) as an eighth-semester alternative to the Major Project courses. The regulations passages reviewed do not mention online internships, so do not assume a short online internship counts for credit.

For interview preparation, the practical link is your own coursework: web technologies, databases, operating systems and networks feed the four question sections above, and project work you can explain in detail is useful in a project walkthrough. The Career Centre page describes a Placement Office and a Career Development Centre, which are the places to ask about documentation. These rules are from 2021 documents, so confirm the current version for your batch.

Checks before a full stack internship goes on your SRM record

• Find the regulations for your batch and read Regulation R 2.7 and the internship or project-work rows of your curriculum.
• Ask your department’s Project Review Committee or faculty mentor whether a short external internship can count, or whether only the eighth-semester route does.
• Ask whether an online internship is permitted, since the 2021 passages reviewed do not address it.
• Ask the Career Centre which documents (offer letter, completion certificate) it expects, as these were not verified.
• Confirm in an email, quoting your register number, campus, programme and internship dates, and keep the reply.

Frequently Asked Questions

How many questions should I practise before a full stack internship interview?

Forty well-reviewed questions are better than 200 skimmed ones. Aim to score at least 28 out of 40 in each section, and re-answer your weakest ten questions a few days later.

Should I focus on frontend or backend?

Prepare both, but go deeper on the side your project used. Interviewers usually probe the area on your resume, then test whether you understand the other side well enough to work with it.

Do I need to know data structures and algorithms for a web internship?

Some companies include one or two basic problems, such as arrays, strings or hash maps. Others focus on projects. Check the posting or ask the recruiter what the rounds are.

What if I do not know the answer to a question?

Say so, then reason aloud from related knowledge. For example, if you have not used GraphQL, compare what you would expect to REST. Honest reasoning scores better than a confident wrong answer.

Is it fine to use a framework without knowing plain JavaScript?

It is risky. Questions on closures, promises, scope and the event loop are common, and framework behaviour is built on them. Spend a few days on core JavaScript first.

How should I explain a group project?

Describe the whole system briefly, then specify the modules you wrote and one decision you made yourself. Be ready to open that code and walk through it.

Will an online internship certificate help in interviews?

A certificate alone says little. The work you did during the internship, and how well you explain it, is what an interviewer can assess.

How do I practise if I have no one to mock-interview me?

Record yourself answering aloud, play it back and score it with the rubric. Writing out answers and comparing them with the “strong answer” lists above also works.

Related Full Stack Web Development guides

• Chandigarh University Students: Choosing Between Full Stack Web Development Internship Roles
• Lovely Professional University Students: Presenting a Full Stack Web Development Internship Project Demo
• RV College of Engineering Students: A Full Stack Web Development Internship Preparation Roadmap
• All Full Stack Web Development internship guides