> Markdown version of [/jobs/ext/4011523-salesforce-developer](https://www.wearedevelopers.com/jobs/ext/4011523-salesforce-developer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Salesforce Developer

- **Company:** TechDigital Corporation
- **Location:** Washington, DC, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Cloud Computing, Software Debugging, Software Design Documents, DevOps, Middleware, OAuth, Object-Oriented Software Development, Package Development Process, Performance Tuning, Cloud Services, Salesforce.Com, Web Services, Apex Code, Test-Driven Development (TDD), SOAPAPI, Change Data Capture
- **Published:** October 29, 2026
- **Apply:** https://www.thejobnetwork.com/job/1d81459c-c23d-4421-94f5-f4d1e76a1603/salesforce-developer

## About the Role

* Advanced Flow design across all flow types - Screen, Record-Triggered, Scheduled, Autolaunched, and Platform Event-Triggered. Mastery of fault paths, error handling, subflow architecture, loop optimization, collection management, and Flow debugging. Ability to design Flows that are as maintainable and production-ready as handwritten code.
 * Advanced Apex development: object-oriented design, asynchronous processing (Batch, Queueable, Schedulable), exception handling, and test-driven development.
 * Lightning Web Components: component lifecycle, wire service, event handling, base components, and performance optimization.
 * Salesforce security model: profiles, permission sets, sharing rules, record-level and field-level security - with the ability to implement configurations that comply with least-privilege principles.
 * Integration implementation: REST/SOAP API callouts, Platform Events, Change Data Capture, Named Credentials, and OAuth flows.
 * Financial Services Cloud: working knowledge of the FSDM, FSC-specific objects, and client lifecycle data patterns.
 * Experience Cloud: LWC development for portal contexts, guest user security implementation, and Experience Builder configuration.
 * DevOps practices: Source-driven development, CI/CD pipelines, and Unlocked Package development.
 * Strong debugging and troubleshooting skills across Apex, Flow, and integration layers.
 * Ability to read and implement from solution design documents, and to communicate implementation decisions clearly to architects and business stakeholders.

Experience

At least 5-7 years of Salesforce development experience, including:

 * Demonstrated experience implementing solutions on Financial Services Cloud, including FSDM-based object customization and FSC-specific feature configuration.
 * Hands-on Flow, Apex and LWC development across multiple Salesforce clouds.
 * Demonstrated experience developing for Experience Cloud, including custom LWC components and portal security models.
 * Integration implementation experience using REST/SOAP APIs, Platform Events, and middleware connectors.
 * Source-driven development using Salesforce CLI and Unlocked Packages.
 * Experience working in agile delivery teams, contributing to sprints alongside architects, administrators, and analysts.
 * Experience in financial services, or similarly regulated industries is strongly preferred.

Certifications

Required:

 * Salesforce Certified Administrator
 * Salesforce Certified Platform App Builder
 * Salesforce Certified Advanced Administrator
 * Salesforce Certified Platform Developer I
 * Salesforce Certified Platform Developer II, * Salesforce Certified Experience Cloud Consultant
 * Salesforce Certified Financial Services Cloud Accredited Professional
 * Salesforce Certified Sales Cloud Consultant
 * Salesforce Certified Service Cloud Consultant

## Description

* Standard Salesforce configuration: Proficiency in the full range of declarative tools - validation rules, approval processes, record types, assignment and escalation rules, standard automation, and platform-native features. Demonstrated discipline in exhausting configuration options before introducing Flows or Apex, in alignment with the standard configuration decision framework.