System test coupon
End-to-end verification
Interface
- range
- Angular · React
- focus
- the screen
Application
- range
- TypeScript · Node
- focus
- the logic
Platform
- range
- Docker · CI/CD
- focus
- the runtime
Network
- range
- Linux · infrastructure
- focus
- the path
From UIto infrastructure.
Giorgi PaikidzeFull-Stack TypeScript Engineer
- Web
- 5Y
- Infrastructure
- 5Y
I build TypeScript systems end to end - Angular and React on top, Node underneath - backed by five years running the infrastructure those systems depend on.
GP-FT-001
- CH-01
- 5Yweb development
- CH-02
- 5Yinfrastructure
- CH-03
- UTC+4Tbilisi, Georgia
- CH-04
- OPENavailable for work
Selected evidence.
Real work, with the problem, constraints, decisions, and disclosure attached. No anonymous “case study” theatre.
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
Angular / TypeScript
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
Customer CRM
An internal CRM for managing the bank's customers and clients. I redesigned screens, added features, built a reusable component layer, and cut the app's change-detection load.
EvidenceTraced a single keystroke in one input to 17+ change-detection runs and brought it down to 3
- result
- change detection per keystroke: 17+ runs → 3
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.”
Irakli PavliashviliCloud & Security Operations Manager, Prodware Georgia
RecordedThe layers I can cross.
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-02inference
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-03platform
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-04network
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.
- 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.
Bring me the complicated part.
A build, migration, performance problem, or role that needs someone comfortable on both sides of the deployment boundary.