Salesforce Developer
You write the Apex, you own the design behind it, and you are in the room when the client decides what it should do. Six seats, six orgs, no queue between you and the person using what you built.
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
Most Salesforce developer jobs are one third of a job. Someone else talks to the client, someone else decides the design, and you build what lands in the ticket. We don't run it that way, mostly because it doesn't work. The person who has never heard the client explain the problem builds the wrong thing confidently.
So this seat is all three. You go into a client's org and see exactly what's broken or missing. You decide how it should be built, data model, automation, sharing, integration, and you write it down before you build it. Then you write the Apex, the Flow, and the Lightning Web Components yourself, and you're on the call where the client's IT lead asks why you did it that way.
We're hiring six people into this. You'll be staffed across the pod's accounts and you'll review each other's work, so you're not the only person who has ever looked at what you shipped.
What you'll actually do
- Own the build inside client orgs: objects, data model, Flow, permissions and sharing, Apex, triggers, Lightning Web Components, and the integrations that connect it to the rest of their stack
- Decide how something should be built, then write it down clearly enough that another developer could build against it without a meeting
- Run discovery sessions, requirement workshops, and solution walkthroughs directly with US enterprise customers, sometimes with CXOs in the room
- Take a vague ask like "our sales team doesn't trust the data" and come back with a data model and an approach, not a list of clarifying questions
- Review the Apex, Flow, and LWC your teammates ship, and say no when the shortcut costs the client later
- Design the screens, not just the logic. Lightning pages, Flow screens, LWC layouts, laid out so the person using it doesn't need a training session first
- Wire client orgs up to the AI agents our engineers build, including deciding what the agent is allowed to write and what happens when it's wrong
- Debug the thing that broke in production the morning of a demo, and fix it before the client notices
- Document to a standard another developer could pick up tomorrow
- Make the technical call when the answer isn't obvious yet, and be able to explain it six months later
What makes you a fit
- You write real Apex in production, and you can walk us through a class line by line: why it's structured that way, where the governor limits bite, what you'd do differently now. Same for Lightning Web Components and the JavaScript underneath them
- You know Salesforce deeply enough to work without hand-holding: Sales Cloud or Service Cloud, Flow, the data model, sharing and visibility, and why the org someone else built is slow
- You can design, not just implement. Given a business problem and no spec, you can produce an approach and defend the tradeoffs to someone technical who disagrees with you
- Salesforce Certified Platform Administrator and Platform Developer. If you don't have the Developer cert yet but you can show us Apex you shipped, that counts, and we'll expect you to sit it in your first six months
- You can hold a technical conversation with a client's IT lead without an interpreter, and explain the same fix to someone who has never opened Setup
- You can own configuration on at least one CRM or ERP platform beyond Salesforce, HubSpot, NetSuite, or similar, enough to not be starting from zero. Our clients don't run Salesforce in isolation
- You have an eye for how a screen or a Flow should feel to the person using it, not just whether the logic behind it works
- Excellent spoken and written English, most of your calls are with US teams
- You debug past the first Google result
- Realistically this fits someone two to five years into Salesforce as a developer, admin, or consultant. We're not fixed on degrees or years. If you're at eighteen months and you've clearly built more than that sounds like, apply and show us
Use AI like you mean it
This matters more here than at most places you've interviewed. The agents we build sit on top of the orgs you configure, so we care that you already point AI at your own work rather than talk about it. If you've built yourself even a small agent or automation that quietly handles part of your job, that counts for more with us than another certification.
Bring one thing you built or automated with AI that saved you real time on Salesforce work. Two minutes, screen shared. We'll ask where it gave you a confidently wrong answer, and what you changed so it couldn't do that again.
Even better if
- Salesforce Certified Platform Developer II, or a consultant-level certification like Agentforce Sales Consultant or Agentforce Service Consultant
- You've run a real integration or migration between Salesforce and another system, with the failure handling designed in rather than added later
- You've worked with Salesforce CPQ or Revenue Cloud
- You've been the person who had to un-break a badly built org, and you can tell us what you'd have done at the start
- You've built or reviewed something on Agentforce, Data Cloud, or another Salesforce AI surface
- You've written real code outside Apex: Python, TypeScript, anything
- You've worked at a consulting firm or an SI, and you know which parts of that process are worth keeping and which are theatre
- A technical degree is fine to have, it's not required and we don't weight it heavily
What it's actually like here
Some weeks are heavier than others. A Flow breaks in production the morning of a demo, a call runs long because the real problem was three layers under what they asked for, a go-live moves. When that happens everyone shows up, in the org, not on a call about the org. The rest of the time we don't perform busyness. If you want work that stops moving at 6pm every day regardless of what's happening in a client org, this will annoy you.
What you get in return: you own the org, not a queue. Six of you means real code review and someone to argue a design with, which most Salesforce developers never get. The people who scoped the work and the people who build the agents on top of it are sitting in the same room as you. And when a design turns out wrong, you're the one who finds out, which is the only way anyone gets good at this.
Compensation and logistics
₹10-13 LPA based on experience and interview performance, plus ESOP consideration as an early member of the services organization. Comprehensive health insurance included. First comp review at six months, not twelve.
Full time, in office, HSR Layout, Bangalore. Not remote, our delivery model depends on people overhearing each other's client calls. Direct US client exposure, and travel is likely. We'll walk you through what that involves, including visas, before you join.
How we're hiring for this
Six seats on this one, and we're hiring four Software Engineers alongside it, plus interns on both sides. Same pod, same accounts. The Software Engineers build the AI agents that run on top of the orgs you configure, so you'll be in each other's work constantly.
Interview process
Three steps, not ten. We don't drag interviews out and we don't leave you wondering — you'll know where you stand after each one.
- Thirty minutes with the hiring manager: role fit, your AI demo, your questions
- A ninety-minute live session in an org. Walk us through something you built, Apex included, then we hand you a broken configuration and watch how you approach it. Then a real scenario from one of our accounts, which you design out loud while we ask why. Bring a screenshot of a Flow or Lightning page you designed and be ready to defend the layout
- A conversation with the founder, we share more account context, you meet the people you'd work with
We aim to close this in under two weeks from the first call. If we pass, you'll hear why.
Apply
Apply for Salesforce Developer
Resume and a way to reach you is all we need to start. The rest helps, but skip anything that doesn't apply.