Currently at Snapp · Mashhad, Iran

Alireza Pazook

Software Engineer

Backend Engineer · Golang · Microservices · Distributed Systems

Building scalable systems, one service at a time.

I’m a software engineer focused on building high-performance backend systems, scalable APIs, and reliable distributed services.

View Experience Contact Me Resume

LinkedIn Email

alireza — services · zsh

About

Backend systems that stay reliable as traffic scales.

I’m a backend-focused software engineer with experience building and maintaining services with Golang, PHP, and Laravel. I care about clear service boundaries, predictable APIs, efficient data access, caching, and systems that remain operable under high traffic. I keep learning, but prioritize solutions that are reliable, maintainable, and measurable.

Backend Engineering
Distributed Systems
Microservices
Performance
Scalability
Clean Architecture
API Design
Database Optimization

Years Experience: 8+
Roles: 5
Engineering: Backend
Systems: High-Traffic

Experience

From product delivery to high-traffic backend systems.

A timeline of software engineering work since 2018. Current focus is backend systems at Snapp.

Current role

Snapp

Software Engineer

2024 — Present

Backend development with Golang
Microservices architecture
PostgreSQL
Redis
RESTful APIs
Distributed systems
Performance optimization
System reliability
High traffic workloads
Collaboration with DevOps and frontend teams

How I approach service design

Gateway

Services

PG / Redis

Shayan Pardazesh

Project Manager · Software Engineer

2020 — 2024

Project implementation and analysis
Technical and support team management
Product introduction meetings
Laravel
PHP
Eloquent ORM
Blade
MySQL

Satrex

Software Engineer

2019 — 2020

Vue.js
VueX
Vuetify
Vue Material Design
SASS
Styled Components

Alfateam

Software Engineer

2018 — 2019

Laravel
PHP
Eloquent
Blade
SASS

Freelance

Software Engineer

2018 — Present

Independent software engineering work alongside full-time roles

Systems

How I think about backend systems

This conceptual request path shows how I separate responsibilities across entry points, domain services, data stores, and external dependencies.

API Gateway

A single entry: routing, auth, rate limits, and a stable contract for callers.

Stack

Backend first. Everything else supports the system.

Golang, services, data, and cache sit at the center. Frontend and tooling are here because the work sometimes crosses that line.

Backend

GolangPrimary language for services, APIs, and concurrent backends.
MicroservicesService boundaries, reliability, and independent deployability.
REST APIsContract-first HTTP APIs that stay predictable under load.
PHPProduction backend work across PHP applications.
LaravelApplication backends, Eloquent, and maintainable PHP services.
Core PHPFramework-agnostic PHP when the problem needs it.

Database

PostgreSQLRelational modeling, query performance, and durable state.
MySQLSchema design and everyday production data work.

Caching

RedisCaching, hot paths, and reducing pressure on primary stores.

Frontend

JavaScriptApplication UI when the product needs it.
TypeScriptTyped interfaces across frontend and shared contracts.
Vue.jsComponent-driven frontend work from earlier roles.
ReactModern UI work when collaborating across the stack.
HTMLSemantic structure and accessible markup.
SASSStructured styling for product interfaces.
BootstrapRapid, consistent UI scaffolding.

Testing

TDDTests that lock behavior before the design hardens.

Dev Tools

GitHistory, review, and collaboration on evolving systems.
DockerReproducible environments for services and local workflows.

Contact

Have a system to build?

Whether you’re building a scalable product, improving an existing backend, or looking for an experienced engineer, feel free to get in touch.

alirezapazook@gmail.com

Get In Touch Download Resume