Senior Salesforce Developer · 4x Certified

I build the hard parts of Salesforce.

Async Apex, integrations, Lightning Web Components and data models that hold up in production. Platform Developer II certified, nearly four years on the platform.

4Salesforce certifications
4open-source Apex projects
274Apex tests in public repos
PD IIPlatform Developer II
Sonu Goswami
What I build

The parts that have to work every time

From background jobs that process thousands of records to the screens people use all day.

Async Apex at scale

Batch, Queueable and Schedulable jobs sized to governor limits, with retries, backoff and status you can see.

Batch ApexQueueableFinalizers

Integrations

REST and SOAP callouts with OAuth 2.0, cached tokens, Named Credentials and polling jobs that recover when the other side fails.

RESTOAuth 2.0Platform Events

Lightning Web Components

Fast, accessible screens built with Lightning Data Service, GraphQL and SLDS, wired to Apex only where it earns its place.

LWCLDSSLDS

Data models and sharing

Custom objects, relationships and sharing rules designed so the right people see the right records, and nothing more.

Data modelingSharingSecurity

Business logic and automation

Bulk-safe triggers, Flows and calculation engines where every number has to add up, with tests that prove it.

TriggersFlowsBulkification

Releases and quality

Sandbox-first delivery with validated deploys, targeted test runs, code analysis and a rollback plan for every data change.

Salesforce CLICode AnalyzerGit
Try it

Why my batch jobs run five records at a time

A batch that sends each file to an external AI service makes two callouts per record. Salesforce allows 100 callouts per transaction, but all of them must finish within 120 seconds. Move the slider and watch which limit breaks first.

10callouts of 100
100 scallout time of 120 s

Fits, with 20 seconds to spare on a slow day.

Assumes a slow day: 20 seconds of callout time per record.

Open source

Featured projects

Patterns from real production work, rebuilt from scratch with sample data. Every repo ships with Apex tests.

Review queue 8 files
FileSuggested typeScore
contract-signed.pdfContract96%
invoice-1042.pdfInvoice93%
w9-form.pdfTax form90%
IMG_4471.jpgNeeds review54%
id-front.pngID document88%

apex-async-document-pipeline

Callout-enabled Batch Apex sends files to an AI classifier, and a Queueable files each one, with retry, backoff and an LWC review screen.

Batch ApexQueueableLWCNamed Credential
65 Apex testsView code
Before regenerating 3 changes
FieldWasNow
Opportunity.Amount48,00052,500
Account.BillingCityAustinDenver
Contact.Title–Added
Quote.StatusDraftDraft

apex-oauth-integration-kit

OAuth 2.0 client-credentials calls with cached tokens, 401 and 429 handling, Queueable status polling and a versioned JSON diff shown in an LWC.

OAuth 2.0Platform CacheRESTLWC
112 Apex testsView code
Journal entry JE-0187 30/360
AccountDebitCredit
Cash254,218.75
Selling cost1,250.00
Receivable250,000.00
Premium2,500.00
Interest income2,968.75
Total255,468.75255,468.75

apex-ledger-engine

Double-entry ledger lines that always balance, with day-count conventions, idempotent regeneration and variance routing to an approval queue.

ApexTriggersCustom MetadataQueues
53 Apex testsView code
Cedar Ridge Partners LP Approved
  • Maple Holdings LLC50%
    • Alex Rivera60%
    • Jordan Lee40%
  • Sam Patel50%

apex-layered-ownership

Ownership followed through companies owned by other companies, with cycle detection, 100% checks at every layer and immutable approved snapshots.

Graph algorithmsApexLWCCustom Permissions
44 Apex testsView code
Process

How a change gets to production

The same route every time, so production never hears about a change first.

  1. Understand the ask

    A requirement call, then the work split into small tickets.

  2. Build in a sandbox

    Never in production. Code, metadata and permissions together.

  3. Test with 200 records

    Bulk-path tests, not one happy record.

  4. Retrieve and diff the target

    So nobody else's work gets overwritten.

  5. Validate, then quick deploy

    Validated with the tests that matter, deployed after sign-off.

  6. Verify the org

    Checked in the org itself, even when a deploy says it was cancelled.

Experience

Where I've done it

  1. 2025 to now

    Senior Salesforce Developer

    Astrea IT Services

    Senior developer on a US client's Salesforce org: async processing, integrations, Lightning Web Components and data models, from requirement call to production release.

  2. 2024 to 2025

    Salesforce Developer

    Astrea IT Services

    Built screening tools, data management screens, PDF generation and document automation on a production org.

  3. 2023 to 2024

    Associate Software Developer

    Cyntexa

    Apex services, Lightning Web Components and two-way REST integrations on an enterprise Salesforce org.

Certifications

Platform Developer IISalesforce · 2026
AdministratorSalesforce · 2024
Platform Developer ISalesforce · 2024
AssociateSalesforce · 2023
B.Tech, Computer Science Anand International College of Engineering · 2019 to 2023
Sonu Goswami

Got a hard Salesforce problem?

A batch that keeps timing out, an integration that fails at 2am, a data model that outgrew itself. I'm always happy to talk it through.