Services

Software Engineer

The person who builds the agent is the person who sits with the client using it. You’ll ship into production in your first month and carry the pager for it.

Full-time·On-site, HSR Layout, Bangalore, India·Entry level·₹8-16 LPA

Apply now

About Clientell AI

Clientell AI is a San Francisco company. We run Salesforce and revenue operations for enterprise clients, hands-on, and we build the custom AI agents that live inside those systems to handle the work our clients’ teams don’t have time for. The pod that designs, ships, and stands behind this for our largest accounts sits in HSR Layout, Bangalore.

We’re building that team on purpose: one pod, the same accounts, working together instead of handing tickets to each other. Those accounts include a Fortune 100 pharmaceutical company, a European home improvement retail group, and a US commercial fleet safety manufacturer. We’ll share more account detail as your interview progresses.

We’re seventeen people, and about to be more. The next few hires shape what this company becomes, not just what it ships this quarter.

About this role

We build AI agents on top of Salesforce, HubSpot, and whatever other CRM or ERP stack a client runs. Agents that do the work, not agents that tell someone what to click. That means someone has to go sit with the client, understand the workflow as it actually happens including the spreadsheet they use instead of the CRM, and build the thing that fits their business rather than a generic version of it.

That’s this role. You embed with an account, build fast, and own what you shipped until it works in production and keeps working. You’re not writing a service and handing it to an ops team. There isn’t one.

The second half of the job is the part that decides whether this company scales: every time you build the third version of something, you turn it into a piece of the platform so nobody builds the fourth by hand. We’re hiring four of you, and the difference between four engineers doing bespoke client work and four engineers building a system that does client work is the whole thing.

What you’ll actually do

• Build and ship AI agents that plug into Salesforce, HubSpot, and whatever else the client runs, and do real work inside them
• Sit with a client’s team, watch how they actually work, and figure out what to build before you write code
• Own the full loop: prototype in front of the client, harden it, deploy it, and be the person who gets the call when it breaks
• Build the evals. If you can’t measure whether the agent is right, you haven’t shipped it, you’ve demoed it
• Instrument what you ship: traces, failure logs, a way to know it broke before the client tells you it broke
• Design what the agent is allowed to do, and what happens when it’s wrong. Non-deterministic systems writing to a client’s system of record is the actual hard problem here
• Turn the third bespoke build into a reusable piece of the platform, so the fourth client takes a week instead of a month
• Work directly with the Salesforce Developers on the account so the agent understands the org it lives in
• Turn a vague complaint into a working demo fast, then decide what’s actually worth hardening
• Make judgment calls with incomplete information, and be able to explain them afterward

What makes you a fit

• You can actually build: Python or TypeScript, real API work, and enough command of LLMs and agent tooling that wiring an agent into a live system isn’t foreign territory
• You’ve put something with an LLM in it in front of real users, and you know exactly what it got wrong. Not a weekend project, something that had users who complained
• You build evals as part of shipping, not after. You have an opinion about what makes an agent unreliable and it’s based on something that failed on you
• You’ve owned something in production. You’ve been paged, you’ve debugged under time pressure with a customer waiting, and you know what you changed afterward so it couldn’t happen the same way twice
• You can read Salesforce’s REST and Bulk API docs and get a call working without hand-holding. You don’t need to be a Salesforce developer, you do need to not be lost
• You’d rather ship something rough in front of a client today than something polished in front of nobody next month
• You’re comfortable being dropped into a mess with no spec, and comfortable being on the call where the mess gets explained to you badly …