About Marcelo · Professional profile
I’m Marcelo Ellwanger, a multilingual builder with a non-traditional engineering path across electrical work, operations management, international customer-facing roles and practical software development. I like understanding how systems behave, finding what is inefficient or unclear, and building something better around the real constraints.
My route into software wasn’t linear. The common thread was: understand the system, find the fault, and leave it better than I found it.
The path
I spent years doing electrical work in Canada, accumulating roughly 4,000 hours of hands-on experience with electrical and mechanical equipment, high- and low-voltage wiring, troubleshooting and work that had to be correct in the physical world.
At Alma on the Gold Coast, I managed the coffee side of an upscale all-day venue: employee scheduling, stock ordering, inventory awareness and specialty-coffee quality. Recipes and calibration were treated precisely, with professional baristas, premium equipment and measurements down to dose, yield and extraction time.
Software became the place where those instincts converged. I started solving problems I actually had: local AI workflows, resale research, unstable PCs, media organization and small desktop interfaces. Those projects became increasingly rigorous products rather than throwaway scripts.
I’m most interested in software where the messy parts matter: real hardware, imperfect data, human workflows and failures that need explaining.
Selected achievements
Built and released CrashScope 1.2, a local-first Windows crash-diagnostics system with a native WPF/WebView2 desktop shell, 266/266 automated .NET tests, persistent incident evidence, Event Log + WER correlation, ConfigTrace 1.0.1 provider integration and genuine second-PC validation.
Designed and built a local-first AI workstation manager with runtime safety, GGUF Model Intelligence, telemetry, Smart Launch recommendations, CI and live post-update smoke validation. Source available.
Built a provenance-first photo-to-decision resale pipeline that grew to hundreds of canonical items and more than a thousand physical observations while preserving evidence lineage and uncertainty.
Built a non-destructive WPF/.NET 10 local-media application with read-only multi-drive discovery, 219 automated tests, zero build warnings, validated installer + portable win-x64 artifacts, and a completed privacy-sanitization pass. MIT-licensed public source and the verified v1.4.0 release are live on GitHub.
Years of electrical work taught me to value failure modes, reproducibility, safety and systems that behave correctly outside a controlled demo.
International work across Canada, Australia and Japan developed a communication style built around adapting quickly, explaining clearly and working with people from different backgrounds.
Current engineering focus
Validated local-first Windows crash diagnostics with a native WPF/WebView2 desktop shell, persistent incidents, Event Log + WER evidence and privacy-safe support bundles. CrashScope 1.3 is the current development line; 1.2.0 remains the public release.
Open case study ↗1.4 RELEASED / WINDOWS LOCAL MEDIAEasyFlixA WPF/.NET 10 desktop application for legally acquired local media with read-only multi-drive scanning, unified shortcuts, artwork and quality-gated subtitle workflows that leave source media untouched. EasyFlix 1.4.0 is publicly released under MIT.
Open case study ↗Goals
Professionally, I’m targeting software engineering, QA / automation and technical systems roles where practical debugging, reliability and systems thinking matter. Local software, developer tools, automation, data systems and diagnostics are especially natural fits.
I’m also open to technical support or operations roles where strong communication, troubleshooting and independent work are central to the job. I can work flexibly across global time zones and schedules.
I want this site to work as a portfolio for employers, a professional introduction for collaborators and clients, and the URL or QR code I can put on a business card without needing a second explanation.
How I work
I prefer a real messy problem over a clean tutorial prompt. Constraints reveal the architecture.
Data provenance, explicit uncertainty and reproducible validation matter more than a confident-looking answer.
A bug should become a test, a clearer boundary or a product rule rather than something quietly patched around.
Monitoring, AI tooling and background automation should be conscious of CPU, RAM, GPU and user control.
Update, repair, diagnostics, idempotence and clear project state are part of the product, not post-release chores.
If software recommends, classifies or diagnoses something, I want the user to understand why.
Professional use
The website is the public overview; GitHub contains implementations and engineering notes. For remote roles, technical collaborations or project conversations, LinkedIn and the contact page are the current public routes.
For a business card, résumé footer or in-person introduction.
MARCELO