Roomster shared-housing marketplace

Shared housing is the hardest kind of marketplace to run, for a reason that has nothing to do with software: the transaction is not a purchase, it is moving in with a stranger. Both sides are exposed. A renter can lose a deposit to a listing that does not exist; a host can end up living with someone who misrepresented themselves. The stakes are high, the money moves off-platform, and the people involved are frequently at their most vulnerable — new to a city, new to a country, in a hurry.

That shapes every engineering decision downstream of it. Fraud is not an edge case to be handled later; it is the adversary the product is designed against, and it adapts. Liquidity is local rather than global — a hundred thousand listings in the wrong city is the same as none. And the same flows have to work identically for someone searching in Los Angeles and someone searching in Warsaw, on a mid-range Android phone, in the eighteenth of eighteen supported languages.

• Phone and email validation at signup, so an account has a cost to create.
• ID validation combining automated checks with human moderator review — the two catch different things, which is why both exist.
• Automated content filters against scam and spam patterns, running continuously rather than at submission only.
• Validated badges, plus user reporting and blocking, so the community itself is part of the detection surface.

Embedded senior engineering: our team works inside Roomster's process and repositories, delivering alongside their in-house engineers. What an engagement like this supplies is sustained capacity at global-marketplace scale — throughput that stays consistent across the feature work, the platform work and the operational hardening a system of this size demands, without the client having to re-explain the domain every quarter.