Professional profile
Earl Hayes
Senior Software Engineer · mobile, web & delivery
Summary
End-to-end product delivery
I am a Michigan-based full-stack developer specializing in cross-platform mobile and web software. My deepest work is in C#/.NET and .NET MAUI, with React, Python, Azure, SQL, and Linux when a product crosses into web, cloud, or hardware.
I am a Senior Software Engineer at WorkWave, focused on application architecture, shared cross-platform foundations, mentoring, and end-to-end mobile and web delivery. Outside the day job, I publish mobile products, web software, physical designs, and public repositories through Big Bwain LLC.
Selected evidence
Public work, stated precisely
- I build internal AI tooling and agents used by other engineers, and use LLM-assisted development and design workflows, including Claude, as one part of a delivery system that still includes testing, release engineering, and direct product ownership.
- Publishes and maintains five mobile products represented by nine current Apple and Google store listings.
- Modernized Adventure Cache from Xamarin.Forms to a .NET 10 MAUI single-project implementation while preserving its iOS and Android identities, offline workflows, and release paths.
- Built Keydial Commander, an MIT-licensed Linux driver and React configuration interface for the Huion Keydial Mini K20, covering all 18 keys and the dial, profiles, macros, application launch, and local API control.
Experience
Employment history
- Approx. — Present
Real Green Systems to WorkWave
Current title: Senior Software Engineer
Previous titles (earliest to latest): Mobile Software Technical Support → Software QA and Automation Developer → Software Engineer
Continuous employment that began at Real Green Systems around August 2015 and continued without a break when WorkWave acquired the company in June 2021.
- Promoted in under six months after 2,000+ calls; built a peer-used tool that sped documentation for recurring mobile-platform support calls.
- Wrote Selenium automation and helped implement Service Assistant 5 regression/performance testing; my formal title became Software Engineer about nine months after starting, then Senior Software Engineer around 2020.
- Moved into Automated Marketing Assistant development, then began direct mobile platform development less than two years after starting; later worked as one of two developers on that platform.
- Work at WorkWave has included PestPac and WorkWave Service, with growing use of LLM-assisted development and design tools such as Claude.
Skills
Technical range
- Core
- C# · .NET · .NET MAUI · ASP.NET Core · SQLite · SQL
- Web & tools
- TypeScript · React · Node.js · Python · Kotlin · Linux
- Cloud & delivery
- Azure · GitHub Actions · CI/CD · App Store · Google Play
- Product practice
- Architecture · Offline-first systems · AI-assisted development · Release engineering · Accessibility · Technical writing
Scope
How this chronology is bounded
The current WorkWave title, approximate August 2015 start at Real Green Systems, uninterrupted continuation into WorkWave in June 2021, prior title sequence, less-than-two-year move into direct mobile platform development, and around-2020 Senior Software Engineer transition are owner-confirmed. Mobile Software Technical Support, Software QA and Automation Developer, and Software Engineer are listed in chronological order. The first promotion is bounded only as occurring less than six months after the approximate start, the Software Engineer title change as about nine months after that same approximate start, direct mobile platform development as beginning less than two years after the approximate start, and the Senior Software Engineer title change as around 2020; none is assigned an exact calendar date. The support-sheet generator is described only as documentation support for other technicians' mobile-platform work, not as product development. Automated Marketing Assistant and subsequent mobile development remain functional milestones in the highlights. Exact promotion dates and any other HR title wording remain unpublished. The downloadable PDF uses this same evidence-backed dataset and adds nothing the page does not say.