Mike Bros
Software Engineer
Seeking: Senior Backend Engineer · Platform Engineer
Minneapolis · Remote
Robust distributed systems. 24,730 automated invoices created, 0 duplicate line items.
Idempotency, fault isolation, and ownership from day one.
About
Five years at one company, four promotions, and effectively four different jobs. Each role put me in a different part of the stack with different stakeholders: from frontline tech support for 250+ dealerships, to full-stack development across billing and integrations, to owning the invoicing pipeline with the CFO as my primary stakeholder, to leading a platform migration to Go on GCP. The codebase, team structure, and tech stack all changed substantially during that time. I stayed because the problems kept getting harder.
I've adapted more than the single employer suggests. In a startup environment I wore whatever hat the team needed: project management, QA, customer service, writing onboarding docs and LMS course content, building report queries alongside our data analyst, and acting as a de facto technical account manager for accounting because so much of their workflow runs through the platform I built. The tech stack changed underneath me too, from PHP monolith on DigitalOcean to Go microservices with React frontends on GCP. What I bring to a new team is the habit of finding the problem with the most potential for impact, taking ownership of it, and leaving it better than I found it. That works whether I wrote the original code or not.
What I'm Looking For
Small teams solving hard backend problems: billing, integrations, distributed systems. The kind of work where getting the contracts between services wrong costs real money.
Fully remote. I've built deep expertise at one company across six domains and two tech stacks. I'm looking for a team where that depth of ownership is valued, and where I can bring the same intensity to new problems.
Experience
Roof Maxx Technologies
Roof Maxx Technologies
Remote
From technical support to platform engineering — promoted four times through five years of building the systems that run the business.
Roof Maxx sells a plant-based bio-oil treatment that extends the life of asphalt shingle roofs by up to 15 years, at a fraction of the cost of a full replacement. The company delivers this through a nationwide franchise dealer network.
Roof Maxx Connect (RMC) is the platform I help build to power that network. It started as a territory-based lead routing engine that uses zipcode and census tract data to match homeowner leads to the right dealer. Dealers range from solo owner/operators to 30+ employee roofing companies, all truck-based with no fixed storefronts, so routing can't rely on simple proximity. Over time RMC grew into the operational backbone: warranty management, automated corporate invoicing, SMS workflows for sales and customer outreach, compliance enforcement, dealer webhook integrations, and job completion reporting.
Software Engineer II
Jun 2024 – Present-
›
Leading the platform's microservices migration from Laravel to Go on GCP with Pub/Sub and Cloud Tasks. The team used document-driven development to produce ADRs for three domains (Stripe payments, QB invoicing, Lead Gen), define service contracts, and establish data ownership boundaries. First services are actively being built with a bridge approach where new services go live while v1.0 keeps running. Lead Gen is on track for production within months
-
›
Designed technical plans for features built by teammates, including multi-tenant dealer QuickBooks integration and a dealer webhook permission system
-
›
Wrote team quality standards (PR review checklists, testing expectations, code style guides), onboarded new developers, screened engineering applicants, and trained support agents on platform systems. Longest-tenured IC and default escalation point for system questions
Software Engineer I
Apr 2022 – Jun 2024-
›
Replaced a broken CSV-upload billing workflow with automated invoicing: OAuth2 built from scratch, webhook-driven QuickBooks sync, and self-healing payment reconciliation across two financial systems. $155M+ processed ($60M+ in 2025), 82K invoices with per-line-item failure detection. Worked directly with the CFO on billing requirements throughout
-
›
Built the lead pricing engine with accounting and operations, determining per-dealer cost-per-lead across billing zones, deal types, and three pricing models. Validated invoice structure and automated reporting with stakeholders. Found a campaign attribution design flaw during code research months before it hit production. 775K+ deals priced, 373K line items
-
›
Designed 4-layer idempotent batch processing for weekly dealer invoicing (200–300 dealers). The TDD test for the exact double-run scenario was written before it happened in production. Accounting ran billing twice on 69 dealers. Zero duplicates
-
›
Championed async-first processing for a crash-prone single-server monolith. Built buy-in by delivering 8 specialized queue supervisors incrementally, each justified by a specific production incident. ~20K jobs/day on dedicated worker infrastructure, zero peak-hour crashes after implementation
-
›
Diagnosed a cascading queue failure caused by Horizon's cache tracker consuming unbounded Redis memory, which spiked latency from 0.5ms to 25,000ms, backing up all supervisors. Single config change resolved it
-
›
Partnered with the business opportunities team to build a custom SMS and voice platform with dynamic per-salesperson inboxes, HubSpot-triggered workflows, and opt-in/opt-out compliance. Third-party vendors including Genesys Cloud couldn't deliver what we needed — dynamic inbox assignment, salesperson-specific tokens, and full HubSpot deal integration. ~1M messages sent, 380K+/year sustained
-
›
Built PAWS compliance system with tech support and operations — started as automated policy distribution and read-tracking to back up support ticket decisions, then grew into a system that gates lead ordering and dispute eligibility on dealer acknowledgment. 26K+ policy assignments
Senior Technology Specialist / Software Developer
Jul 2021 – Apr 2022-
›
Leveraged a year of frontline support experience to redesign the Deal View as a unified, permission-driven interface, replacing separate admin and dealer pages with dynamic component rendering based on user roles — consolidating duplicate views and establishing a scalable UI pattern for the platform
-
›
Built a reusable Notes service integrated with the HubSpot Engagements API, enabling full CRUD on notes against any HubSpot object (deals, companies, contacts) — an early internal communication layer that gave field teams a lightweight way to log updates without leaving the app
-
›
Delivered end-to-end dispatch resend capability with appointment time tracking, timezone-aware scheduling, and a dedicated API endpoint — enabling ops to recover and reroute failed jobs without manual HubSpot intervention
-
›
Integrated QuickBooks, Armatic, BlueSnap, HubSpot, Katana MRP, and Google Workspace Admin SDK for billing, CRM sync, manufacturing, and user management
Technology Specialist
Jun 2020 – Jul 2021-
›
Provided tech support for 250+ active dealerships and corporate users
-
›
Overhauled the warranty system into a fully self-service, error-resilient workflow. 68K+ warranties processed through the improved system
-
›
Created the company Help Center and LMS with training content and onboarding workflows
-
›
Built a dynamic email signature tool used by every employee and dealer organization-wide
What Colleagues Say
LinkedIn recommendations from Roof Maxx teammates
From the moment I joined the team, it was clear that Bros had some of the deepest knowledge of our systems. His ability to retain that information and understand how the different moving parts fit together made him indispensable in discussions around complex design, large features, and overall architecture.
His commitment to seeing things through… he never shied away from hard problems and always followed up until things were fully resolved.
His ability to read, understand and work with complex legacy code was absolutely critical to the team and the company. Bros was always quick to jump in and help when there were critical and urgent issues.
No problem was too big. He always remained calm, cool and collected while delivering high quality solutions… excellent as both an individual contributor and as a collaborator.
Case Studies
Systems I've owned, decisions I've made, and what I'd do differently
Idempotent Batch Processing
Accounting ran billing twice on 69 dealers. Zero duplicates. Designed a batch processing pipeline with 4-layer deduplication, row-level locked invoice number generation, and a self-healing sync architecture against an inherited schema I couldn't modify.
Billing Pipeline
Inherited a CSV-upload billing workflow and rebuilt it into a webhook-driven invoicing pipeline with per-line-item failure detection. Discovered a campaign attribution bug months before it hit production. Three architectural trade-offs I'd make differently today.
Async-First Architecture
Production crashed during peak hours because every operation ran synchronously on a single server. Championed an incremental migration to async-first processing with 8 specialized worker supervisors on dedicated infrastructure.
Platform Migration
Migrating the monolith to Go microservices on GCP. The team planned a full rewrite, but business pressure forced a pivot: scope to Lead Gen as the first domain, prove the architecture, then migrate the rest. I lead the Lead Gen domain from docs through implementation.
Tech Stack
Primary: Deep Production Experience
Proficient
Familiar / Learning
How I Work
Foundational: Baseline Skills
- Git
- SQL
- HTML
- CSS
- Bash
- SSH
- JSON
- YAML
- HTTP
- Composer
- npm
- Webhooks
- PHPUnit
- Laravel Horizon
- Cloud Tasks
- Blade
- DigitalOcean
- Forgejo
- REST
- OAuth
- CORS
- DNS
- SSL/TLS
- Cron
- Regex
- Migrations
- Database Design
- API Design
- Load Balancing
- Agile
- Code Review
- ADR Documentation
- Incident Response
- Root Cause Analysis
- Remote Collaboration
- Async Communication
- Technical Writing
- Cross-functional Communication
- Mentorship
- Stakeholder Management
- System Design
- Production Ownership
- Postman
- Jira / Asana / Trello
- Slack Integrations
- JetBrains IDEs
- Docker Compose
- Make / Makefiles
- Feature Flags
- Rate Limiting
- Caching Strategies
- Job Scheduling
- Input Validation / Sanitization
- CSRF Protection
- RBAC / Role-Based Access Control
- Pair Programming
- Sprint Planning / Estimation
- Onboarding Documentation
- Knowledge Transfer
- TDD
- TypeScript
- JavaScript
Featured Projects
Systems I've designed, built, and operate
Neptune: Personal Infrastructure
Live
Neptune: Personal Infrastructure
I run my own infrastructure because I learn best by operating real systems with real consequences. The Neptune cluster runs the tools I use daily: Git hosting with CI pipelines (Forgejo), credentials management (Vaultwarden), project tracking (OpenProject), and single sign-on across all of them (Authentik, OAuth2/OIDC). Forgejo is publicly accessible; other services are invite-only to limit bot exposure, but access is available on request. It's also where I develop and test the Go microservices and React frontends for the v2.0 platform migration at work. Operating my own platform means I'm the one managing upgrades, testing backup recovery, debugging failures, and planning capacity. The same operational discipline I bring to production systems.
Built for learning and flexibility, not production uptime SLAs, but reliable enough that I trust it as a development environment for real work. Multi-host XCP-ng hypervisor cluster backed by a 40 TiB ZFS NAS on mirrored vdev pairs (max redundancy, max IOPS, nearly always expandable), with services deployed as version-controlled Docker Compose stacks, automated differential backups, and point-in-time restoration.
View network topology
Where The Heart Is
LiveMortgage affordability calculator with real-time rate comparisons, DTI analysis, and location-specific cost breakdowns. Iterated through three stacks (Jupyter notebook, Laravel + Vue, and now Go + React) as a proving ground for learning new frameworks end-to-end.
Other Projects
Education
B.S. Computer Science
Western Governors University
Capstone: Board Game Rating Predictor
LiveML pipeline predicting BoardGameGeek ratings using scikit-learn. Compares Linear Regression vs Random Forest on Kaggle dataset, served via Streamlit with a Docker multi-stage build that trains models at image build time.
Open to What's Next
Open to senior engineering roles and select contract work.