Senior AI Engineer (Go/Ruby) – Gateways & Enterprise AI Infrastructure

Responsibilities

We're building the infrastructure layer that connects enterprise systems to AI: an MCP Gateway, an AI Gateway, and the services around them. These are the systems that sit between LLM providers and everything else — routing, auth, rate limiting, observability, protocol translation. We're looking for a Senior Software Engineer (Go/Ruby) – Gateways & Enterprise AI Infrastructure who understands both the systems layer and the AI protocol layer, and who can build production-grade services in Go and/or Ruby.

In this role, you will also be responsible to:

• Design and develop the MCP Gateway and AI Gateway — production services that mediate between applications, AI agents, and LLM providers. This means protocol-level work: MCP server/client implementations, request routing, streaming, tool-call proxying, authn/authz, and tenant isolation. You'll build the core infrastructure, not just applications on top of it.

• Build high-throughput, low-latency network services. You'll work close to the wire: TCP, TLS, HTTP/1.1 and HTTP/2, JSON streaming, connection pooling, backpressure. When latency matters, you'll know exactly where it goes.

• Own the data layer from the application side. Deep PostgreSQL knowledge — schema design, indexing strategies, query planning, transactions and isolation levels, connection management. You're not a DBA, but you can read EXPLAIN ANALYZE output and fix the query, not just add an index and hope.

• Design for concurrency. Worker pools, queues, graceful shutdown, backpressure, race-free shared state. You can profile a service under load (pprof, flamegraphs, query stats), find the bottleneck, and fix it.

• Drive observability for AI systems. Metrics, tracing, and logging that actually tell you what's happening — token usage, latency per provider, cache hit rates, failure modes, cost per request.

How We Work with AI

• We encourage — but never force — the use of AI/LLM tools in development. If AI-assisted workflows make you faster, use them heavily. If you prefer to write something by hand, that's equally respected. What we care about is the quality of what ships, not how it was typed.

• You'll have access to nearly every major tool and model on the market — coding agents, IDEs, frontier models — with very generous usage limits. We want tooling budget to never be the reason a good idea goes unexplored.

• We actively explore and enhance automated development. You'll help shape how the team uses AI: agent workflows, code review automation, internal tooling. We build AI infrastructure, so we hold ourselves to being its most sophisticated users.

• We believe LLM tools give a single engineer full visibility across the product, regardless of area — frontend, backend, infra, docs. We want people who use that leverage to own problems end-to-end rather than stay inside one layer.

• But the accountability never shifts to the machine. You own what you merge. You can explain every statement and decision in the final output, and justify and defend the architectural choices to human colleagues in design and code reviews. "The AI suggested it" is never an acceptable rationale.

Requirements

Qualifications / Experience / Technical Skills

• Senior-level experience (5+ years) in Go, Ruby, or both. Any combination works: deep Go, deep Ruby, or strong in both. What matters is that you've shipped and operated production services in at least one of them.
• Go candidates: you know the stdlib deeply and prefer it over frameworks. net/http, crypto/tls, context, goroutines and channels, the memory model. You've done performance optimization on real services — allocations, GC pressure, lock contention — and you understand networking (TCP, TLS, HTTP, JSON) in depth, not just through a framework's abstraction.
• Ruby candidates: strong Rails in production — you know where Rails ends and Ruby begins, you've tuned ActiveRecord rather than fought it, and you've built services that stay fast under load.
• PostgreSQL depth from an application developer's perspective. Query optimization, indexing, transactions, connection pooling, migrations at scale. You don't need to administer the cluster; you need to write code that treats it well.
• Concurrency and profiling as a practiced skill, not a bullet point. You've debugged a production incident with a profiler open.
• Familiarity with Kubernetes and containers. You can deploy, debug, and reason about your services in a containerized environment — resource limits, health checks, rolling deploys, networking basics.
• You've built production services with proper observability, deployment pipelines, and security. You know how to run reliable systems and debug distributed systems when things break.

AI/LLM Experience

• You've worked with LLMs at the protocol level — message structures, tool calling, streaming responses, caching strategies. You know what's happening on the wire, not just what the SDK abstracts away.

• Familiarity with MCP (Model Context Protocol) is a strong plus — ideally you've built or integrated MCP servers/clients and understand the transport and capability negotiation layers.

• You can integrate with OpenAI-compatible and Anthropic APIs directly, evaluate responses, understand token usage, and optimize for latency and cost.

• You can judge, audit, and verify LLM output. You catch subtle bugs, security issues, and hallucinated APIs before they ship — and you're fluent enough in the underlying systems to know why the output is wrong, not just that it's wrong.

Soft Skills / Personal Characteristics

• You learn fast and stay current. AI infrastructure is moving weekly; you follow it and can evaluate new protocols and approaches quickly.

• You participate in technical design discussions and code reviews, and you can explain complex concepts clearly to engineers and non-technical stakeholders alike.

• You're comfortable owning the full lifecycle: design, implementation, deployment, monitoring, and continuous improvement.

Environment

• Go and/or Ruby (Rails), PostgreSQL, Kubernetes, modern CI/CD.

• We use frameworks where they earn their place, but we prefer engineers who understand what's underneath and can drop to the protocol level when needed. 

• This role is based in Singapore.

(REQ ID: 2457)