Back to jobs

Senior AI Engineer — Inference & Agent Systems

Pay
Pay not listed
Work setting
Working pattern needs review — work setting source
Title: Senior AI Engineer — Inference & Agent Systems Location: - BLR/Remote India What We're Building
Listed location: Bangalore, Hybrid
Read the full posting
Employment
Not stated

What you’ll work on

Full posting
  • Drive TTFT below 400ms for multi-step agent pipelines

  • Design and implement Plan-Execute-Synthesize pipelines that run sub-agents in parallel DAGs, not sequential chains

  • Own the eval framework end to end: ground truth datasets, automated scoring pipelines, regression detection on every PR

From the employer’s posting
Inference Optimization Drive TTFT below 400ms for multi-step agent pipelines Streaming optimization: first token to user while sub-agents are still running
Agent Architecture Design and implement Plan-Execute-Synthesize pipelines that run sub-agents in parallel DAGs, not sequential chains Build reliable orchestration on top of Temporal: retries, timeouts, partial failure recovery, idempotency
Evaluation & Harness Own the eval framework end to end: ground truth datasets, automated scoring pipelines, regression detection on every PR LLM-as-judge pipelines for qualitative output assessment
Apply at Arcana Analytics

Posting record

Report an error

Open 5 monthsWe first saw this posting 172 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.

Status in our records
Live
First seen by us
Jun 2, 2026172 days ago
Recorded sightings
53
Last seen by us
Nov 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 172

Up longer than most. Similar jobs usually come down between day 1 and day 15.

From 1,376 similar postings that came down. Coming down is not always a hire.

Arcana Analytics is hiring

8 open jobs

  • No new data jobs since June
  • Its jobs tend to stay up a long time
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • Docker
  • Kafka
  • PostgreSQL
  • Go
Where the posting names them
- Strong ML research background without systems exposure Stack familiarity (we care more about depth than match): Go, Python, Temporal, Kafka, PostgreSQL, Docker Why This Role

Your next step

Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.

Applying through Greenhouse

  • No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
  • Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.

Already applied? Track this application

Has Arcana Analytics posted this job before?

Yes. We’ve followed one other Senior AI Engineer — Inference & Agent Systems job there since June 2026. It is still up.

  1. Place not statedStill up after 173 days, first seen Jun 2
  2. This jobUp 173 days so far, first seen Jun 2

Job description

View original posting ↗

Title: Senior AI Engineer — Inference & Agent Systems

Location:
- BLR/Remote India

What We're Building

Arcana is building AI agents that synthesize information across heterogeneous sources and deliver structured, reasoned answers in real time. The product only works if the agents are fast, reliable, and correct, not approximately correct.

Our stack: Go + Temporal for orchestration, a Plan-Execute-Synthesize agent architecture, and an evaluation harness we use to measure every regression. The problems are hard. The latency bar is aggressive. The accuracy requirements are unforgiving.

The Work

Inference Optimization

- Drive TTFT below 400ms for multi-step agent pipelines

- Streaming optimization: first token to user while sub-agents are still running

- KV cache strategy, prompt compression, dynamic context window management

- Multi-provider routing: model selection by latency, cost, and task type across OpenAI, Anthropic, Gemini, and open-weight models

Agent Architecture

- Design and implement Plan-Execute-Synthesize pipelines that run sub-agents in parallel DAGs, not sequential chains

- Build reliable orchestration on top of Temporal: retries, timeouts, partial failure recovery, idempotency

- Structured output enforcement: JSON schema validation, retry loops on malformed LLM output, graceful degradation

- Tool call design: schema design that LLMs actually follow reliably across providers

Evaluation & Harness

- Own the eval framework end to end: ground truth datasets, automated scoring pipelines, regression detection on every PR

- LLM-as-judge pipelines for qualitative output assessment

- Latency regression testing - p50/p95/p99 tracked across every deployment

- Adversarial test case design: ambiguous queries, missing data, conflicting sources, malformed tool responses

Infrastructure

- Model serving and cold start optimization

- Async worker architecture for parallel sub-agent execution

- Observability: trace every token, every tool call, every synthesis step

What We're Looking For

You've built something that runs in production at a meaningful scale and you understand why it's fast (or why it isn't).

Strong signal:

- You've worked on inference pipelines where TTFT was the primary metric and you moved it meaningfully

- You've built multi-step agent systems and you know where they break not from reading papers but from watching them fail in production

- You've written eval harnesses from scratch and you have opinions about what makes a ground truth dataset actually useful

- You've debugged LLM non-determinism in production and built systems resilient to it

- You've worked with streaming LLM responses and built infrastructure around partial output handling

Weaker signal (but not disqualifying):

- You've fine-tuned models but haven't shipped inference systems

- You've used LangChain/LlamaIndex but haven't built the layer underneath

- Strong ML research background without systems exposure

Stack familiarity (we care more about depth than match): Go, Python, Temporal, Kafka, PostgreSQL, Docker

Why This Role

The problems here don't have blog posts about them yet. Parallel agent DAG execution under hard latency budgets, streaming synthesis across partial sub-agent results, eval harnesses for non-deterministic multi-step systems: these are genuinely unsolved at production quality. Small team. High ownership. Every engineer's decisions ship to production.

Who We Want to Hear From

You've shipped inference systems at:

- A real-time AI product (search, coding assistant, chat at scale)

- A model serving infrastructure company

- An agent platform (any domain)

Or you've built eval/harness infrastructure that a team of 10+ engineers actually trusted to catch regressions.

Apply

Send to: [careers@arcana.io]

  1. One system you built where latency was the primary constraint what you measured, what you changed, what moved
  2. Link to anything public (code, writing, talks)
  3. No cover letter required

We respond to every application.

Demand for AI Engineer roles

New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.

Weekly new AI Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 78, the most 803, and the latest week had 438.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Bangalore, Hybrid

Title: Senior AI Engineer — Inference & Agent Systems Location: - BLR/Remote India What We're Building
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.