---
title: "Senior Backend Engineer at Nexovia Systems"
description: "In short: Go engineer for the core of a B2B multi-tenant transaction platform. Ledgers, balances, real-time transactions, rewards and the partner integrations behind them, for many brands at once, on"
---

# Senior Backend Engineer

**Company:** Nexovia Systems  
**Location:** Tbilisi, Georgia  
**Posted:** 2026-11-20

**Tags:** backend

[Apply / View original posting](https://www.linkedin.com/jobs/view/4491962076)

## Job description

In short: Go engineer for the core of a B2B multi-tenant transaction platform. Ledgers, balances, real-time transactions, rewards and the partner integrations behind them, for many brands at once, on Kafka, PostgreSQL and Redis, running on AWS, with ScyllaDB and Aerospike next on our scaling path. Remote, mid to senior. About Nexovia Systems At Nexovia Systems we build and run a multi-tenant transaction platform that businesses use to launch and operate their own consumer products. It covers customer accounts, balances, payments, real-time transactions, rewards, CRM and back-office tooling, delivered as a service. One platform powers many brands across different markets, each with its own configuration, partners and requirements. Because the platform moves real money around the clock, we care about correctness first and speed second, and we ship to production every day. What you'll work on • The wallet and the ledger: balances, holds, reward balances, double-entry movements and reconciliation, exact to the cent. • Transaction lifecycles: authorise, settle, void and reverse, with partner callbacks that arrive late, twice or out of order. • Rewards and incentives: cashback, credits, loyalty programmes and eligibility rules, all configured per brand. • The event backbone on Kafka: transactional outbox, idempotent consumers, sagas with compensation, dead-letter handling and replays. • Data at scale: PostgreSQL with declarative partitioning and retention, Valkey (Redis) for caches and rate limits, ClickHouse for reporting. Our ScyllaDB and Aerospike read models are written and tested but not in production yet; they switch on when load requires. • Scaling the platform past today's ceiling: load tests, profiling, connection pooling, read replicas for reads that are not money, and sharding on tenant_id when one primary is not enough. • Taking the ScyllaDB per-customer history read models and the Aerospike balance cache from code to production: backfill, verify against PostgreSQL, switch reads service by service. • Third-party integrations: payment providers (instant payments in and out, such as Pix), partner platforms that debit and credit customer balances in real time through our APIs, real-time data feeds, KYC and CRM, and our Partner Payments API. Signed and unsigned webhooks, read-back confirmation, reconciliation against statements. • Multi-tenancy: tenant isolation with PostgreSQL row-level security, per-brand settings and feature switches, never a leak between brands. • Shared foundations: our shared Go packages (the tenant-scoped transaction, the outbox, the exactly-once inbox, circuit breakers) and contract-first APIs with protobuf/buf, OpenAPI and versioned JSON Schema events. Responsibilities • Design and build Go services and gRPC/REST APIs that move money correctly under retries, timeouts and partial failure. • Write the tests that prove it: unit, DB integration, idempotency and concurrency (race) tests, written to fail first. • Change live schemas safely: online migrations, lock timeouts, partition swaps, backfills. • Own your service in production: metrics, logs and traces, canary rollouts, rollback. • Review code and designs with the team, with a strong focus on money paths. About you • 5+ years building backend systems; 3+ years with Go in production. • You have built or run systems that move money or value: wallets, payments, trading or fintech. • Distributed systems in practice: idempotency keys, exactly-once effects over at-least-once delivery, outbox, sagas, ordering, back-pressure. • Kafka in production: partitions, consumer groups, offsets, rebalances, lag. • Strong PostgreSQL: indexes, query plans, locking, partitioning, RLS, migrations without downtime. • Comfortable with Redis/Valkey, caching and rate limiting at high volume. • You have made a system faster and can show it: load tests (k6 or Gatling), pprof, flame graphs, before and after numbers. • You read a flame graph and a slow query plan, and you know when a cache is the wrong fix. • Clear written English; you explain trade-offs in a few lines. Nice to have • Rust, for hot paths where Go is not enough. • ScyllaDB/Cassandra or Aerospike in production: data modelling per partition, consistency trade-offs, operations. • PostgreSQL sharding (Citus or similar) and multi-region data. • Real-time balance integrations with partners, settlement engines, rewards and incentive engines. • ClickHouse, protobuf/buf, OpenTelemetry. • Kubernetes (EKS), Argo CD and Argo Rollouts, Istio, Terraform, AWS with several accounts. • Regulated markets, regulatory reporting and audit trails. Our Stack Go · gRPC · protobuf (buf) · Kafka (AWS MSK) · PostgreSQL 18 (RDS) · Valkey/Redis (ElastiCache) · ClickHouse Cloud · Kubernetes (EKS, Karpenter, KEDA) · Argo CD and Argo Rollouts · Istio (ambient) · Kyverno · Terraform · Cloudflare · GitLab CI · OpenTelemetry, Prometheus, Loki, Tempo, Grafana. Next on the scaling path: ScyllaDB, Aerospike, PostgreSQL sharding (Citus). How we work • Every change goes to staging first. In production the wallet and payment services roll out as canaries that abort on their own when errors rise; every roll is watched and has a written rollback. • Money changes are exact, server-side, idempotent and audited. One money change rolls at a time. • Money is watched, not trusted: the ledgers are checked against each other every 15 minutes and reconciled every day, and every tenant table has row-level security forced, checked by tests. • Small PRs, tests before code on money paths, written decisions instead of long meetings. What we offer • Fully remote work. • A competitive salary, above the market average, set by your experience level. • Real ownership: you design, ship and run what you build, and you see it handle real money in production. • Room to grow: as the platform and the team grow, your scope grows with them, towards technical leadership or leading people if that is where you want to go. • A young, fast-moving team that ships every day, keeps meetings short and writes things down. • Commitment that gets noticed: people who care about the product and own their work are trusted with the bigger problems. • Hard problems worth solving: real money, many brands and high volume, where correctness matters. Skills to tag: Go, Distributed Systems, Apache Kafka, PostgreSQL, ScyllaDB, Aerospike, Rust, gRPC, Payments, AWS

---

🔔 [Monitor similar jobs on Gurify](https://gurify.com/?utm_source=techgeo&utm_medium=jobboard&utm_campaign=monitor_similar&role=Senior+Backend+Engineer) — get alerted when matching roles are posted in Georgia.

```json
{"@context":"https://schema.org/","@type":"JobPosting","title":"Senior Backend Engineer","description":"<p>In short: Go engineer for the core of a B2B multi-tenant transaction platform. Ledgers, balances, real-time transactions, rewards and the partner integrations behind them, for many brands at once, on Kafka, PostgreSQL and Redis, running on AWS, with ScyllaDB and Aerospike next on our scaling path. Remote, mid to senior. About Nexovia Systems At Nexovia Systems we build and run a multi-tenant transaction platform that businesses use to launch and operate their own consumer products. It covers customer accounts, balances, payments, real-time transactions, rewards, CRM and back-office tooling, delivered as a service. One platform powers many brands across different markets, each with its own configuration, partners and requirements. Because the platform moves real money around the clock, we care about correctness first and speed second, and we ship to production every day. What you'll work on • The wallet and the ledger: balances, holds, reward balances, double-entry movements and reconciliation, exact to the cent. • Transaction lifecycles: authorise, settle, void and reverse, with partner callbacks that arrive late, twice or out of order. • Rewards and incentives: cashback, credits, loyalty programmes and eligibility rules, all configured per brand. • The event backbone on Kafka: transactional outbox, idempotent consumers, sagas with compensation, dead-letter handling and replays. • Data at scale: PostgreSQL with declarative partitioning and retention, Valkey (Redis) for caches and rate limits, ClickHouse for reporting. Our ScyllaDB and Aerospike read models are written and tested but not in production yet; they switch on when load requires. • Scaling the platform past today's ceiling: load tests, profiling, connection pooling, read replicas for reads that are not money, and sharding on tenant_id when one primary is not enough. • Taking the ScyllaDB per-customer history read models and the Aerospike balance cache from code to production: backfill, verify against PostgreSQL, switch reads service by service. • Third-party integrations: payment providers (instant payments in and out, such as Pix), partner platforms that debit and credit customer balances in real time through our APIs, real-time data feeds, KYC and CRM, and our Partner Payments API. Signed and unsigned webhooks, read-back confirmation, reconciliation against statements. • Multi-tenancy: tenant isolation with PostgreSQL row-level security, per-brand settings and feature switches, never a leak between brands. • Shared foundations: our shared Go packages (the tenant-scoped transaction, the outbox, the exactly-once inbox, circuit breakers) and contract-first APIs with protobuf/buf, OpenAPI and versioned JSON Schema events. Responsibilities • Design and build Go services and gRPC/REST APIs that move money correctly under retries, timeouts and partial failure. • Write the tests that prove it: unit, DB integration, idempotency and concurrency (race) tests, written to fail first. • Change live schemas safely: online migrations, lock timeouts, partition swaps, backfills. • Own your service in production: metrics, logs and traces, canary rollouts, rollback. • Review code and designs with the team, with a strong focus on money paths. About you • 5+ years building backend systems; 3+ years with Go in production. • You have built or run systems that move money or value: wallets, payments, trading or fintech. • Distributed systems in practice: idempotency keys, exactly-once effects over at-least-once delivery, outbox, sagas, ordering, back-pressure. • Kafka in production: partitions, consumer groups, offsets, rebalances, lag. • Strong PostgreSQL: indexes, query plans, locking, partitioning, RLS, migrations without downtime. • Comfortable with Redis/Valkey, caching and rate limiting at high volume. • You have made a system faster and can show it: load tests (k6 or Gatling), pprof, flame graphs, before and after numbers. • You read a flame graph and a slow query plan, and you know when a cache is the wrong fix. • Clear written English; you explain trade-offs in a few lines. Nice to have • Rust, for hot paths where Go is not enough. • ScyllaDB/Cassandra or Aerospike in production: data modelling per partition, consistency trade-offs, operations. • PostgreSQL sharding (Citus or similar) and multi-region data. • Real-time balance integrations with partners, settlement engines, rewards and incentive engines. • ClickHouse, protobuf/buf, OpenTelemetry. • Kubernetes (EKS), Argo CD and Argo Rollouts, Istio, Terraform, AWS with several accounts. • Regulated markets, regulatory reporting and audit trails. Our Stack Go · gRPC · protobuf (buf) · Kafka (AWS MSK) · PostgreSQL 18 (RDS) · Valkey/Redis (ElastiCache) · ClickHouse Cloud · Kubernetes (EKS, Karpenter, KEDA) · Argo CD and Argo Rollouts · Istio (ambient) · Kyverno · Terraform · Cloudflare · GitLab CI · OpenTelemetry, Prometheus, Loki, Tempo, Grafana. Next on the scaling path: ScyllaDB, Aerospike, PostgreSQL sharding (Citus). How we work • Every change goes to staging first. In production the wallet and payment services roll out as canaries that abort on their own when errors rise; every roll is watched and has a written rollback. • Money changes are exact, server-side, idempotent and audited. One money change rolls at a time. • Money is watched, not trusted: the ledgers are checked against each other every 15 minutes and reconciled every day, and every tenant table has row-level security forced, checked by tests. • Small PRs, tests before code on money paths, written decisions instead of long meetings. What we offer • Fully remote work. • A competitive salary, above the market average, set by your experience level. • Real ownership: you design, ship and run what you build, and you see it handle real money in production. • Room to grow: as the platform and the team grow, your scope grows with them, towards technical leadership or leading people if that is where you want to go. • A young, fast-moving team that ships every day, keeps meetings short and writes things down. • Commitment that gets noticed: people who care about the product and own their work are trusted with the bigger problems. • Hard problems worth solving: real money, many brands and high volume, where correctness matters. Skills to tag: Go, Distributed Systems, Apache Kafka, PostgreSQL, ScyllaDB, Aerospike, Rust, gRPC, Payments, AWS</p>","identifier":{"@type":"PropertyValue","name":"TechGeo","value":"4491962076"},"url":"https://techgeo.ge/job/senior-backend-engineer-f8a2556","jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Tbilisi","addressCountry":"GE"}},"hiringOrganization":{"@type":"Organization","name":"Nexovia Systems"},"directApply":false,"datePosted":"2026-11-20","validThrough":"2026-12-20T23:59:59+04:00","jobLocationType":"TELECOMMUTE","applicantLocationRequirements":{"@type":"Country","name":"Georgia"}}
```
