Architecture, audits, and technical planning
Target architecture, risk reviews, API boundaries, and delivery plans for projects that need clear technical decisions before more code is written.
What I actually deliver.
PHP/Symfony backends and APIs
Business logic, integrations, queues, data models, and APIs for products, SaaS platforms, and internal systems.
Web apps, SPAs, and frontend systems
Customer-facing apps, internal tools, dashboards, and admin surfaces with the same attention to speed, clarity, and maintainability as the backend.
Modernization and legacy rescue
Incremental rewrites, strangler migrations, framework upgrades, and platform cleanup without months of disruption.
CI/CD, deployments, and custom servers
Pipelines, release automation, observability, container setups, and custom infrastructure when managed platforms do not fit the project reality.
Solo engineering lead, expandable when needed
I stay hands-on as the primary engineer. If scope or timeline grows, I can add additional developers or specialists and keep delivery coordinated through one technical lead.
Name the real constraint
The start is about the real problems: fragile releases, slowed-down teams, opaque legacy, broken integrations, or missing operational control.
Build the right slices first
Architecture, prioritization, and implementation are handled together. That produces useful increments instead of activity without real delivery.
Ship with operations in place
Deployments, monitoring, rollback paths, and documentation are part of the delivery so the system does not become a risk the moment it ships.
Typical engagements.
Most engagements start when a system needs to scale, integrate, modernize, or finally be delivered cleanly.
When a product needs a reliable core
Backends, admin tooling, integrations, and delivery structures for products that need to move beyond prototype quality.
When data has to move cleanly across systems
APIs and data flows for environments spanning SaaS tools, ERP, CRM, legacy systems, and internal services.
When growth or operations start stressing the system
Release hardening, observability, caching, queueing, and server architecture for phases where performance and stability become visible business concerns.
When an old platform must keep running while it is being renewed
A senior engineering partner who can own the difficult transition from the current system to a usable next version.
Recent thinking from the blog.
Interfaces that keep teams from working against each other
As soon as posts are available, they will render here automatically. Until then the homepage shows this placeholder.
Modernization without months of disruption
These cards stay in place but are automatically replaced by real blog content once entries exist in the system.
Observability that helps in day-to-day operations
Even without posts the layout remains complete. The data binding for future entries is already in place.
Contact
Describe what is blocked, fragile, or overdue. I will reply with a concrete next step.
The most useful messages include product context, the systems involved, and the delivery pressure behind the problem. Whether you need architecture help, hands-on implementation, or both is usually clear quickly. Replies typically go out within one business day.
Email
info@mdsolutions.swiss
Phone
+41 78 243 66 64
Location
Embrach, Canton Zurich. Remote and hybrid across Switzerland and Europe.
Working hours
Mon-Fri 09:00-18:00 CET, additional slots by arrangement.
Suitable for new products, existing platforms, API work, modernization, CI/CD, infrastructure, and frontend delivery.