Skip to content

Open nowPosted 13 days ago

Senior AI Engineer

MyCareersFuture94,028 open roles

Pay
SGD 12,000 – SGD 16,000 a Monthly
Where
Central, Singapore
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowSenior AI EngineerMyCareersFuture · Central, Singapore
  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on MyCareersFuture's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

7.7% of postings close within 7 days. Measured by our own scanner across the market.

Share of postings closed within
  1. 1.6%1 day
  2. 3.3%3 days
  3. 7.7%7 days
  4. 14.0%14 days
  5. 33.7%30 days
This job: posted 13 days ago

The posting

Application instructions:

Interested applicants, please apply for this job at this link: https://grnh.se/7o1evgyx2us

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 engineer 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.
From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against MyCareersFuture's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.
  3. We apply on MyCareersFuture's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.
  4. Every reply, sorted

    MyCareersFuture's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.
  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

By hand5–10
With CV Rocket100
applications a day

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.