Gecko Robotics logo

Gecko Robotics Interview Questions
& Process

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

Based on 97 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
46.4% Positive experience

Which role are you interviewing for?

28 roles · 97 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Gecko Robotics.

Showing 4 of 97
Gecko Robotics logo
Gecko Robotics

Machine Learning Engineer

Engineering · a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Technical screen Take home
Interview formats
Technical Coding

I feel they were more interested in gathering new ideas for their technical problems than actually hiring someone. The HR reached out to me directly. After meeting with the hiring manager, I was quickly invited for an onsite interview. During the onsite, they presented me with a real problem they were facing and asked for all possible solutions I could think of, even showing me their notebook. Other technical interviews were similar, focusing on theoretical solutions for their problems. I think these went well, as I could answer everything and even proposed an ML model for their data with good accuracy. The final part was a coding challenge, which was poorly managed due to the interviewer. She seemed to be actively noting down every mistake I made, which was quite demotivating. A few days later, HR called to say they weren't moving forward, mentioning they'd keep me in mind for future roles, but I'm not keen on re-engaging with them.

Confirmed questions2 questions
  • Can you suggest ways to automatically validate ultrasound signals and how to code them?
  • How would you implement automatic validation of ultrasound signals in code?
Gecko Robotics logo
Gecko Robotics

Software Engineer

Engineering · a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Take home Technical screen Onsite Panel Background check Offer
Interview formats
Coding Behavioral Technical System Design

It started with an online assessment with Medium difficulty questions, then a behavioral interview with typical questions. After that, there was a pair programming session focused on data processing using non-Leetcode style problems. The process concluded with a final panel interview in the office, which covered system design, more data processing tasks, and behavioral questions. The whole thing was pretty smooth, and the recruiter was very nice and kept in touch well.

Confirmed questions2 questions
  • Can you explain your interest in Gecko?
  • Could you introduce yourself?
Gecko Robotics logo
Gecko Robotics

Mechanical Engineer Intern

Engineering · a year ago

Intern Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Presentation Technical screen Onsite
Interview formats
Behavioral Technical Presentation

The interview process kicked off with a 20-30 minute HR phone screening. Following that, there was a 20-30 minute engineering manager phone screen where they asked a mix of behavioral and technical questions. The final stage involved a 15-minute portfolio presentation, followed by a 60-minute whiteboard technical interview, and a 30-60 minute behavioral interview with some of the engineers.

Confirmed questions3 questions
  • Can you discuss your technical experience and any projects you've worked on?
  • Tell me about a difficult situation you had to navigate.
  • What are you looking for in terms of company culture?
Gecko Robotics logo
Gecko Robotics

Forward Deployed Engineer

Engineering · more than a year ago

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

After the recruiter call, the first interview was a technical one. I was expecting a verbal technical interview, but instead, I was thrown into a coding test on an IDE I'd never seen before. I hadn't coded in about two months prior, so I was totally unprepared and very frustrated. The video feed in the platform was obscuring the console output. So, as I was trying to get familiar with the interface and test for an output, nothing was showing - which just made things worse. It was really unfair because the recruiter had told me beforehand "this is not a test" and that the platform was "similar to zoom".

Confirmed questions7 questions
  • Analyze existing code to produce a specific output.
  • Demonstrate understanding of Arrays.
  • Show proficiency in Linear calculations and Algebraic geometry.

Gecko Robotics Interview Questions

Quoted word for word from Gecko Robotics interview reports.

Can you estimate the number of gas stations in the United States?

Read reports

How can you time one hour using two ropes that burn at different rates?

Read reports

Given a number randomly generated between 0 and 100, what is the binary search approach?

Read reports

Based on the provided lines for current, velocity, and code runtime, what can you infer about the robot's actions?

Read report

How would you approach the problem of robot localization in an environment lacking distinct features?

Read report

If a particular sensor on the robot were malfunctioning, what steps would you take to troubleshoot it?

Read report

How would you implement automatic validation of ultrasound signals in code?

Read report

Can you suggest ways to automatically validate ultrasound signals and how to code them?

Read report

Formats, difficulty and experience

Across all 97 Gecko Robotics interview reports.

Interview formats

Behavioral 40.4%
Technical 26.6%
Coding 18.2%
Presentation 6.4%
System Design 4.4%

Interview difficulty

Easy 25.8%
Average 61.9%
Difficult 12.4%

Candidate experience

Positive 46.4%
Negative 35.1%
Neutral 18.6%

Reports by job function

Engineering 69
HR 8
Operations 5
Sales 5
Design 3
Product 3