Salesforce Developer for Financial Services Cloud, OmniStudio and Agentforce
I build Salesforce solutions end to end: Apex frameworks, Lightning Web Components, managed packages, integrations and Agentforce agents. Four years across Commerce, Sales, Service and Experience Cloud for clients in healthcare, aviation, logistics, travel and wine, and now Financial Services Cloud for a leading US bank.
SELECT Name, Title__c, Experience_Years__c, Clouds__c, Certifications__c FROM Developer__c WHERE Name = 'Tarun Sharma' LIMIT 1
| Name | Years | Clouds | Certs |
|---|---|---|---|
| Tarun Sharma | 4+ | FSC; Sales; Service; Commerce; Experience | 5 |
| Query Results · Total Rows: 1 | |||
Associate Salesforce Developer, Apr 2023 – Jul 2024 · Salesforce Trainee Developer, Jul 2022 – Mar 2023
Client systems are private, so these describe the problem, the build and the result.
OmniScripts and FlexCards backed by Integration Procedures that give bankers one guided flow and a single view of the customer, households and financial accounts.
An Agentforce agent that answers "who's on which project?" by rendering a custom LWC right in the chat, listing each employee's project allocations and hours.
An Apex controller feeds an LWC that charts employee efficiency with Chart.js, so leads can compare output across people and periods.
Employees add or remove skills in an LWC. A skill appears only after the manager approves it, and each level gets an email table of employees with missing skill names.
A generic 2GP that calculates Avalara tax for any object: pass a record Id and the field names for quantity, address, product, tax and errors. Callable from Apex and Flow.
When Sales Order lines become Invoice lines, my logic reuses the tax Avalara already calculated on the order and applies it per unit invoiced, so partial quantities stay accurate.
A Java Spring Boot middleware between Salesforce and Kafka for UnitedHealthcare, streaming high volumes of records in real time.
A Spring Boot app with login and logout and employee records stored through Hibernate (Spring Data JPA). I built the UI first in Thymeleaf, then rebuilt it in React, pairing with AI assistants along the way.
Connected the winery's Shopify store with Salesforce so orders and customers stay in sync across both systems.
An LWC app that replaced a manual claims process with submission, validation and approval inside Salesforce.
Financial Services Cloud, Commerce Cloud, Sales Cloud, Service Cloud, Experience Cloud. FSC data model, Action Plans.
OmniScripts, FlexCards, Integration Procedures, Data Mappers (formerly DataRaptors), Expression Sets.
Agent Builder, Topics & Actions, Prompt Builder, Einstein AI. AI-assisted development with Claude, ChatGPT, GitHub Copilot and Cursor.
Classes, triggers, frameworks, Queueable, Batch, Schedulable, Platform Events, CDC, Named Credentials, SSO.
Lightning Web Components, Aura, Chart.js, JavaScript, HTML, CSS, Visualforce.
MuleSoft Anypoint, REST & Bulk API, Kafka, Spring Boot, Shopify, Stripe, Avalara, Google Drive, Firebase, Strapi.
SOQL, SOSL, SQL, Data Loader, Flows, Approval Processes.
Apex test classes across triggers, async, callouts and APIs, 90%+ coverage, Git, SFDX, CI/CD.
Core Java, Spring Boot, Spring Data JPA / Hibernate, REST APIs, Thymeleaf, React (working knowledge).
See all badges and credentials on my Trailhead profile ↗
Awarded for creating Money Ease Tax, a tax calculation product, and for consistently delivering new solutions, including managed and second-generation managed packages.
172 badges, 102,900 points, 16 trails and 3 superbadges: Agentforce Service, Prompt Builder Templates and Apex Specialist.
Hiring for Salesforce FSC, OmniStudio or Agentforce, or have a project in mind? Tell my assistant what you need and it lands straight in my inbox. I usually reply within a day or two.
Or message me on LinkedIn ↗ View my Trailhead profile ↗ Download my resume (PDF) ↓An Agentforce agent that answers managers' staffing questions right in chat, and replies with a custom Lightning Web Component instead of a wall of text.
To see who was working on what, managers had to open reports, filter by project and add up hours themselves. The questions were simple, but getting answers was slow.
Managers get staffing answers in seconds by asking a question, without building or filtering reports.
An Apex controller and LWC that chart each employee's expected versus actual performance with Chart.js, with hover values and time filters.
Leads wanted to compare what each person was expected to deliver against what they actually delivered, over different periods, and spot the gap quickly.
Expected and actual performance became one interactive chart that leads can filter by week, instead of separate reports to compare by hand.
An internal Salesforce portal where employees manage their skills, managers approve them, and every level of the company is emailed the gaps it is responsible for.
Nobody had one reliable view of who knew what. Skills lived in people's heads and spreadsheets, so managers could not see gaps in their teams, and branch heads and HR could not see gaps across branches or the company.
Skills became an approved record instead of guesswork, and every level, from team managers to HR, regularly sees the missing skills in its own area.
A generic second-generation managed package that calculates tax through Avalara for any object, configured by field names instead of custom code.
Several projects needed tax calculation, and each one was about to rebuild the same Avalara integration for its own objects.
One reusable package replaced per-project tax integrations, and any object in any org could get Avalara tax by configuration.
Logic that reuses the tax already calculated on Sales Order lines when they are invoiced, so invoices get accurate tax without calling Avalara again.
Sales Orders and their lines already had tax calculated through Avalara. When an order was converted into an Invoice and Invoice Lines, the system called Avalara again for the same goods, adding callouts for numbers we already had.
A Sales Order has 3 lines totalling ₹300, with ₹30 tax calculated by Avalara (₹10 per line). One line has a quantity of 10 units and ₹10 tax, so ₹1 per unit. Only 5 of those 10 units are converted to an invoice.
| Step | Value |
|---|---|
| Order line tax | ₹10 for 10 units |
| Tax per unit | ₹10 ÷ 10 = ₹1 |
| Units invoiced | 5 |
| Invoice line tax | 5 × ₹1 = ₹5 |
| Avalara callouts at invoice | 0 |
Invoices carry the same tax as their orders, partial quantities included, and the invoice step no longer makes Avalara callouts.
A Java Spring Boot middleware that keeps Salesforce in real-time sync with events arriving on Kafka for UnitedHealthcare.
UnitedHealthcare needed Salesforce to reflect changes as they happened. Events were published to Kafka, and each one had to become a create, update or delete in Salesforce without manual steps or batch delays.
Salesforce stays in sync with Kafka events in real time, with no manual updates or batch jobs.
A small full-stack app built when the team needed Java developers: login and logout, employee records, and a UI rebuilt from Thymeleaf to React.
My team at CRMIT needed Java developers, so I picked up the Spring ecosystem by building a working app end to end, using ChatGPT and Claude as pair programmers to learn quickly.
How a Java web app is layered from controller to service to repository, how JPA maps entities to tables, and how a React front end talks to a Spring Boot back end.