Edaptive Computing logo

Edaptive Computing Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
42.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Edaptive Computing.

Showing 3 of 7
Edaptive Computing logo
Edaptive Computing

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Phone screen Technical screen Onsite Offer
Interview formats
Technical Behavioral

The interview process involved zoom calls. It started with a phone screen, followed by an interview with management where I was asked technical questions. Next, I interviewed with the CEO. Salary was discussed in the final interview.

Confirmed questions1 question
  • How are you doing today?
Edaptive Computing logo
Edaptive Computing

Software Engineer

Engineering · more than a year ago

Entry Difficult Neutral experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical Coding

It kicked off with a non-technical chat on the phone, covering talking about myself from the resume, then moved to technical questions. These included Java and object-oriented programming concepts. There were also programming parts where you figure out what code does. It also had a bit of Java programming involved.

Confirmed questions8 questions
  • Tell me about the difference between break and continue.
  • Is it possible for multiple catch blocks to be executed?
  • What is your understanding of MVC (Model-View-Controller)?
Edaptive Computing logo
Edaptive Computing

Senior Developer

Engineering · more than a year ago

Senior Average Negative experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Coding Presentation Behavioral

The interview process was pretty standard. It kicked off with a phone call, then I had a technical interview at their office. They asked me how I'd tackle some problems, which turned out to be directly from a contract they needed done. I had to go to the whiteboard and draw out my answers like I was giving a presentation. If you can handle the whiteboard and have the right technical skills, you should be fine with their questions. I wasn't given a tour, but they do give tours to clients and can give you one too. You should definitely ask for one and make sure you see the working conditions before you commit. I got an offer and accepted it. The catch was, they gave me only 24 hours to decide. They said I was their top candidate out of four and if I passed, they'd offer it to someone else the next day. Since I was unemployed, I took it. The pay seemed okay, but when I mentioned the 'four candidates' thing to my new supervisor (who interviewed me), he just laughed and said they hadn't interviewed anyone else, and he wasn't happy HR lied to me. Lying to get someone to accept a job offer is pretty messed up. Finding out you were lied to in your first month isn't great. They're really short-staffed, so don't let them pressure you. Ask yourself if you're desperate enough to take the job.

Confirmed questions1 question
  • Can you write the VHDL code for a 4-input multiplexer on the whiteboard?

Edaptive Computing Software Engineer Interview Questions

Quoted word for word from Edaptive Computing interview reports.

Is it possible to manually initiate Java garbage collection?

Read reports

What is the distinction between an error and an exception?

Read reports

Is it possible for multiple catch blocks to be executed?

Read report

Are there any specific restrictions when overriding a method?

Read report

What would be the output of the following code snippet?

Read report

Could you explain the difference between a set, a list, and a map?

Read report

Formats, difficulty and experience

Across all 7 Edaptive Computing interview reports.

Interview formats

Technical 43.8%
Coding 31.2%
Behavioral 18.8%
Presentation 6.2%

Interview difficulty

Easy 14.3%
Average 57.1%
Difficult 28.6%

Candidate experience

Neutral 42.9%
Positive 42.9%
Negative 14.3%