Poshmark software engineer candidates describe DSA-heavy loops of four to five stages, with project deep-dives, system design and schema questions, and an HR or behavioral round. Timelines and feedback can be slow.
$155K
Avg. Base Comp
$182K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Poshmark's software engineer interviews as heavy on data structures and algorithms, with real depth on your own past projects. One candidate reports a sequence of an online assessment, a virtual technical round, an in-person round, a manager round and an HR conversation. Their questions covered stacks, sliding window, max product subarray, grouping anagrams and 2D matrix problems, and they felt difficulty rose across rounds.
A second candidate, interviewing for Software Engineer II, reports five rounds. DSA appeared in four of them, using arrays, hashmaps, sets, priority queues and linked lists. The rounds also covered databases, git, Elasticsearch, system design for previous work, and a schema design exercise. Interviewers kept returning to the decisions behind projects the candidate had built, so be ready to explain why you chose a design, not just what you shipped.
A third candidate, also for Software Engineer II, reports a four-round onsite covering coding, system design and behavioral interviews. They found the technical content substantive. They also describe disorganized logistics, a prep guide that arrived only the day before, and months of waiting without a clear decision. Ask early for the schedule, interviewers and a decision date.
One of the three candidates reports a rejection with no feedback, and one reports a stalled process that ended in withdrawal. Prepare for the technical bar, and plan to follow up on timing.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Poshmark process.
I'll start with how it ended, because that's the part I still think about. I withdrew from a Software Engineer II process at Poshmark after nearly four months, and nobody ever told me no. Nobody told me yes either.
The onsite was four rounds in June covering coding, system design, and behavioral interviews. The technical rounds were substantive, and I'm not complaining about difficulty. The logistics were a mess, though. I had to contact the recruiter from inside the office to confirm where I needed to be and when the interviewers would arrive. The recruiter openly admitted things were disorganized. A detailed technical prep guide did arrive, which helped, but only the day before the onsite, so I had almost no time to use it.
Afterward, the recruiter called my feedback stellar and asked for a day or two to check with the team. A week-plus later I learned the team was stepping back from the role. The recruiter said I'd performed well and suggested other engineering openings, noting that my interview results could be reused so I wouldn't have to repeat the loop. Those openings froze within days.
Months later I saw the same SWE II role had been reposted and reached out. The recruiter said he'd raise me with the team. After a week of silence I followed up, and he said he had forwarded my old notes to the hiring manager. When I checked again and asked directly whether I was still under consideration, I was told the hiring manager had responded enthusiastically and I'd hear within a couple of days. Two days later, the hiring manager still needed to speak with several other people, and there was no timeline.
That's when I withdrew. The problem wasn't a rejection. I understand that companies freeze roles and weigh multiple candidates, and good feedback never guarantees an offer. Still, there's a real difference between an unfavorable decision and leaving a candidate in limbo for months with no endpoint.
Prep tip from this candidate
Ask the recruiter for the interviewer schedule and logistics well before the onsite, since the prep guide here arrived only the day before. If the team says a decision is pending, request a specific date and a named decision-maker, because open-ended timelines were the main source of frustration in this process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Poshmark
Find the average yearly purchases for each product
| Question | |
|---|---|
| Groups of Anagrams | |
| Rearranging Digits | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Random SQL Sample | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| P-value to a Layman | |
| Scrambled Tickets | |
| Delivery Estimate Model | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| Recurring Character | |
| Real-Time Transaction Streaming | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports starting with an online assessment before any live interviews. Other candidates do not describe this step, so it may not apply to every role or team. Prepare for coding problems on core data structures.
Candidates report DSA in most technical rounds, including stack, sliding window, max product subarray, anagram grouping and 2D matrix questions. Another candidate reports problems solvable with arrays, hashmaps, sets, priority queues and linked lists. Clean code and clear reasoning out loud were expected.
Candidates report rounds on system design, behavioral questions and previous projects. One describes a database schema exercise, plus questions on databases, git and Elasticsearch. Expect follow-ups testing the reasoning behind your own design choices, which may vary by interviewer and team.
Candidates report a manager round and a conversational HR round on culture fit and working style, though one says the order was swapped. Outcomes reported include no offer with no feedback, a withdrawal after months without a decision, and a declined offer. Ask recruiters for specific decision dates.
