Skip to contentSkip to footer

Junior Software Engineer Interview Questions

Salaries
Interviews

7,249 junior software engineer interview questions shared by candidates

Technical Interview: The technical interview was long, lasting about 2.5 hours. The interviewer asked a range of questions, including React, Promises in JavaScript, HTTP vs. HTTPS, DSA basics, garbage collection, and a database question. Unfortunately, the interview environment felt uncomfortable due to the interviewer's unclear communication and behavior, which made it difficult to engage effectively. Question 1: React Component The interviewer asked me to code a React component. I was expected to implement a working solution for a specific problem, which tested both my understanding of React and my ability to code under pressure. Question 2: Promises in JavaScript I was then asked about JavaScript Promises. Specifically, the interviewer asked about the behavior of a return statement inside a .then() block, followed by another statement after the return. I explained that the statement after the return wouldn’t execute, as the function would exit after returning. The interviewer disagreed and insisted that the statement would execute, which didn’t align with how JavaScript promises work. Question 3: HTTP vs. HTTPS Next, I was asked to explain the difference between HTTP and HTTPS. I described HTTPS as the secure version of HTTP, using SSL/TLS encryption to ensure data security. While I provided a basic explanation, I felt the question was quite fundamental and didn't delve into much detail. Question 4: DSA Basics The interviewer also asked a couple of basic DSA (Data Structures and Algorithms) questions, testing my foundational understanding. These included questions on arrays, linked lists, and trees. While I felt confident in answering these, the interviewer didn’t always seem satisfied with my explanations and often seemed to push for more advanced answers without giving me the chance to elaborate on the basics. Question 5: Database Question The interviewer presented a database-related question, but the wording and explanation were unclear, making it difficult for me to fully grasp what was being asked. I did my best to engage with the question, but due to the ambiguity, I wasn’t able to provide a satisfying answer. Question 6: Garbage Collection I was also asked about garbage collection. I explained how garbage collection works in Java, including an example related to removing the head of a linked list, where the garbage collector automatically cleans up unreachable objects. However, the interviewer dismissed this explanation, saying he wasn’t going to go into that level of detail, which left me feeling like my explanation wasn’t valued. 4. Conclusion: Overall, the interview experience was disappointing due to the interviewer's attitude and the unclear communication. While the questions covered a wide range of topics, I struggled with the unclear database question and the interviewer's reluctance to engage in a meaningful discussion. The interview environment felt toxic, as the interviewer didn't appear to listen to my explanations or provide constructive feedback. The interview also felt poorly structure, and questions being asked without much clarity. This gave me a negative impression of the overall process.
avatar

Junior Associate Software Engineer

Interviewed at Unthinkable

3.6★
Nov 26, 2024

Technical Interview: The technical interview was long, lasting about 2.5 hours. The interviewer asked a range of questions, including React, Promises in JavaScript, HTTP vs. HTTPS, DSA basics, garbage collection, and a database question. Unfortunately, the interview environment felt uncomfortable due to the interviewer's unclear communication and behavior, which made it difficult to engage effectively. Question 1: React Component The interviewer asked me to code a React component. I was expected to implement a working solution for a specific problem, which tested both my understanding of React and my ability to code under pressure. Question 2: Promises in JavaScript I was then asked about JavaScript Promises. Specifically, the interviewer asked about the behavior of a return statement inside a .then() block, followed by another statement after the return. I explained that the statement after the return wouldn’t execute, as the function would exit after returning. The interviewer disagreed and insisted that the statement would execute, which didn’t align with how JavaScript promises work. Question 3: HTTP vs. HTTPS Next, I was asked to explain the difference between HTTP and HTTPS. I described HTTPS as the secure version of HTTP, using SSL/TLS encryption to ensure data security. While I provided a basic explanation, I felt the question was quite fundamental and didn't delve into much detail. Question 4: DSA Basics The interviewer also asked a couple of basic DSA (Data Structures and Algorithms) questions, testing my foundational understanding. These included questions on arrays, linked lists, and trees. While I felt confident in answering these, the interviewer didn’t always seem satisfied with my explanations and often seemed to push for more advanced answers without giving me the chance to elaborate on the basics. Question 5: Database Question The interviewer presented a database-related question, but the wording and explanation were unclear, making it difficult for me to fully grasp what was being asked. I did my best to engage with the question, but due to the ambiguity, I wasn’t able to provide a satisfying answer. Question 6: Garbage Collection I was also asked about garbage collection. I explained how garbage collection works in Java, including an example related to removing the head of a linked list, where the garbage collector automatically cleans up unreachable objects. However, the interviewer dismissed this explanation, saying he wasn’t going to go into that level of detail, which left me feeling like my explanation wasn’t valued. 4. Conclusion: Overall, the interview experience was disappointing due to the interviewer's attitude and the unclear communication. While the questions covered a wide range of topics, I struggled with the unclear database question and the interviewer's reluctance to engage in a meaningful discussion. The interview environment felt toxic, as the interviewer didn't appear to listen to my explanations or provide constructive feedback. The interview also felt poorly structure, and questions being asked without much clarity. This gave me a negative impression of the overall process.

Viewing 1521 - 1530 interview questions

Glassdoor has 7,249 interview questions and reports from Junior software engineer interviews. Prepare for your interview. Get hired. Love your job.