Improving logo

Improving Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 37 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
70.3% Positive experience

Which role are you interviewing for?

19 roles · 37 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Improving.

Showing 4 of 37
Improving logo
Improving

Product Engineer

Engineering · nearly a year ago

Mid Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Take home Technical screen Technical screen Background check Offer
Interview formats
Coding Technical Behavioral

Got contacted by a recruiter on LinkedIn who laid out the whole interview process. It took about three weeks because we had to reschedule a couple times, but they communicated well the whole time. First, I had to do an online coding assessment and submit my code on GitHub. Then, I had two technical interviews. After passing those, I had a chat with HR, and then they made the offer.

Confirmed questions8 questions
  • Regarding Autowired, what is it?
  • What about annotations?
  • Can you explain Rest Controller?
Improving logo
Improving

Software Engineer

Engineering · nearly a year ago

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 logo
Improving

Senior Frontend Developer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Technical Coding

The interview process was pretty simple. It started with a recruiter screening. During this call, they make it clear that the salary range for engineers in Latin America is significantly lower than for those in the US. Next, there was a technical interview and a take-home assignment, which I completed. After waiting for about a week, the recruiter got back to me with some feedback. It was quite vague, and rather than pointing out specific weaknesses or areas for improvement, it felt like the tech lead who reviewed the assignment either couldn't articulate their feedback clearly or just didn't care enough to do so.

Confirmed questions7 questions
  • Can you tell me about your experience with Javascript?
  • Explain Closures in Javascript.
  • What is hoisting in Javascript?
Improving logo
Improving

Tech Lead

Engineering

Lead Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

I got referred by someone who works there. A recruiter called me and we chatted for about 30 minutes about the company, salary ranges, and the types of positions they were hiring for. We also went over my background and experience. After that, a panel of people called me for a technical screening, where we mostly talked about specific things from my past work and some technical subjects. Then, I was invited for an onsite interview with a tech lead. During that, I was asked technical questions that they expected me to know and we discussed different kinds of problems and how to solve them.

Confirmed questions1 question
  • What makes you want to work here?

Improving 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 report

In React, what is the purpose of useMemo, and how would you implement it?

Read report

Explain the concepts of call by reference and call by value.

Read report

Can you explain what truthy and falsey mean in JavaScript?

Read report

Formats, difficulty and experience

Across all 37 Improving interview reports.

Interview formats

Behavioral 38.8%
Technical 37.6%
Coding 16.5%
System Design 2.4%
Presentation 2.4%

Interview difficulty

Easy 16.2%
Average 70.3%
Difficult 13.5%

Candidate experience

Positive 70.3%
Negative 24.3%
Neutral 5.4%

Reports by job function

Engineering 22
Consulting 7
Operations 3
HR 2
Design 1
Sales 1