Skip to content

Open nowFirst seen 34 hours ago

Lead AI Engineer

Bridge-it3 open roles

Where
New Delhi, Delhi, India, Remote
Work mode
Remote
Get the CV for this job

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

Your applicationOpen nowLead AI EngineerBridge-it · New Delhi, Delhi, India, Remote
  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 Bridge-it'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.

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

Share of postings closed within
  1. 2.1%1 day
  2. 4.4%3 days
  3. 11.9%7 days
  4. 18.6%14 days
  5. 35.6%30 days
  6. 45.1%60 days
This job: first seen 34 hours ago

The posting

Lead AI Engineer — Bridge-it AI Team

Location: Remote

Experience: 4–8 years in industry

Team: AI Platform (Copilot)

About Bridge-it

Bridge-it is an early-stage EdTech company building a career-readiness platform for K-12 students, counselors, and districts. Students explore careers, colleges, and non-college pathways; build multi-year plans; and get guidance from an AI Copilot that is grounded in their own plans, school data, and a curated knowledge base. Counselors use the same platform to supervise, nudge, and intervene at scale.

The AI Copilot is the heart of the product — a production LangGraph-based agentic system serving real students, where being right matters more than being fluent. We hold ourselves to strict grounding, safety, and tenant-isolation standards, and we measure everything.

About the role

You will join a small AI team that owns the Copilot end to end: the agentic orchestration graph, retrieval and grounding, safety guardrails, response contracts with the frontend, and the evaluation platform that keeps it honest. We are mid-flight on an ambitious redesign — collapsing multiple experimental graph variants into a single workflow-first architecture with typed claim verification, constitutional rules, and per-turn decision records — and you would step directly into that work.

This is a senior role with a visible leadership runway. Beyond writing excellent code, we expect you to analyze ambiguous product requirements, turn them into well-scoped technical specs and tickets, distribute work across the team, and communicate trade-offs clearly to product and leadership. For the right person, this role grows into a techno-management position.

What you'll do

  • Design, build, and operate agentic LLM workflows in LangGraph — routing, planning, parallel retrieval, tool execution, verification, and streaming — serving live student and counselor traffic over WebSockets.
  • Own RAG quality: multi-source retrieval across vector stores (Milvus, pgvector), a knowledge graph (Neo4j), and structured platform data; chunking strategy; reranking; and grounded generation with typed claims and evidence citation.
  • Enforce safety and trust: input/output guardrails, constitutional rules, faithfulness verification, abstain/escalate behavior, and strict multi-tenant data isolation.
  • Build and extend our evaluation platform: online LLM-as-judge evaluators, offline regression suites on curated datasets (LangSmith), latency baselines, and A/B experimentation (PostHog feature flags).
  • Drive latency and cost optimization: model selection across providers (OpenAI, Gemini, open-weight models via OpenRouter), prompt and context engineering, selective retrieval, caching, and streaming intermediate responses.
  • Instrument and debug production behavior with LangSmith tracing, OpenTelemetry, New Relic, and Sentry; treat live-QA findings as first-class inputs to design.
  • Partner with backend (Django/Postgres), frontend (Next.js), and product teams on response envelopes, interaction contracts, and rollout plans.
  • Lead by doing: break epics into staged implementation plans with acceptance criteria, sequence work across engineers, review code, and mentor teammates.

What we're looking for (required)

  • 4–8 years of professional software engineering experience, with at least 2–5 years building LLM-powered products in production (not just prototypes or notebooks) and 2 years of leading a team.
  • Strong Python engineering fundamentals — typing, testing, async, service design.
  • Strong grasp of agentic architecture patterns — supervisor/executor splits, planner–retriever–verifier pipelines, tool/capability registries, routing and fallback tiers — and sound judgment about when a workflow should be deterministic versus agentic.
  • Hands-on experience with agent orchestration frameworks (LangGraph strongly preferred; LangChain, or comparable state-machine/agent frameworks acceptable) including multi-step graphs, tool calling, and streaming.
  • Context engineering / harness engineering: deliberate construction of what the model sees each turn — context budgets, retrieval selection, system-prompt and tool-schema design, structured state passed between nodes — and the harness discipline (contracts, guards, fallbacks) that makes model behavior predictable.
  • Experience designing and optimizing agent memory: short-term conversation state (windowing, summarization/compaction, token-budget management) and long-term memory (user profiles, episodic stores, rollups) with sensible retrieval and staleness policies.
  • Deep practical knowledge of RAG systems: embedding models, vector databases (Milvus/Zilliz, pgvector, or similar), hybrid retrieval, rerankers (e.g., Cohere), chunking and knowledge-base design.
  • Proven experience building and operating LLM evaluation systems: online evaluators (LLM-as-judge) on live traffic, offline golden datasets and regression suites, faithfulness/hallucination and groundedness metrics, A/B experiment design — and the discipline to gate releases on eval results.
  • Hands-on AI observability: end-to-end trace instrumentation of agent runs (LangSmith, OpenTelemetry GenAI conventions, or similar), per-node latency/token/cost tracking, trajectory analysis, drift and quality-regression monitoring, and turning production traces into eval datasets and fixes.
  • Experience shipping structured outputs (JSON contracts, schema-validated responses) as the interface between models and product surfaces.
  • Comfort with cloud infrastructure (GCP preferred: Cloud Run, Pub/Sub, GCS, BigQuery).
  • Excellent communication and interpersonal skills: you can explain a retrieval-quality trade-off to a product manager, write a spec another engineer can execute, and disagree constructively.
  • Demonstrated ability in requirement analysis and task decomposition — turning fuzzy asks into staged, dependency-ordered work — and willingness to step up into team-lead responsibilities.

Desirable

  • Experience at an early-stage startup — comfort with ambiguity, wearing multiple hats, and shipping under constraints.
  • Model Context Protocol (MCP): working knowledge of the spec and hands-on experience building or integrating MCP servers/clients to expose tools and data to agents.
  • Knowledge graphs (Neo4j/Cypher) in retrieval or recommendation contexts.
  • Durable workflow engines (Temporal) and event-driven architectures (Pub/Sub).
  • Multi-tenant SaaS security models (row-level tenancy, FERPA/COPPA-adjacent compliance awareness).
  • EdTech or other regulated/high-trust consumer domains.

Nice to have

  • AI infrastructure: model serving, GPU inference, gateway/router layers, and cost/latency-aware routing across providers.
  • SLMs and self-hosted LLMs: deploying and operating small language models or open-weight LLMs (vLLM, TGI, Ollama, or similar), quantization, fine-tuning/distillation for task-specific workloads, and knowing when a small model beats an API call.
  • Traditional ML: classification, ranking, embedding fine-tuning; scikit-learn/PyTorch.
  • Recommender systems: candidate generation + ranking pipelines, personalization.
  • Forecasting and data analytics: time-series methods, cohort analysis, product analytics.
  • Big data processing/streaming: BigQuery at scale, Spark/Flink/Kafka or Pub/Sub streaming pipelines, dbt-style transformation workflows.

Our stack (so you know what you're signing up for)

Python · LangGraph/LangChain · OpenAI + Gemini + open-weight models (OpenRouter) · Milvus/Zilliz · pgvector · Neo4j · Cohere reranking · LangSmith · Django + PostgreSQL · Temporal · GCP (Cloud Run, Pub/Sub, GCS, BigQuery) · PostHog · OpenTelemetry/New Relic/Sentry · Next.js frontend over a WebSocket streaming protocol.

Bridge-it is an equal opportunity employer. We welcome applicants of all backgrounds and are committed to an inclusive, respectful remote-first workplace.

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 Bridge-it'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 Bridge-it'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

    Bridge-it'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

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

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.