Improving Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Improving.
Improving
Power Apps Developer
Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Background check
Interview formats
Technical Behavioral
The interview process was pretty standard and went well. First, I spoke with the main recruiter and got a good vibe. Then, I had a technical review, and they called me back to say it looked good and they were just waiting for the end client's okay to start. After a few days, I followed up and was told the client was offsite and they were waiting for them to return, but things were still positive and they were keen to bring me on board. That was the last I heard. I emailed and called multiple times, but the recruiter never even bothered to reply. Even considering that something might have happened, I waited patiently but kept looking for other opportunities. Interestingly, I then saw the same job reposted with a new date. I tried to contact the recruiter again, but it's clear now they're just unprofessional and couldn't even send a simple 'no longer interested' message.
Confirmed questions1 question
- Were you asked about your experience developing with Power Apps?
Improving
Software Engineer
Senior Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Onsite
Interview formats
Coding System Design Technical
The initial communication with the recruiting team was fine, but the technical part of the process doesn't make much sense for experienced people. The good things are that the recruiters are nice and keep you updated. The initial system design talks were good for showing technical knowledge. The bad things are: they made me do the same coding and system design tests again, just in a different language (Python instead of Node.js). This seems unnecessary. They should trust that a senior candidate can solve problems and design systems, regardless of the programming language. Making senior people repeat the same tests just because of a language change is tiring and a waste of time. Professionals with 10 years of experience should have their time respected. My suggestion is: trust the architects and problem-solvers. If someone is good with one tech, don't make them do pointless extra steps.
Confirmed questions2 questions
- Discussing the details and complexities of Node.js and TypeScript.
- Exploring modern system designs with an emphasis on serverless architectures and cost efficiency.
Improving
Software Engineer
Mid Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Technical Behavioral
Started with a call and then went for a face to face. They asked some technical questions about .Net and my experience with UI and front end tech like angular, blazor, and react. We also had a good chat about where the company is headed. Seemed like a nice group of people.
Confirmed questions2 questions
- Can you tell me about your most recent experience using a front-end framework?
- What's your latest experience with a front end framework?
Improving Software Engineer Interview Questions
Quoted word for word from Improving interview reports.
“Implement a function to identify the largest valid substring containing bracket pairs and other characters.”
Read reports →“Can you write a function that accepts a String and outputs the count of characters in the longest matching set of parentheses, brackets, or braces?”
Read reports →“What is the significance of inheritance?”
Read reports →“Explain the concepts of call by reference and call by value.”
Read reports →“How would you classify an inheritance model: coupled or loosely coupled?”
Read report →“What are the benefits offered?”
Read report →“What do you know about Java?”
Read report →“Can you explain your understanding of model exercising?”
Read report →“How would you approach this algorithm problem?”
Read report →Formats, difficulty and experience
Across all 11 Improving interview reports.