
Immonet GmbH // Axel Springer AG
Java EE Development for Real Estate Portal
Software Developer Java Enterprise
Relevance
Why this case matters
The case shows how problem understanding, responsibility, decisions, and implementation came together in this context.
Impact
Owned customer-facing search in a Java EE real estate portal with multi-tier architecture, TDD, pairing, Jenkins deployments, and production-near application monitoring.
What carries forward today
Small feedback loops, testability, and shared product responsibility form the delivery foundation that modern AI-assisted work still depends on.
Defensible proof
Java EE
Enterprise stack
Used EJB, JPA/Hibernate, MySQL, Tomcat/JBoss, and PL/SQL in portal development.
Scrum
Agile practice
User stories, sprint planning, retrospectives, and pair programming in a real product context.
TDD
Quality
Used JUnit, Mockito, and Selenium for test-driven development and quality assurance.
Where this experience creates value
- For teams that want to see agile practice before later leadership roles.
- For organizations with classic enterprise systems that need maintainable product development.
Case context
Overview
In the customer-facing real-estate search team, I owned work from problem definition through concept, implementation, and delivery to Jenkins deployments, log analysis, and application monitoring. Dedicated administrators owned the underlying platform operations. Immonet's web-based real estate portal combined Java multi-tier architecture, complex development tasks, software ergonomics, and reengineering for better portal usage.
Scrum with user stories, sprint planning, retrospectives, and pair programming shaped the delivery work. Test-driven development, continuous integration, and code review supported quality; conceptualization, design, and forward-/reverse-engineering supported the architecture.
Responsibility
Activities
- Java Enterprise Development: Multi-tier architecture, EJB 3.1, JPA/Hibernate for real estate portal
- Real Estate Search: Owned customer-facing search functionality and behavior end to end within the portal team
- Complex Problem Solving: Analysis and solution of complex development tasks, software ergonomics
- Architecture & Design: Conceptualization, design, forward-/reverse-engineering for scalable solutions
- Quality Assurance: Test-Driven Development, code review, pair programming, continuous integration
- Production Proximity: Jenkins deployments, log access, and monitoring of the team's applications in collaboration with administrators
Operating mode
Methodology
- SCRUM Framework: User stories, sprint planning, retrospectives, sprint reviews, scrum of scrums
- Agile Development: Pair programming, code review, refactoring, continuous integration
- Test-Driven Development: JUnit, Mockito, Selenium, quality assurance, automated testing
- Architecture Design: Conceptualization, design, forward-/reverse-engineering, software ergonomics
- Shared Production Responsibility: Deployment and application monitoring in the product team, with underlying operations owned by dedicated administrators
Technical context
Technology stack
The tools are not the point by themselves. What matters is which system layers had to work together.
DevOps
4Backend
8Frontend
1Databases & Storage
4Tools
5Practices
5CI/CD & Delivery Pipelines
1Next step
If you need similar responsibility, we can identify the next useful leverage point directly.
Send the situation, goal, and decision in front of you. I will respond personally with a clear view of the value I could add.