Backend & API systems
The services your product runs on — designed, built, tested and documented. Sync or async, REST or event-driven, chosen for the load you actually have rather than the load you might.
- Django
- FastAPI
- Flask
- Sanic
- Tornado
- Celery
Bahman Shadmehr Full-stack developer Python · Go · Kubernetes Remote, UTC+3
I build the systems that place the order at 3 a.m. — and the alerts that wake me if they don't.
Eight years of production backends: energy and equities trading pipelines, a national payment gateway, Kubernetes clusters that stayed up through it. I take a system from architecture to the deploy pipeline to the dashboard you check on Monday morning. Open to contract work and full-time roles.
Status: Available
Local time —
Replies within 24h
~/career.log
2017rahpa.logisticstornado backends for real-time location
trackingok
2018crawler.pipelineselenium ingest + django ping
dashboardok
2020zibal.gatewaypayment monolith decomposed into
microservicesok
2021pyango.commercestore builder dockerized, gitlab ci/cd
pipelinesok
2022vgang.retailkubernetes cluster + shopify sync
microservicesok
2023brainshuttle.apiflask services, load-tested and tuned with
locustok
2023equities.tradingaws job orchestration + anomaly
alertingok
2024ercot.energyautomated order placement on gcp batch
jobsok
2026your.projectawaiting deploy▮
Eight years, five companies, fifteen-plus
shipped projects
Add the next line →
/services
What you can hand me
Four kinds of work I'm hired for, and what each one usually looks like in practice.
Cloud, containers & CI/CD
Get off manual deploys. Containerise the app, write the Kubernetes manifests, wire the pipeline, and add the monitoring that tells you when a release went wrong before a customer does.
- Kubernetes
- Docker
- GitHub Actions
- GitLab CI
- Terraform
- Prometheus
Data & trading pipelines
Scheduled jobs that collect data, evaluate it and act on it without a human watching — plus the alerting that catches a bad run. Built for energy and equities markets on both AWS and GCP.
- AWS Lambda
- Step Functions
- Athena
- GCP Batch
- RabbitMQ
- Airflow-style jobs
Monolith to microservices
For a system that has outgrown itself. I find the real seams, split along them in stages, and keep the thing serving traffic the whole way — the same job I led on a live payment gateway.
- Architecture review
- Staged migration
- Load testing
- Observability
How we can work
Project contract
Fractional / part-time
Full-time, remote
One-week architecture audit
/work
Selected work
Four projects that show the range: money moving, markets trading, traffic scaling. Some clients are under NDA and named by sector.
Automated energy trading on ERCOT
Wholesale electricity market · Texas
A platform that places and manages orders on the ERCOT wholesale power market with no one at the keyboard — which means every failure has to announce itself.
- Built the services for market data collection, order placement and system monitoring.
- Designed the trading pipeline on GCP container batch jobs, orchestrated from GitHub Actions.
- Instrumented health metrics across the pipeline and wired automated alerting on top of them.
US equities trading automation
Stock market execution platform
An automated trading platform for US stock markets, where a missed job is a missed market window.
- Maintained the AWS services behind the trading path, keeping execution uninterrupted through market hours.
- Built automated monitoring for the daily trading jobs, with alerts on anomalous runs.
A retail platform that speaks Shopify
Dropshipping & e-commerce
A scalable retail platform that pulls Shopify and Instagram into one shopping experience for sellers and suppliers.
- Built and ran the Kubernetes cluster the platform sits on, for high availability under real traffic.
- Automated releases end to end with GitLab CI/CD, turning deploys into a routine event.
- Wrote the microservices handling Shopify integration and data exchange, in Python and Go.
Modernising a live payment gateway
Payments infrastructure
A critical payment gateway that needed to scale, without a maintenance window anyone would accept.
- Drove the initiative to decompose the monolith into microservices, splitting it along real domain seams.
- Dockerised the whole application so every environment ran the same thing.
- Authored the Kubernetes manifests behind scalable deployments.
- Put Prometheus and Grafana monitoring in place so reliability became measurable, not anecdotal.
Full history
2024 — 2025Python DeveloperEnergy trading platform, ERCOTNDA
2023 — 2024Python DeveloperUS equities trading automationNDA
2023 — 2024Backend DeveloperEducational games for university
studentsBrain Shuttle
2022 — 2023Full-Stack DeveloperRetail & dropshipping platformVgang
2021 — 2022Full-Stack DeveloperHosted e-commerce store builderPyango
2020 — 2021Senior Django DeveloperPayment gateway modernisationZibal
2018 — 2020Django DeveloperWeb crawling & real-time monitoring
dashboardNDA
2017 — 2020Full-Stack DeveloperThree location-based apps: logistics &
family safetyRahpa
/lab
Things I build when nobody asked
Side systems, mostly built to learn a hard part properly: sandboxing, leader election, metaprogramming.
NeetCoders
A coding practice platform in the spirit of LeetCode. Submissions run inside a Docker-based sandbox, queued through RabbitMQ so untrusted code never touches the app.
Django · RabbitMQ · Docker sandbox · Next.js · Asyncio · S3CoffeeChat
A chat system built to scale horizontally: etcd handles leader election and real-time message routing between nodes. An excuse to implement consensus rather than read about it.
Go · etcd · WebSockets · Leader electionSmartTrader
A Forex trading pipeline on AWS, split into four stages — signal generation, evaluation, simulation, execution — so a strategy can be tested before it ever spends money.
Python · AWS · S3 · Athena · Step FunctionsMasterYourCourses
A microservices-based learning platform with chat, online exams and calendar management. I also teach Python, Go and JavaScript on it.
Microservices · Python · S3 · Real-time chatFile-Based ORM
An ORM whose backing store is the filesystem, written to explore how far Python metaprogramming can be pushed before it stops being readable.
Python · Metaprogramming · Descriptors · Metaclasses76 posts on DEV
Working notes on relational database design, SQL, Python and the financial concepts behind the trading work — published as I learn them.
dev.to/bshadmehr · databases · sql · python · go
/stack
The toolkit
Depth on the left of each list, working familiarity on the right. I pick the tool the project needs, not the one I used last.
Languages
- Python 8 yrs
- Golang services
- TypeScript front-end
- JavaScript front-end
- Bash tooling
- SQL daily
Backend
- Django core
- FastAPI core
- Flask core
- Tornado / Sanic async
- Celery tasks
- RabbitMQ queues
Infrastructure
- Kubernetes built & ran
- Docker core
- GitHub Actions ci/cd
- GitLab CI ci/cd
- Terraform iac
- Nginx edge
Cloud
- AWS Lambda compute
- AWS S3 storage
- Athena / Glue analytics
- Step Functions orchestration
- ECS containers
- GCP Batch jobs
Data
- PostgreSQL
- MySQL
- MongoDB
- Redis
- InfluxDB time series
- Athena analytics
Observability
- Prometheus metrics
- Grafana dashboards
- ELK logs
- Sentry errors
- Locust load tests
Front-end
- Next.js
- Vue
- Angular
- Responsive UI
Architecture
- Microservices
- Event-driven
- Hexagonal
- Serverless
- Layered
/writing
Notes from the work
Seventy-six posts on DEV, mostly on database design, SQL and the finance behind the trading systems.
/about
How I work
I started with Python and JavaScript, drifted into Go and infrastructure, and ended up spending most of my career on the unglamorous half of software: the part that has to still be running tomorrow.
That shapes how I build. I want to know the failure modes before the feature list. I containerise early so environments stop being a source of surprise. I put metrics in from the start, because a system you can't observe is a system you're guessing about. And I write the tests for the paths that would cost money if they broke.
I've worked as the sole backend engineer on NDA trading systems and as part of cross-functional teams at product companies, so I'm comfortable either owning a domain end to end or slotting into an existing codebase and its conventions. I've also taught Python, Go and JavaScript to beginners for a few years — which is the fastest way I know to find out whether you actually understand something.
Right now I'm taking on new projects and open to full-time roles, remote, working comfortably across European and US-morning hours.
BasedTürkiye · UTC+3
Work modeRemote
Experience8+ years in production
FocusBackend · distributed systems · cloud
DomainsFintech · energy · e-commerce · edtech ·
logistics
LanguagesEnglish · Persian
AvailabilityContract, fractional or full-time
/contact
Tell me what's breaking, or what you want built
info@bshadmehr.me
I read every message and reply within a day, including to say no if I'm not the right fit for it.
Useful things to put in a first message
- What you're building, in a sentence.
- Where it's stuck — or what doesn't exist yet.
- Your stack, if there is one already.
- Timeline and whether this is contract or a role.