PetDesk logo

PetDesk Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

4.4 Rounds average
Easy Typical difficulty
60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at PetDesk.

Showing 3 of 5
PetDesk logo
PetDesk

Software Engineer

Engineering · more than a year ago

Mid Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding

So basically, the interview process is pretty standard. You first chat with the hiring manager, then you get a take-home project. After that, there's a review of that project, which was a full-stack app involving an API call. During the project review, the interviewer kept putting down my ideas and my past experience. It felt like they were more focused on showing off how smart they were instead of actually seeing if I was a good fit. It was a really awkward and discouraging vibe. I'm someone who really appreciates respectful and helpful conversations, so I was super bummed about the lack of professionalism. I think interviews should be a place where both sides can have a good talk, letting candidates show what they can do and letting interviewers figure out if they fit the company culture. My experience was nothing like that, honestly. Because of all this, I decided to just stop the interview process and not move forward.

Confirmed questions1 question
  • Can you build a full stack application with an integrated API call and show its response?
PetDesk logo
PetDesk

Software Developer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding

So, the whole process took about 2 weeks which was super fast. It started with a recruiter chat about my background and experience. Then, I spoke with the head of engineering, and if that went well, I got a take-home assignment. It was a practical test, and they got back to me quickly. After submitting, I had a project review where I discussed my design choices. The final stage was a 2.5-hour session with my potential teammates where they asked about my experience and past wins/losses. It was a pretty smooth and friendly process overall.

Confirmed questions2 questions
  • Can you share some of your past successes?
  • Can you share some of your past failures?
PetDesk logo
PetDesk

Software Engineer

Engineering

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

First, you talk to a recruiter on the phone. Then, you have a call with the hiring manager or director. If that goes well, you get a take-home assignment, which is a basic web API. It shouldn't take more than a couple of hours to finish. After you send it in, there's another interview to go over your work and ask you some questions about it. If that's good, the last step is meeting with different teams for a few hours. This last interview involves behavioral questions, going over your resume, and technical questions about your background, plus some easy coding problems. They also check your references near the end.

Confirmed questions1 question
  • Can you tell me about a project you're especially proud of?

PetDesk Software Engineer Interview Questions

Quoted word for word from PetDesk interview reports.

Can you build a full stack application with an integrated API call and show its response?

Read reports

Can you share an example of a project where you improved system performance?

Read reports

Can you tell me about a project you're especially proud of?

Read report

Tell me about your background relevant to this position.

Read report

Formats, difficulty and experience

Across all 5 PetDesk interview reports.

Interview formats

Technical 35.7%
Coding 28.6%
Behavioral 21.4%
System Design 7.1%
Presentation 7.1%

Interview difficulty

Easy 40%
Average 40%
Difficult 20%

Candidate experience

Negative 40%
Positive 60%