200 OK · open to full-stack & backend roles

Pouya Sadeghzadeh —
I build the layer
between request
and response.

Full-stack engineer, 22. Comfortable across Node, PHP and their frameworks — from a shop's checkout page to a membership platform built on DDD.

SELECT * FROM education

Background

Two records, most recent first.
table: education — 2 rows
degree
B.Sc. Software Engineering — Zand University
status: current / latest
degree
Associate Degree, IT — Bahonar Shiraz
status: completed
docker-compose.yml

The stack, as services

What I reach for by default across the request lifecycle.
$ docker compose ps — 6 services, all running
next.js
up
Rendering layer — SSR, server actions, routing for the front of every app.
role: frontendport: 3000
nestjs
up
Structured Node APIs — modules, guards, DTOs for services that grow in complexity.
role: apiport: 4000
laravel
up
PHP backbone — Eloquent, queues, and lately a DDD structure for a membership platform.
role: apiport: 8000
node.js / express
up
Lighter runtime for services that don't need a full framework, like the meeting manager.
role: runtimeport: —
mysql / postgres / mongo
up
System of record — relational where the data is structured, Mongo where it isn't.
role: storageport: 5432
redis
up
Queues and caching — the part that keeps background jobs off the request path.
role: queue/cacheport: 6379
C#
midlevel
Windows Forms apps, DLLs, Entity Framework.
Python
midlevel
Scripting and scraping — BeautifulSoup, requests.
WordPress
as needed
Custom PHP payment gateway integrations.
branch: learning/go~in progress
Go — just started, working through the basics.
branch: learning/cpp~in progress
C++ — early days, building up the fundamentals.
$ apt list --installed | grep tooling
git, github, gitlab — team workflows, git-flow for larger projects
daily
docker — containerizing and running services
daily
linux — server setup and day-to-day operation
daily
queues — background jobs, deferred work
familiar
data structures — applied when it matters for performance
familiar
networking — fundamentals
basic
microservices — fundamentals
basic
selected work

Projects, traced

Each bar is roughly proportional to where the build effort went.
Membership website (in progress)
current · Laravel, DDD

Building a membership platform on Laravel using a domain-driven design structure — separating domains, application logic, and infrastructure instead of the typical MVC-only layout.

LaravelDDDMySQL
CRM platform
full-stack

Customer-relationship management app with a NestJS API and a Next.js frontend, backed by MongoDB.

NestJSNext.jsMongoDB
Ads website
full-stack

Classifieds-style ads platform built entirely on Next.js, using server actions instead of a separate API layer, with PostgreSQL for storage.

Next.jsServer ActionsPostgreSQL
Office meeting manager
full-stack

Tool for scheduling and tracking office meetings — Express API, React frontend, MongoDB for storage.

ExpressReactMongoDB
Legacy Laravel refactor
maintenance & features

Took over a large, existing Laravel codebase — refactored problem areas and shipped a steady stream of new features without breaking what was already in production.

LaravelMySQL
Also shipped
Simple shop site for an employer
Pure PHP + HTML
Telegram mini app
Next.js
WordPress payment gateway integration
PHP
POST /contact

Let's talk shop

$ curl -X POST https://api.pouyasdz.dev/contact \
-d "message=Let's build something"
202 Accepted. Reachable by phone or GitHub.