Senior/Staff Full-Stack Engineer | LLM & agentic systems, platform & CI/CD | Python, TS/JS, React, AWS Serverless
Full-stack engineer with 10 years across frontend, backend, and cloud. I build end to end: TypeScript and React on the front, Node and Python on AWS serverless (Lambda, DynamoDB, SQS, SNS, API Gateway, Cognito) on the back. My range runs from the browser to the platform: 1. A broker-facing reporting dashboard (broker satisfaction up 24%) 2. A quote-generation frontend that automates new-business follow-ups 3. A serverless migration from a v3 framework to AWS SAM + Terraform that cut ~$20k, and the CI/CD that gates security, quality, and regression checks on every release 4. The team's Claude Code workflow and ran the training that got the whole team using it Open to senior, staff, architect full-stack roles
Markdown supported · ⌘↵ to post
Ken
Nice practical framing. I’m biased because this maps to patterns I’m building around nxusKit SDK, but the design point stands on its own: a builder/chain makes each guard independently testable and makes the chain itself a reviewable artifact.
In practice, I’d map the stages as structured-output extraction -> deterministic rule checks -> repair/escalation packet. Python is the most natural place for a fluent .add() version; Rust and Go can do the same with trait/interface stages, just with less syntactic fluidity.
The production fields I’d add per stage are guard id/version, observed facts, authority boundary, verdict, and trace id, so the pipeline is not only reusable but auditable.