Orca Security logo

Orca Security Software Engineer Interview Questions
& Process

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

Based on 18 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Orca Security.

Showing 3 of 18
Orca Security logo
Orca Security

Software Engineer

Engineering · a year ago

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

The process was pretty standard. First, a Zoom call with the manager for some quick technical questions. Then, an in-office system design round. HR was involved too. They also gave a home assignment, which was actually quite easy with ChatGPT and online help. They were really quick with their follow-ups.

Confirmed questions1 question
  • Can you tell me about your strongest skill area?
Orca Security logo
Orca Security

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience Decline offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Behavioral

The technical parts of the interview process were pretty good. They didn't drag on, and the people interviewing were great. However, my impression of the company soured after meeting with the R&D directors. They came across as really arrogant and unreceptive to different viewpoints.

Confirmed questions1 question
  • Can you tell me about a system you've previously worked on?
Orca Security logo
Orca Security

Senior Software Engineer

Engineering · more than a year ago

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

A third-party recruiter contacted me. First, there was a take-home task where I had to build a basic API service, which took about 3-8 hours depending on how I set up the environment since they didn't provide runtime details. The recruiter said it went well and I advanced. Next, a 2-hour coding and system design interview. It involved a straightforward coding problem and a medium-difficulty system design for a chat app, assuming knowledge of a specific web stack. The interviewers were not very interactive, so it was hard to ask questions or discuss ideas. I think I did okay since I was invited to the next stage. Finally, an interview with the Hiring Manager and Team Lead, which was the complete opposite of the previous one – very open and conversational about the project and role. It's been over three weeks now with no response to my follow-ups, so I assume I've been ghosted.

Confirmed questions4 questions
  • Take-Home task to implement a simple API service.
  • Perform a simple coding task and design a chat system.
  • Perform a simple coding task.

Orca Security Software Engineer Interview Questions

Quoted word for word from Orca Security interview reports.

Explain the constraint that virtual machines with the same tag cannot access each other unless a firewall rule explicitly allows it.

Read reports

What information should the /stats endpoint return, and how should it be formatted?

Read reports

What is the structure of a firewall rule, including fw_id, source_tag, and dest_tag?

Read reports

How should the /attack endpoint function, including its input and output?

Read report

What is the structure of the JSON that describes the cloud environment, including its VMs and firewall rules?

Read report

Given a JSON describing a customer's cloud environment with VMs and firewall rules, which other VMs can attack a specific target VM?

Read report

Can you describe the structure of a Virtual Machine object, including its vm_id, name, and tags?

Read report

Formats, difficulty and experience

Across all 18 Orca Security interview reports.

Interview formats

Coding 34.1%
Technical 29.5%
Behavioral 20.5%
System Design 15.9%

Interview difficulty

Easy 5.6%
Average 66.7%
Difficult 27.8%

Candidate experience

Positive 33.3%
Negative 50%
Neutral 16.7%