Interview prep · Entry Level

Internship interview questions and answers

Interviewers for a technical internship want to know whether you have a solid foundation in coding, databases and version control, and whether you can learn quickly. They also look at how you communicate, work with a team and handle ambiguity or mistakes. Since interns rarely arrive knowing everything, they are looking for curiosity, clear thinking and coachability as much as raw skill.

1. Question 1

   Tell me about yourself.

   What they're asking: The interviewer wants a short, relevant summary of your skills, projects and motivation for this internship.

   Sample answer

   I'm a [year] studying [major] at [school], and I enjoy turning ideas into working software. Most of my experience is in [Python and JavaScript]. Recently I built [project name], a [React front end with a Node.js API and a MySQL database] that [what it does]. I use Git for all my work, and on a team project with [number] classmates we ran short sprints and weekly check-ins, which taught me a lot about Agile habits. I also [led the web team for a club/tutored peers], which helped me explain technical ideas to non-technical people. I'm looking for an internship where I can contribute to real tasks, learn from experienced engineers and grow in [area], and this role fits that goal.

2. Question 2

   Walk me through how you would build a simple REST API with Node.js that reads and writes data in a MySQL database.

   What they're asking: They want to see whether you understand API design, database connections and basic security, not just syntax.

   Sample answer

   I'd start by defining the resources and endpoints, for example GET and POST routes for /[resource], and use Express to handle routing. I'd connect to MySQL with a connection pool and use parameterized queries so user input can't cause SQL injection. I'd validate incoming data before it reaches the database and return clear status codes, like 201 for created and 400 for bad input. I'd wrap handlers in error handling so the server doesn't crash, and keep credentials in environment variables, never in the repository. Then I'd test endpoints with a tool like Postman and write down the routes so a front-end teammate can use them. In my project [name], I did this for [feature].

3. Question 3

   In React, what is the difference between state and props, and how would you display data fetched from an API in a component?

   What they're asking: This checks whether you understand core React concepts and can apply them to a common real-world task.

   Sample answer

   Props are read-only values a parent passes down to a child, while state is data a component owns and can change, which triggers a re-render. To show API data, I'd create state for the data, plus loading and error states. Then I'd use useEffect with an empty dependency array to call fetch when the component mounts, parse the JSON and update state. In the return, I'd show a loading message first, an error message if the request fails, and otherwise map over the data to render a list with unique keys. I'd also handle cleanup if the component unmounts mid-request. I used this pattern in [project] to display [type of data].

4. Question 4

   You're given a messy dataset in a MySQL table with duplicates and missing values. How would you clean and analyze it using SQL and Python?

   What they're asking: They are testing your data analysis process, SQL fundamentals and attention to detail.

   Sample answer

   First I'd explore the data: check row counts, column types, and use COUNT, GROUP BY and HAVING to find duplicates, and IS NULL checks to find missing values. I'd confirm with the data owner what counts as a duplicate before deleting anything, and I'd work on a copy rather than the original table. For missing values, I'd decide case by case whether to remove rows, fill with a default or flag them. Then I'd pull the cleaned data into Python with pandas, calculate summaries such as averages or trends by [category], and chart the results. I'd document each step so someone else could repeat it. I did something similar in [class/project] with [dataset].

5. Question 5

   Tell me about a time you disagreed with a teammate on a project. How did you handle it?

   What they're asking: They want evidence that you can collaborate respectfully and resolve conflict productively.

   Sample answer

   In [course/project], my teammate and I disagreed on whether to build [feature] with [approach A] or [approach B]. As the person responsible for [your part], I needed us to agree quickly so we could meet our deadline. I suggested we each spend 15 minutes listing pros and cons, then compare them against our requirements. I listened to their concerns about [issue] and shared mine about [issue]. We realized a hybrid approach covered both, so we chose that and divided the work. The result was that we delivered on time, our instructor praised [aspect of the project], and we had a smoother working relationship afterward. I learned that focusing on shared goals makes disagreements easier to solve.

6. Question 6

   Describe a time you had multiple deadlines at once. How did you manage your time?

   What they're asking: Interns juggle tasks, so they want to see how you prioritize and stay reliable.

   Sample answer

   During [semester/period], I had a [project] due, two exams and my part-time job at [type of workplace] all in the same week. I needed to finish everything without lowering quality. I listed every task with its due date and estimated hours, then ranked them by deadline and impact. I blocked time on my calendar, broke the coding project into smaller milestones and pushed working code to Git daily so I could track progress. When I saw one task running long, I told my teammate early and we adjusted the scope. As a result, I submitted everything on time and scored [result] on the project. I now plan backward from deadlines on every project.

7. Question 7

   Tell me about a time you had to learn a new technology or tool quickly.

   What they're asking: They want to see adaptability and a repeatable way of learning, since interns constantly meet unfamiliar tools.

   Sample answer

   For [project/class], my team decided to use [new tool, e.g., Node.js or Linux command line], and I had only [limited experience]. My task was to build [specific piece] within [timeframe]. I started with the official documentation and a short tutorial, then built a tiny practice version before touching the real code. When I got stuck on [issue], I searched error messages, read similar examples and asked a teammate one focused question instead of a vague one. Within [number] days I had my part working, and I wrote a short setup guide for the team. The project was completed on schedule, and I felt much more confident using [tool] afterward.

8. Question 8

   Tell me about a time you caught a mistake or bug before it caused a bigger problem.

   What they're asking: They are checking your attention to detail and whether you take ownership of quality.

   Sample answer

   While working on [project], I was responsible for [feature, e.g., a form that saved data to a database]. Before merging my code, I wanted to be sure it worked beyond the normal case. I tested unusual inputs, like empty fields and very long text, and noticed that [specific bug, e.g., blank entries were being saved]. I fixed it by adding validation on both the front end and the back end, then wrote a few test cases to confirm it. I also mentioned the issue in my pull request so reviewers knew what to check. The result was that the bug never reached our final version, and our team adopted a short testing checklist before merging.

9. Question 9

   You've been stuck on a bug for two hours and can't find the cause. What do you do?

   What they're asking: They want to see your problem-solving process and whether you know when to ask for help.

   Sample answer

   I'd first step back and make sure I can reproduce the bug reliably, then narrow it down by checking logs, adding print statements or using a debugger, and testing one piece at a time. I'd re-read the error message carefully and search for it, checking documentation too. If I still had no progress after a set time, maybe 30 more minutes, I'd ask for help. I'd explain what I expect to happen, what actually happens, and what I've already tried, so I respect the other person's time. Once fixed, I'd write down the cause and solution so I don't repeat it. Asking early enough keeps the team moving and helps me learn.

10. Question 10

    Midway through a sprint, a non-technical stakeholder asks for a new feature. How would you respond?

    What they're asking: They are testing your understanding of Agile, communication and customer service.

    Sample answer

    I'd start by listening and asking questions to understand the problem behind the request, such as who needs it and why it matters now. I'd then estimate roughly how much work it involves and check how it affects what we already committed to in the sprint. Since I'm an intern, I'd bring this to my supervisor or the team lead rather than promising anything myself. In Agile terms, I'd suggest adding the request to the backlog and discussing priority at planning, unless it's urgent enough to swap with another task. I'd explain this to the stakeholder in plain language, thank them for the idea and follow up once a decision is made.