Max Gobeil
Software Engineer & Technical Lead
I build systems by understanding the business first, then writing the code that actually fits it.
Business-First Engineering
I don't just implement requirements. I dig until I find the actual problem underneath them. That's led to rebuilding core systems from scratch after spotting where the real bottlenecks were, not just where I was told to look.
End-to-End Ownership
Architecture, code, infrastructure, deployment, and the process around it. I've run all of it solo, and I've led teams through it: code review, patterns, mentoring, so the work stays maintainable by more than one person.
Fast, Accurate Reads on Unfamiliar Systems
I tend to map out how an organization actually works faster than expected. That's usually where the real opportunities to improve things become visible, often before anyone else has finished mapping the current state.
Notable Projects
Custom ERP System
Architected and built a full ERP system from the ground up for a multi-site healthcare operation, including patient management, inventory, purchasing, SMS communication, and custom reporting. Migrated production infrastructure off Azure to a self-managed stack, cutting hosting costs by ~96% while improving control and uptime.
Custom Quoting & CRM Platform
Designed and built a platform for a line striping business covering quote creation, digital signature capture, inventory, sales tracking, and CRM. Took the business from manual quoting to a streamlined digital process end-to-end.
View WebsiteIoT Irrigation and Field Monitoring System
Built an IoT monitoring system for irrigation and field conditions. Built a sensor data pipeline into PostgreSQL/TimescaleDB, a real-time web dashboard, and a mobile app for visualization, with automated alerts for critical conditions like frost.
What I Bring to the Table
Sees the System, Not Just the Task
I default to understanding why something works the way it does until I can see the shape of the whole system, not just the piece I was asked to look at. That's where most of the real improvements live.
Technical & Business Fluency, Both Ways
I can sit across from a non-technical stakeholder and translate their actual problem into a clear technical plan, and just as easily sit with a dev team and go deep on architecture and tradeoffs.
Builds for the Team, Not Just for Today
Code that I write, or that I have a team write, is built to be understood and extended by someone else later. Patterns, structure, and code review aren't an afterthought; they're how the work stays fast six months in instead of just on day one.