Hiring London based Go Engineers (Mid-Senior) – Building Real Payment Infrastructure
If you care about:
-
Writing clean, idiomatic Go
-
Designing systems that don’t fall over at scale
-
Concurrency done properly (not just goroutines everywhere)
-
Low latency, high-throughput APIs
-
Production-grade distributed systems
…this might be worth a look.
The Context
We’re building core payment infrastructure at a scaling FinTech.
Not dashboards.
Not internal CRUD tools.
Actual transaction-processing systems moving real money.
Think:
-
Idempotent payment flows
-
Exactly-once / at-least-once tradeoffs
-
Event-driven architecture
-
Failure handling & graceful degradation
-
Observability that actually matters
The Stack
-
Go (primary language)
-
gRPC / REST
-
Kafka (event-driven architecture)
-
PostgreSQL
-
Kubernetes
-
AWS
We care about:
-
Clear interfaces
-
Proper error handling
-
Testing (unit + integration)
-
Performance profiling
-
Simplicity over cleverness
You’ll Probably Enjoy This If
-
You’ve built backend systems in Go in production
-
You understand context propagation & cancellation
-
You think about race conditions before they happen
-
You’ve debugged something painful in prod and lived to tell the story
-
You prefer shipping well-designed systems over over-engineering
Payments experience is a bonus. Strong engineering fundamentals matter more.
Level
Mid-level or Senior
(If you can own services end-to-end, we want to talk.)
If you’re interested, open to a conversation, or just curious about the architecture - DM me or drop a comment.
Happy to share more technical detail.