Fullstack Software Engineer - Backend & Devops

We are now hiring a mid-level Software Engineer, weighted toward backend and DevOps, to help us build one of the most demanding things a team can build: a wallet and payment ecosystem where money must be correct every single time.

The project you'd be working on

You'd join the team building a national-scale wallet and payment platform - a ledger-backed system that moves real money between real people, under real regulatory obligations. Think double-entry ledger, exactly-once money movement, two-phase holds, reconciliation to zero variance at daily close, KYC/AML, and a zero-trust security posture. Mistakes here are not cosmetic; they are financial.

This is event-driven, service-oriented backend work with a heavy operational footprint: self-hostable, data-resident infrastructure where you own the system in production, not just in the repo.

What this role is really about

At KVY TECH, we care about three things - in this order:

1. Strong computer science fundamentals. Frameworks change. Fundamentals do not. We want engineers who understand what is actually happening beneath the abstractions - especially when the abstraction is a ledger and the thing underneath is someone's money.
2. Product thinking. You should not need to be told why a feature exists. In a payment system, "why" is often a regulatory, correctness, or trust requirement - you should be able to work backwards from the business and compliance context to the technical decision, and push back when the two do not line up.
3. AI-native fluency. AI tools are part of how we work. You should use them with judgment: not to skip the thinking, but to think faster and sharper. You are responsible for every line that ships - and in a financial system, that accountability is not negotiable.

What you will do

• Own backend services end to end - from understanding the business and compliance problem, to design, to implementation, to production, to whatever comes after production.
• Own the DevOps and platform side. Containerized services, CI/CD with build/test/dependency-and-secret-and-container scanning, infrastructure-as-code, data-resident deployments, secrets management, and observability (metrics, logs, traces). You keep the system running, not just shipping.
• Design for correctness and failure. Idempotency, reconciliation, retries, concurrency, and DR/failover runbooks are part of the job, not an afterthought.
• Contribute to architecture decisions, not just execute them - including the trade-offs behind broker choice, authz approach, and self-host-vs-managed.
• Build the thin edges too. Enough full-stack range to build BFFs and touch the React admin console when the feature needs it - you're backend-first, but you're not backend-only.
• Use AI coding assistants daily as a thought partner and force multiplier, while staying accountable for correctness, security, and quality.
• Write code a teammate can pick up six months from now without cursing your name - and participate in code review as both author and reviewer, because quality is a team sport.

What we are looking for

Computer science fundamentals

• Solid grasp of data structures, algorithms, and their trade-offs - not memorized, internalized.
• Real comfort reasoning about system design under money constraints: concurrency, consistency, idempotency, exactly-once semantics, latency, and failure modes. You know why "check-then-act" is a bug and what a two-phase commit buys you.
• Strong sense for what is actually happening under the hood - databases, transactions, networks, message queues, runtimes, memory.
• You can explain a complex technical topic - say, why balances should be derived from a ledger rather than stored - in plain language. If you cannot explain it, you do not understand it.

Backend & DevOps

• You are comfortable owning services in production: containers, orchestration, CI/CD pipelines, IaC, secrets, and observability.
• You understand event-driven architecture - brokers, outbox pattern, consumer idempotency, schema evolution - and the traps in each.
• You've operated stateful systems (relational databases, caches, queues) and know the difference between "it works on my machine" and "it survives a node failure at 2 a.m."
• Security is a default, not a feature: TLS/mTLS, least privilege, secrets handling, and not trusting the client.

Product thinking

• You ask who benefits, what changes for them, how will we know it worked before you ask what framework should I use.
• You are comfortable saying "we should not build this" when the evidence points that way.
• You think in outcomes, not outputs - and you treat client, business, and regulatory context as first-class inputs to technical decisions.

• 3+ years of professional software engineering experience, ideally shipping systems that real users and businesses depend on.
• Hands-on experience with most of the core stack, and the ability to get productive fast in the rest:
• Languages: TypeScript and/or Go (Python a plus)
• Backend: Node.js, service-oriented / event-driven architectures
• Data: PostgreSQL, Redis; message brokers (Kafka or equivalent)
• Frontend (working familiarity): React, Next.js, Tailwind CSS - enough to build BFFs and admin surfaces
• Infra & DevOps: Docker, Kubernetes, CI/CD, infrastructure-as-code, cloud (AWS), observability tooling (OpenTelemetry or similar)

• Competitive compensation
• Laptop and equipment available on request
• 15 days off annually
• Birthday off with a company gift
• Continuing education budget so you can keep learning outside of your day-to-day job
• Work with an exciting and growing company on genuinely hard technical problems - the kind where getting the fundamentals right actually matters

About KVY TECH We are a software engineering studio helping businesses modernize their digital infrastructure through composable, AI-augmented systems - so they can compete with companies twice their size. Since 2018, we have built composable commerce platforms, AI-powered products, and enterprise web systems for clients across the region. We are deliberately small and deliberately senior. Every engineer owns outcomes, not just tickets. Our aspiration is to be the Toyota of software development: predictable, high-quality, and obsessed with getting the fundamentals right every single time.