Postscript Software Engineer Interview Questions
& Process

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.

First there's a recruiter screen and then they send you a ByteBoard test from Karat. Honestly, I'd say don't bother with any company that uses another company for their technical tests, especially Karat, it's a waste of your time and energy.

I did a take-home assignment for a task/volunteers app. It involved a design doc, which had some missing info and implementation ideas, and a coding exercise where a feature was missing.