ecoATM | Gazelle logo

ecoATM | Gazelle Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.1 Rounds average
Average Typical difficulty
66.7% Positive experience

Which role are you interviewing for?

10 roles · 15 reports

Candidate interview experiences

First-hand accounts from people who interviewed at ecoATM | Gazelle.

Showing 4 of 15
ecoATM | Gazelle logo
ecoATM | Gazelle

Operations

Operations · nearly a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

Standard interview questions with HR, Hiring manager. Situational questions regarding role and current state of business. Long breaks with no communication between rounds and ghosted by HR despite multiple emails to HR for status. Don't post a position if you don't have an intention to hire and communicate

Confirmed questions1 question
  • Can you describe your background and how it fits this position?
ecoATM | Gazelle logo
ecoATM | Gazelle

Finance

Finance · a year ago

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call Background check
Interview formats
Behavioral

The first call with the recruiter was helpful and gave me a good understanding of the company and its operations. I felt I understood the role well and was overqualified. It was a good conversation, and I was told I'd hear back about the next steps soon. I followed up a week later for an update and got a vague response. Weeks went by, and I never even got a simple, standard rejection. Honestly, very unprofessional.

Confirmed questions1 question
  • Can you share an instance where you gave a presentation?
ecoATM | Gazelle logo
ecoATM | Gazelle

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Behavioral Technical System Design

The process started with a typical, non-technical phone call from a recruiter. Then, I had about an hour-long call with a senior engineer where we reviewed my experience and the technologies I've used. It was technical but high-level, focused on my resume rather than requiring specific studying. The final round was about 4 hours long, with several senior engineers and a product person, all in individual 1-on-1 sessions. This part went deeper into my experience, asking about design patterns I've used and my thoughts on certain technologies. They weren't trying to trick me; the whole process felt fair and was designed to assess my experience with their tech stack, my willingness to learn, and my desire to take on challenges. It felt like a good way to assess software engineers at this level, and a refreshing change from typical processes. Everyone was friendly and not confrontational.

Confirmed questions2 questions
  • Can you describe your experience with this technology or design pattern, and what you liked or disliked about it? Would you consider any alternatives?
  • Tell me about challenging projects you've worked on and explain your decisions, as well as what you might do differently now. These are typical experience-related questions.
ecoATM | Gazelle logo
ecoATM | Gazelle

Director of Product Marketing

Marketing

Director Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

The initial HR screening was pretty standard, involving a review of my resume and discussing my interest in the company. Things seemed to be going well until about 10 minutes in when the HR rep asked for my salary expectations. I mentioned that I couldn't provide a figure yet due to not having a clear understanding of the job scope, responsibilities, or team size. She then insisted on knowing my current salary. I declined, citing my employment agreement and the irrelevance of the figure without a clear job scope. I reiterated my interest in assessing team fit and suitability for the role, confident that compensation could be discussed later. The HR rep then stated that without a figure, she wouldn't continue the discussion. I acknowledged this, expressing disappointment but maintaining my stance on not disclosing the information. She then ended the call. It was a surprising and negative experience, making me feel like a mere commodity rather than a potential team member. The focus seemed to be solely on compensation, which isn't my priority over understanding the bigger picture and team dynamics.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

ecoATM | Gazelle Interview Questions

Quoted word for word from ecoATM | Gazelle interview reports.

What action would you take if you got an email about non-compliance with local laws and potential legal action?

Read reports

Can you describe your experience with this technology or design pattern, and what you liked or disliked about it? Would you consider any alternatives?

Read reports

Can you share an instance where you gave a presentation?

Read report

Regarding the technologies you utilized in your last position, what aspects did you find appealing, and which did you dislike?

Read report

Can you describe your background and how it fits this position?

Read report

Can you share a recent challenge you faced and explain how you handled it?

Read report

Tell me about challenging projects you've worked on and explain your decisions, as well as what you might do differently now. These are typical experience-related questions.

Read report

Formats, difficulty and experience

Across all 15 ecoATM | Gazelle interview reports.

Interview formats

Behavioral 55.6%
Technical 33.3%
Other 7.4%
System Design 3.7%

Interview difficulty

Easy 20%
Average 73.3%
Difficult 6.7%

Candidate experience

Negative 26.7%
Positive 66.7%
Neutral 6.7%

Reports by job function

Operations 7
Engineering 3
Legal 2
Finance 1
Sales 1
Marketing 1