Zup Innovation logo

Zup Innovation Interview Questions
& Process

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

Based on 182 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
72.5% Positive experience

Which role are you interviewing for?

30 roles · 182 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Zup Innovation.

Showing 4 of 182
Zup Innovation logo
Zup Innovation

SRE/DevOps Engineer

Engineering · a year ago

Mid Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check Offer
Interview formats
Behavioral Technical Coding

I recently interviewed for the SRE DevOps position at Zup and had a really great experience. The process was well-organized from the start, with clear info about each step. After I applied, they got in touch quickly for an initial chat, where the recruiter talked about the company culture and the job's challenges. The technical interview was with the engineering team and focused on my background in automation, infrastructure as code, and monitoring. I also got a practical assignment that fit the daily tasks well, with a fair deadline. In the final stage, I spoke with leadership about the team's strategic vision and how SRE impacts the company. Feedback was fast and thorough, and I got approved! They even sent materials for a structured onboarding before I started. It was one of the best hiring processes I've been through, with honesty and respect for candidates.

Confirmed questions1 question
  • Can you discuss your experience with Cloud Native Tools and Agile methodologies?
Zup Innovation logo
Zup Innovation

Backend Developer

Engineering · a year ago

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

In the call with the recruiter, we talked about me, the company, culture, benefits, and compensation. The technical round included a live coding session where I developed and solved a problem. Afterwards, we discussed development best practices and code review using another code example. Following the live coding, we had a discussion about cloud and software architecture. In the meeting with the tech manager, I was introduced to the team for the role, and then we had an in-depth conversation about architecture and cloud.

Confirmed questions7 questions
  • Could you explain SOLID principles?
  • What distinguishes relational from non-relational databases?
  • Can you describe the CQRS pattern?
Zup Innovation logo
Zup Innovation

Front End Developer

Engineering · a year ago

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

Had a standard chat with HR about past experiences and goals. Then, a technical interview with live coding, which included two exercises. The first was a tough one to create a TypeScript interface for a dataset, involving concepts like recursion and generic types. The second was a medium-difficulty code analysis exercise, focusing on fetching an API and using useEffect. The task was to implement logic for sequential requests with a delay. The feedback given was vague and generic.

Confirmed questions1 question
  • What is the purpose of the key in the Javascript map method?
Zup Innovation logo
Zup Innovation

Python Developer

Engineering · a year ago

Mid Easy Positive experience Accept offer 6 rounds
Interview process
Recruiter call Technical screen Technical screen Presentation Background check Offer
Interview formats
Technical System Design Coding Behavioral

The recruiter first reached out about a different role, had that interview, and then I was sent to a technical interview with the tech lead and another developer. I was cut for that role due to not having the necessary experience, even though I did well. The recruiter let me know in 2 days and redirected me to another role. I interviewed with the manager and then had another technical interview with the Tech Lead, where we did an architecture design, built an API, and discussed some challenges. After that, a cultural fit interview was scheduled and a proposal was sent. The whole process took about 4 weeks, but that was because of the redirection, and the process itself was very quick and professional. A+ experience.

Confirmed questions2 questions
  • What challenges have you faced working asynchronously with Python?
  • Can you share your experience with Generative AI?

Zup Innovation Interview Questions

Quoted word for word from Zup Innovation interview reports.

What is the error in this docker-compose file that includes a postgres image?

Read reports

What is the purpose of the key in the Javascript map method?

Read reports

What is the difference between weak, strong, and unowned references?

Read reports

Could you explain the difference between a while loop and a do-while loop?

Read reports

If Globo's voting system for Big Brother couldn't handle the demand when saving to a database, what solution would you propose to fix it?

Read report

Could you explain the different types of access control (public, open, private, internal)?

Read report

Build a Kanban board using the company's specific framework, in this case Angular and Nest.

Read report

What is the best way to create a screen flow for user registration?

Read report

How would you solve the problem of consuming an external API that went offline?

Read report

Formats, difficulty and experience

Across all 182 Zup Innovation interview reports.

Interview formats

Behavioral 46%
Technical 36.9%
Coding 11.3%
System Design 1.7%
Presentation 1.4%

Interview difficulty

Easy 24.7%
Average 59.9%
Difficult 15.4%

Candidate experience

Positive 72.5%
Neutral 7.1%
Negative 20.3%

Reports by job function

Engineering 131
Other 11
Design 9
Operations 8
Analytics 7
HR 5