11+ Semantic search Jobs in Bangalore (Bengaluru) | Semantic search Job openings in Bangalore (Bengaluru)

About Sentiaflow

Sentiaflow is an AI engineering and IT services company building production-grade agentic AI systems, sitting at the intersection of LLMs and real business operations — data, APIs, permissions, workflow state, human decisions, security, and measurable outcomes. Our initial domain focus is healthcare, particularly clinical trials, where reliability, traceability, and clear human-decision boundaries matter more than a slick demo.

Job Description

As a Level 1 engineer, you'll implement bounded parts of a production agentic workflow under an Agent Captain or senior engineer, connecting models to application services, tools, data sources, and human approval points.

You will:

• Translate a scoped business workflow into typed inputs, outputs, states, actions, and escalation paths
• Build backend services and tool integrations (Node.js/TypeScript or Python)
• Use LLMs only where model judgment adds value; keep rules, validation, authorization, and workflow control in deterministic code
• Design and validate structured model outputs before they touch downstream systems
• Handle partial data, tool failures, duplicate events, retries, timeouts, rate limits
• Add logging, traces, metrics, and decision records for diagnosability
• Write tests and evaluation cases that check whether the full workflow behaves correctly — not just whether output sounds fluent
• Protect sensitive data; participate in code, design, and release-readiness reviews
• Explain implementation trade-offs clearly to engineers and stakeholders

Success in 6 months: own a bounded workflow module end-to-end, integrate models without letting probabilistic output bypass deterministic controls, produce release-ready evaluation evidence, and diagnose cross-boundary failures with less supervision.

Desired Skills

• Approximately 3–6 years hands-on backend/application engineering experience, with demonstrable hands-on work building agentic systems — not just calling an LLM API from a backend service
• LangGraph (or comparable agent orchestration framework) experience is required — building multi-step, stateful agent workflows with conditional branching, tool-calling loops, and recovery/retry logic, not a single-prompt wrapper
• Deep RAG experience, including:
• Chunking strategy design, embedding model selection, and retrieval evaluation (not just "connected a vector DB")
• Hybrid search (dense + sparse/keyword), re-ranking, and query rewriting/decomposition
• Handling retrieval failure modes: irrelevant context, stale data, contradictory sources, citation/grounding accuracy
• Measuring RAG quality (precision/recall on retrieval, faithfulness/groundedness of generation) — not eyeballing outputs
• Experience designing agent state machines / workflow graphs: tool selection, planning loops, human-in-the-loop interrupts, checkpointing, and state persistence across long-running workflows
• Strong programming in JS/TypeScript (preferred), Python, Java, C#, or Go
• Solid grasp of API design, databases, async processing, auth, testing, deployment
• Comfort reasoning about state, retries, idempotency, concurrency, permissions, audit trails, failure recovery
• Real production debugging experience, not just greenfield builds
• Clear technical communication

We're looking for engineers who've actually built and tuned agentic/RAG systems in production — not those who've only wired together frameworks or prompted an LLM API.

Nice to have: experience with other orchestration frameworks (CrewAI, AutoGen, custom state machines), observability/eval tooling (LangSmith, Langfuse, custom trace pipelines), healthcare or regulated-industry background. Bachelors from IIT or NIT highly preferred.

Founding Engineer (Bangalore)

The problem:

Business enterprises overpay vendors - on every batch of invoices, on every month because the data that would catch lives in different systems. We are building an AI agent that processes invoices end-to-end, reasons across all the relevant sources, flags genuine discrepancies, and acts - without a human having to investigate each one.

What you will own

Everything engineering. Schema design to deployment to the 2am fix when something breaks in production. There is no tech lead above you. There is no platform team. There is the architecture, you, and the founders. Concretely, this means building:

• A multi-stage agentic pipeline that takes a vendor invoice and produces a structured decision - fully autonomous for clear cases, escalating to human review for genuinely ambiguous ones. We use LangGraph, but if you've built equivalent systems with Temporal, Prefect, or custom state machines with LLM orchestration, that works
• An LLM-powered extraction layer that handles real invoices - scanned PDFs, stamped documents, inconsistent layouts - and returns structured output
• A graph data model that connects invoices to various sources and can traverse those relationships to detect discrepancies
• ERP connectors, GST validation logic, and a write-back layer that closes the loop

What we need

• Strong Python. Async FastAPI, clean service boundaries, tests that actually catch bugs. You have shipped Python backends that handled real production load
• Solid Postgres. Complex queries, schema design, migrations without downtime, row-level security for multi-tenant data. pgvector is a plus - if not, you pick it up fast
• LLM API experience in production. You have called an LLM API for something that real users depended on. You know about structured output, retry logic, cost management, prompt versioning. A side project counts if it was genuinely deployed
• Comfort with graph data models. You understand when a graph is the right structure and when it is not. You do not need deep Neo4j production experience - you need to understand graph relationships conceptually and be willing to learn Cypher. It is a 2-day ramp for the right person
• Working knowledge of deployment. Deployed and operated production workloads on GCP. Cloud Run, Cloud SQL, Cloud Storage, Redis — you're comfortable across the stack. If you've done it on AWS, the translation isn't hard, but GCP is where we are
• You own things. Not "I contributed to" - you designed it, shipped it, and fixed it when it broke. That pattern needs to be visible in your history

Good to have, not mandatory

• Built an agentic pipeline with multiple stages
• Any fintech, P2P domain experience - even tangential
• Worked at a startup with under 20 people
• Has a GitHub, blog, or writeup that shows how you think about a hard technical problem

What you get

• The hardest engineering problem you would have worked on. This is not CRUD with an LLM bolted on
• Real ownership. First engineering hire. Your architectural decisions will be in this product five years from now
• Equity that matters. ESOP - Open to discussion. We are pre-seed - this is a bet, not a guarantee. We will not pretend otherwise
• No meetings tax. You work directly with the founders. The product is specified clearly. You know what you are building and why

Honest about stage: We do not have a production ready infra yet. We have a complete architecture specification and a working prototype. If you need the stability of an established engineering org, this is not the right moment. If you want to build something real from zero and own a meaningful piece of it, it is.

The founders

One of us has spent 20 years building revenue and operational engines at companies where there was no playbook - part of the pilot team that established the world's largest search company's direct sales operations in India, managed global operations for a global mobile advertising platform, scaled a B2C platform to become one of India’s leading edtech platforms and most recently worked on building an enterprise Agentic Voice AI platform. The other has spent 15 years taking AI from demo to production in domains where failure is expensive - voice, lending, and conversational systems across a Series D conversational AI company, a major telco, a Big 4, and a leading NBFC.

Two IIT/IIM alumni who have both watched AI work in enterprise, and know exactly what it takes to get it there. We are not building this product because it sounds interesting. We are building it because we have both sat across the table from CFOs who know they are losing margin and have no tool capable of doing anything about it.

Detailed JD: 

Responsibilities:

- Interface with product owners and software architects to review and finalize requirements

- Participate in the full SDLC including analysis, design, development, testing, deployment, and support

of new features and applications

- Actively lead and participate in agile ceremonies (Standups, Refinements, Retrospectives, Planning,

and Requirement discussions)

- Communicate effectively, clearly, and thoroughly with the Scrum Team and Stakeholders

- Provide innovative solutions to complex problems

- Design, develop and modify software applications/systems according to specifications

- Develop technical documentation including services, object, and data model

- Create high quality code and perform code reviews

- Create unit and integration tests to ensure the code quality and functionality

- Proactively learn and share knowledge of technology and compare advantages and disadvantages of

alternative solutions/technologies

- Identify areas needing process improvements and see them through to resolution

- Support and coach other Developers, provide technical guidance

- Help onboard new team members

Tech Stack:

C#, .NET Core, XUnit, Entity Framework Core, MS SQL Server, PostgreSQL, Git, JIRA, Web API

NET Profile 

DESIRED SKILLS

·         Experience in Microsoft technologies (Microsoft Dot Net, C#, http://asp.net/" target="_blank">ASP.NET, MVC, Microsoft SQL, .NET Core, Web API, WCF, Bootstrap, JavaScript, Angular JS, Web API, Web services, Rest API)

·         Design a complex architecture landscape involving API integrations.

·         Hands-on experience in ASP.Net, C#, MVC, WCF, Restful services, Web API, AngularJS, Entity Framework

·         Strong analytical & problem-solving skills

·         Must have excellent oral & email communication skills.

·         Strong analytical and problem-solving skills

·         Must have a positive attitude and a yearning to get things done and demonstrate ownership of deliverables.

NICE TO HAVE SKILLS

·         Knowledge in Microsoft Azure.

·         Good Command on Agile Development & Azure DevOps.

·         Knowledge in Angular / React / Node JS

·       Mainly they are looking for:

C#

http://asp.net/" target="_blank">ASP.NET MVC,

AJAX,

LINQ,

jQuery,

WebApi.

4 - 6years of experience in web and API development

4+ years experience with http://asp.net/MVC/C" target="_blank">ASP.NET/MVC/C#.

4+ years working with SQL Server (2012+).
Good Knowledge of scripting libraries like jQuery, Knockout, Angular JS

• A strong sense of ownership
• Exceptional technical skills
• Ability to understand the problem and craft the right solution
• Strong software architecture skills
• Dedicated to completing projects of the highest standards, on time
• Passionate about the work they undertake

QUALIFICATIONS:

To be considered for this position you must possess the following qualifications:

• A minimum of 3.5 years of industry experience
• Previous experience working with a team on a large, complex project
• Excellent communication skills (verbal and written skills in the English language)

SKILLS:

Please find the below mandatory skills required for Senior .Net resources, kindly source accordingly.

• Strong in C#.Net
• MVC (Min 2 Yrs)
• Web API (Min 1 Yr)
• Good in SQL and DB operations
• Should have used latest features of C#.Net

Database:

• Entity Frameworks (LINQ) (Min 1 Yr)
• ADO.Net (SQL)