Zuzex
Backend developer
Feb 2023 — Present
I develop Go services for distributed audio processing, contribute to architecture and code review, and own CI/CD pipelines.
Go / gRPC / Kafka / NATS / PostgreSQL / OpenTelemetry
Sergey / Go backend engineer
Go backend.Built for failure and load.
I’m Sergey. I build Go services for streaming audio, event processing and cloud infrastructure, with explicit handling of failures, retries and load.
GoPostgreSQLKafkagRPCCloud
Experience & impactProfessional experience & impact
Full experience →Less latency. More room to scale.
Webpraktik
Backend developer
May 2022 — Jan 2023
REST APIs and external service integrations, backed by PostgreSQL and Redis. Containerized applications, wrote unit tests, and participated in code review and CI/CD.
REST / PostgreSQL / Redis / Docker
Audio chunk processing
200ms30 ms
I profiled the critical path and removed processing bottlenecks in distributed audio services.
- Less processing time
- 85%
- Processing speedup
- 6.67×
- Lower API latency
- 15–20%
- Intent Macro F1
- +0.1
- Entity F1
- ≈ +0.1
- Negation errors
- 4× fewer
- JSON validity
- +5–6 pp
Selected engineering work
Three perspectives on backend engineering: an experiment, a learning system, and professional practice.
Serverless / Experimental
FuncWarm
Serverless Warmup Control Plane.
A Go control plane for scheduled Cloud Run warmups.
The decision
Schedule requests independently; observe the full round trip.
Go / GCP Cloud Run / HTTP / Observability
Read case studyEvent-driven / Learning project
EventForge
Order processing with an outbox and idempotent consumers.
An order-processing system built around delivery guarantees.
The decision
Commit order and outbox together; deduplicate at the consumer.
Go / PostgreSQL / Kafka / Docker
Read case studyProfessional practice / Integration
Voice / ML Platform
Go services for streaming audio and ML integrations.
Backend interfaces between voice workflows and ML services.
The decision
Propagate context and cancel stale output across service boundaries.
Go / gRPC / NATS / Kafka / PostgreSQL / OpenTelemetry
Read case studyInteractive engineering lab
Open EventForge →Follow a request through the system.
Scroll to build the map. Explore delivery, durable writes and idempotency at your own pace.
cover / architecture labArchitecture demo
Trace the decision.
active / committedretryfailure / cancellation
Step 1 / 5Ready
A request is only the beginning.
Follow order-42 from request to durable write, delivery and an idempotent business update.
- Delivery
- not started
- Effect
- 0 changes
Inspect / Request
A request begins a workflow, not a guarantee of completion.
Technical focus
Go services, data and operations.
Go at the core. Clear contracts between services. Enough observability to understand what happens in between.
- Services & interfaces
- Go / REST / gRPC
- Data & messaging
- PostgreSQL / Redis / Kafka / NATS
- Infrastructure
- Docker / Linux / GCP / CI/CD
- Observability
- OpenTelemetry / Prometheus / Grafana
Let’s talk
Let’s discuss your backend project.
I’m happy to discuss Go roles, distributed systems and backend architecture.
Write an emailbxmbuksss@gmail.com