Open to Salesforce & development roles
I build Salesforce automation where a bad write is an incident, not a retry.
Four years of Apex, Flow, LWC and Salesforce-to-SAP integrations inside an enterprise org with 75,000 users — governor limits, retry paths, audit trails, and a governance board that has to agree the design is right. I also rebuilt how that work gets done: a system of Claude Code skills that forces design before code.
Current
Arcadia Tech
Consulting for Becton Dickinson
Scale
75,000 users
4+ years, one enterprise org
Building
Apex & integrations
Flow, LWC, Copado, SAP via MuleSoft
Based in
Tucumán, AR
Remote UTC−3 · ES native, EN C1/C2
What I build
Four years, one enterprise org.
Automation, integration, delivery
Automation
Flow + invocable Apex
Sync vs. batch dispatch, governor-limit headroom
Integration
Salesforce → SAP
Named Credentials, retries, audit object
Field Service
Work Order lifecycle
Cases, Service Appointments, mass actions
Delivery
Copado & governance
Change control across business units
Credentials
All current. Click any badge to view it.
Certifications(5)
Full list →Toolkit
What I build with.
Day to day
Platform
Apex, Flow, LWC
Triggers, batch, queueable, screen flows
Clouds
Service Cloud, FSL
Cases, Work Orders, Service Appointments
Integration
REST via MuleSoft
Idempotency, retries, error logging
Working with AI
Claude Code skills
20+ by lifecycle phase, design gated
Writing
Notes from real builds.
Articles(2)
View all →Building an AI-Augmented Development Workflow for Salesforce
How I used structured AI skills and workflows to enforce process discipline in a large Salesforce org,and why it's still not finished.
Trigger Frameworks That Actually Scale
How one interface and a factory pattern keep 400+ Apex triggers manageable — bulkification, data access separation, and production safety.
Next step
Hiring a Salesforce developer? Let's talk.
I reply to email within a day. Tell me about the org and what needs building.