PFL logo

PFL Software Engineer Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

4.4 Rounds average
Average Typical difficulty
75% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at PFL.

Showing 3 of 8
PFL logo
PFL

Software Developer

Engineering · more than a year ago

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

I really liked interviewing here. The HR person I talked to was super professional and always gave me good feedback, encouragement, and was really easy to get ahold of. First, I talked to 2 developers who asked me some basic get-to-know-you questions and some technical ones about my background. Then, I got a programming project that took me about a week. After that, I had an hour-long phone chat with HR about my work history. The last part was 3 separate meetings with 6 people, including the CTO. They asked some deep questions to see if I'd be a good fit and if I'd like it there. Everyone was professional and encouraging, and the company culture seemed great. It was tough and took a while, but I get that they're serious about hiring the right people. My impression is that PFL is a top-notch company with smart, supportive people. Definitely recommend!

Confirmed questions3 questions
  • What are your career goals?
  • Where do you see your career going?
  • What's your career path look like?
PFL logo
PFL

Software Developer

Engineering · more than a year ago

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

The interview process kicked off with a phone screen from HR. The HR person was very professional and nice, and the chat went well. After that, I had a call with the CTO the next day. They asked more about my technical background, but there weren't any real technical questions. It was a good chance to get a feel for the CTO's personality, and it was a really good experience. Then came a coding test, which felt like a pretty long step before the technical interview. It would be better if the code sample was shorter and the technical interview came first. I'm not sure how much the code test matters. I finished the minimum required for the code test, but if you only looked at the technical interview, you might think I'd never used C# before. The next stage was a technical video interview with lots of technical questions. These questions are good for seeing how much people know off the top of their head, but software development often involves looking up documentation for less common things, which might not show how well someone can build good applications. Still, this is their process and it works for them to find the right people. This company seemed very professional all the way through. Many companies don't even bother to tell candidates they weren't selected, but PFL actually called me to let me know what I needed to improve to join their team, which I thought was really professional.

Confirmed questions1 question
  • Can you explain what a struct is in C#?
PFL logo
PFL

Software Developer

Engineering · more than a year ago

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

It started with a standard phone screen with HR. Then, I had a call with the CTO who made me feel defensive about my background. The CTO then gave me a take-home coding project to build a shopping system using their API, covering everything from product display to checkout and order confirmation. Given the large scope, I focused on implementing a few key features with solid code, spending over 8 hours on it and using my own framework. I sent the completed project to HR. A few days later, I got an email from HR stating that based on my provided information, they didn't have a matching role, which I found inaccurate and unprofessional given the time I invested. Ironically, I used much of the same code in another interview and got an offer.

Confirmed questions1 question
  • Can you justify your senior developer title?

PFL Software Engineer Interview Questions

Quoted word for word from PFL interview reports.

What is the reason for normalizing a database from 1NF to 2NF?

Read reports

Could you write the code to generate a Fibonacci sequence?

Read reports

Tell me about your pets, specifically if you have a dog.

Read report

Describe your approach to designing and developing a large-scale social media platform similar to Twitter.

Read report

Formats, difficulty and experience

Across all 8 PFL interview reports.

Interview formats

Technical 29.2%
Coding 29.2%
Behavioral 25%
Presentation 8.3%
System Design 4.2%

Interview difficulty

Easy 0%
Average 50%
Difficult 50%

Candidate experience

Positive 75%
Negative 25%