John AlynSenior SWEResume
Software Engineer | Systems & AI Infrastructure

John AlynQuantitative trading algorithms + production-grade systems.

I design and build robust backend systems, trading infrastructure, and AI-assisted applications with a focus on correctness and performance.

Selected work

View all projects

web_template

Production project hosted on GitHub.

0Forks 0Updated Feb 2026
TypeScript

bms-claude

Production project hosted on GitHub.

1Forks 0Updated Feb 2026
JavaScript

ghoasis.github.io

Gentle Hands Oasis website. A home health care business.

1Forks 0Updated Feb 2026
HTML

Biz_Web_Template

Production project hosted on GitHub.

1Forks 0Updated Feb 2026
TypeScript

Tesla_Dealership_Database

This database models a Tesla car dealership that manages inventory, customers, sales transactions, and customer reviews of vehicles. The system tracks vehicle specifications, availability, purchase history, and post-purchase feedback to support dealership operations and customer insights.

1Forks 0Updated Feb 2026
PLpgSQL

BTC_Quant_Agent

An end-to-end algorithmic trading framework designed for Bitcoin (BTC), featuring an AI-driven alpha signal generator, rigorous backtesting engine, and risk-managed execution layer.

1Forks 0Updated Feb 2026
Python

Engineering philosophy

Built for production reality

I design systems to survive traffic spikes, bad deploys, and incomplete requirements. That means strict interfaces, clear ownership, and instrumentation that makes failures obvious.

Production readiness reviews for every release.
Observability-first: logs, traces, metrics, and alerting.
Clear rollback strategies and runbooks.
Security and data protection as defaults.
Read my detailed approach

Capabilities

Execution across the stack

Architecture & technical strategy
Full-stack delivery (React, Next.js, Node)
Cloud & infrastructure (AWS, Docker, Terraform)
Data platforms (Postgres, Redis, ETL)
Operational excellence (CI/CD, SLOs, observability)
Security & compliance readiness

Production checklist

What I ship every time

If it isn't operable, it isn't done. Each delivery includes the systems needed to run safely in production: testing, monitoring, and clear ownership.

Availability

99.9%+

Service health with monitored SLIs/SLOs.

Performance

<200ms

Critical endpoint latency under load.

Change safety

CI/CD

Automated tests, previews, and rollbacks.

Operations

On-call

Runbooks, alerts, and incident reviews.

Deliverables

Architecture diagrams, PRDs, runbooks, dashboards, and production-ready code.

Preferred stack

React, Next.js, TypeScript, Node, Postgres, Redis, AWS, Terraform, GitHub Actions.

Resume

Full timeline, impact, and stack

This is the complete record of roles, outcomes, and the systems I've shipped in production.

Snapshot

Full-stack, cloud, and platform delivery with ownership of reliability and performance.

Core domains

Internal tools, customer-facing platforms, data workflows, and ops tooling.

Notes

Field notes from production

Short writes on reliability, system design, and operational tradeoffs I've learned firsthand.

Read notes

Recent topics

Designing SLOs that the team will actually use.

Migration plans that don't break production.

How to ship safely with small teams.

Let's build something resilient.

Open to full-time roles, consulting, and high-impact collaborations.

Start a conversation