Senior Salesforce Developer with 9 years of experience designing and building on the Salesforce platform: Apex, Lightning Web Components, Flow, and enterprise integrations. Recent work includes Agentforce and Prompt Builder. Most of my experience is in banking and healthcare, where security, data quality and auditability matter as much as features.
- Platform development: Apex (trigger frameworks, async Apex, Queueables and Finalizers), Lightning Web Components, Flow, Custom Metadata-driven design
- Integrations: REST callouts, Named and External Credentials, Platform Events, Change Data Capture, Apex REST, MuleSoft
- AI on Salesforce: Agentforce agent actions, Prompt Builder, Einstein Trust Layer considerations, human-in-the-loop design
- Quality and DevOps: Apex tests, Jest, Salesforce Code Analyzer (PMD), Copado, Git, Jenkins, GitHub Actions, scratch orgs and SFDX
- Security: CRUD/FLS/sharing enforcement (
USER_MODE,stripInaccessible), Shield Platform Encryption, least-privilege permission sets
| Repository | What it proves |
|---|---|
| apex-trigger-framework | Metadata-driven trigger architecture with recursion control, declarative bypass and service/selector layers, tested at 200-record bulk |
| lwc-service-console | Accessible, wire-based LWCs with debounced search, shared error handling, and a full Jest suite with Apex wire mocks |
| salesforce-integration-patterns | Secure callouts via Named Credentials, retry with exponential backoff and a Finalizer, Platform Events, CDC, validated inbound REST, plus a tested Node mock server |
| agentforce-case-triage-actions | Read-only, bulk-safe invocable actions for Flow and Agentforce, with PII redaction, explainable deterministic logic and human-in-the-loop guardrails |
Note: Each repository above is a representative portfolio project built independently with synthetic data. It is not code from any employer or client. They are clean-room projects, and no real organisation or customer data appears in any of them.
- Bulk-safe by default, and tested with realistic data volumes
- Security enforced in code, not assumed
- Configuration over code where admins benefit
- Small, readable classes with clear seams for testing
- CI that runs on every pull request
The best way to reach me is on LinkedIn.