Software Developer Interviews

Software Developer Interview Questions

Software development is an in-demand career path, and it's also a job that can provide opportunities for high earnings and professional fulfillment. When interviewing for software developer positions, you'll likely face questions about your hard and soft skills and how you manage projects efficiently.

Top Software Developer Interview Questions & How to Answer

Question 1

Question #1: What type of software development do you currently do?

How to answer
How to answer: When answering a question about your current software development projects, emphasize the coding languages and technology stack that you use. This question helps an interviewer determine if you have the skills needed to handle the workload.
Question 2

Question #2: Describe a development issue you faced and how you solved it.

How to answer
How to answer: Talking about a specific situation allows you to describe your problem-solving methods and the actions you took to resolve the problem. Use the STAR method (situation, task, action, result) to provide a clear picture of the problem you faced in development and what you did to fix it.
Question 3

Question #3: How do you handle the QA process?

How to answer
How to answer: Quality assurance is an important aspect of software development, and the process may fall on the developers in a smaller organization that doesn't have a designated QA team. If you face a question about the QA process, the interviewer may be trying to determine whether you would be willing and able to take on testing and bug fixing as part of the role.

96,233 software developer interview questions shared by candidates

The chessboard problem. I first mentioned BFS and use of a Queue but the interviewer kept asking about some data structure with less memory that I could extract due to the simple structure of the graph. I did not understand what he meant. I eventually mentioned DFS and proved it works uses less memory. The cache problem took a long time. I kind of though I failed it at some point. I had no prior knowledge of the topic since I am not a CS guy. I eventually, used an array to store the access time to different items and O(n) search through it to find the least frequently used one. The interviewer did not raise the complexity. He wanted me to write code on a paper (which is hard, esp. in C).
avatar

Financial Software Developer

Interviewed at Bloomberg

4
Jul 11, 2014

The chessboard problem. I first mentioned BFS and use of a Queue but the interviewer kept asking about some data structure with less memory that I could extract due to the simple structure of the graph. I did not understand what he meant. I eventually mentioned DFS and proved it works uses less memory. The cache problem took a long time. I kind of though I failed it at some point. I had no prior knowledge of the topic since I am not a CS guy. I eventually, used an array to store the access time to different items and O(n) search through it to find the least frequently used one. The interviewer did not raise the complexity. He wanted me to write code on a paper (which is hard, esp. in C).

Copy a block of memory from source to destination. You need to consider the overlapping cases. Yet I don't think copy from behind will solve the problem. Because the memory may overlap at the beginning. So a pre-check of overlapping region is necessary. In my view, for a typical copy operation the source should not be overwritten, but the answer allows for that. I was pretty confused...
avatar

Software Developer

Interviewed at Bloomberg

4
Oct 9, 2014

Copy a block of memory from source to destination. You need to consider the overlapping cases. Yet I don't think copy from behind will solve the problem. Because the memory may overlap at the beginning. So a pre-check of overlapping region is necessary. In my view, for a typical copy operation the source should not be overwritten, but the answer allows for that. I was pretty confused...

Viewing 841 - 850 interview questions

Glassdoor has 96,233 interview questions and reports from Software developer interviews. Prepare for your interview. Get hired. Love your job.