Zego logo

Zego Interview Questions
& Process

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

Based on 38 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
63.2% Positive experience

Which role are you interviewing for?

20 roles · 38 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Zego.

Showing 4 of 38
Zego logo
Zego

Client Success Manager

Sales · nearly a year ago

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

The interview process wasn't too difficult and involved meeting with three interviewers, who were current CSMs. It all went pretty smoothly and wasn't super challenging. The mock QBR part was the most stressful, but they were more focused on how I handled myself than the specifics.

Confirmed questions1 question
  • Could you prepare and present a mock QBR?
Zego logo
Zego

Site Reliability Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Group Panel
Interview formats
Technical Coding Group Behavioral

So I had this interview process that started with a phone screen for about an hour, where we just talked about my resume and what I've done. After that, I got a coding challenge to design a postfix calculator using PHP. I had four days to do it. Then came a group interview that was pretty long, like 2.5 hours. It was split into three different panel interviews, and I had to answer the same questions with each panel, which felt inefficient. During this, I got a feel for the company culture. Two interviewers actually walked out halfway through, which was pretty rude considering they set aside the time. Another one kept interrupting me and asking the same questions I'd already answered, seemed like he wasn't paying attention. They also twisted my words a bit, like when I said I personally didn't find QA challenging, they took it as me saying QA isn't challenging for anyone, which wasn't my point. And when I mentioned projects I did in school for world-class applications because I'm a recent grad, they interpreted it as me not liking to code with people, even though I think coding together and collaborating are different things, and people have different styles. It all took about two weeks and a few days off work for that challenge.

Confirmed questions1 question
  • Could you write a query that performs an inner join on two tables, including a selector?
Zego logo
Zego

Software Engineer

Engineering

Entry Average Positive experience No offer 6 rounds
Interview process
Recruiter call Take home Technical screen Phone screen Onsite Panel Presentation Background check Offer
Interview formats
Behavioral Technical Coding System Design Presentation

The whole interview process was pretty standard, a bit tougher than I thought, but overall a good experience. I initially contacted HR after a professor recommended me. HR quickly had me fill out an online application. Within a few days, I had to take an online behavioral test and a timed IQ test. To make sure I wasn't cheating on the IQ test, I had to retake it live on webcam with HR, who asked me some simple questions about myself and my background. A couple days later, HR called to set up a phone interview with an Engineering Manager. This call was mainly technical questions for the role, plus some 'why PayLeaser' questions. After that, I was invited for an in-person interview the following week. This was an interesting stage with a panel of middle managers, one of whom was on webcam. They asked me intermediate technical questions, and I had to draw two things on the whiteboard. Then they reviewed code from my Github, like a peer review. Immediately after the panel, I had a one-on-one with a senior manager, mostly about my background and soft skills. The final step was another in-person interview, another panel, but this one was less technical and more focused on my resume and what I could contribute. I didn't get an offer in the end, but it was a valuable experience. The entire process took about a month and involved 2 tests, 1 webcam interview, 1 phone call, 1 one-on-one in-person, and 2 panel interviews. The HR was super helpful in getting me ready for everything, so definitely ask them questions! Good luck!

Confirmed questions8 questions
  • Can you explain what OOP is, what benefits it offers, and how it compares to procedural programming?
  • What is the static keyword used for? Please provide an example.
  • How do you implement an interface in Java? When is it appropriate to use an interface? Is it possible to create an instance of an interface?
Zego logo
Zego

Director of Engineering

Engineering

Director Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Other

After submitting your resume, if they liked it, they'd send you an online aptitude test. But don't get your hopes up for an interview even if you ace the test... it felt like a waste of time. My resume was reviewed, and then I got an email saying: "Having reviewed your career history, we are pleased to extend you an invitation to complete our two pre-employment assessments: a cognitive assessment and a personality assessment. ..." The recruiter confirmed I passed the tests. Then after a week of silence, they sent this: "we are moving forward with other candidates who more closely match our current requirements ..." What a joke!

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Zego Interview Questions

Quoted word for word from Zego interview reports.

What would this code snippet print (concerning getters and setters for objects in PHP)?

Read report

What output will be produced by the following PHP code snippet?

Read report

What would be the output of this code snippet (related to pass by reference versus copy)?

Read report

What is the static keyword used for? Please provide an example.

Read report

Formats, difficulty and experience

Across all 38 Zego interview reports.

Interview formats

Behavioral 42.3%
Technical 30.8%
Coding 9%
Other 6.4%
Presentation 3.8%

Interview difficulty

Easy 10.5%
Average 84.2%
Difficult 5.3%

Candidate experience

Positive 63.2%
Neutral 21.1%
Negative 15.8%

Reports by job function

Engineering 15
Operations 11
Sales 6
Analytics 2
Research 2
Product 1