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
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
Pay: ₹1,000,000.00 - ₹1,300,000.00 per year
Application Question(s):
- Are you available to join immediately? If not, what is your current notice period?
- What is your total experience in this domain?
- What is your current CTC?
- What is your expected CTC?
Work Location: In person
