Software engineer · Backend specialization
Software engineer working across Java, Spring Boot, PostgreSQL, and Flutter. I've modernized a legacy fixed-asset system and grown a college project into a production content-and-commerce platform as its CTO.
01 / 01Core expertise
Backend engineering
Java · Spring Boot · PostgreSQL
01 Understand the operating reality
02 Make the consequential decisions visible
03 Verify the system with retained evidence
Selected work
Two commercial journeys where discovery, architecture, implementation, and product responsibility stayed connected.
Enterprise asset management
I reconstructed an undocumented legacy workflow for a 40-year-old finance firm, then rebuilt procurement, custody, depreciation, verification, and disposal around traceable physical assets.
Read case studyConsumer content platform
As CTO / Lead Architect, I lead the architecture and delivery of a production content-and-commerce platform connecting creator publishing, customer access, payments, and entitlements.
Read case studyAdditional engineering work
Independent product development and earlier applied cloud work that support the main engagement story.
Independent product work · field operations
A deliberately narrowed local-first trip-to-report pilot within a broader Spring Boot and Flutter field-operations architecture.
Read supporting case studyEarlier engineering work · industrial IoT
An AWS ingestion path transforming form-encoded Raspberry Pi logger data into structured timestamped MongoDB documents.
Read supporting case studyExperience
A progression from applied cloud work to client modernization and continuing product responsibility.
AstroVista
Product architecture, releases, creator commerce, payment and entitlement workflows, and production recovery.
FAMS client modernization
Discovery, architecture, Flutter and Spring Boot implementation, financial workflow design, UAT remediation, and delivery.
G S Solar Systems / SGC Enterprises
AWS cloud ingestion for Raspberry Pi solar data-logger telemetry.
About
My background in Mechatronics taught me to see products as systems: inputs, constraints, failure modes, and feedback loops.
Today I apply that thinking to backend and product engineering: turning business rules into APIs, database models, permission boundaries, operational tools, tests, and explicit release decisions.
What I bring
Backend-first engineering across discovery, architecture, implementation, debugging, test evidence, and delivery. Flutter remains an important product surface.