Last login: from 172.16.0.42
SESSION RESTORED: services online and pipelines green
guest@system:~$ ./boot --user nedyalko_demirev
Backend Engineer / DevOps Practitioner
I build APIs, delivery pipelines, and production systems that stay readable under load. The focus is backend ownership, deployment automation, and operational clarity.
MODE
SYSTEM
backend / ops profile
FOCUS
API + OPS
delivery and reliability
STATUS
ONLINE
available for backend work
STACK
APIs / Docker / CI
services and deployment flow
A compact system readout for the engineer behind the terminal.
I work closest to the systems layer: APIs, jobs, deployments, monitoring, and the small decisions that keep production calm. I like clear boundaries, predictable releases, and debugging that starts with evidence instead of guesswork.
user=nedyalko_demirev
class=backend_ops_engineer
mission=ship_services_that_survive_production
Capabilities presented like running services, host specs, and operational tooling.
Nedyalko Demirev
Bulgaria / EU Remote
Open for backend, infra, and automation work
shell fluency, host inspection, and system-level troubleshooting
containerized services, local parity, and deployable environments
automated delivery, validation gates, and repeatable releases
schema design, migrations, and safe data access patterns
logs, metrics, traces, and incident-friendly diagnostics
scripts, runbooks, environment setup, and deployment helpers
Selected systems listed like a directory index, with one expanded ops note.
2026-05-14
A personal site framed like a live shell session: boot sequence, command-led navigation, reusable terminal primitives, and an ops-first narrative that keeps the implementation readable.
2026-04-02
A delivery workflow that promotes builds through consistent checks, environment parity, and deployment steps you can trust under pressure.
2026-02-18
An operational view into service health, tracing, and failure modes with enough signal to shorten debugging loops and reduce guesswork.
| PERMISSIONS | UPDATED | NAME | STATUS | SIZE |
|---|---|---|---|---|
| -rwxr-xr-x | 2026-05-14 | terminal-portfolio A personal site framed like a live shell session: boot sequence, command-led navigation, reusable terminal primitives, and an ops-first narrative that keeps the implementation readable. | ACTIVE | 14K |
| -rw-r--r-- | 2026-04-02 | deploy-pipeline-lab A delivery workflow that promotes builds through consistent checks, environment parity, and deployment steps you can trust under pressure. | STABLE | 28K |
| -rw-r--r-- | 2026-02-18 | service-observability An operational view into service health, tracing, and failure modes with enough signal to shorten debugging loops and reduce guesswork. | MAINTAINED | 19K |
terminal-portfolio :: ACTIVE
A personal site framed like a live shell session: boot sequence, command-led navigation, reusable terminal primitives, and an ops-first narrative that keeps the implementation readable.
root@services:~$ cat ./runbooks/terminal-portfolio.md
> structured to show systems thinking instead of generic personal-site language
> centered on repeatable deployment, diagnostics, and service ownership
> tuned for mobile so the page still reads like a terminal client
A compressed timeline of the kind of systems work this node is optimized for.
Building backend services and delivery workflows
Shipping systems that balance correctness, clarity, and operational safety without drifting into unnecessary complexity.
Automating releases and environment setup
Improving delivery speed by standardizing pipelines, environment handoffs, and repeatable service checks early.
Sharpening observability and incident response habits
Treating backend work as both engineering and operations, not just request handling.
Open a line if you want backend delivery that cares about reliability, deployment flow, and operational clarity.
If you need someone who can own backend delivery end-to-end, from API design to deployment and operations, this node is accepting inbound requests.
guest@system:~$ ping delivery-node
reply: stable connection
reply: async-friendly workflow
reply: implementation + ops judgment available
PROJECT STATUS
available for selected collaborations
remote-friendly / async-friendly / ops-aware
RESPONSE TIME
< 48h
for serious inquiries and delivery discussions