Requirements

Expected technologies

SQL

PostgreSQL

CI/CD

REST/gRPC

Linux

Docker

microservices

Prometheus

Grafana

RabbitMQ

Operating system

Linux

Our requirements

• 2–4+ years of hands-on Go development in production environments.
• Strong knowledge of Linux and shell tooling.
• Solid understanding of concurrency (goroutines, channels, sync primitives), memory management, and idiomatic Go patterns.
• Experience building and consuming REST/gRPC APIs; protobuf familiarity.
• Confident with databases: SQL (e.g., PostgreSQL/MySQL) and at least one NoSQL store; query optimization and migrations.
• Message brokers/queues experience (e.g., RabbitMQ, NATS, Kafka) and event-driven design.
• Containerization and CI/CD (Docker; familiarity with Kubernetes or Nomad is a plus).
• Git proficiency and standard branching/review workflows.
• Observability tools (Prometheus/OpenTelemetry, Grafana, structured logging) and troubleshooting in distributed systems.
• Ability to analyze production issues from support tickets and turn them into stable fixes.
• English sufficient for technical documentation and team communication.

Your responsibilities

• Design, develop, and maintain production-grade services in Go (microservices, CLI tools, daemons).
• Implement new features, optimize existing functionality, and drive architectural improvements.
• Handle L3 support requests: investigate incidents, process support tickets, provide root-cause analysis, and create permanent fixes.
• Integrate and interact with peripherals (sensors, controllers, edge devices), including protocol handling, I/O, and hardware diagnostics.
• Write clean, testable, and maintainable code with unit/integration tests and benchmarks.
• Profile and debug performance issues (pprof, tracing), improve reliability and latency.
• Participate in design reviews, code reviews, and technical discussions; mentor junior engineers.
• Collaborate closely with frontend, UX/UI, QA, DevOps to deliver end-to-end solutions.
• Maintain service observability (metrics, logs, alerts) and contribute to runbooks and on-call readiness.
• Document APIs, modules, and operational procedures.