Why This Role Exists

This role exists to own architecture, quality, and delivery.

If production breaks, this person is accountable — not “involved.”

What You’ll Actually Do

• Own end-to-end Salesforce solution architecture
• Design scalable Apex architectures (trigger frameworks, async orchestration, data models)
• Decide when to use Apex vs LWC vs declarative tools
• Lead complex integrations with external systems (REST/SOAP, OAuth, AWS, third-party tools)
• Enforce governor-limit-safe design and security best practices
• Lead code reviews with high standards for maintainability and test quality
• Mentor and technically lead SDE-1 and SDE-2 engineers
• Translate vague business requirements into scalable technical designs
• Own production stability, RCA, and preventive improvements

Requirements

• 4–7 years of hands-on Salesforce development experience
• Minimum 2 years of experience leading a technical team
• Strong hands-on expertise in:
• Apex (Triggers, Batch, Queueable, Schedulers, Async patterns)
• Lightning Web Components (LWC)
• SOQL & SOSL optimization
• Deep understanding of:
• Salesforce Security Model (Profiles, Permission Sets, Sharing, Roles)
• Governor limits and bulk-safe design
• Proven experience designing and owning Salesforce integrations
• Hands-on experience with CI/CD using Salesforce DX and Git-based workflows
• Ability to defend architectural decisions with clear reasoning

What Gets You Rejected Instantly

• Confuses “seniority” with years of experience
• Relies heavily on Flows for core business logic
• Avoids ownership when production issues occur
• Can’t design a trigger framework independently