- Grounding
- A knowledge base generated from the same project and post files this site renders.
- Guardrails
- Answer from that base, decline when the evidence is missing, and keep withheld names withheld.
- Fit check
- Paste a job description for an honest comparison, including the gaps - not a flattering rewrite.
- Plumbing
- A streaming API route with per-IP rate limiting and a deliberately narrow scope.
Rust & TypeScript engineerInfrastructure-minded builder
GiorgiPaikidze
I build products in TypeScript and back ends in Rust, from the interface down through the services, delivery pipelines, and infrastructure underneath.
02 / Selected work
Work built to hold up.
Product work and independent builds, documented with the decisions, constraints, and honest boundaries intact.
POS Terminal Management
An internal platform for operating a POS terminal estate from the browser - devices, merchants, commands, batch operations and transactions, with a live analytics dashboard and reporting. Built from scratch in zoneless Angular.
EvidenceBuilt from scratch in modern Angular - signals throughout, and no zone.js
- scale
- 50,000+ POS terminals, up to 200 operations/second
Angular / TypeScript
Cadence
A scheduling API in Rust: hosts publish weekly availability rules, invitees book the slots those rules generate, and confirmation and reminder emails leave through a transactional outbox so they can never describe a booking that did not happen.
EvidenceAvailability is stored as weekly rules rather than materialised slots - `slots_for_day` expands a rule into bookable start times on request, so a host edits one row instead of a calendar
Rust / Axum / Tokio / sqlx / PostgreSQL
Betsson.ge
An online gaming platform where registration was gated behind identity verification. I separated the two, so an account can be created first and verified inside a window afterwards.
EvidenceSplit a single coupled sign-up flow into two independent processes - registration, then verification
- result
- verification no longer blocks registration
Angular / TypeScript
Observed by someone else.
One real recommendation carries more weight than a wall of anonymous praise.
“Giorgi has analytical skills that set him apart from many engineering counterparts.”
04 / Range
I design the interface. And own what runs it.
Most problems ignore team boundaries. I can follow one from the interface through application state, delivery, Linux, and the network below it—then fix the layer that is actually failing.
- CH-01interface
Full-Stack TypeScript
5 years professional experience
Angular and React on the front end, Node underneath, TypeScript throughout. Signals, NgRx, and the state and performance work that keeps a large application responsive as it grows.
Inspect project evidence - CH-02services
Rust Services
Current build focus
Async HTTP services on Axum and Tokio, Postgres through sqlx with queries checked against the schema at compile time, Argon2 sessions, and background workers. Cadence is the worked example: a booking API where conflicts are a database constraint and email leaves through a transactional outbox.
Read the Rust case study - CH-03inference
AI Engineering
Current focus area
Working toward production AI rather than demos. The assistant on this site is the current artifact: an API route grounded in a knowledge base generated from this repo's own content, with guardrails that make it decline rather than invent.
Test the live artifact - CH-04platform
DevOps & Delivery
Working knowledge
Containers, CI/CD pipelines, build and environment configuration - the deployment end of the applications I build, rather than a platform practice of its own.
See deployment evidence - CH-05network
Network Administration
5 years, before development
Networking, Linux, and infrastructure. It is the reason a problem stops being someone else's the moment it turns out to sit below the application.
Read the experience record
Don’t take the AI claim on trust.
The assistant on this site is the artifact. Ask it about my work, or give it a job description and let it tell you where I do - and do not - match.
06 / Get in touch
Bring me the complicated part.
A build, migration, performance problem, or role that needs someone comfortable on both sides of the deployment boundary.