Postscript logo

Postscript Interview Questions
& Process

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

Based on 55 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
43.6% Positive experience

Which role are you interviewing for?

21 roles · 55 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Postscript.

Showing 4 of 55
Postscript logo
Postscript

Customer Experience Advisor

Operations · a year ago

Senior Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral Technical

The recruiter got back to me quickly and I liked that I could book my own interview slot. But, the interview process is way too long and not organized at all. The recruiter asked the same questions as the hiring manager, who is a Director. This made me think about how they handle staffing and organization for this role. The hiring manager's questions felt repetitive and were all about my resume, which is quite extensive since I have 10 years of experience in this field. I would advise against wasting your time interviewing here. It became obvious they were just trying to get information about my current role for their own benefit, and they weren't planning to hire me. Also, if you're a woman of color, you should probably look somewhere else. There aren't any women of color here, and even though I've worked with many people and companies, this one clearly won't hire you for that reason. They also seem behind for a tech company, lacking workforce management tools and any clear daily work structure for this role. As advice for the interviewers, you should rephrase the reason for rejection to not say you're looking for someone with "deeper technical experience," because I'm certain no one currently employed or applying has more technical expertise than I do, and I'm considered overqualified but always happy to help.

Confirmed questions1 question
  • On a scale of 1 to 10, how would your manager from a decade ago evaluate you?
Postscript logo
Postscript

Software Engineer

Engineering · a year ago

Senior Average Neutral experience No offer 2 rounds
Interview process
Technical screen Take home Technical screen
Interview formats
Technical Coding Other

The interview started with a tech screen that was pretty chill and worked with my schedule. It gave me a good feel for the role and they asked some questions to see where I might fit in. The first coding screen was outsourced to Byteboard, which I usually find a bit iffy, but I gave it a shot. The first part was a 40-min tech doc review. Honestly, this part was super annoying because you don't get enough time to really read and get what they're asking. By the time I finished reading, I only had 7-10 mins left to go back, read comments, figure out what they wanted, and then suggest changes with pros & cons. It's like walking into a new job with zero clue about the app, goals, frameworks, or data, and then being expected to comment and suggest stuff in the first 30 minutes after a quick overview. I'd be kinda worried about anyone who's okay with that. I think they expect you to just comment as you read, but I like to read the whole thing first to get the full picture before suggesting anything. The second part was a 70-min coding assessment. Again, didn't feel like enough time to really understand the code and give the best solutions. I'd say if there weren't time limits, the difficulty would be easy to average. But with the time crunch, it's tough and seems to favor people who just dive in based on the specs. Overall, it wasn't good or bad. I bet the right person would do great with this style.

Confirmed questions5 questions
  • How would you extend an app for friends to find a midpoint to reduce travel for an activity, to support more than two friends?
  • If the app used one database per city, how would you scale it as it grows?
  • How would you tune the algorithm for suggesting activities using the provided data?
Postscript logo
Postscript

Front End Developer

Engineering · a year ago

Senior Average Neutral experience No offer 7 rounds
Interview process
Recruiter call Technical screen Phone screen Recruiter call Phone screen Recruiter call Phone screen
Interview formats
Coding Behavioral Technical

I started with a recruiter interview at Postscript in November 2024. Next, I did a technical assessment, which was pretty cool, mixing practical coding with talking about cross-functional teamwork. After that, things got a bit weird. I had an interview with the hiring manager, a normal chat, and they said I'd move on. But the next day, the recruiter told me the role was filled, though there was another job on a different team. I interviewed for that the following week, and it also went well. A few days later, the recruiter said that one was filled too. Then, last month, another position opened up. I talked to the recruiter and hiring manager again, moved to the next stage, and then was told a few days later this new role was also filled. It's frustrating because if they already had strong candidates, why interview me or move me forward only to reject me later? I don't think they meant any harm, and everyone was nice. I got a good vibe about their engineering culture. I'd probably interview there again, but their process seems to need some work.

Confirmed questions1 question
  • Review this product specification, identify areas needing clarity, and then explain how the feature would be built, considering either yourself or a less experienced developer as the implementer.
Postscript logo
Postscript

Operations

Operations · more than a year ago

Entry Easy Positive experience No offer 5 rounds
Interview process
Recruiter call Take home Presentation Onsite Onsite
Interview formats
Behavioral Presentation Behavioral

The first part was a 30 minute video call with the hiring manager. After that, I got a link for a homework exercise. I then presented the homework to the hiring manager and another team member. The final interviews were a values fit interview and an interview with leadership, each lasting 45 minutes. This process really made me feel positive about Postscript - it seemed like everyone truly enjoyed working there. A special thanks to Hannah S. for being so responsive and helpful!

Confirmed questions1 question
  • What do you consider your greatest strength at work?

Postscript Interview Questions

Quoted word for word from Postscript interview reports.

If the app used one database per city, how would you scale it as it grows?

Read reports

Could you implement a short feature to sort packages by size and weight during this live coding session?

Read reports

How would you design an efficient system for a scheduled SMS campaign?

Read report

What are your thoughts on Python idioms, data types, and performance?

Read report

If you had to rate your luck on a scale from 1 to 10, what would it be?

Read report

How would you extend an app for friends to find a midpoint to reduce travel for an activity, to support more than two friends?

Read report

Formats, difficulty and experience

Across all 55 Postscript interview reports.

Interview formats

Behavioral 38.9%
Technical 23.9%
Presentation 15%
Coding 13.3%
Other 4.4%

Interview difficulty

Easy 14.5%
Average 69.1%
Difficult 16.4%

Candidate experience

Positive 43.6%
Negative 43.6%
Neutral 12.7%

Reports by job function

Sales 21
Engineering 18
Operations 11
HR 3
Other 1
Marketing 1