Principal Golang Engineer

About The Role We are looking for a Principal Golang Engineer to help build our next-generation financial control system.

The FinnOps team develops services for financial reconciliation, real-time accounting, data consistency checks, and integrations with financial data providers. The system is built in Go and designed for high performance, scalability, and auditability.

This is a hands-on individual contributor role with an approximate 80/20 balance between coding and architecture. You will design and implement complex backend components, make key technical decisions, and help maintain high engineering standards across the team.

Job Description Design and implement backend services in Go.

Develop components for financial reconciliation, accounting, data processing, and provider integrations.

Define service boundaries, data ownership, APIs, and event flows.

Design reliable asynchronous processing and failure-recovery mechanisms.

Ensure data consistency, traceability, and auditability.

Make technical decisions related to performance, scalability, and reliability.

Review code and technical designs.

Prepare RFCs, system diagrams, and sequence diagrams for architecture reviews.

Help engineers solve complex technical problems and improve engineering practices.

Qualifications You have:

5+ years of backend software development experience, with strong production experience in Go.

Experience designing and building distributed systems.

Strong knowledge of PostgreSQL, including transactions, locking, indexing, and query optimization.

Experience with event-driven architecture and at least one message broker.

Understanding of idempotency, retries, duplicate processing, message ordering, and partial failures.

Experience with gRPC, Protocol Buffers, and HTTP APIs.

Experience with Docker and Kubernetes.

Ability to independently design complex technical solutions and clearly document architectural decisions.

Russian for day-to-day team communication and English for code and technical documentation.

Would Be a Plus Production experience with NATS.

Experience with event sourcing or append-only data models.

Experience with financial, payment, reconciliation, ledger, or accounting systems.

Experience with OpenAPI, ogen, sqlc, or other spec-first development tools.

Experience with distributed tracing, structured logging, metrics, and production diagnostics.