Technology
The stack, and what each part was actually used for
A list of logos proves nothing. Every entry below carries a note on how it was applied in real delivery, and the ones marked as core are where the depth is.
Salesforce platform
Where the majority of the work lands.
11 items · 5 core
Apex
Triggers, asynchronous processing, REST services, and integration classes.
Lightning Web Components
Reconciliation views, guided flows, and record-page components.
Salesforce Flow
Record-triggered automation and approval processes.
Apex REST
Inbound endpoints with DTO-based contracts decoupled from the Salesforce schema.
Asynchronous Apex
Keeps integration work off the synchronous path.
Triggers
Thin entry points delegating to a service layer.
SOQL
Querying against operational objects.
Custom Metadata
Endpoint configuration and scoring rubrics held as data rather than code.
Agentforce
Agent topics delegating to invocable Apex actions.
Visualforce
Maintenance of earlier-generation pages.
Reports & dashboards
Operational reporting and end-user enablement.
Integration & middleware
The layer between Salesforce and everything else.
6 items · 4 core
REST API integrations
Both directions — consumed and exposed.
MuleSoft
Integration layer in front of a government registry, keeping Apex off the external contract.
AWS Lambda
Middleware bridging Salesforce and external delivery providers.
AWS SQS
Queueing to absorb high-volume update bursts.
Named Credentials
Externalised endpoints and authentication, no secrets in Apex.
Oracle Fusion
Accounts Receivable interface for automated financial data exchange.
Architecture & delivery
How decisions get made before code is written.
9 items · 5 core
Solution design
Requirement to data model to architecture to build.
Enterprise integrations
Contract design across system boundaries, and the failure behaviour at each one.
Data modelling
Orders, inventory, receiving, payments, and financial transactions.
System architecture
System context, integration landscape, and the trade-offs recorded.
Security & sharing model
Profiles, permission sets, roles, sharing rules, field-level security.
DTO contract design
API shape held separate from the platform schema.
Business requirements analysis
Translating an operational question into something a platform can carry.
Production support
Diagnosis and resolution on live systems carrying real load.
Stakeholder management
Working with business, QA, finance, and integration teams.
Languages & tooling
Beyond the platform.
6 items · 3 core
JavaScript
Lightning Web Components and integration functions.
Java
Academic and platform-adjacent background.
Apex unit testing
Mockable service interfaces so behaviour is provable without live callouts.
Git & GitHub
Branching, review, and version-controlled metadata.
VS Code
Primary development environment.
Jira
Delivery tracking inside structured teams.
In context
See these applied to a real problem
The case studies show how these choices were made, what they cost, and what they bought.