A complete application in a minute
Tailored resume and cover letter, ready to send.
CellStrat is seeking a Full-Stack AI Product Engineer to join our US client project with responsibilities across backend, AI systems design, and occasional frontend work with React/Next.js. You will own real systems, engage directly with clients, and operate with minimal specs.
The role emphasizes end-to-end ownership, strong Python/FastAPI skills, and a platform-thinking approach. Remote work is offered, with IST-friendly coordination for night calls.
Experience: 1.00 + years
Salary: Confidential (based on experience)
Shift: (GMT+05:30) Asia/Kolkata (IST)
Opportunity Type: Remote
Placement Type: Full time Permanent Position
(*Note: This is a requirement for one of Uplers' client - CellStrat)
Must have skills required:
Python, FastAPI, Agentic AI, Multi-Agent AI
CellStrat is Looking for:
About Cellstrat
CellStrat is an AI startup with two sides to the business. The services arm builds end-to-end AI engineering solutions for US-based clients across industries. This is the more mature side of the company, running real projects with real deadlines.
The product side is CellAssist, our healthcare AI platform. We are building AI systems for healthcare operations with a voice-first approach: AI receptionists for clinics and hospitals, automated patient triage, and admin operations powered by voice agents. We have active pilots running and are early in the product journey. If you want to work on something that is still being shaped, this is it.
This role sits primarily on a US client project, with a partial contribution to CellAssist. You will own real systems, talk directly to clients, and be expected to figure things out without being handed a spec.
You write clean, async Python and understand why things are structured the way they are. FastAPI is your default for backend work and you're comfortable owning a service end to end.
You think at a platform level: how services are structured, where state lives, how async workflows are orchestrated, what failure modes look like, and how the codebase will hold up as the product and team scale. You've worked on systems with real users and real operational stakes, and that experience shows in how you make decisions.
You think at the class, module, and data model level before writing code. Separation of concerns, error boundaries, retry logic, and observability are first-class concerns, not afterthoughts. This is not interview-prep system design — it's the kind of thinking that shows up in how you structure a pull request, how you name things, and how you handle edge cases before they become incidents. Understanding patterns like multi-tenancy, service isolation, and configuration management matters here — not because you'll design them from scratch on day one, but because working within them well requires knowing why they exist.
You understand how to build production-grade AI systems from first principles. You know Applied AI engineering beyond just wrapping OpenAI — you know what agent skills are, how dynamic context discovery works, when to use tool calling vs MCP servers, how filesystem-based approaches factor into agent design. You can design a pipeline that mixes LLM calls, deterministic logic, and tool use, and you know which problems don't need an LLM at all. You don't default to slapping RAG and embeddings over every problem, and you can write custom solutions without always reaching for LangChain or LlamaIndex.
You can take a feature or requirement from a client conversation all the way to a deployed, working system. You ask good questions, translate ambiguity into concrete decisions, and don't wait to be unblocked.
You can represent the engineering side on a call with a US client. That means asking the right questions, pushing back when something doesn't make sense, and learning enough about the domain to solve problems from first principles.
Client calls run at night (IST) — this needs to genuinely work for you.
You routinely figure out things you haven't done before. When you hit an unfamiliar API, an undocumented edge case, or a domain you know nothing about, you work it out.
React and Next.js at a working level — enough to make feature changes, understand what's happening on the UI side, and contribute when needed. Full ownership of the frontend is not required, but being blind to it is not an option.
Backend: Python FastAPI PostgreSQL GCP Cloud Run Docker Docker Compose CI/CD GitOps Cloud Tasks Pub/Sub Redis SQS Observability
AI: LLM APIs Tool Calling Prompt Engineering Evals RAG Embeddings Document Parsing Data Ingestion Sandbox Agents Multi-Agent Orchestration AI Observability
Frontend: React Next.js TailwindCSS shadcn/ui
This is not a role for someone who needs clear specs to get started or wants to be managed closely. The people who do well here are genuinely curious, form opinions quickly from first principles, and have a high tolerance for ambiguity. If you've shipped something that involved a real backend, real infrastructure, and real users — we want to hear about it.