Larry Miami

Selected work

Systems, not just screens.

A selection of product, platform, and cloud-security work showing how I approach the problem, architecture, implementation, and evidence — not only the finished interface.

AfyaBridge Cloud Security

A multi-country cloud-security reference implementation for a fictional community-health organization, covering country isolation, Terraform, keyless delivery, software supply-chain security, posture governance, and evidence-backed controls.

Role: Cloud / Security Engineer
Stack: Google Cloud · Terraform · GitHub Actions · TypeScript
Control state: Designed · Implemented · Validated by boundary

App baseline · Validated GCP IaC · Static Security gates · Complete Supply chain · Validated Posture · In review Live GCP · Pending

View case study GitHub

Ticket Trove Africa

An East African event platform built around checkout-time inventory reservation, KCB Buni / M-PESA payments, organizer controls, ticket issuance and transfer, and entry validation.

Reserve inventory at checkout, not add-to-cart
Atomic payment completion and safe inventory release
Dynamic QR, OTP validation, and ticket-transfer lifecycle

View case study Open product

PawSuite

A Kenya-first veterinary practice platform designed around clinic, mobile, mixed-practice, and field workflows — with tenancy, authentication, offline state, payments, inventory, and clinical operations treated as one connected system.

Workflow-first clinic + field operating model
Verified identity, tenancy, RLS, and browser auth foundation
Bounded offline drafts with server-authoritative final actions

View case study Open product

Product systems · Community health

AfyaBridge

A community-health workflow concept connecting CHW screening, nurse review, referrals, follow-up tasks, and reporting in one operational layer.

Community-to-facility workflows
Referral and follow-up operations
Low-connectivity product thinking

Open project

Selected professional work

Production problems change the way you engineer.

Sanitized examples from healthcare product work. Architecture and identifying details are simplified to protect proprietary systems and data.

Human-in-the-loop AI

AI-assisted healthcare workflows

Product and engineering work around patient questions, AI-generated draft responses, clinician review, queueing, and safe hand-off back to the patient.

Patient→AI draft→Clinician→Reply

Community health

Field-to-clinic workflows

Systems supporting community-health registration, screening, referrals, follow-up, and operational reporting across field and clinical teams.

CHW→Screen→Review→Referral

Operational integrations

Payments and clinic operations

Working through the integration boundaries between clinic systems, point-of-sale workflows, mobile-money payment rails, and the reconciliation needed to make operations trustworthy.

Clinic→POS→Payment→Reconcile

Capabilities

Across the application boundary.

My strongest work sits where product behaviour, backend systems, cloud infrastructure, and security decisions meet.

01

Product Engineering

React · Next.js · TypeScript · workflow modelling · design systems · offline-first UX

02

Backend & Data

Node.js · PostgreSQL · MongoDB · Redis · GraphQL · REST · authentication · authorization

03

Cloud Engineering

Google Cloud · Cloud Run · Cloud SQL · VPC · IAM · Terraform · logging · monitoring

04

Security & DevSecOps

Threat modelling · least privilege · keyless CI/CD · secrets · infrastructure security · application security

About

I build products with the system around them in mind.

I started from product engineering: understanding users, workflows, interfaces, APIs, and the operational constraints around software. That foundation now extends into cloud architecture, secure delivery, infrastructure, and security controls.

I care about clear engineering decisions, operational constraints, and being precise about what is designed, what is implemented, and what has actually been validated.

Product first: Understand the workflow and failure modes before choosing the architecture.
Security by design: Make identity, authorization, data boundaries, auditability, and recovery part of the system model.
Evidence over claims: Separate designed, implemented, and validated controls instead of treating documentation as proof.

Contact

Let's talk.

For product engineering, cloud infrastructure, DevSecOps, cloud security, or technical collaboration, email is the best starting point.

miamielarry@gmail.com