Payoneer Interview Experience | SSE | Rejected
Summary
I interviewed for a Senior Software Engineer position at Payoneer in Gurugram, cleared the low‑level design round but was rejected after the high‑level design round.
Full Experience
Recently I went did an interview with Payoneer(Gurugram) for SSE role.
Would like to share my interview experience.
- Approached by some outsourcing firm, talked about role and screening tech round was scheduled
- It was via third party service called Bar raiser.
- Problem was to design a working LLD solution(your choice of language) for an e-commerce site. They had a VS code IDEA in their platform with no auto suggestion/auto complete
- Cleared this round, On site was scheduled next day to their office
- First round was LLD about Splitwise, expectation was ER diagram, entities, control flow and efficient debt clearance with balance summary for each user.(It's a classic LLD problem). Cleared this
- Second round after ~2hrs. HLD round. Feed generator with emphasis on near real time feed update + scale of 100M. Talked about post service + fanout(push, pull both), fumbled a bit with back to envelope calculations.
Overall this round was good for me but not as good as first.
- After 30min recruiter said the profile was not selected for next round and asked to leave with saying feedback would be shared in 1-2 days(never got)
P.S: The recuiters were definetly under-prepared for this onsite. No clear management. Lots of delays btw rounds and most of all no refreshers :( If someone is coming to your office for whole day, atleast arrange some basic refreshers. No pantry/canteen in office(In my current firm, food is free, maybe I got spoiled!!!!)
Interview Questions (3)
LLD Design for E-commerce Site
Design a working low‑level design solution for an e‑commerce site using any programming language. The interview platform provides a VS Code‑like IDE without autocomplete or suggestions.
LLD Design for Splitwise‑like Debt Settlement
Create a low‑level design for a Splitwise‑style debt settlement system. Include an ER diagram, define the entities, describe the control flow, and propose an efficient algorithm for debt clearance with a balance summary for each user.
HLD Design for Real‑time Feed Generator
Design a high‑level architecture for a feed generator that supports near real‑time updates and must scale to 100 million users. Discuss the post service, fan‑out mechanisms (push and pull), and provide back‑of‑envelope calculations for scalability.