Curriculum Vitae · Open to the right role
Hamed HadiSpahbod
Full-Stack Engineer
Websites · SEO · AI · React · Next.js · Cloudflare · DevOps
I design the site, make it findable, and keep it in production.
I design websites, improve their SEO, and wire AI where it actually saves time — then ship the stack in Python, PHP, Node.js, React, and Next.js on Docker, CI/CD, and Cloudflare. What I optimize for is not a demo that works once. It is a system a team can deploy on a Tuesday without fear.
ihamedhadi · hamed.hadi1010@gmail.com
Since
2022
Shipping software & infrastructure
Focus
Web · SEO · AI
Sites, search, and intelligent products
Edge
Cloudflare
Workers, DNS, delivery, static at the edge
Languages
FA · EN · TR
Persian, English, Turkish
What I take on
Websites, search, and AI — then the platform that keeps them up.
Website design
Landing pages, company sites, stores, portfolios, and custom web apps. Designed to look considered, built to ship, and ready for real traffic.
SEO
Technical SEO: structure, metadata, sitemaps, performance, and pages that search engines can actually understand — so the site can be found.
Artificial intelligence
LLM-backed features, automation, and AI-assisted products — from chat interfaces to workflows that save a team hours, not slide-deck demos.
Skills
Depth where it counts. Honest range everywhere else.
Application
- TypeScriptExpert
- JavaScriptExpert
- Node.jsExpert
- ReactAdvanced
- Next.jsAdvanced
- PHPAdvanced
- PythonAdvanced
Cloud & edge
- CloudflareAdvanced
- LinuxExpert
- NginxAdvanced
- DockerExpert
- KubernetesProficient
- TerraformProficient
Product & growth
- Website DesignAdvanced
- SEOAdvanced
- AI IntegrationAdvanced
- LLMsProficient
Delivery
- CI/CDExpert
- GitHub ActionsAdvanced
- GitLab CIProficient
- GitExpert
- PostgreSQLAdvanced
- PrometheusProficient
Experience
Independent work with production consequences — not textbook labs.
2024 — Present
Full-Stack Engineer
Independent · selected engagements
Websites, SEO, AI-backed features, and the release path underneath — designed so production stays boring.
- Design and ship websites — landing pages, company sites, stores, portfolios — then keep them findable with technical SEO.
- Integrate AI where it earns its place: LLM-backed features, automation, and workflows that save hours, not pitch-deck demos.
- Design CI/CD so build, test, and release are reviewable and repeatable — not a ritual that only one person understands.
- Containerize services with Docker, keep staging faithful to production, and refuse deploys without health checks and a backup story.
- Operate on Cloudflare — DNS, edge delivery, Workers, and static sites — so software is close to the people who use it.
- In one production pipeline I cut GitHub Actions wall time from ~12 minutes to ~2.5 minutes with lockfile-keyed caches and Docker layer cache.
2022 — 2024
Full-Stack Developer & DevOps
Startup projects
I owned both the product surface and the infrastructure that carried it — from first commit to first users.
- Built web products and APIs with React, Next.js, Node.js, PHP, and Python — landing pages to custom apps that had to survive real traffic, not slide decks.
- Stood up Linux, Nginx, PostgreSQL, and Docker so a small team could deploy without waiting on a platform hire.
- Learned production the expensive way: wrong volumes, green pipelines with broken data, 45-minute rollbacks — then wrote the checklists so it does not happen twice.
Selected work
Field notes — the kind of detail a hiring manager can verify.
CI/CD
An 80% faster GitHub Actions pipeline
Separated dependency cache from Docker layer cache, keyed on the lockfile, and made cache hit-rate a first-class signal. Feedback loops got short enough that the team started trusting CI again.
Read the note02Production
The night a volume mount emptied the database
A compose change pointed Postgres at an empty folder. I now treat health checks, pre-merge backups, and staging that matches production paths as non-negotiable — not as polish.
Read the note03Release
A 45-minute rollback that changed the strategy
Green pipeline, broken sessions, no revert button. Immutable tags, a simple blue-green slot, feature flags where rollback is hard, and a one-page runbook. A green build is not the same as a healthy release.
Read the noteHow I work
The operating system behind the stack.
Staging is not a sketch
Volume paths, schema, and smoke tests should match production. “Close enough” is how you lose three days of data.
Pipelines should be measured
If CI is slow, people stop using it. Cache keys, layer strategy, and hit-rate are engineering work — not decoration.
Rollback is a product feature
Immutable images, a known previous version, and a person who is allowed to revert without a meeting.
Own the last mile
The page, the ranking, the AI behind it, and the edge in front. I am useful because I do not hand the deploy over the wall.
Open to the right role
If the work is real, I want to hear it.
Send the role, the team, and the constraints. I reply to complete invitations within 72 business hours — same channel.