The Problem
ImmoScout24 is one of the most-used real-estate platforms in Austria and part of the wider Scout24 group. The work sat inside a mature distributed system: search and listing flows, SEO-sensitive pages, marketing automation, and integration points that had to keep working under normal product delivery pressure.
The existing system already had strong unit, integration, and e2e coverage. My contribution was not a rewrite. It was the work of getting productive in that environment, making targeted changes, and matching the team's expectations for testing, review quality, and production safety.
My Biggest Challenge
The steepest learning curve was adapting to the quality expectations of a DAX-listed engineering organization. The codebase was tested at every layer across distributed services, with SSO federated from Scout24's German platform. Small changes still required clear reasoning, good test coverage, and careful review.
I had to level up my testing discipline, communicate more precisely with senior engineers, and learn when to sync with my mentor. That calibration mattered: ask too early and you create noise; wait too long and you block delivery.
What I Delivered
UX Improvements
Shipped focused improvements in search and listing flows, with changes reviewed against an existing product and testing culture rather than a greenfield codebase.
SEO-Sensitive Delivery
Worked on technical SEO changes where page structure, rendering behavior, and release quality had direct product impact. The team tracked organic visibility closely, so regressions had to be avoided.
Marketing Automation (Iterable)
Integrated Iterable so marketing teams could run targeted campaigns and automate lifecycle messaging without depending on engineering for every campaign change.
Enricher Task Upgrades
Upgraded the functional programming-style enricher tasks that process and transform property data — improving reliability and maintainability of the data pipeline.
Business Impact
The impact was practical: SEO changes supported organic visibility, UX work contributed to engagement, and Iterable reduced the amount of engineering effort needed for marketing campaigns. Some exact business metrics are not mine to disclose in detail, so I keep the public proof focused on the work I owned and the production context it shipped into.
For a contract buyer, the useful signal is not a greenfield demo. It is evidence that I can enter a mature system, respect the quality bar, and ship targeted product/integration changes without increasing release risk.
What I Took Away
This project changed my default expectations for test coverage and review quality. A fully tested distributed system does not remove the need for judgment; it gives good engineers the confidence to make smaller, better-scoped changes.
On the human side, I learned when to reach out to a mentor and when to push through on my own. That calibration — knowing when to sync and when to execute — is something I now consider a core part of how I operate in any team.