- Senior Tech Lead
- Software Architect (Full-Stack)
- End-to-end ownership
Recruiter
Profile
Freelance Software Architect and hands-on Tech Lead for complex full-stack and platform projects. I focus on systems where architecture truly matters and responsibility is not delegated. I design robust solutions and take end-to-end ownership — from concept and architecture to stable production operation.
This page is intended for quick technical assessment in recruiting — concise, structured, and decision-oriented.
Quick Assessment
I am a strong fit if you are looking for a senior professional who structures complexity, drives technical decision-making, and independently delivers critical components — including production responsibility.
Requirements Analysis & Structuring
I turn unclear goals, dependencies, and risks into a clear delivery plan and translate business requirements into robust architecture and API designs, drawing on long-term experience with microservices, event-driven systems, and cloud platforms.
Legacy Modernization — Without Big Bang Rewrites
I modernize legacy systems incrementally and with controlled risk, avoiding unstable big-bang rewrites while keeping production stable and risks manageable from the start.
End-to-end Ownership
I take full responsibility end to end — from architectural decisions and implementation to quality assurance and production-grade operations, ensuring sustainable and maintainable releases.
Technical Enablement & Standards
I support existing teams through code reviews, mentoring, and clear technical standards to ensure consistent quality and long-term knowledge retention within the organization.
Quick fit check
A brief assessment to determine whether the role and project context are a good match for my profile.
Good fit
- ✓Senior or lead roles with clear end-to-end responsibility
- ✓
Full-stack systems or focused backend/frontend roles with architectural responsibility
- ✓Modernization, migration, or continued development of production systems
- ✓API-centric architectures with clear system boundaries (REST, GraphQL, OpenAPI)
- ✓Domain-driven product environments with high technical and business complexity
Not a fit
- ×Roles without technical decision-making authority
- ×Projects without a clear product owner or decision mandate
- ×
Permanent on-site requirements without a realistic remote option
Competencies
Architecture & APIs
- Full-stack system architectures
- Microservices & platform architectures
- REST, GraphQL, OpenAPI
- API-first & domain-driven design
- Security & IAM (Keycloak)
Engineering & Core Technologies
- Java / Kotlin (Spring Boot)
- TypeScript
- React & Material UI
- SQL & NoSQL (Neo4j, InfluxDB)
Cloud & Operations
- Google Cloud (Pub/Sub, Storage)
- Docker, Kubernetes, Helm
- CI/CD pipelines (design & integration)
- Observability (Prometheus, Grafana)
Testing & Delivery
- Unit & integration testing
- BDD (Cucumber)
- End-to-end testing
- Agile product delivery (Scrum / Kanban)
Project Highlights
Selection of projects with focus on measurable economic success.
Building a Platform for Automated Regulatory Reporting
Platform Architecture
End-to-End Technical Ownership
Regulatory reporting requirements
The Initial Situation
Regulatory reporting for electricity, heating, and gas consumption was largely handled manually, resulting in significant operational overhead. The existing process focused solely on producing mandatory reports for authorities, while the collected data was not reusable for downstream business or analytical use cases. With a growing number of metering devices, this approach became economically unsustainable and posed a scalability risk.
The Objectives
- Fully automate regulatory reporting processes
- Enable on-demand generation of regulatory reports
- Build a scalable and extensible data platform beyond pure regulatory needs
My Approach
As Tech Lead with full end-to-end responsibility, I designed the overall platform architecture and led its implementation. I defined clear system boundaries for data ingestion, normalization, aggregation, and reporting, ensuring independent scalability, clean separation of concerns, and long-term extensibility.
The Result
Manual reporting processes were completely eliminated and replaced by automated, on-demand generation of regulatory reports. The platform now serves as a scalable data foundation, enabling additional business and analytical use cases beyond mandatory compliance reporting.
Technology Stack
Strategic Database Decision & Migration from ArangoDB to Neo4j
Architecture Decision-Making
Migration Risk Reduction
Database Strategy
The Initial Situation
As part of a platform migration, an existing ArangoDB-based solution had to be replaced due to rising costs and growing complexity. The strategic choice was between introducing a graph-native database (Neo4j) or adopting a more complex multi-database alternative. This decision had to be validated quickly to avoid delivery delays and long-term architectural risk.
The Objectives
- Design and implement a focused Neo4j proof of concept for key use cases
- Perform graph modeling and evaluate performance and maintainability risks
- Provide a solid, decision-ready foundation for management
My Approach
I evaluated architectural options under significant delivery pressure by designing and implementing a focused proof of concept covering the platform’s core use cases. In parallel, I supported the team in transitioning existing data access logic into a production-ready graph-based model.
The Result
The proof of concept enabled a fast and well-founded architectural decision. Migration risk was significantly reduced, allowing the platform transition to be completed within the committed timeline and without introducing unnecessary complexity.
Technology Stack
Legacy Modernization — Replacing Vignette StoryServer Without a Full Rewrite
Risk Reduction
Cost Optimization
Legacy Modernization
The Initial Situation
A legacy CMS caused high and continuously increasing operating and licensing costs and had to be replaced. The originally planned full rewrite exceeded time and budget constraints and introduced additional licensing risks, putting overall project delivery at risk.
The Objectives
- Replace the legacy CMS within strict time and budget constraints
- Ensure full functional equivalence in production under significant delivery pressure
My Approach
I challenged the rewrite-based approach and designed an alternative solution that preserved the existing business logic. By executing the legacy templates in a modern application runtime, the dependency on the original CMS runtime was fully removed.
The Result
A full rewrite was avoided, significantly reducing migration effort, risk, and cost. The legacy system was successfully replaced on time and within budget, without introducing new vendor or licensing dependencies.
Technology Stack
Working Approach
You build it, you run it — I make architecture and implementation decisions with production viability in mind. Risks are identified early, actively reduced, and owned — not passed on.
Initial Phase: Clarity & Decision Foundation
- Clear definition of target state and scope
- Transparent assessment of technical risks (including POCs where appropriate)
- Executable roadmap for incremental, production-safe delivery
Delivery: Production-Ready Reference Components
- Hands-on implementation of critical core components (services, APIs, optional frontend integration)
- Quality from day one: tests, observability, clean interfaces
- Structured handover enabling teams to continue independently
Contact / Quick Fit Check
For a quick assessment, 3–5 bullet points are sufficient. I’ll respond promptly with a clear fit / no-fit and a concrete next step.