Full-stack software engineer · Denver, CO
Zach Sykes
Production web applications, APIs, and internal tools with React, TypeScript, .NET, Azure, and SQL.
- React
- TypeScript
- .NET
- Production systems
About
How I work
I own delivery across the stack — API contracts, service boundaries, deployment pipelines, and production health. Observability is part of shipping, not an afterthought: Grafana, Application Insights, GitHub Actions, and Azure Pipelines are how I keep releases safe and incidents diagnosable.
I collaborate directly with product, design, and business stakeholders to turn requirements into shipped features, invest in code review and mentoring, and use AI-augmented workflows (Copilot, Claude) where they measurably speed delivery. Based in Denver and open to hybrid roles for the right engineering team; experienced working effectively in remote environments.
Role fit
What I bring
- Full-stack product engineering
- Production API ownership
- React/TypeScript frontend delivery
- Backend systems across stacks
- Observability and reliability
- Internal tools and stakeholder-facing systems
Currently seeking
Currently looking for full-stack software engineering roles where I can own production features end-to-end — frontend through APIs and backend services — and partner directly with product, design, operations, or business stakeholders.
Featured projects
Selected projects
Deeper write-ups on selected work — with demos and source links where available.
Planning Poker — internal collaboration tool
ShippedReal-time estimation platform for distributed delivery teams at Forvis Mazars, integrated with Jira for viewing stories and updating estimates. Replaced manual estimation coordination with a single internal workflow that improved session consistency and reduced meeting friction.
At a glance: 0-to-1 internal product: WebSocket realtime, Jira integration, .NET services, React UI — adopted across all verticals.
Agentic chat with tool use + evals
ShippedStreaming chat where Claude calls seven structured resume tools (get_role, search_resume, list_projects_by_skill, get_metrics, list_recent_shipped, get_narrative, get_faq). Tool calls show up in the transcript. Evals hit the same HTTP endpoint; results power the pass/fail table on the project page.
At a glance: Structured tool use over real data, with evals so regressions show up as failing rows—not just a prettier UI.
Chat Demo
Portfolio assistant — production AI integration
I build production software; this assistant is one example — a streaming chat backed by a real ASP.NET Core API, structured data, and guardrails. Ask about my work, stack, or role fit.
Starter prompts — tap to send.
Try one of these — each one fires a structured tool call so you can see how it works.
Experience
Career so far.
Full Stack Software Engineer
June 2023 – present
Forvis Mazars (remote)
Build and maintain production web applications and APIs serving enterprise users — owning architecture, delivery, reliability, and operational health across the full stack. Highlights: end-to-end React/TypeScript/Next.js/.NET delivery; Planning Poker (WebSockets) from 0 to 1; shared component systems and API patterns across teams; CI/CD and observability (GitHub Actions, Azure Pipelines, Grafana, Application Insights); stakeholder collaboration, mentoring, and AI-augmented workflows (Copilot, Claude).
Freelance Full Stack Engineer
2024 – present
Calathea Web Design · Selected client work (remote)
Part-time freelance practice outside full-time engineering work. Production websites and e-commerce for small-business clients — from discovery through deployment. Own UI/UX, implementation, backend integrations, custom CMS creation when clients need tailored editorial workflows, and hosting on Vercel.
Kitchen Manager
2012 – 2022
Asheville Pizza and Brewing Company
Earlier career: led kitchen operations for a 40+ person team, including hiring, onboarding, training, scheduling, and performance management.
Software Engineering Bootcamp
Graduated
General Assembly
Career change from operations leadership into software engineering.
The traditional resume page has the print-friendly layout and download.
Contact
Email is the fastest way to reach me.
For hiring or anything that needs a real thread, email or LinkedIn is best. The chat here reads from structured resume data—it isn't a direct line to me.