~/dhairya koshti/portfoliocontact

// Salesforce & Full Stack Developer

I build the systems behind the screens.

Salesforce developer with 3 years of experience connecting the platform to everything around it: Apex services, REST APIs, AWS backends, and AI integrations.

view_systems()download_resume()ping --contact
● request-lifecycle.svgSalesforceAWSExternal API
invokebuildHTTPSproxyPutObjectemitruleDMLLWCUI · imperativeApexService · QueueableREST CalloutNamed CredentialAPI GatewayHTTPS · authorizerLambdaBusiness logicsObjectsDML · SOQLEventBridgeRules · schedulesS3Object storageSESTransactional email

// 01 · stack

Architecture layers

Skills grouped the way a system is actually built: platform at the core, integration and cloud around it.

L1layer

Salesforce Platform

Where the business logic and data model live.

ApexLWCSOQLFlowsREST APIsPermission setsReportsPage layouts
L2layer

Integration

Making Salesforce talk to the outside world.

Apex RESTNamed CredentialsMicrosoft Graph APIGmail APICallouts
L3layer

AWS

Serverless backends for the heavy lifting.

LambdaAPI GatewayS3CloudFrontEventBridgeSES
L4layer

AI & Web

Intelligent features and the UIs around them.

AgentforceClaudeGeminiReactJavaScriptFull stack web

// 02 · pipeline

Apex execution pipeline

How I structure a Salesforce-to-cloud call: thin entry points, async callouts, secrets out of code.

  1. 01

    Trigger / Flow

    A record change fires the entry point. Keep it thin.

  2. 02

    Service layer

    Business rules live in handler and service classes, not in the trigger.

  3. 03

    Queueable

    Callouts run async so the transaction stays fast and within limits.

  4. 04

    Named Credential

    Secrets and endpoints stay out of code; auth is handled by the platform.

  5. 05

    AWS / external API

    Lambda or a third-party API does the work and returns a result.

  6. 06

    Write-back

    Results land on the record, or are published as an event.

DocGenQueueable.clsillustrative
public with sharing class DocGenQueueable
    implements Queueable, Database.AllowsCallouts {

    private final Id recordId;

    public DocGenQueueable(Id recordId) {
        this.recordId = recordId;
    }

    public void execute(QueueableContext ctx) {
        // Endpoint + auth come from the Named Credential
        HttpRequest req = new HttpRequest();
        req.setEndpoint('callout:AWS_Gateway/render');
        req.setMethod('POST');
        req.setHeader('Content-Type', 'application/json');
        req.setBody(JSON.serialize(new Map<String, Object>{
            'recordId' => recordId
        }));

        HttpResponse res = new Http().send(req);
        if (res.getStatusCode() != 200) {
            throw new CalloutException(res.getBody());
        }
    }
}

// 03 · systems

Systems I've built

Each project drawn as the system it is: what talks to what, and in which direction.

SYS-01architecture

Signature App

Document-signing app spanning Salesforce LWC, a React signing experience, and an AWS backend.

storeoriginserveLWCLaunch + statusApexRequest signingAPI GatewayHTTPSLambdaSign workflowS3DocumentsCloudFrontCDNReactSigning UI
LWCApexReactAPI GatewayLambdaS3CloudFront
SYS-02architecture

Document Generation App

Generates documents from Salesforce data through an AWS Lambda rendering service.

invokestoreattachRecordTemplate + dataApexBuild payloadLambdaRender documentS3Generated filesFilesContentVersion
ApexQueueableLambdaS3ContentVersion
SYS-03architecture

AI Summaries in Salesforce

Claude and Gemini integrations that summarize Salesforce records and uploaded files in place.

promptpromptRecord / FileSource contentApexPrompt builderClaude APISummarizeGemini APISummarizeSummarySaved to record
ApexClaude APIGemini APIFiles
SYS-04architecture

Email Integrations

Microsoft Graph and Gmail API integrations for sending and syncing email inside Salesforce.

sendsendsyncsyncApexSync engineMS GraphSend + syncGmail APISend + syncEmailMessageLogged in SF
ApexMicrosoft GraphGmail APIOAuth
SYS-05architecture

Custom REST API

A custom Salesforce REST API that lets a client's website read and write platform data.

callClient siteHTTPS clientApex REST@RestResourceService layerValidate + mapsObjectsDML · SOQL
Apex REST@RestResourceSOQLDML
SYS-06configuration

Client Platform Configuration

Declarative work for client orgs, the unglamorous layer that makes everything else usable.

ReportsPermission setsPage layoutsFormula fieldsFlowsList viewsEmail templates

// 04 · experience

Commit history

Where I've worked and what I've shipped.

  1. 02/2024 → present

    Salesforce Developer

    MV Clouds Private Limited · Ahmedabad

    • Led a team of 4–5 on Salesforce AI training-data creation.
    • Built the Signature App (LWC + React + AWS) and the Document Generation App (Salesforce + Lambda).
    • Delivered a custom Salesforce REST API integration for a client website.
    • Built Claude and Gemini integrations that summarize records and uploaded files.
    • Built Microsoft Graph and Gmail API integrations for email send and sync.
    • Client platform configuration: reports, permission sets, page layouts, formula fields, flows, list views, email templates.

  2. 08/2023 → 01/2024

    Salesforce Developer Intern

    MV Clouds Private Limited · Ahmedabad

    • Started on the Salesforce platform; moved into the full-time developer role in February 2024.

  3. 2025

    Degree completed

    Silver Oak University

// verified credentials

Platform Developer I

Salesforce

Dec 2024

Agentforce Specialist

Salesforce

Oct 2024

AI Associate

Salesforce

Sep 2024

// 05 · contact

Open a connection

Have a Salesforce or integration problem? Send a request, or book a time to talk.

terminal

$ curl -X GET /contact

HTTP/1.1 200 OK

{

"email": "koshtidhairya99@gmail.com",

"github": "https://github.com/Dhairya-21",

"linkedin": "https://www.linkedin.com/in/dhairya-koshti-01538122a",

"calendar": "book a call"

}

$

// schedule

Prefer to talk it through?

Pick a time that works for you.

schedule_call() →
POST /contact