Salesforce Technical Lead

Salesforce Technical Lead Location: Cincinnati, OH (Onsite) Roles & Responsibilities This role is technical in nature. Responsibilities center on solution Leading, hands‑on engineering, code quality, performance, security, and platform stability across Sales Cloud and Service Cloud. Technical Leading & Solution Design Own the end-to-end technical architecture of Salesforce solutions across Sales Cloud and Service Cloud, including object/data model, sharing & visibility model, and system landscape. Design scalable, governor-limit-safe solutions; make explicit declarative‑vs-programmatic (Flow vs Apex vs LWC) decisions with documented trade‑offs. Define the data model and relationships (master-detail vs lookup, junction objects, external objects) and the large-data-volume (LDV) strategy — skinny tables, indexing, selective SOQL, archiving. Lead the security model: profiles, permission sets/permission set groups, role hierarchy, sharing rules, OWD, restriction rules, and field‑level security; apply Shield where required. Produce technical design documents, sequence/component diagrams, and ERDs; review and sign off all low‑level designs from the team. Hands‑on Apex & Backend Engineering Write and review production‑grade Apex — triggers (one-trigger-per-object handler pattern), batchable, queueable, schedulable, and future methods — with bulkification and governor-limit awareness throughout. Build reusable Apex frameworks: trigger frameworks, service/domain/selector layers (e.g., fflib / Enterprise patterns), and exception/logging utilities. Author efficient, selective SOQL/SOSL; eliminate queries and DML inside loops; manage CPU time, heap, and query‑row limits. Enforce 90%+ meaningful Apex test coverage with proper assertions, Test.startTest/stopTest, mocking via Stub API, and TestSetup data factories — not coverage padding. Maintain and refactor legacy Apex/Visualforce; drive technical‑debt reduction. LWC & Front‑end Engineering Design and build Lightning Web Components — reactive properties, lifecycle hooks, parent‑child and pub‑sub (Lightning Message Service) communication, and composition patterns. Use wire adapters, imperative Apex calls, and the UI API appropriately; implement caching, optimistic UI, and error handling. Handle Aura LWC interop for legacy coexistence; build for Lightning App Builder, Experience Cloud, and Service/Sales Console embedding. Apply SLDS, accessibility (a11y), and performance best practices (lazy loading, minimizing re‑renders, Lightning Data Service to reduce server round‑trips). Set up Jest unit testing for LWC and enforce front‑end code‑review standards. Service Cloud & Sales Cloud Configuration Depth Lead Service Cloud implementations: case lifecycle & assignment, Omni‑Channel routing, queues, Entitlements & Milestones, Knowledge (KCS), Service Console, CTI/Open CTI telephony integration, and macros/quick actions. Lead Sales Cloud implementations: lead/opportunity management, lead‑to‑cash flows, forecasting, products/price books, and quoting touchpoints. Design Flow‑based automation (record‑triggered, scheduled, screen flows, subflows) with sound bulk and ordering behavior; consolidate overlapping automation. Tune assignment rules, escalation, approval processes, and platform events for real‑time orchestration. Integration & API Engineering Design integration architecture using REST/SOAP APIs, Platform Events, Change Data Capture, Streaming API, and Bulk/Composite APIs. Implement inbound/outbound integrations with named credentials, External Services, callouts (synchronous & async), and OAuth 2.0 flows; secure secrets appropriately. Define middleware/ESB patterns (e.g., MuleSoft) for high‑volume, decoupled, and resilient integrations; handle retries, idempotency, and error queues. Build and govern integration contracts and payload schemas; manage API limits and throughput. Performance, Security & Quality Conduct technical health checks and code audits; identify and remediate governor‑limit risks, inefficient queries, and recursion/ordering issues. Profile and optimize Apex, SOQL, LWC rendering, and batch throughput; resolve LDV and timeout bottlenecks. Run static analysis (PMD/Apex PMD), enforce code‑review gates, and maintain Apex/LWC/Flow coding standards and checklists. Lead security reviews — CRUD/FLS enforcement, SOQL/SOSL injection prevention, sharing enforcement (with sharing), and secure callout handling. DevOps, Release & Environment Engineering Define the branching strategy (Git), CI/CD pipeline (Salesforce DX, Copado/Gearset/Jenkins), and automated deployment/validation gates. Lead sandbox and environment strategy, including source tracking, scratch orgs, and package‑based development (unlocked/2GP) where applicable. Own release and deployment architecture, data seeding, metadata management, and rollback strategy; resolve deployment failures. Technical Leadership & Hands‑on Mentoring Act as the final technical authority on the build; provide hands‑on guidance and pair on complex Apex/LWC/integration problems. Run code reviews, set engineering standards, and mentor developers on platform patterns and limits. Build POCs and reference implementations to de‑risk technical approaches and demonstrate platform capability. Stay current with Salesforce seasonal releases (Spring/Summer/Winter), API version upgrades, deprecations, and new platform features (including AI/Agentforce), and assess their technical impact. Reusable Assets & Engineering Accelerators Create and govern reusable technical assets — LWC component libraries, Apex frameworks, integration templates, and deployment accelerators. Identify recurring technical problems across engagements and productize solutions into shared accelerators. Maintain technical reference architectures, design/coding guidelines, and best‑practice repositories. What Success Looks Like Code is bulkified, governor-limit-safe, and passes audits and security reviews with minimal rework. Apex/LWC architecture is well‑factored, testable, and supported by reusable frameworks. Integrations are resilient, performant, and within API limits; releases deploy cleanly through CI/CD. The team consistently follows the technical standards and patterns defined by the Lead. Required Qualifications Salesforce Technical Lead with strong experience in customer handling, system architecture design, and team oversight Proven experience delivering 3–4 Sales/Service Cloud implementations Strong hands‑on experience with LWC and Apex Salary and Other Compensation Applications will be accepted until 07/10/2026. The annual salary for this position is between $ 80,000– $ 130,000 depending on experience and other qualifications of the successful candidate. This position is also eligible for Cognizant’s discretionary annual incentive program, based on performance and subject to the terms of Cognizant’s applicable plans. Benefits Medical/Dental/Vision/Life Insurance Paid holidays plus Paid Time Off 401(k) plan and contributions Long-term/Short-term Disability Paid Parental Leave Employee Stock Purchase Plan Disclaimer: The salary, other compensation, and benefits information is accurate as of the date of this posting. Cognizant reserves the right to modify this information at any time, subject to applicable law. Please note, this role cannot offer visa transfer or sponsorship now or in the future. #J-18808-Ljbffr Cognizant