> Markdown version of [/jobs/ext/3692573-salesforce-developer](https://www.wearedevelopers.com/jobs/ext/3692573-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:** TekWissen LLC - **Location:** San Antonio, TX, United States - **Experience:** Expert - **Contract:** Temporary contract - **Skills:** Microsoft Access, Application Programming Interfaces (APIs), User Authentication, Cloud Computing, Code Review, Continuous Integration, Extract Transform Load (ETL), Data Manipulation Languages, Data Migration, Software Design Patterns, Design Web Format, Middleware, Github, Web Servers, Metadata, OAuth, Mockito, Cloud Services, Copado, Oracle Apex, Salesforce.Com, Systems Integration, Talend, Web Services, Apex Code, Process Builder (Salesforce), Delivery Pipeline, Change Data Capture, Git, Salesforce Sales Cloud, Visualforce, Event Driven Architecture, Data Loader, Apex Programming, Salesforce Object Query Language (SOQL), Data Objects, Restful APIs, Software Version Control, Marketing Cloud, Mulesoft, Custom Reports - **Published:** October 11, 2026 - **Apply:** https://www.careerjet.com/jobad/usc8e72de8079d23bc672c721ce6f33138 ## About the Role a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } PD1 and PD2 Certifications Preferred. * PD1 and PD2 Certifications Preferred. Minimum 6+years of experience. * Minimum 6+years of experience. ## Description Job Description: a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Configuration * Declarative Tools: Flows, Process Builder, Workflow Rules, Approval Processes. * Object & Field Management: Custom objects, fields, relationships (lookup, master-detail, many-to-many). * Security & Access: Profiles, Permission Sets, Roles, OWD, Sharing Rules, Field-Level Security. * UI Customization: Page Layouts, Record Types, Dynamic Forms, App Builder (Lightning). * Reports & Dashboards: Custom report types, dynamic dashboards, joined reports. Customization (Apex & LWC) * Apex: Classes, Triggers, Batch Apex, Queueable, Scheduled Jobs, Future Methods. * Governor Limits: Bulkification, SOQL/DML best practices, avoiding limits violations. * Lightning Web Components (LWC): Component lifecycle, wire service, event handling, parent-child communication. * Aura Components: Legacy support and migration to LWC. * Visualforce: Pages, Controllers, Extensions (legacy support). * Testing: Apex test classes (75%+ coverage), mocking, @TestSetup, assertions. Integrations * REST & SOAP APIs: Salesforce standard APIs, callouts from Apex, named credentials. * Data 360. * Platform Events & Change Data Capture (CDC): Event-driven architecture, real-time integrations. * Middleware: MuleSoft, Informatica, or similar iPaaS tools. * External Services: Connecting external REST APIs declaratively via External Services. * Authentication: OAuth 2.0 flows (JWT, Web Server, Username-Password), Connected Apps. * ETL & Data Migration: Data Loader, Workbench, third-party tools (Jitterbit, Talend). Architecture & Best Practices * Design Patterns: Trigger frameworks (e.g., FFLIB), Service/Selector/Domain layers. * Separation of Concerns: Enterprise architecture patterns. * Source Control: Git, Salesforce DX (SFDX), scratch orgs, unlocked packages. * CI/CD: GitHub Actions, Copado or similar deployment pipelines. * Metadata API & Tooling API: Understanding of deployment mechanisms. Salesforce Ecosystem Knowledge * Core Clouds: Sales Cloud, Service Cloud, Financial Cloud (deep expertise expected). * Additional Clouds: Data 360 and Marketing Cloud. * Salesforce Releases: Staying current with 3x annual releases, pre-release orgs. * AppExchange: Evaluating and managing managed packages. Soft Skills * Translating business requirements into technical solutions. * Code reviews. * Communicating with stakeholders and architects. * Strong documentation habits (technical specs, solution design docs).