Software Engineer applicants have rated the interview process at Paperless Post with 2.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 34.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 52 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Paperless Post overall takes an average of 33 days.
Common stages of the interview process at Paperless Post as a Software Engineer according to 4 Glassdoor interviews include:
One on one interview: 33%
Phone interview: 33%
Group panel interview: 17%
Skills test: 17%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 7 weeks. I interviewed at Paperless Post (New York, NY) in Aug 2016
Interview
Consisted of an 1 hour initial phone discussion, 1 hour technical phone discussion, and a 6 hour on-site interview. However, the recruiter always wanted to have briefing/debriefing calls, so it became challenging to coordinate everything.
Most companies try to find talented people, and then the role will develop. Paperless Post was hiring for 2 particular roles. However, they seemed rather in-flux throughout the process, including on-site, with me being sold sometimes for a certain role, sometimes the other.
Ultimately they told me they're not hiring for either of the roles, but want to stay in touch incase that changes.
I applied through a recruiter. I interviewed at Paperless Post in Sep 2025
Interview
recruiter cold emailed to then sent out assessment.
assessment was very easy and after that recruiter just ghosted even after 2-3 follow-up. Should not be wasting time for other if they're going to ghost.
Interview questions [1]
Question 1
React fundamental questions. Build a small feature to transform string using React.
I applied through a recruiter. I interviewed at Paperless Post
Interview
The first round was a HR conversation. The second round was a series of basic programming questions. Then we had a short programming exercise around an important frontend concept. Overall, the experience was very pleasant. I did not get the because it was a lead role.
Interview questions [1]
Question 1
What is the difference between == and ===?
How are keys used in react?