Good systems. Real-world roots.
A career shaped by production systems, practical automation, APIs, cloud resilience, and technical standards.
The path so far
From operations to principal-level engineering
Different roles.
The same curiosity about how things work—and how to make them better.
Principal Software Applications Engineer
Help engineering teams build on dependable foundations: clearer API standards, practical security guidance, thorough testing, and repeatable AI-assisted workflows.
Selected work
- Standardized rolling-window quotas and traffic protection across APIs, using production usage analysis to understand the effect on integrations.
- Built Playwright API checks for pricing workflows, covering successful requests, invalid inputs, and consistent behavior across test environments.
- Coordinated dependency-security fixes and translated security and recovery requirements into reusable guidance for service owners.
- Developed spec-driven workflows and reusable agent guidance for engineering teams.
Selected technologies & practices
- Node.js
- Apigee X
- Playwright
- OpenSpec
- Application security
- Spec-driven development
Principal Software Engineer
Brought new pricing services into production while improving the tools that help teams see what is happening, catch failures, and release changes with confidence.
Selected work
- Delivered pricing and promotions APIs from design through release, including request validation, clear error handling, documentation, and production-readiness checks.
- Contributed to the API gateway migration and reviewed changes across services, keeping deployment configuration and testing consistent.
- Built shared alerts for failed background jobs and contributed distributed tracing tools to make production issues easier to investigate.
Selected technologies & practices
- Node.js
- AWS Lambda
- Amazon SQS
- Apigee X
- OpenTelemetry
- Redis
- PagerDuty
- OpenAPI
Senior Software Engineer
Built services that connect business workflows, then turned recurring engineering and security tasks into reusable tools. The work grew from individual APIs into patterns other engineers could build on.
Selected work
- Built subscription-change and quoting workflows with request validation, background processing, and status tracking so integrations could follow work through to completion.
- Took webhook notifications from prototype to production, giving integrations a way to receive updates instead of repeatedly checking for changes.
- Owned account-update API delivery from design through production, including validation, testing, and release preparation.
- Built security and trust reporting automation to collect findings, track changes, validate data, and generate reports that made review work more manageable.
- Created reusable service templates and infrastructure modules, alongside on-call guidance, threat models, and release documentation to support the people maintaining the services.
Selected technologies & practices
- Node.js
- AWS Lambda
- Amazon SQS
- Terraform
- OpenAPI
- Grafana
- Splunk
- SSM Parameter Store
Senior Software Engineer
Built cloud-native subscription services with the operational details in mind: protecting exported data, handling background work, testing real integrations, and preparing for production recovery.
Selected work
- Built secure subscription exports with background processing, data transformations, encryption, and retention controls for generated files.
- Developed a GraphQL API layer and strengthened integration tests, request validation, traffic limits, and production monitoring.
- Maintained shared service clients and documented deployment, rollback, and regional failover practices so teams had a clearer path through releases and recovery.
Selected technologies & practices
- Node.js
- AWS Lambda
- Amazon SQS
- Amazon S3
- Terraform
- GraphQL
- Jest
- API Gateway
Software Engineer
Moved from production support into software engineering by applying root-cause analysis, regression automation, and monitoring to improve the reliability of integration services.
Selected work
- Investigated recurring production failures and converted findings into runbooks and recovery guidance.
- Built and maintained automated regression checks and daily operational reporting.
- Helped transfer support knowledge and strengthen access and security routines.
Selected technologies & practices
- Java
- API testing
- Operational monitoring
- Regression automation
Production Support Engineer
Supported business-critical order, pricing, and support services while expanding troubleshooting documentation, contact-center administration, and automation foundations.
Selected work
- Maintained troubleshooting guidance for business systems and support APIs.
- Resolved complex system and data issues by tracing behavior across services.
- Improved repeatable support workflows and baseline reliability checks.
Selected technologies & practices
- Incident response
- API support
- Monitoring
- Automation
Production Support Engineer
Provided application and production support for business services, building the operational habits in monitoring, incident response, documentation, and practical automation that shaped later engineering work.
Selected work
- Created troubleshooting and monitoring guides for production support teams.
- Supported escalations and routine operational recovery.
- Wrote small automation scripts to reduce repetitive reporting work.
Selected technologies & practices
- Production support
- Logging
- Incident management
- Automation
There’s more to making than the day job.
Explore the side projects