APAman Parate
Resume

13× Salesforce Certified·Triple Star Ranger·4.8+ years

Aman Parate

Senior Salesforce Developer

  • Apex
  • LWC
  • Experience Cloud
  • Integrations
  • Agentforce

I design and own Salesforce systems end to end — from Experience Cloud portals to the billing, logistics and LMS integrations behind them.

▶ View Case Files ⓘ Contact Me

4.8+ years on the platform · 13 certifications · 2,000+ Apex Doctor downloads · Pune, India · open to relocation

Aman Parate AP
13× Certified · Triple Star Ranger
Open to relocation & visa sponsorshipUpdated September 2026

Now Streaming

About the Engineer

Episode Synopsis
Origin & Vision.

I grew up in Nagpur and finished my B.E. in Computer Science at RTMNU in 2020. My first job at Cognizant put me on Salesforce for US retail clients — a Case Management System in LWC and Apex — and I learned early that on this platform the hard problems aren't in the code. They're in where the code meets the business process.

In 2023 I joined Salesforce itself as a Service Cloud Engineer, working with UK and US customers on the unglamorous end of things: SSO and MFA that wouldn't cooperate, triggers and async Apex hitting limits, integrations across REST, SOAP, Bulk API, Platform Events and Change Data Capture. Seeing how the platform breaks at scale, across many different orgs, was the best architecture education I could have asked for.

Since 2025 I've owned the customer-facing Salesforce estate at Tarana Wireless end to end: the Experience Cloud onboarding journey, a Case dashboard rebuilt from scratch in LWC, SAML SSO into LearnUpon, usage-based US billing on Chargent that processed ~$3M last quarter, and the Kafka, EDI and Boomi integrations that keep Salesforce in step with logistics, partners and finance. Along the way I've mentored a junior developer and a QA engineer onto the estate.

Along the way I built Apex Doctor because I was tired of spending 30 minutes reading debug logs by hand. It's now used by 2,000+ developers. That's the pattern I keep coming back to: find the manual work, design the system that removes it, and leave behind the tooling and documentation so the next person doesn't have to rediscover it.

Years of Experience
4.8+ (Nov 2021 – present)
Certifications
13 Salesforce certifications
Apex Doctor Downloads
2,000+ (VS Code Marketplace · Open VSX)
Billing Automated (last quarter)
~$3M via auto-invoicing
Current Focus
Experience Cloud · Integrations (Boomi, EDI, NetSuite) · Apex & LWC
Education
B.E. Computer Science & Engineering, RTMNU Nagpur (2020) · 8.3 CGPA
Languages
English, Hindi, Marathi
Relocation
Open to international relocation & visa sponsorship

Core Competencies

Director's Cut
Technical Capabilities.

Production tech stack — the instruments behind every episode. Drag, use the arrows, or just let it turn.

Working Principles

Production Notes
How I Work.

01

Design the system, not the ticket.

Every feature lands inside an estate — portal, finance, logistics, LMS. I map the data flow and the failure modes across systems before I write a line of Apex.

02

Bulkify, then automate.

Governor limits are a design constraint, not a bug to fix later. Once it's solid, remove the human step entirely — usage-based billing, self-registration, single sign-on.

03

Integration boundaries are contracts.

Each system owns specific records. Syncs are safe to re-run. Failures surface as work items, not silent log lines. Boomi for orchestrated sync, Kafka for events, EDI where partners live.

04

If it hurt to debug, build the tool.

Apex Doctor exists because 30-minute log triage was a tax on the whole team. Good engineering leaves behind tooling and documentation, not just closed tickets.

Where I add value as a lead

  • Architecture & integration designDeciding what lives in Salesforce, what lives in the surrounding systems, and how they talk — Boomi, Kafka, EDI, SAML — with clear ownership per object.
  • End-to-end ownershipFrom a stakeholder's requirement through design, build, release and the first month in production. No hand-offs into the void.
  • Developer experienceTooling, documentation and standards a team actually uses — Apex Doctor was adopted internally before it was public.
  • Business ↔ technical translationFinance, support and sales don't speak Apex. I turn their process into a design they can validate, then into a system that runs it.
  • Mentoring & reviewBrought a junior developer and a QA engineer up to speed on the Salesforce estate — pairing, code review, and the reasoning behind the standards, not just the standards.
  • Delivery & release disciplineSource-driven development with SFDX and Git branching on GitHub, Gearset pipelines for promoting changes between orgs, and change sets where they still fit. Every change is reviewed, covered by Apex tests, and traceable to a ticket.

Case Files

Problem → Approach →
Architecture → Outcome.

The system landscape I own at Tarana Wireless

Salesforce is the hub. Everything a customer touches — onboarding, cases, billing, training — and everything finance and logistics need from it, runs through the integrations below.

portal SAML SSO events docs Apex Doctor · VS Codedebug-log diagnostics for the team Experience Cloudcustomer portal · onboardingCase dashboard (LWC) Salesforce CoreAccounts · Contacts · CasesChargent billing · Invoices · PaymentsApex · Flows · Platform Events · SAML IdP LearnUpon (LMS)one-click training access Boomiin progress NetSuitefinance · in progress Kafkanear real-time event streaming EDI Integration Layerorders · shipments · fulfilment docs 3PL / Warehouselogistics · WMS Customer & Distributor Systemspartner platforms
  • Salesforce
  • Integration layer
  • External system
  • Developer tooling
  • In progress

Usage-based US billing on Chargent & finance sync

Tarana Wireless · 2025 → present · Salesforce · Chargent · Apex · Boomi · Kafka

Problem

US customers pay for what they use, so every month finance had to work out each customer's usage, raise the invoice by hand and collect payment separately. Slow, error-prone in the one place errors cost the most, and it got worse with every new customer.

Approach

  • Usage-based monthly billing on Chargent — each customer's charge is computed from actual usage for the month, not a fixed recurring amount.
  • Customers authorise a payment mandate once (with auto top-up); Chargent collects each month's invoice automatically against it.
  • Invoice generation and charge runs driven by scheduled and batch Apex, designed around governor limits from day one.
  • Billing and customer records flow onward to finance — Boomi flows syncing with NetSuite (in progress) and Kafka for events that can't wait for a batch.

Design decisions

  • Chargent over custom payment code. Card data and PCI scope stay with the payment gateway; we own the usage → invoice logic, which is where the business rules actually live.
  • Metering separated from charging. The month's usage is computed and reviewable before the charge run, so a bad reading never becomes a bad charge.
  • Salesforce owns the customer and the billing schedule. Downstream systems consume the results — Boomi for orchestrated, auditable sync, Kafka for low-latency events — so ownership per record never gets ambiguous.
metered usage mandate · auto top-up finance sync · in progress billing events Monthly usageper customer, per month Customerpayment mandate (portal) Salesforce + Chargentusage → invoice, monthlyauto-charge via stored mandatescheduled & batch Apex Boomi NetSuitefinance Kafkadownstream consumers
Billed via auto-invoicing
~$3M last quarter
Manual finance effort
−90%
Collection
Automatic monthly · usage-based · stored mandate

Experience

Three Seasons.
One Platform.

Season 3Now airing

Tarana Wireless

Senior Salesforce Developer · Jan 2025 – Present · Pune, India

  • Implemented Single Sign-On (SSO) between Salesforce and LearnUpon, enabling secure one-click SAML access (~6–10 new user logins daily) and eliminating manual identity management.
  • Designed and built the complete customer onboarding journey on Salesforce Experience Cloud — full site, guided flows, and self-service portal — supporting 20–30+ new customer self-registrations per day.
  • Rebuilt the customer-facing Case dashboard on Experience Cloud from scratch as a custom Lightning Web Component UI — a modern, responsive experience for customers to track, filter, and manage their support cases in one place.
  • Built usage-based monthly billing for US customers on Chargent — each customer is charged for actual usage against a stored payment mandate with auto top-up — processing ~$3M in customer billing last quarter via auto-invoicing while cutting manual finance effort by ~90%.
  • Building Boomi flows and NetSuite saved searches to keep financial and customer records in sync with Salesforce (in progress), with Kafka powering event-driven, near real-time data streaming.
  • Built EDI integrations connecting Salesforce with 3PL / logistics warehouse systems and customer & distributor systems — automating the exchange of order, shipment, and fulfilment documents across multiple systems.
  • Built a sign-up verification process that detects non-company-domain emails and routes them to guest-level access, protecting data quality at the source.
Season 2Complete

Salesforce

Service Cloud Engineer · Mar 2023 – Dec 2024 · Hyderabad, India

  • Delivered Service Cloud solutions for UK- and US-based clients, translating business and technical requirements into scalable Salesforce implementations.
  • Resolved complex issues across Single Sign-On, MFA, Flows, Apex triggers/classes, asynchronous Apex, Visualforce, and LWC.
  • Built integrations using REST, SOAP and Bulk APIs, Platform Events, and Change Data Capture; designed custom objects and deployed Apex classes, controllers, and triggers.
  • Developed Lightning Web Components for communities to locate and create investment applications; authored knowledge articles and documentation.
  • Participated in Agile/Scrum ceremonies and wrote Apex test classes to ensure maximum code coverage.
Season 1Complete

Cognizant Technology Solutions

Programmer Analyst · Nov 2021 – Feb 2023 · Pune, India

  • Developed Salesforce solutions for US-based retail clients, including a Case Management System using LWC, Apex classes, and triggers.
  • Configured Salesforce administration: profiles, roles, page layouts, org-wide defaults, sharing rules, permission sets, approval processes, and assignment rules.
  • Built automation with Workflows, Process Builder, Flows, Phone-to-Case, and Email-to-Case; implemented IVR functionality and batch Apex.
  • Performed metadata migration and bulk data operations using Change Sets, Workbench, Apex Data Loader, VS Code, and GitHub.

Side Project·Open Source

Apex Doctor
Debug logs, diagnosed in seconds.

Apex Doctor

VS Code extension · open source (MIT) · sole architect & maintainer

Diagnose Salesforce Apex debug logs in seconds. AI root-cause analysis, live log streaming, CPU & heap profiling and one-click navigation to Apex source — all inside VS Code, all offline by default.

View on GitHub Read the docs
  • VS Code Marketplace
  • Open VSX
  • TypeScript
  • Salesforce CLI & Tooling API
Performance Insights, Issues & Errors — the root cause of a failed transaction surfaced on one screen.
Downloads
2,000+
Latest release
—
Releases
14+
Last commit
—
Open issues
—
Log triage
30 min → sec

  • Deterministic diagnostics engine

    Governor-limit parsing, SOQL-in-loop and full-table-scan detection, trigger-order visualisation, async tracer — runs offline, no API calls.

  • CPU & heap profiler

    Self-time attribution, DevTools-style — pinpoints the exact method and SOQL query consuming runtime and memory.

  • Live log streaming & trace flags

    Watch Apex logs arrive in real time and manage trace flags for any user without leaving VS Code.

  • AI root-cause analysis

    Five providers including the Salesforce Einstein Trust Layer. Only a distilled, PII-safe summary leaves the machine; keys live in encrypted SecretStorage.

  • SOQL Query Plan & coverage overlays

    Selectivity problems surfaced from the Query Plan tool; covered and uncovered lines shown in the editor gutter.

  • Suggest Fix & Ask the Log

    One-click refactors with a diff preview, execution-path diffs between two logs, and natural-language questions against the log.

Reading a huge Apex debug log by hand to find one SOQL-in-a-loop took me and my team about 30 minutes, every time. I wanted the answer in seconds — offline, deterministic, and without pasting customer data into a chatbot. So I built the tool I wished existed, and then shipped it for everyone else.

Adopted internally at Tarana before public release · stats fetched from the GitHub API when this page loads.

Awards & Recognition

13 Certifications.
Triple Star Ranger.

Developer

  • PD IIPlatform Developer II
  • PD IPlatform Developer I
  • JS IJavaScript Developer I
  • PABPlatform App Builder

Consultant

  • DCData Cloud Consultant
  • SCSales Cloud Consultant
  • SvCService Cloud Consultant
  • ECExperience Cloud Consultant

AI

  • AFAgentforce Specialist
  • AIAI Associate

Admin & Foundations

  • AAAdvanced Administrator
  • ADMAdministrator
  • ASCAssociate

Contact

Let's build something on Salesforce. Looking for a Lead Salesforce Developer role — 30 days' notice, open to international relocation & visa sponsorship.

Email
amanparatesfdc@gmail.com
LinkedIn
linkedin.com/in/amanparate
GitHub
github.com/amanparate
Location
Pune, Maharashtra, India (IST, UTC+5:30)
Looking for
Lead Salesforce Developer · architecture & team ownership
Availability
30 days' notice · relocation & visa sponsorship welcome
Send Email Download Resume