Real, anonymous reports from people who interviewed for Software Engineer at Poshmark, newest first and distilled into what to expect across the loop.
I applied online and first received a standard rejection email from a recruiter. Then, later on, the same recruiter reached back out with the same position again—at that point, I couldn’t tell if it was genuine progress or just noise.
My process for Poshmark felt like it went too far into “real work” territory. I was given a heavy case study with a three-day deadline that covered global network and endpoint standardization, compliance, IAM design, rollout plans, and risk planning. It wasn’t framed like a small interview exercise—it looked like something a full team would normally own, and the time pressure made it feel unfair.
The interview process heavily emphasizes technical skills, particularly data structures and algorithms (DSA), with multiple rounds dedicated to coding challenges that resemble LeetCode problems. Candidates should prepare for a range of DSA topics, including arrays, stacks, and linked lists, as well as system design and optimization questions.
Some candidates experienced a case study that required them to present solutions to complex, real-world problems, including compliance and risk management, which felt more like a deliverable than a traditional interview exercise. This aspect tests not only technical skills but also structured thinking and project management abilities.
Interviews often include discussions with managers that assess both technical capabilities and cultural fit, focusing on how candidates approach problems and collaborate with teams. Candidates should be ready to demonstrate their interpersonal skills and alignment with company values during these rounds.
Candidates reported varying experiences with communication throughout the process, with some feeling a lack of transparency and timely feedback, particularly after rejections. It's important to remain proactive in seeking updates and clarifications during the interview process.
The overall interview structure is typically organized into multiple rounds, often starting with a coding assessment followed by technical interviews and concluding with HR discussions. Candidates should expect a relatively quick timeline, with some processes moving from initial screening to final interviews in a week.
The difficulty of the interviews can range from average to challenging, with a strong focus on problem-solving processes rather than just correct implementations. Candidates should be prepared to articulate their thought processes and reasoning during technical discussions.