Philo logo

Philo Interview Questions
& Process

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

Based on 31 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
35.5% Positive experience

Which role are you interviewing for?

14 roles · 31 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Philo.

Showing 4 of 31
Philo logo
Philo

Product Designer

Design · more than a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Presentation Onsite
Interview formats
Behavioral Presentation Technical

The interview process at Philo was top-notch. My recruiter was super helpful and made sure I knew what was going on every step of the way. They even set up prep calls and gave me feedback on how I did. Even though I didn't get the job, the recruiter still called me for 30 minutes to give me pointers on how to get better and shared insights from the team. It was the best interview experience I've had, and it really showed how much Philo values their candidates. I'd have loved to work there with their design team. I'll definitely be looking for other jobs there that are a better fit and keep working on my interview skills. Big thanks to the Philo team for the chance!

Confirmed questions4 questions
  • Recruiter call to discuss background and role.
  • Hiring Manager chat about your experience and fit.
  • Portfolio presentation to a panel of designers.
Philo logo
Philo

Senior IT Engineer

Operations · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Technical Presentation

The interview process was pretty standard, starting with a phone screen with the recruiter. For this role, they apparently have candidates complete an exercise focused on communication skills. This exercise involves tasks like drafting company-wide and leadership communications via Slack, writing basic documentation, and creating a vendor evaluation template. Your performance on this exercise acts as the initial screening, determining if you proceed to further interviews.

Confirmed questions3 questions
  • Craft Slack messages for two scenarios: one to all employees about a critical MacOS security update (urgent, timeline, how-to) in a friendly, helpful, simple, and concise manner, and another to an IT stakeholders channel proposing an SSO policy for SaaS app requests, detailing criteria (e.g., usage, cost) and reasoning.
  • Document the setup of new Zoom phone numbers, including a shared switchboard/IVR and specific department lines (Recruiting, Accounting, People team), explaining their functions, end-user instructions, and configuration details for IT personnel.
  • Develop a vendor evaluation template for selecting an MDM solution, specifying key criteria (must-haves vs. nice-to-haves) and the testing/evaluation process for making a selection.
Philo logo
Philo

Customer Support Representative

Operations

Entry Easy Negative experience No offer 1 round
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

So my resume got looked at and then I got put into the phone screening phase. The interview itself was decent, like, standard interview questions, lasted about 30-40 minutes. I thought it went well and I answered the questions they threw at me pretty well. Then, the very next day, I got an email saying they decided not to go forward with my application. I was curious what the reason was, so I hit up the interviewer. He mentioned his manager was actually looking for folks with experience in things like logistics management for business process outsourcing or using Jira/Atlassian for bug tracking, stuff like that. Which is whatever, but that wasn't what the job description said, and they didn't even ask me one question about those skills during the interview. Plus, those skills aren't really what you'd expect for a typical customer support job. Honestly, it felt pretty sloppy and unorganized. A company should really figure out what they need before they post jobs and make sure the descriptions match. So yeah, the whole experience was pretty bad, and I hope they get their act together.

Confirmed questions1 question
  • Can you discuss your previous work history?
Philo logo
Philo

Software Engineer

Engineering

Entry Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Onsite
Interview formats
Coding

I saw the job posting and it sounded like a great fit, so I reached out to the recruiter. We talked, and then they sent me a take-home assignment to do on my own time. I mentioned I might need a couple days because I was planning a trip, and they were cool with it. But, I got really into the assignment and finished it that same night. They liked what I did and set up an on-site interview for the following week. Since I lived in another state, they covered my flights and put me in a nice hotel close to the office. The company feels pretty relaxed but also driven; it was definitely stressful interviewing, but also cool to hear about how the company is growing and what they want to achieve. After meeting some people and seeing the place, I was hoping to get an offer.

Confirmed questions1 question
  • Were you able to install our application?

Philo Interview Questions

Quoted word for word from Philo interview reports.

Implement a web server that can prioritize and deprioritize different types of connections.

Read reports

Could you describe the system design and architecture for a website?

Read report

In your view, what constitutes diversity and inclusion?

Read report

When talking to a front-end developer on the team, I was asked about how I would annotate for handoff.

Read report

Formats, difficulty and experience

Across all 31 Philo interview reports.

Interview formats

Behavioral 29.5%
Technical 23.1%
Presentation 17.9%
Coding 16.7%
System Design 5.1%

Interview difficulty

Easy 16.1%
Average 74.2%
Difficult 9.7%

Candidate experience

Positive 35.5%
Negative 54.8%
Neutral 9.7%

Reports by job function

Engineering 13
Design 5
Marketing 5
Operations 4
Analytics 2
Product 1