Property Finder Software Engineer (SDE) Interview
Medium coding, a signature whiteboard class-diagram/OOP round, portal-scale search design, and a values deep-dive.
Start the Property Finder mock interview → See all boards
A free AI panel interview that questions you in Property Finder’s style, follows up when an answer is thin, and returns a scored, evidence-backed report — seeded from your own practice history on Wrexa Edge.
The Property Finder interview, in brief
Property Finder is the leading proptech / real-estate portal in MENA and a Dubai-based unicorn, connecting property seekers with agents and developers across the region. Engineering is 100+ engineers across Dubai and Istanbul, organised into agile squads on a modern stack (AWS, Go, Next.js, React, React Native), with an ownership-heavy, "speed beats perfection" culture and portal-scale search/geo problems.
A common shape is an HR introductory call, a technical phone screen (one LeetCode-medium problem such as a prefix-sum calculation), and a breadth-heavy HackerRank online assessment mixing CS-fundamentals and security with coding. The virtual/on-site loop adds a coding round, a standard system-design round, a signature OOP/class-diagram (LLD) round on a whiteboard tool with no coding, a design-flavoured coding problem, and a behavioural round with the hiring manager that follows up hard on your projects.
Interview rounds
-
1. HR introductory call 15–30 min
-
2. Technical phone screen ~45 min · 1 LeetCode-medium
-
3. Online assessment HackerRank · breadth-heavy (~17 items / ~75 min)
-
4. Coding round LeetCode-medium
-
5. OOP / class-diagram (LLD) Whiteboard tool · no coding
-
6. System design + behavioural Portal scale + values
Coding & DSA topics
System design
Two design surfaces. First, a standard system-design round at proptech-portal scale: property search and filtering, listings ingestion, geo/location search, ranking, high-read traffic and caching. Second, the distinctive class-diagram/OOP LLD round on a whiteboard tool — model classes and relationships with no code. Frontend roles also get component design.
Behavioural round
Property Finder publishes five values: Think Future First; Data Beats Opinions, Speed Beats Perfection; Optimise for Impact; Act Like An Owner; and The Biggest Risk is Taking No Risk at All. Behavioural rounds probe ownership, measurable impact over effort, data-driven decisions and calculated risk — with deep technical follow-ups on any project you claim, so be ready to defend your architecture and decisions.
Representative question categories
Patterns in Property Finder’s style — not verbatim proprietary questions.
- Prefix sums & arrays — Array-calculation medium problem on the phone screen.
- CS fundamentals & security — Complexity, data structures and security-flavoured quiz items in the assessment.
- Class-diagram / OOP — Model classes and relationships for a domain on a whiteboard — no code.
- Portal system design — Design property search / geo-search / listings at read-heavy scale.
- Big-O reasoning — Explain and justify the complexity of your solution.
- Ownership & impact — An "act like an owner" story with metrics, plus a project deep-dive.
How to prepare
Do
- Manage the clock on the breadth-heavy HackerRank assessment — many CS-fundamentals and security items in about 75 minutes.
- Prepare OOP/LLD explicitly — practise modelling classes and relationships on a whiteboard, since it is a separate gated round.
- Anchor answers to the five values, especially "Act Like An Owner" and "Optimise for Impact"; bring metrics and impact.
- Be ready for hard project deep-dives — interviewers follow up on anything you claim to have built.
Avoid
- Preparing only LeetCode and being caught off-guard by the class-diagram / OOP design round.
- Underestimating the CS-fundamentals and security portion of the assessment and running out of time.
- Telling effort-narratives with no measurable impact — their culture explicitly values impact over effort.
- Vague or unowned project stories that collapse under technical follow-up.
Who can apply
Public titles include Software Engineer (Frontend/Backend), Senior Software Engineer, Engineering Manager and Principal, plus DevOps/Security roles. Postings commonly target roughly four to six-plus years of experience; new-grad hiring and a formal graduate program are not publicly documented. The org is squad-based across Dubai and Istanbul.
Property Finder interview FAQ
- What is the Property Finder class-diagram round?
- A signature low-level-design round where you illustrate classes, responsibilities and relationships on a whiteboard tool with no coding. It is assessed on the model — clear responsibilities, correct relationships and extensibility — not on syntax.
- What is on the Property Finder online assessment?
- A breadth-heavy HackerRank test — candidates report around 17 items in roughly 75 minutes — mixing CS-fundamentals and security questions with coding. Manage your time; the breadth catches people out. Counts are approximate and role-dependent.
- How hard is Property Finder's coding interview?
- Coding is LeetCode-medium (for example prefix-sum / array-calculation problems); it is not a hard-algorithm gauntlet. There is more emphasis on OOP design and CS fundamentals than on exotic algorithms.
- What are Property Finder's values?
- Five: Think Future First; Data Beats Opinions, Speed Beats Perfection; Optimise for Impact; Act Like An Owner; and The Biggest Risk is Taking No Risk at All. Behavioural rounds probe impact over effort and follow up hard on your projects.
Practise now
Rehearse the full loop with an AI panel modelled on Property Finder’s process, in text, voice, or video.
Other company interviews
Verified from
- Property Finder — Our Culture (values)
- Property Finder — Engineering
- Glassdoor — Property Finder Software Engineer interviews
Wrexa Edge is an independent exam-prep platform and is not affiliated with, authorised by, or endorsed by Property Finder. This guide is based on publicly documented interview practice; it does not reproduce any employer’s internal rubric or question bank, and it does not predict a hiring outcome.