
Immonet GmbH // Axel Springer AG
Java EE Development for Real Estate Portal
Software Developer Java Enterprise
Relevance
Why this case matters
This framing makes the decision signal explicit: impact, proof, fit, and AI / delivery relevance for hiring or collaboration.
System impact
Early real-world agile and Scrum context in a Java EE real estate portal with multi-tier architecture, TDD, pairing, and portal reengineering.
AI / delivery relevance
This is not an AI case, but it is an important delivery origin: small feedback loops, testability, and shared product work.
Proof
Java EE
Enterprise stack
Scrum
Agile practice
TDD
Quality
Especially relevant for
- 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
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
- 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
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
Technical context
Technology stack
The tools are not the point by themselves. What matters is which system layers had to work together.
Backend
7Frontend
1Databases & Storage
4DevOps
3Tools
5Practices
5CI/CD & Delivery Pipelines
1Next step
If you want to explore similar leverage for hiring, collaboration, or a concrete transformation, this is the right starting point.
Send a short note about the situation you are trying to assess. I reply personally and will be direct about fit.