EGYM logo

EGYM Software Engineer Interview Questions
& Process

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

Based on 23 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
87% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at EGYM.

Showing 3 of 23
EGYM logo
EGYM

Software Developer

Engineering · more than a year ago

Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen Offer
Interview formats
Coding Technical

I applied on May 13th, 2022, and got a response for an intro interview on May 18th. The intro interview went well. Then I got a take-home project due May 22nd, which I submitted by May 19th. I followed up on May 27th and was told my project was accepted. I then scheduled a tech interview for June 2nd, which involved live coding and questions about my take-home project. The people were great. I was told I'd hear back within a week, but on June 24th, I got an email saying the process was delayed. The whole thing is taking about 43 days, and I'm still waiting, though I'm losing hope even though I was excited about the relocation offer.

Confirmed questions2 questions
  • What were your thoughts on the tasks involved in the interview?
  • Can you describe your approach to the tasks presented during the interview?
EGYM logo
EGYM

Software Engineer

Engineering

Mid Average Positive experience Accept offer 3 rounds
Interview process
Take home Technical screen Phone screen
Interview formats
Technical Coding Behavioral

The whole thing took about five weeks. Every part felt like it had a purpose, and the questions asked were super relevant to the job. I got to talk to different people at each stage, and they were all really motivated and positive, which was cool. It made me more excited about maybe joining such a great team. First, there was a take-home project, then a technical interview to go over it, and then a behavioral interview. Everything was done professionally, and they explained the role really clearly. Honestly, it was one of the best-organized and most interesting interview processes I've been through. They were upfront about everything and so energetic, you could totally see why people like working here.

Confirmed questions4 questions
  • Discussion on software development practices relevant to the take-home assignment
  • Exploring understanding of OOP principles in relation to the assignment
  • Review of design patterns used or applicable to the take-home project
EGYM logo
EGYM

Software Engineer

Engineering

Senior Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical System Design

The interview process was quick and straightforward, with HR recruiters guiding me effectively from start to finish. I noticed how the technical difficulty of questions ramped up with each stage, which is a smart way to filter candidates and provide them with immediate feedback. For me, the entire process took under two weeks, from the initial contact to receiving the offer. I also got to visit the office, which gave me a clearer picture of the company's structure and culture, solidifying my decision to join.

Confirmed questions4 questions
  • Questions about Golang, depending on the specific stack and role
  • Questions regarding code structure and design principles
  • Questions about system design

EGYM Software Engineer Interview Questions

Quoted word for word from EGYM interview reports.

What are the reasons against using floating-point numbers for storing and manipulating monetary values?

Read reports

Can you find two numbers in a vector that add up to a given integer?

Read reports

What are the differences between inheritance and composition?

Read report

Could you explain the difference between a class and a struct?

Read report

Formats, difficulty and experience

Across all 23 EGYM interview reports.

Interview formats

Technical 37.5%
Behavioral 26.6%
Coding 25%
System Design 4.7%
Other 3.1%

Interview difficulty

Easy 21.7%
Average 69.6%
Difficult 8.7%

Candidate experience

Positive 87%
Negative 13%