Open to Salesforce roles

Abhijit Kumar

Salesforce developer specializing in US healthcare on Health Cloud — eligibility, patient cost estimates and prior authorization, in live production orgs.

Two and a half years at Mirketa, a Salesforce consulting and ISV firm in Noida, delivering for client teams across Europe, the US, Brazil and India. I gather the requirements, design and build it in Apex, LWC and Flow, run the release, and then support it in production.

  • 7th

    country onboarded into a live multi-country Salesforce org — ~240 components in a 3-hour go-live, zero downtime, no post-release defects Read the case study

  • ~50%

    of inbound call-tracking leads were noise before I filtered them — CallRail-to-Salesforce integration, with reps notified in real time Read the case study

  • Shipped

    a prior-authorization completeness engine on my own time — selected by leadership for the firm's flagship product Read the case study

  • 2026

    Winner, Mirketa internal AI Agent Hackathon — an agent build competition

Selected work

Four builds, written for engineers. Client names are withheld; everything else is exactly what happened.

  • Global food safety and testing company · July 2024 – February 2025

    Added a seventh country to a shared production org in a 3-hour window: ~240 components, zero downtime, no post-go-live defects.

    ApexLightning Web ComponentsFlowExperience CloudSalesforce Knowledge

  • US behavioral health provider · November 2024 – present

    Cut inbound lead noise ~50%, and automated the up-front cost estimate patients receive at admission.

    Salesforce Health CloudApex (Queueable, Batch)FlowLightning Web ComponentsREST API integration

  • Behavioral health · selected for the firm's flagship product · Personal project → productization

    Started as a personal project, pitched to leadership, and selected for integration into the company's flagship product.

    ApexSalesforce Health CloudRAG pipelineLLM orchestrationAgentforce

  • Internal tool · Ongoing

    One orchestrator coordinating Jira, email and Salesforce cases into a single priority-ranked triage dashboard.

    LLM orchestrationJira APIEmail integrationSalesforce CasesAgentic tooling

Built and released for teams across Europe, the US, Brazil and India

  • Ireland
  • France
  • Spain
  • Portugal
  • United States
  • Brazil
  • India

Working directly with client stakeholders across time zones — requirements through to production support.

New development

Greenfield features on Apex, LWC and Flow — built against real compliance requirements, not just acceptance criteria.

Enhancement of live orgs

Extending systems other people built and other teams depend on, without breaking what is already in production.

Continuous support

Ongoing production support: functional and data analysis, user and data management, incident triage, and legacy refactoring under strict release management.

Integrations and AI

REST/SOAP integrations, OAuth, and AI agents wired into CRM workflows — RAG, orchestration, Agentforce and MCP tooling.

How I work

I take features end to end rather than picking up specs — and I stay on them after go-live.

  1. 01

    Requirement gathering

    I talk to the people who do the work, not just the ticket. Most of what I have shipped started as a conversation with a client stakeholder about a workflow that was leaking time — and more than once the stated requirement turned out to be the wrong problem.

  2. 02

    Solution design

    Data model, automation boundaries, and where the platform limits will bite. I write down the trade-offs before building, including the option I rejected and why.

  3. 03

    Build

    Apex, LWC, Flow and integrations, built to the org's existing patterns rather than my preferred ones. Additive changes over clever refactors when other teams are already live on the thing I'm touching.

  4. 04

    Release

    CI/CD pipelines, sandbox-to-production release management, and a rehearsed go-live — including the manual steps that never live in metadata.

  5. 05

    Support and enhancement

    I keep running what I ship. Ongoing enhancement, production monitoring, functional and data analysis, and the unglamorous refactoring that keeps an aging org healthy. Two of my three engagements are open-ended support relationships, not projects I handed over.

In their words

Written client feedback, quoted as received. Client and colleague names are removed; nothing else is changed.

What I work on

Salesforce
Apex (triggers, async, Queueable, Batch)Lightning Web Components (component architecture, performance)AuraVisualforceFlowSOQLExperience CloudHealth CloudRevenue CloudSales CloudSharing and FLS modelPermission sets and profiles
Integration
REST and SOAP APIsOAuthBoomiHubSpotCallRailZohoTableau embeddingEmail-to-case
Release and ops
CI/CD pipelinesGitLab and GitHub branchingSandbox-to-production release managementWorkbenchData LoaderPostmanProduction monitoring and troubleshooting
AI in the CRM
RAG pipelinesMulti-source orchestration agentsAgentforceMCP-based toolingPrompt design
Foundations
JavaPythonJavaScriptSQLData structures and algorithms (500+ problems solved)

Now

Updated September 2026

  • Extending PriorAuth Assist — the deterministic completeness engine, citation post-validation in Apex, and Agent Script gating around the AI steps.
  • Working through the Dreamforce '26 platform changes: Headless 360 MCP servers, Agentforce Testing Center evals, Agent Fabric and Guardian.
  • Exploring voice agents on top of Salesforce data — speech stacks, latency budgets, and where the deterministic control has to sit.

About

I am a Salesforce developer in Noida, India. Since April 2024 I have been at Mirketa, a Salesforce consulting and ISV firm, working with client teams across Europe, the United States, Brazil and India — a food safety and testing group operating in seven countries, and a US behavioral health provider, among others.

I own the work end to end rather than picking up specs. That means sitting with client stakeholders to gather requirements, proposing the solution design, building it in Apex, LWC and Flow, running the release myself, and then supporting it in production. Two of my three engagements are open-ended: continuous enhancement and support on live orgs, not projects I handed over and walked away from.

More about how I work

Looking for a Salesforce developer who owns what he ships?

I'm open to roles in Noida, elsewhere in India, or remote — 30-day notice. Email is the fastest way to reach me, and I reply to everything.