The Farmer's Dog Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 156 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 156 reportsCandidate interview experiences
First-hand accounts from people who interviewed at The Farmer's Dog.
The Farmer's Dog
Software Engineer
Senior Average Positive experience Decline offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Coding System Design Behavioral
The interview process involved a recruiter call, a coding question, a system design question, a behavioral interview, a reference check, and finally an offer call. I really liked interviewing at TFD; the questions felt practical for the job and not like tricks. Everyone was nice and smart. The only downside was the reference check, which feels a bit outdated and unnecessary now, plus it inconveniences former coworkers. Despite that, it was a good interview experience overall, and I'd recommend TFD.
Confirmed questions1 question
- How would you implement an Object-Oriented Programming system for hotel bookings?
The Farmer's Dog
IT Systems Administrator
Mid Average Negative experience No offer 1 round
Interview process
Recruiter call Recruiter call
Interview formats
Behavioral
I saw this listing reposted for a while and figured it might be a ghost listing or that their interview process was flawed. Since I hadn't applied yet, I went ahead and did. Surprisingly, they reached out the next day and scheduled me for Monday. On Monday, I waited 15 minutes on Zoom, and then got an update a couple hours later saying the recruiter was sick and wanted to reschedule. During the rescheduled interview on Friday, the recruiter was 5 minutes late, almost as if he was hoping I'd leave. He seemed uninterested in my background and asked repetitive questions, as if he already had someone in mind or wasn't seriously looking to hire. By the end, I wasn't very interested myself.
Confirmed questions1 question
- Can you tell me about your experience with Jamf?
The Farmer's Dog
Director, People Operations
Director Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical
I applied and a few weeks later I got an email to set up a phone screen. The phone screen was casual and had some specific questions. The recruiter was nice and friendly, and gave me good info about the team, why the job is open, how the interviews will go, and about the company. She mentioned there would be an assessment and the final interview would be with the CEO. About a week after, I had a virtual first round interview. I was really let down by that conversation and experience. The interviewer seemed really uninterested and gave me the same basic answers to questions like 'what is working on this team like?', 'can you describe the company culture?', and 'what has your personal experience been like working here?' with 'its a beautiful thing/place, its all for the dogs'. At one point, she left her desk while I was answering her question and didn't come back for about 30 seconds and didn't apologize or say anything. After that, I knew I wouldn't move forward. The start of the process was great and positive, I learned more from the recruiter than the interviewer, but it ended poorly, which was a bummer since I'm a customer of the brand.
Confirmed questions4 questions
- Can you tell me about a project where you collaborated across teams?
- Tell me about system projects you have worked on.
- Describe your experience working with leaders.
The Farmer's Dog
Software Engineer
Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen
Interview formats
Behavioral Technical Coding System Design
So I went through the interview process at The Farmer's Dog and man, it was a bit of a headache. It dragged on for like a month, and there were at least 4 stages, plus some unexpected twists. First up was the Recruiter Screening (30 mins), which was actually great. Then the Engineering Manager Interview (45 mins) – pretty meh. After that, a Systems Design Interview (60 mins), which was also great. But then the Live Coding Challenge (45 mins) was just terrible. One of the biggest frustrations was their coding skills test. They totally threw me off midway through, which left me feeling confused and annoyed. They used so much technical jargon, it felt like they expected me to be a walking encyclopedia. Honestly, I think it's enough to know how something works without needing super deep knowledge of a coding language. What really got me was the hypocrisy in the coding interview. They said there wasn't a 'right' answer, but then they pushed me to use their specific class methods with some obscure utility function. I've built messaging queues before, and it was infuriating to be forced into making a less-than-ideal solution just because they weren't flexible. The whole coding challenge didn't feel like a real test of my skills as a software engineer. The pressure was intense, and it seemed like they were more focused on catching errors than seeing how I could contribute to a team. You can't say collaboration is important and then penalize someone for trying to collaborate when they're stuck. For other engineers, think about it: do you have someone breathing down your neck while you code at work, just waiting for you to mess up? This interview felt like being interrogated by people who didn't seem to know how to interview well. The general feeling was that I was wasting their time, except for the Systems Design interview, which was enjoyable. The Farmer's Dog's talk about their company culture didn't match what I experienced, at least on the engineering side. I'm over just accepting this as the industry standard. We need to improve, and that's why I'm sharing this.
Confirmed questions3 questions
- Could you design a Javascript Messaging Queue class that handles promises, executing up to 10 requests concurrently until the queue is depleted?
- The Queue class should include two methods: add() and start().
- A utility function will supply an array of anonymous functions (jobs), passed using the rest parameter syntax to the add() function, like so: add(...jobs).
The Farmer's Dog Interview Questions
Quoted word for word from The Farmer's Dog interview reports.
“Imagine The Farmer's Dog on a billboard! What would be a perfect OOH advertising concept?”
Read reports →“Could you create a GIF that points out the ingredients like "beef," "sweet potato," and "kale" in our food, and uses "?" for the ingredients in kibble, to communicate that our food looks like food and kibble looks like processed brown balls?”
Read reports →“Could you implement a Queue class with Add and Start methods, where Add takes an array of promises and Start executes them with a constant concurrency of 10?”
Read reports →“Can you explain what Net Promoter Score is and the method for its calculation?”
Read reports →“Can you detail all the aspects of the API for this IOT service?”
Read report →“Can you implement an algorithm for a "dog hotel" where given a list of dates, you return available rooms based on prior check-in and check-out dates?”
Read report →“If you could go back in time and give advice to your younger self, what would it be?”
Read report →“How would you create a class to manage a pool of async JavaScript functions, ensuring only a certain number run at once and new ones start as slots free up, specifically addressing concurrency with promises, async, callbacks, and recursion?”
Read report →“Could you design a Javascript Messaging Queue class that handles promises, executing up to 10 requests concurrently until the queue is depleted?”
Read report →Formats, difficulty and experience
Across all 156 The Farmer's Dog interview reports.