Employed as an application developer with focus on production-stable integration flows.
Personal Context
About
Integration developer focused on stable data workflows in day-to-day operations.
Profile Snapshot
- Entry via retraining with early full-time employment during that phase.
- Current focus: B2B integration between ERP, TMS, and platform systems.
- Distance-learning B.Sc. in Computer Science currently starting.
- Collaboration model: remote-first, German/English, DACH focus.
Employed Application Developer Distance B.Sc. CS Remote DACH
Patrick Scharf works as a fully remote employed software developer and supports teams in stabilizing long-grown system landscapes. Core focus areas are API integration, data mapping, legacy modernization, and Lobster Data implementation in live environments.
Patrick Scharf built this path through practical delivery: entry via vocational retraining in software application development, early employment already during that phase, structured self-driven implementation, ownership in production contexts, and iterative hardening under operational load. Instead of large disruptive rewrites, the delivery model prioritizes small, reversible changes with controlled risk.
Current project focus is B2B integration between ERP, TMS, and external platform contexts. Long term, Patrick Scharf is expanding this track toward SAP-adjacent integration engineering. In parallel, a distance-learning B.Sc. in Computer Science is currently starting to deepen practical engineering experience with formal academic grounding. Delivery language is German plus professional English, with primary collaboration in the DACH region.
Entry via Retraining
Hired as an application developer during retraining and further sharpened through live operations.
Remote-first execution
Fully remote collaboration with structured handover and clear technical documentation.
DACH focus
German and English delivery for European enterprise system landscapes.
Technology Stack
PHP MySQL Python Docker Git Linux Lobster Data REST APIs C# Redis
How I Work
Delivery starts with structured problem analysis: affected process paths, real incident patterns, dependencies, and operational impact are mapped before implementation.
Changes are shipped in small, reversible increments with explicit rollback paths instead of big-bang transitions. This keeps risk controlled while preserving delivery momentum.
Technical decisions are documented so handover and future extension remain transparent and not dependent on individual memory.
If you want to discuss an integration or modernization initiative: Discuss your project