Proofpoint logo

Proofpoint Software Engineer Interview Questions
& Process

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

Based on 60 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Proofpoint.

Showing 3 of 60
Proofpoint logo
Proofpoint

Software Developer

Engineering · nearly a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Take home Technical screen
Interview formats
Technical Coding

The process included an HR screen, followed by a 1-hour technical interview focusing on fundamental data structures and algorithms. Then, there was a 2-hour technical interview covering SQL and database concepts. Additionally, a small Java assessment was required.

Confirmed questions2 questions
  • Could you answer some questions about SQL queries and database concepts?
  • Tell me about database related questions.
Proofpoint logo
Proofpoint

Software Engineer

Engineering · a year ago

Entry Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

First, there was a phone call with the recruiter to talk about my background and experience. Then, I had a call with the group lead where we talked about my experience, responsibilities, and the technologies I've used. After that, I was ghosted, and didn't hear back, even after following up.

Confirmed questions1 question
  • Can you tell me about your institutional experience?
Proofpoint logo
Proofpoint

Senior Software Engineer

Engineering · more than a year ago

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

So I interviewed with Proofpoint and the team was really great, very professional and cool from the hiring manager to the other engineers. I had a take home assessment, then a technical screen, and then an onsite interview. I even got to talk to some really senior folks, VPs and stuff. They gave me good feedback and I got a verbal offer and then a written one too. But then the negotiations got weird. The recruiter kept saying he was working on getting approval for the number we discussed and made it seem like it was just a formality. Then, after a few days of making me think I had the offer locked down, they just rescinded the verbal offer and said they were going with someone else. I was expecting a final offer with a deadline to accept or reject, but instead, it was super unprofessional and they weren't transparent at all. Definitely not interviewing there again.

Confirmed questions6 questions
  • How did you approach the take home assessment?
  • What was your process for the technical screen?
  • Describe your experience with system design.

Proofpoint Software Engineer Interview Questions

Quoted word for word from Proofpoint interview reports.

What is the most recent common ancestor of a binary search tree?

Read reports

Can you write a function that takes a number and determines if it's a power of 2?

Read reports

Can you determine if a string is a palindrome without using any data structures?

Read reports

Regarding graphs, how would you find all neighbors of a given node?

Read reports

Design an algorithm to calculate the sum of numbers, given an example like 1 + 2 + 6.

Read report

Could you write a regex for combinations of 'a' followed by 'b' where 'b' can repeat any number of times, but 'a' cannot appear consecutively, using only *, ?, +, union, and grouping, and avoiding lookahead/lookback?

Read report

How would you check if a string is a palindrome using a data structure, and what is the reasoning behind that approach?

Read report

Could you write C++ code to implement a read-write lock?

Read report

What's a strategy for locating Social Security Numbers within a dataset of 50,000 log files?

Read report

Formats, difficulty and experience

Across all 60 Proofpoint interview reports.

Interview formats

Technical 39.4%
Behavioral 31.5%
Coding 22.8%
System Design 4.7%
Presentation 1.6%

Interview difficulty

Easy 30%
Average 60%
Difficult 10%

Candidate experience

Negative 33.3%
Positive 50%
Neutral 16.7%