Quick facts
As a passionate Information Systems Engineer, I turn business goals into reliable processes & data products: Measurable, maintainable, human-friendly.
- RegionMunich Area, Bavaria (DE)/Salzburg (AT) · DACH-remote
- LanguagesGerman (C2), Czech (C2), English (C1)
- Role focusEnterprise Architecture (EA) · Business Analysis (BA) · Business Intelligence (BI) · (Process) Digitalization
- Tech stackSQL · Python · Power BI/Tableau · BPMN 2.0 · LC/RPA · Jira/Confluence
Impact
- Improved report creation speed
- Reduction in process throughput time
- Increased release frequency / month
- Great acceptance of new dashboards/reports in the business units
Source: Project artifacts like Jira/Confluence/BI usage and audit logs.
Selected Case Studies
Audit-ready for ISO 27001: Risks organized through protection requirements. Thus audits under control.
Summary
Ensured consistent control processes, prioritised risks, and supported audits with clear accountability and verifiable evidence.
What I did
- Cleaned up the risk register: Assessment, prioritization, action plan with SLAs.
- Audit support: tracked findings, assigned owners, documented closure paths.
- Architecture reviews: checked implementation against guidelines, closed gaps.
Impact
- Decreased number of critical findings
- Reduced time-to-close (days)
- Increased control coverage
Evidence: Positive reference (performance, autonomy, collaboration).
Stakeholders
IT-Management · Information Security
Change
Auditable regular checks · Clear ownership · Transparent roadmap
One language for Business & IT: Standards in, rework out
Summary
Unified requirements, KPIs, and process artifacts so business and production meant the same thing and hand-offs worked for the first time.
What I did
- Introduced and enforced templates for elicitation & specification.
- Workshops & enablement: Trained business teams to deliver clean inputs.
- Harmonized monitoring/reporting (KPI catalog, consistent dashboards).
Impact
- Decreased time-to-spec
- Decreased rework per change
- Increased report usage rate
Stakeholders
Product owners · Business · Engineering
Handoffs
Clear artifacts · Explicit acceptance · Precise requirements documents
Fewer surprises at go-live: Test strategy for card processing
Summary
Translated requirements into testable scenarios. Built targeted test cases, and tracked results with full traceability.
What I did
- Derived a test strategy (Critical paths, negative cases, regression).
- Created test-data & case library.
- Structured execution & logging.
- Established traceability (Requirement → Test case → Defect).
Impact
- Decreased error rate
- Increased test coverage
- Decreased Test/Release cycle time
Stakeholders
Business · Compliance · Operations
Change
Reproducible QA artifacts as a common decision base
Developing an understanding of the platform: Usability checks that cut rework
Summary
Tested throughout the rollout process and improved the portal through usability assessments/minor requirement changes.
What I did
- Defined test scenarios and documented results.
- Prioritised user insights and derived realisable improvements.
- Planned & facilitated workshops; accelerated decisions.
Impact
- Contribution to increased project success
- Reduced time required for tasks due to experience gained
- Increased cross-departmental usability
Stakeholders
Product · User Experience (UX) · Engineering
Assets
Requirement document fragments · Workshop notes · Processing test logs