Gorilla Logic logo

Gorilla Logic Software Engineer Interview Questions
& Process

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

Based on 13 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
61.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Gorilla Logic.

Showing 3 of 13
Gorilla Logic logo
Gorilla Logic

Senior Software Engineer

Engineering · half a year ago

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

Submitted CV, then had an HR chat about my background, when I can start, and salary. Then I got a link for online tests, like HackerRank. I didn't make it past that because the first problem was LeetCode style, and I'm not sharp on those anymore, especially with AI tools now. The next one was about an Azure architecture scenario. It was cool, but you had to record yourself explaining your plan. Thinking about the salary, I felt it wasn't worth it to keep going since they were basically asking for Architect-level thinking for a Developer job. Heard from others they lowball offers too, making it a mid-level pay for a senior role. So, I bailed.

Confirmed questions5 questions
  • What is the longest combination of strings in an array, LeetCode style?
  • Regarding migrating workloads to Azure, how do we make those decisions?
  • What are the risks associated with migrating workloads to Azure?
Gorilla Logic logo
Gorilla Logic

Software Engineer

Engineering · more than a year ago

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

The interview process was a great experience. Everyone was supportive and guided me well. The technical parts were challenging but manageable. I'd suggest this role to anyone with at least a couple of years of experience.

Confirmed questions1 question
  • What kind of scenario-based questions were asked?
Gorilla Logic logo
Gorilla Logic

Software Engineer

Engineering · more than a year ago

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

The whole process was pretty great, it took about a week and a half. The recruiter was super friendly, and from their initial emails, you could tell they genuinely care about the candidates. The interviewers were professional, and the questions they asked were straightforward and to the point. Honestly, I have no complaints.

Confirmed questions2 questions
  • Can you discuss your full stack development experience?
  • Could you share details about the technologies you've utilized in your projects?

Gorilla Logic Software Engineer Interview Questions

Quoted word for word from Gorilla Logic interview reports.

What's the difference between IQueryable<T> and IEnumerable?

Read reports

What is the longest combination of strings in an array, LeetCode style?

Read reports

Can you list some benefits of using .NET Core compared to .NET Framework.

Read reports

What are the risks associated with migrating workloads to Azure?

Read reports

What are the reasons for migrating workloads to Azure?

Read report

How can one push back against a manager who only wants to migrate to VMs?

Read report

Regarding migrating workloads to Azure, how do we make those decisions?

Read report

Formats, difficulty and experience

Across all 13 Gorilla Logic interview reports.

Interview formats

Technical 38.2%
Coding 29.4%
Behavioral 26.5%
Presentation 2.9%
System Design 2.9%

Interview difficulty

Easy 7.7%
Average 69.2%
Difficult 23.1%

Candidate experience

Positive 61.5%
Negative 38.5%