Cairo, Egypt · open to remote & relocation

Andrew Anter

I build products from idea to production: requirements, frontend, backend, deployment.

I ship to the cloud — and to machines with no internet at all.

how the air-gapped build works

Title Product Engineer
Experience 3 yrs · since Sep 2023
Team 2 engineers · led by me

Hands-on experience

Programming languages

  • Pythonmy main language — strict typing, production backends and tooling
  • GoCLI, TUI, desktop & other tools via agentic coding — single binary, easy cross-compilation; I read, debug and ship the result

Frameworks & architecture

  • DjangoORM tuning, custom middleware
  • Django Ninja + Pydanticthe production API layer
  • Vuefrontend, replaced HTMX + templates
  • Service-layer architecturebusiness logic in its own layer
  • RBAC + OBACrole- and object-level document access
  • EAVdynamic, per-document schemas
  • Event-driven processingjobs triggered by domain events

Queues & caches

  • Celeryqueues partitioned by workload, backpressure tuning
  • Celery Beatscheduled sweeps that re-drive stuck jobs
  • RabbitMQdurable delivery — a lost message costs delay, never a job
  • Valkeycache and locks every service shares

Databases & search

  • PostgreSQLper-host tuning, full-text search
  • PgBouncera dozen services sharing one database without exhausting it
  • Meilisearchbeside PostgreSQL full-text; exact & exclusion operators

Document AI & vision

  • Self-hosted VLM inferenceQwen3.5-9B on the client's own GPU — data never leaves the site
  • Tesseract OCRwith an in-house-trained orientation model I integrated
  • PDF page pipelinespypdfium rendering, QR slicing, text-layer extraction
  • OpenCV2catches faded scans and artifacts before they reach review

Infrastructure & networking

  • Proxmox VE + ZFSone machine, many VMs, snapshots that make rollback cheap
  • Docker Composethe whole deployment as one reviewable file
  • Workstation + RTX GPU selectionso client data never goes to the cloud
  • pfSensethe site's perimeter, internet or not
  • Sambadomain + DNS; GPO blocks USB, WiFi, Bluetooth
  • CaddyHTTPS from our own CA, no public certificate
  • restic + PBS + NASbackups on separate media; restore drilled for real

Security

  • Cloudflare WAFrate limiting and bot rules before our firewall
  • UFWdefault-deny, only the ports a deployment needs
  • CrowdSecintrusion prevention fed by what others saw first
  • OSV-Scannerpre-commit vulnerability scans
  • Banditsecurity static analysis in the commit loop

Quality & delivery

  • Self-hosted GitLabprivate repos and CI on our own hardware
  • Pytestfrom one function to the whole pipeline
  • Locustload checks at 600 concurrent users (observed)
  • Rufflint and format in one fast pass
  • BasedPyrightstrict types, so Python's guesses get caught
  • uvdependencies locked in one file, installed in seconds
  • Nuitkapackaging & keygen.sh licensing

Things I've built

Personal projects

  • Mirrorling (opens in new tab) Mirrors a Linux desktop to a Samsung TV over AirPlay 2 — no dongle, no cloud account, nothing installed on the TV. Pairing, capture and encoding stay local, and it all ships as one file with a control panel and tray icon. Go · Linux · pre-release
  • TaskMaster (opens in new tab) A Django task manager that feels like a single-page app — HTMX swaps keep your filters in place, Celery beat writes the reminders, and notifications dedupe at the database level. Labels, a REST API and light/dark themes come along. Python · Django · HTMX
  • td (opens in new tab) A terminal task manager in Go with real vim editing — motions, operators, counts. TUI and scriptable CLI share one numbering, saves are atomic under a file lock, and projects sync two-way with a self-hosted GitLab, conflicts resolved by timestamp. Go · Apache 2.0 · tested per command
  • content-searcher (opens in new tab) Offline search across PDF and Word files where Arabic and English are equals — hamza, diacritics and letter variants fold to one spelling on both sides of the query, so documents match even when spellings disagree. Snippets keep the original text. Go · Wails · Vue · SQLite FTS5
  • pages_counter (opens in new tab) Counts pages straight out of .tar.zst archives — the archive streams through memory, never fully loaded, and parallel workers count the PDFs as they pass. CLI or GUI, with per-PDF detail on request. Python · CLI + GUI

Open-source contributions

  • ReGreet · #173 (opens in new tab) A wrong password shouldn't look like a broken system. This merged patch replaces the raw PAM error with "Authentication failed" — worded to stay true for lockouts too — and keeps the raw detail in the log where it belongs. Rust · merged Oct 2026
  • avante.nvim · #3310 (opens in new tab) The AI tool promised recursive deletion but called os.remove. This patch does it properly through libuv, guarding symlinks, .git metadata and project roots — and re-checks every guard after confirmation, because a path can change between asking and deleting. Lua · open · 43 targeted tests

Everything else lives on GitHub (opens in new tab)

The story so far

OEC · Sep 2023 – present · Cairo

First engineer, now leading two

Joined a company with no servers, no staging and no product of its own — the first job was finishing a website it had already sold (it is still in service), then building everything underneath: market research and hardware selection, one server running Proxmox, the products, deployment and backups. Those backups have already rebuilt a dead client server in about an hour, and the products now run at three on-prem sites. Today I lead two engineers, both hired as fresh graduates, on a team that runs Linux only — read how a thing is built, then tune it for the job — because the goal is bigger projects on the same team. Four interns have come through the same pairing and review.

One person, every stage — then a team.

OEC · Product · on-prem · live since Dec 2024

A platform rebuilt on purpose

Digitized files need somewhere to live, and clients didn't have one — that gap is why the platform exists. Requirements came out of client demo meetings, went into tracked issues, and whenever a request repeated across clients, it was built into the product. The first build answered the first requirements: Django with templates, in production. When the requirements moved somewhere that design couldn't follow, the choice was to replace it rather than defend it — Vue over a Django Ninja + Pydantic API, both builds still in production. Dual-engine search; three on-prem deployments, all live.

The design followed the requirements, not the other way round.

OEC · Throughput · 10-day deadline

Ten days, 220,000 pages

A client allowed 10 days for a large batch, so the pipeline was mapped step by step and checked against how similar processes are run, then automated end to end for this job — every stage a machine could own, human QC moved to random batches instead of every page. 220,000 pages by day 10, and work kept arriving: the job closed at 235,000 in 12. The server was chosen for value rather than its spec sheet, and every revision since has been asked to do more on less hardware.

Every page automated, a sample checked by hand.

OEC · Delivery · client site

The network is built on the spot

The server travels to the client's building and the network is built around it there: one switch, cables to the operator laptops, no connection out. The air-gap is what the delivery model is, so everything upstream assumes no internet — dependencies collected ahead of time, updates carried in as an image built on the office laptop, on a drive, loaded on site. Bare metal came first, in the office, before any client saw it; the component list kept growing, so containers took over. The first days are spent beside the operators, reading logs while their real work exercises the whole path; when nothing is left to fix, I leave, and the machine runs with nobody administering it.

Built on site, then left running alone.

OEC · Platform · air-gapped · since 2024

Self-hosted document AI

Software that reads scanned documents and pulls out the fields a client needs, on a machine inside their building. Qwen3.5-9B runs via llama.cpp beside Tesseract for plain OCR, and an operator reviews every page before export — except on the ten-day job, where the deadline forced sampled batches instead. That model is the current pick, not the only one tried — larger Qwen and Gemma variants have run on the same GPUs, and the testing continues so every deployment gets the most the hardware already bought can give. Profiling cut measured per-page time ≈62%; the deadline job later pushed far more work through the same platform, a gain nobody stopped to measure, so it stays unquoted.

Customer data never leaves the building.

OEC · Ingest · scanner side

Paper in, fields out

The scanner side of the same system. QR codes split a batch of scans into individual documents, checks catch faded pages, and an in-house-trained orientation model I integrated straightens pages on the GPU instead of one at a time.

Pages arrive sorted, straightened and read.

OEC · Reliability · single host

Background work that survives

Long jobs run in the background without losing work. Each kind of job gets its own queue, the database records what still has to happen, health checks watch the stack, and a sweep every half hour re-drives anything stuck.

A lost message costs delay, never a job.

OEC · Backup · 2024 · first air-gapped site

The backup that ate two months

At the first air-gapped site a backup was wired to the wrong device and wiped a drive. The outputs went; the source scans survived, because every kind of media had always lived on its own drive. The pipeline was run again from the inputs, and colleagues across the company worked through job after job by hand to confirm everything was really back.

Splitting the media is what saved the work.

OEC · Operations · client site · Jun 2025

Recovery, executed

A client's server died. I rebuilt the system from backups onto replacement hardware in about an hour and nothing was lost; the site was down only while the new machine was bought.

Zero data loss — the only cost was the replacement machine.

OEC · Cloud · three systems since 2024

Three systems, none of them the product

Three client systems, separate from the digitization products. The first is the website from the first weeks — half-built by someone before me and in a mess: every broken part fixed, then deployed, and still in service; the certificate-expiry outage that came later was root-caused and engineered out with auto-renewing TLS. The other two were built from scratch: a mobile app's backend on DigitalOcean, and a student management system, live and in its final feedback round before its users start on it. Cloudflare in front of all three, layered firewalls under it; uptime monitoring exists only on the mobile backend.

The outage class is eliminated, not just the incident.

B.Sc. Computer Systems Engineering — Shoubra Faculty of Engineering, Benha University · 2020

Client work is private — I'm glad to walk through any of it.