We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →
← All jobs

Senior Backend Engineer — Distributed Systems (Go, C++, Rust)

SeniorhybridGdynia, PL →2w ago
Market insights
📊 Backend: salaries and demand on the market
Stack
GoC++RustRTSPWebRTCGStreamerc++cloudgolinuxmysqlpostgresql
Details
English
required
Show company and link
Free, after you sign in.
Apply
Open the company and the link above — your application goes straight into the company's hiring system, no middlemen.

Description

About the role

Senior Backend Engineer — Distributed Systems (Go, C++, Rust) Company: Trineo Location: Gdynia, Poland — Remote or Hybrid Contract: B2B English: Communicative (written & spoken) About the project You’ll join a small, dedicated team building a cloud-based Video Surveillance platform for our client — a US company in the security industry. This role sits at the edge of that platform: Go services deployed on edge devices that handle video recording and watchdog duties, WebRTC media relay, multi-node coordination, and delivery of events into downstream alarm systems. It’s a production-grade system with real users and real uptime expectations — when something breaks here, it breaks on real hardware in the field.

We’re looking for a senior owner who can architect and ship a service end-to-end, dig deep into Go runtime behavior (goroutines, atomic pointers, race detection, pprof memory analysis), and reason about real-world distributed-systems failure modes. What you’ll do Own one or more Go services in the edge stack: recording, media relay, event bridge, or panel-side integrations Build and harden multi-node coordination protocols — time-source ownership, recording handover, peer health detection Diagnose tricky production issues — think “recorder restarting hundreds of times over a few hours” or “goroutine leak with multi-GB anon memory after a few hours”: read journal logs, capture coredumps, write the fix Design and implement health and observability surfaces: /health endpoints,

Full description, company and the link to apply — after you sign in. Sign in
Employer contacts (email/phone/telegram) are hidden from the public preview.
Urgent question? Message @termdocs