Frontend
- JavaScript
- TypeScript
- React
- Next.js
- Node.js
- Tailwind
SH‑01 / COVER
Serhii KrepetsFront‑End & Design EngineerDevOps
Polished interfaces, design systems, and the pipelines that ship them.
With great power comes a great electricity bill
#skills
DevOps
- Docker
- Kubernetes
- AWS
- Terraform
- CI/CD
- Linux
AI & Tools
- Cursor
- Claude
- MCP
- AI agents
- ChatGPT
#about me
I started my career in frontend — building web applications and the interfaces people actually touch. It's still core to what I do, but over time I got curious about everything around it.
Back in school, I was the person who spent hours tweaking Windows, trying Linux, and optimizing my PC. Sometimes I made it faster. Sometimes I broke something and had to fix it. That's probably where it started.
On the frontend side I grew into a design engineer. On client projects with no designer — or where the design didn't match the logic — I designed the flows, layouts, and components myself, then shipped them pixel‑perfect. I've built whole platforms rather than one‑off pages, and at my current company I've designed a number of UI blocks that went straight into production.
The more I worked in tech, the more I noticed I enjoy improving processes, automating repetitive tasks, and finding better ways to build and maintain systems.
That curiosity led me toward DevOps, but frontend and design are still a big part of what I do — I keep building and designing interfaces while growing my skills in infrastructure and automation.
I see my path as a combination of both — like two strands of the same DNA: creating things people use and building the systems that make them work.
#What I Do
01
Frontend & Design Engineering
Web apps and interfaces built with Next.js, React, and TypeScript — accessible, responsive, and fast. I work as a design engineer too: when there's no mockup or the design doesn't fit the logic, I design the flows, layouts, and components myself and ship them to production.
02
Infrastructure & DevOps
CI/CD pipelines, containerized deployments, infrastructure as code, and cloud environments — the systems that get code to production and keep it running.
03
AI‑Assisted Workflow
AI tools built into the process — for research, debugging, documentation, and infrastructure planning. A multiplier on judgment, not a replacement for it.
#Deployment Architecture
full history on github→shipped — client & freelance work
client-vps-hostinginfra / hosting2023—
- problem
- Clients had a finished site and no idea where or how to host it — and no budget for a managed platform.
- solution
- Provisioned Ubuntu VPS instances on Hetzner Cloud, configured Nginx as a reverse proxy with automatic SSL via Let's Encrypt, set up DNS, and locked each server down with a basic firewall.
- stack
- Hetzner Cloud · Ubuntu · Nginx · Let's Encrypt · UFW
- result
- Several client projects went from "no idea how to launch this" to a production server that just kept running.
github-push-deployinfra / ci‑cd2024—
- problem
- Releasing an update meant SSH-ing into the server, pulling the repo, and restarting the process by hand — easy to forget a step.
- solution
- Set up GitHub Actions / webhook-triggered deploy scripts so a push to main pulls the latest code, installs dependencies, builds, and restarts the app — no manual steps.
- stack
- GitHub Actions · Webhooks · SSH deploy keys · systemd / PM2
- result
- "Push to deploy" replaced a manual checklist that depended on remembering the right order of commands.
aws-amplify-hostinginfra / cloud2024
- problem
- A project needed hosting with automatic builds and per-branch previews, without managing a server.
- solution
- Connected the repo to AWS Amplify, configured build settings and environment variables, and set up branch-based preview deployments alongside the production build.
- stack
- AWS Amplify · Next.js · Managed CI/CD
- result
- Hands-on experience with a managed cloud deploy pipeline outside the usual Vercel/Netlify defaults.
coolify-selfhosted-paasinfra / platform2025—
- problem
- Wanted the "push and it's live" convenience of a PaaS like Vercel or Heroku, but running on infrastructure I actually control.
- solution
- Deployed Coolify on a Hetzner VPS as a self-hosted PaaS — apps, databases, and preview environments all run through its UI on top of Docker.
- stack
- Coolify · Docker · Hetzner Cloud
- result
- A working self-hosted alternative to a managed PaaS — and the direct inspiration for the platform below.
building now — my own platform
k8s-blue-green-platforminfra / kubernetesin progress
- problem
- A single Docker host can't do a real zero-downtime release — a bad deploy still means a visible blip or a manual rollback.
- plan
- Standing up a Kubernetes cluster with a blue/green rollout pipeline: the new version deploys alongside the old one, passes health checks, then traffic switches over — with an instant rollback if it doesn't.
- stack
- Kubernetes · Helm · Ingress‑nginx · GitHub Actions
- status
- In progress — building this while job‑hunting, not a finished product yet.
easy-deploy-platforminfra / platformplanned
- problem
- Every new project still means wiring up CI/CD and hosting by hand — the exact repetitive work the platform above should remove.
- plan
- A small self-serve platform on top of the Kubernetes cluster: point it at a git repo through a UI, and it builds, containerizes, and deploys the app to my own server automatically — with logs and rollback built in.
- stack
- Kubernetes · Docker · Next.js (control panel) · GitHub API
- status
- Planned — next up once the cluster and blue/green pipeline are in place.
nextjs-supabase-appplatform / reference‑appplanned
- problem
- The platform above needs a real workload to prove it works — not just a "hello world" container.
- plan
- Building a Next.js + Supabase app (auth, Postgres, storage) as both a standalone project and the first real deploy target for the platform.
- stack
- Next.js · Supabase · PostgreSQL
- status
- Planned — the app that puts the platform through its paces.
#Experience
Developer since 2021 — freelance web first, then frontend & design engineering, with DevOps growing fast. AI‑assisted workflow has been part of how I work since 2022.
Freelance Web Development
2021 — 2023Started out taking on client orders — mostly landing pages and small websites built with HTML, CSS, and JavaScript plus libraries (jQuery, Bootstrap, GSAP). Pixel-perfect implementation from designs — my first hands-on web work.
AI‑Assisted Workflow
running · since 2022Using AI as a daily engineering partner since 2022 — from early ChatGPT experiments to Cursor, Claude, and Figma MCP. Speeds up research, prototyping, refactoring, and documentation without replacing judgment. Helped introduce practical AI workflows to colleagues at my current company.
Frontend & Design Engineering
stable · since 2023Building and shipping production web applications since 2023 — Next.js / React frontends, across freelance work and a full‑time role. Increasingly a design engineer: owning UI/UX end‑to‑end, designing components and layouts when no mockup exists, and taking them from idea to deployed, pixel‑perfect production UI.
DevOps / Platform Engineering
in progress · since 2025Took on DevOps‑focused freelance work in 2025 — CI/CD pipelines, deployment automation, and infrastructure for client projects via Upwork and Fiverr. The newest track, and the one growing the fastest.
#Contact
open to new roles — Halifax, Canada
Open to Front‑End / Design Engineer / DevOps roles — remote or hybrid.