peiman@zedx:~$
online admin

peiman@zedx: ~/portfolio — zsh

zsh · 80×24

[ portfolio / 2026 ] // remote :: worldwide

Peiman Mahdavi Parsa

> Senior Backend Developer & AI Practitioner

system.boot typewriter sequence

>Initializing Peiman Mahdavi Parsa...

>Role: Senior Backend Developer & AI Practitioner

>Status: Ready for deployment.

$ ./request_call $ ls ./services > mail --open
  • php8.5
  • laravel13.x
  • postgres18
  • redisqueues
  • airag / llm

peiman@zedx:~$ cat ./about.md

// 01 — profile

Backend systems that hold up under pressure.

[ online ]

I design and ship production backends for teams that need more than a prototype. My work centers on Laravel, PostgreSQL and Redis — clean domain boundaries, observable queues, and APIs that stay predictable as traffic grows.

Lately I spend most of my time wiring AI features into real products: retrieval pipelines, embeddings, guardrails and the boring infrastructure that makes a model useful instead of a demo.

> mission: make complex systems feel simple to the people using them.

user
peiman
role
senior backend developer
focus
APIs · data · AI
database
postgresql / redis
editor
neovim + tinker
timezone
UTC+3:30 · remote
status
accepting new work
  • Laravel
  • PHP 8.5
  • PostgreSQL
  • Redis
  • Docker
  • AWS
  • Livewire
  • OpenAI
  • pgvector
  • REST / OpenAPI
  • Vue
  • CI/CD

peiman@zedx:~$ ls -la ./services --active

// 02 — capabilities

Services loaded from the database.

00 modules

$ cat ./services

No active services published yet. Check back soon.

peiman@zedx:~$ ./run --workflow

// 03 — operations

From first call to production deploy.

4 stages
  1. 01

    Discover

    A short call to map the domain, constraints and what “done” actually means.

    [ scope ]
  2. 02

    Architect

    Schema, API contracts and deployment topology documented before code is written.

    [ blueprint ]
  3. 03

    Build

    Small, tested increments shipped behind feature flags with observability from day one.

    [ shipping ]
  4. 04

    Harden

    Load tests, queue monitoring, error budgets and handover documentation for your team.

    [ production ]

user@zedx:~$ ./request_call.sh

// 04 — contact

Open a channel.

accepting requests

Tell me what you are building and where it hurts. If the fit is right you will get a reply with a calendar link — usually within one business day.

  • response ~24h
  • timezone UTC+3:30
  • channel email / call
  • nda available

> No recruiters. No spam. Just project conversations.

0 / 5000

press ctrl + enter to transmit