Business Data Analyst by alignment.
Technical Solutions Designer by instinct.
System operator built from friction — not theory.
Official: Software Systems Business Analyst
Actual: I translate field dysfunction into structured logic.
Using Python, Excel, teardown workflows, and behavior-aware scripting.
Not tool-centered — failure-pattern centered.
Most of what I work on wasn’t broken loudly — just neglected until it mattered.
I observe where friction lives — in forms, flows, overlooked steps.
Then I map what breaks, trace to repeat logic, and patch it:
automation, teardown, deletion, or reframing.
Quiet fixes. Durable outcomes.
I rebuild civic workflows, reporting pipelines, clinical forms, map user needs.
Sometimes I delete 27 useless steps. Sometimes I script.
Dashboards ≠ delivery.
Reporting is structure — not aesthetic.
Too many “polished” apps collapse in the real world.
If your platform fails under pressure, I’ll find it.
I don’t chase polish. I deliver logic that doesn’t need retraining.
Languages: Python (pandas, openpyxl), SQL, R (used tactically)
BI Tools: Excel (pivot logic + automation), Power BI, Tableau, Looker
Ops/GIS: ArcGIS Pro, MS Access, Outlook scripting, Sheets
Infra: GitHub, automation pipelines, modular logic
Modality: No-code, low-code, script — I use what fits the fracture
Credly Badge Vault →
(Yes, I have badges. But more importantly — I build systems that don’t ghost users.)
Now: Business Data Analyst / Reporting Automation Analyst
Always: Logic builder with TSD instincts
Next: Data Systems Operator. UX debugger. Pipeline stabilizer.
If polish matters more than flow — I’m not your guy.
If you want pipelines that don’t collapse — maybe we talk.
#fromukrainianswithlovetohumankind 🇺🇦