Backend Developer (Go)

Quick Facts

• Role: Backend Developer (Go)
• Focus: Go-based microservices, REST APIs, event-driven messaging, and PostgreSQL for payment and e-wallet systems

Description

You will develop and operate backend services in Go that power payment microservices, including REST API design, integrations, and versioning. The role involves event-driven communication using RabbitMQ and CloudEvents, database schema and transaction work in PostgreSQL, and continuous architecture improvements for reliability and performance.

Responsibilities

• Build and run Go backend microservices for payment systems
• Design and maintain REST APIs and service-to-service contracts, including versioning and backward compatibility
• Implement event-driven/asynchronous messaging via RabbitMQ and CloudEvents
• Design PostgreSQL structures, transactions, migrations, and optimize database operations
• Improve existing services, integration layers, and participate in designing new gateway components
• Contribute to quality and reliability through automated tests, code reviews, and troubleshooting/optimizations
• Collaborate technically with other developers to establish standards and propose pragmatic solutions

Requirements

• 5+ years of backend development experience
• 2–3+ years of Go in production
• Strong Go knowledge (goroutines, channels, context, concurrency, application performance)
• Experience with REST API and microservice design and operation
• Strong PostgreSQL knowledge (transactions, migrations, database design)
• Experience with message brokers (ideally RabbitMQ or Kafka)
• Knowledge of Docker, Kubernetes, and CI/CD principles
• Commitment to testing, code reviews, and readable code
• Ability to communicate in Czech/Slovak and handle technical communication in English

Benefits

• Real impact on product development
• Ability to propose changes and reduce technical debt through architecture and automation improvements
• Small team with direct communication and close collaboration with developers, analysts, and product decision-makers
• Technically interesting work on payment systems that must be fast, secure, and reliable
• A continuously evolving environment where priorities and processes may change as the product grows