I work on long-lived software across native mobile applications, backend services, platform tooling, and security-sensitive integration. Professionally, that includes production mobile and backend delivery, modernization, and cross-team engineering work. The examples below are independent/open-source projects, except for the explicitly labeled OpenArchive collaboration.
The emphasis here is on decisions and verifiable behavior: what a system protects, how it fails, and which claims remain unproven.
Selected professional engineering work
The following is commercial experience, distinct from the independent project case studies that follow. Source code and employer-internal outcome measurements are not publicly available here; the descriptions reflect attributable work, not third-party audits.
- Manulife / John Hancock: Android, iOS and React Native modernization in financial applications, with authentication-state reliability, secure client boundaries, security-testing collaboration, and incremental architecture improvements.
- QuickMobile / Cvent: Mobile/backend event features for live polling, beacon-driven interactions, analytics and high-attendance conference applications.
- ePACT: Mobile/backend synchronization, configurable data-driven workflows, Selenium/Appium automation and junior QA mentorship.
For a deeper discussion, I can walk through the engineering constraints, failure modes and trade-offs without disclosing proprietary implementation details.
Choose an engineering focus
| Focus | Representative evidence |
|---|---|
| Platform / Staff engineering | Config Drift Guard, Repora, tidyfs |
| Mobile / Android / iOS / React Native | OpenArchive Android contributions, Eyespie, Amaryllis |
| Application security / AI governance / developer experience | Anthesis Governance Lab, Keylix, git-autocommit |
Selected case studies
Configuration as a reviewed state transition — Config Drift Guard
An independent internal-platform vertical slice, not a deployed enterprise control plane. The important decision was to separate observed configuration, immutable proposed remediation, approval, mutation, and verification. Fastify, SQLite and a Next.js operator UI make the run observable; stale-plan checks prevent approval of a changed state.
Source, five-minute demo and failure scenarios
Mobile authority without a mandatory backend — Eyespie
An independent, closed-alpha Kotlin Multiplatform application. The Wayfinder implementation uses SQLDelight for authoritative local state, native CameraX/AVFoundation boundaries, MediaPipe embeddings and signed versioned .eyespie game interchange. The former Supabase design is historical.
Android automation and selected signed-artifact checks exist, but cross-device physical acceptance, iOS signed distribution, and the final closed-alpha release gate remain outstanding.
Source, architecture and candidate-bound acceptance criteria
Reversible filesystem changes despite untrusted AI — tidyfs
An independent Rust CLI combining deterministic filesystem classification and cleanup eligibility with optional advisory model output. The model cannot authorize mutation, override exclusions, or determine reclaimable bytes. Changes require explicit interactive approval and use reversible quarantine with recovery evidence, rather than permanent deletion.
CLI, recovery model and threat model
Honest partial failure in Git mirroring — Repora
An independent pre-alpha Go CLI that models repository topology, observation, exact ref plans, authorization, stale-head preflight and per-target execution evidence. It intentionally records incomplete mirror convergence instead of presenting independent remote operations as atomic.
Go implementation and operational examples
Professional collaborative work — OpenArchive Android
OpenArchive’s Save for Android is collaborative project work, not my independently owned product. Public upstream commits under my GitHub identity include internal Tor daemon integration, Orbot proxy enhancements, and callback integration.
These commits are present in the upstream next ancestry as of October 15, 2026. They show authored Android/security-sensitive code, not proof of release adoption or exclusive ownership.
Deeper engineering work
For reproducible starting points, test commands, architectural trade-offs and explicit maturity boundaries, see the GitHub engineering case-study index and the linked project’s own README, tests, release records and CI. Relevant independent research includes secure agent delivery patterns and Anthesis public governance trials.
Project documentation is evidence of design intent until supported by implementation and executed verification. Independent project work does not add employer production tenure.
Work together
I’m open to Senior / Staff engineering and selected contract opportunities in platform/backend systems, native or cross-platform mobile, application security, developer experience and secure AI. Remote-first roles in Canada are preferred.
Email me about a role or technical collaboration, or see my GitHub profile for current public engineering work.