sarvam

SDE2 - Full Stack

Listed by employer · Checked

Posted within 60 days ·

  • onsite
  • FullTime
  • Engineering
  • Bengaluru
Work arrangement
onsite
Employment
FullTime
Stated compensation
Not specified
Stated sponsorship
Not stated
Apply on company website ↗
01 / A QUICK CHECK BEFORE YOU APPLY

Does the location policy fit?

Choose where you would work from. We’ll compare it with the posting’s stated requirements.

Choose the country you will work from. You can change this anytime.

Country and sponsorship changes take effect when you click Check eligibility.

Applying from Papua New Guinea

Not enough information in this posting — confirm with the employer

Checked for applicants in Papua New Guinea; employer sponsorship is not needed. Based on the source posting · not a hiring or work-authorization guarantee.

The posting does not specify whether applicants from your country are accepted.

Why this result?

3 still unclear

  • The posting does not specify whether applicants from your country are accepted.
  • Office attendance is required. Relocation and work permission have not been assessed.
  • Visa sponsorship is not specified.
Source: ashbyChecked Original posting ↗

Requirements

1 with evidence8 unclear or unstated
Remote policy
onsite
“Provider workplace type: onsite”
From employer posting metadata
Employment type
FullTime
9 fields not stated in this posting
Employer sponsorship
Not specified
Geographic scope
Not specified
Degree requirement
Not specified
Security clearance
Not mentioned
Timezone / hours
Not specified
Citizenship requirement
Not mentioned
Minimum experience (years)
Not specified
Work authorization
Not specified
Compensation
Not specified

These details were not stated in the tracked posting. Confirm with the employer.

READ IT IN THE EMPLOYER’S OWN WORDS

Original job description

Reading view uses normalized posting text so exact evidence excerpts can be highlighted.

About the role We're hiring two backend-heavy full-stack engineers (SDE 2 or SDE 3) for the Cowork team at Sarvam. Cowork is the agentic side of Indus: users hand it real work, and an agent plans, uses tools and connectors, works in a cloud sandbox, and hands back files, docs and artifacts across web, Android, iOS, macOS and Windows. The role is full stack, but the centre of gravity is the backend: the BFF that every client talks to, and increasingly the agent harness behind it. You'll ship features end to end, from the API and data model through to the client screens on mobile, desktop and web.
Read full descriptionShow less description
What you'll work on Most of your time goes into the BFF and the services around it; the rest into client work and the harness, depending on what the roadmap needs that quarter. BFF (Chat Service): design and own the APIs that web, mobile and desktop share: sessions, conversations, streaming turns, artifacts, connectors, custom and managed agents. Data modelling, migrations, auth and RBAC, pagination and search. Real-time streaming: stream LLM output, tool calls and agent events from the harness to clients over an event bus, and keep it correct under reconnects, retries and partial failures. Agent harness and platform: contribute to Panja, our agent harness: tool and MCP integrations, sandboxed execution, file and artifact flows, latency and token-cost work. Clients: build features end to end on our Kotlin/Compose Multiplatform apps (Android, iOS, macOS, Windows) and the Next.js web app, so a feature you design in the backend reaches users on every surface. Production ownership: observability, on-call, RCAs, and making the system faster and cheaper with numbers to back it. Tech stack Python and PostgreSQL are the core; you don't need every item below on day one. Backend: Python, SQLAlchemy + Alembic, PostgreSQL, OpenAPI Supporting services: Go Mobile and desktop: Kotlin Multiplatform + Compose Multiplatform (Android, iOS, macOS, Windows) Web: Next.js, React, TypeScript What we're looking for A strong backend engineer who has also shipped real frontend work and is happy to keep doing both. 3+ years (SDE 2) or 5+ years (SDE 3) building and running production backend services. Deep in at least one backend language; Python preferred, Go, Kotlin/JVM or TypeScript/Node also welcome. Solid API and data-model design: REST/streaming APIs, PostgreSQL schema design, migrations, indexing, transactions. Distributed-systems fundamentals: async processing, queues or event streams, idempotency, retries, failure handling. Production experience on Kubernetes or a similar platform, with observability you actually used to debug an incident. Has shipped user-facing features on at least one client platform: Android, iOS, desktop or web (React/Next.js). Kotlin/Compose experience is a plus, not a gate. Willing to pick up the side of the stack they know less, and to learn agent and LLM systems on the job. Clear written communication: design docs, PR descriptions, RCAs. Nice to have Built on LLM APIs: tool calling, streaming, prompt caching, evals, or an agent loop of your own. MCP servers or clients, OAuth connector integrations, or sandboxed code execution. Kotlin Multiplatform / Compose Multiplatform, or native Android/iOS. Real-time systems: WebSockets/SSE, NATS, Kafka, or Temporal-style durable workflows. Go services, or performance and cost work with measurable before/after numbers. Open-source work or public writing we can read.
Original formatting and links

About the role

We're hiring two backend-heavy full-stack engineers (SDE 2 or SDE 3) for the Cowork team at Sarvam. Cowork is the agentic side of Indus: users hand it real work, and an agent plans, uses tools and connectors, works in a cloud sandbox, and hands back files, docs and artifacts across web, Android, iOS, macOS and Windows.

The role is full stack, but the centre of gravity is the backend: the BFF that every client talks to, and increasingly the agent harness behind it. You'll ship features end to end, from the API and data model through to the client screens on mobile, desktop and web.

What you'll work on

Most of your time goes into the BFF and the services around it; the rest into client work and the harness, depending on what the roadmap needs that quarter.

  • BFF (Chat Service): design and own the APIs that web, mobile and desktop share: sessions, conversations, streaming turns, artifacts, connectors, custom and managed agents. Data modelling, migrations, auth and RBAC, pagination and search.

  • Real-time streaming: stream LLM output, tool calls and agent events from the harness to clients over an event bus, and keep it correct under reconnects, retries and partial failures.

  • Agent harness and platform: contribute to Panja, our agent harness: tool and MCP integrations, sandboxed execution, file and artifact flows, latency and token-cost work.

  • Clients: build features end to end on our Kotlin/Compose Multiplatform apps (Android, iOS, macOS, Windows) and the Next.js web app, so a feature you design in the backend reaches users on every surface.

  • Production ownership: observability, on-call, RCAs, and making the system faster and cheaper with numbers to back it.


Tech stack

Python and PostgreSQL are the core; you don't need every item below on day one.

  • Backend: Python, SQLAlchemy + Alembic, PostgreSQL, OpenAPI

  • Supporting services: Go

  • Mobile and desktop: Kotlin Multiplatform + Compose Multiplatform (Android, iOS, macOS, Windows)

  • Web: Next.js, React, TypeScript


What we're looking for

A strong backend engineer who has also shipped real frontend work and is happy to keep doing both.

  • 3+ years (SDE 2) or 5+ years (SDE 3) building and running production backend services.

  • Deep in at least one backend language; Python preferred, Go, Kotlin/JVM or TypeScript/Node also welcome.

  • Solid API and data-model design: REST/streaming APIs, PostgreSQL schema design, migrations, indexing, transactions.

  • Distributed-systems fundamentals: async processing, queues or event streams, idempotency, retries, failure handling.

  • Production experience on Kubernetes or a similar platform, with observability you actually used to debug an incident.

  • Has shipped user-facing features on at least one client platform: Android, iOS, desktop or web (React/Next.js). Kotlin/Compose experience is a plus, not a gate.

  • Willing to pick up the side of the stack they know less, and to learn agent and LLM systems on the job.

  • Clear written communication: design docs, PR descriptions, RCAs.

Nice to have

  • Built on LLM APIs: tool calling, streaming, prompt caching, evals, or an agent loop of your own.

  • MCP servers or clients, OAuth connector integrations, or sandboxed code execution.

  • Kotlin Multiplatform / Compose Multiplatform, or native Android/iOS.

  • Real-time systems: WebSockets/SSE, NATS, Kafka, or Temporal-style durable workflows.

  • Go services, or performance and cost work with measurable before/after numbers.

  • Open-source work or public writing we can read.

Similar roles

All sarvam jobs →

Matched by role category. Review each posting’s requirements before applying.

Explore stated remote geography

These collections reflect applicant location statements, not authorization or citizenship.

THE JOB ELIGIBILITY CHECKER

Check a job