Lead Salesforce Developer

Do you write Apex like you know exactly how it'll break at scale? Can you look at a pull request and spot the governor-limit landmine before it ships? Do developers on your team actually get better because you're in the room?

Then, our Lead Salesforce Developer role here at District360 (a division of CUBE84) may interest you.

In this gig,

1. You're the technical backbone of the platform
   You design and build scalable Salesforce solutions using Apex, LWC, Visualforce, and Flows for a platform that 75+ Business Improvement Districts depend on daily. You take a business requirement and turn it into a technical design that actually holds up — not just one that works in the demo. You build integrations using REST, SOAP, Apex callouts, Platform Events, and Bulk API, and you know when automation is the right call versus when it's just adding complexity.

2. You're the last line of defense before code ships
   You review every meaningful Apex, LWC, and Visualforce PR that crosses your desk, and you catch the stuff that only shows up in production otherwise — missed bulkification, sloppy sharing logic, tests that pass but don't actually test anything. You set the coding standards and PR checklists the rest of the team works against, and when the same bug keeps showing up in different forms, you fix the root cause instead of patching it for the third time.

3. You own release day, good or bad
   You define how code moves through Sandbox, UAT, and Production, and you're the one accountable when a release doesn't go smoothly. You work in Salesforce DX, scratch orgs, and CI/CD pipelines (Copado, Gearset, Flosum, GitHub Actions — whatever the stack calls for), and you keep rollback plans and deployment docs current so a bad release is a delay, not a disaster.

4. You make the developers around you better
   You mentor through code reviews, pair programming, and actual technical coaching — not just "looks good, ship it." You spot skill gaps before they become a pattern, help build development plans around them, and show up for technical interviews and new-developer ramp-up because you know a strong team doesn't happen by accident.

5. You build things that don't fall over
   You write async Apex — Batch, Queueable, Future — that handles real volume, not just the happy path. You build reusable LWCs the rest of the team can actually extend, and you know your way around Profiles, Permission Sets, Sharing Rules, Field-Level Security, and Named Credentials well enough that security isn't an afterthought bolted on before go-live.

It'll be awesome if you...

• Have 6–8 years of hands-on Salesforce development experience, including time spent mentoring developers or leading technical initiatives (this one's non-negotiable)

• Have strong expertise in Apex, LWC, Visualforce, SOQL, SOSL, and Salesforce platform architecture

• Have built and consumed REST/SOAP APIs, Apex callouts, Platform Events, and Change Data Capture in production

• Have hands-on experience across Sales Cloud, Service Cloud, and Experience Cloud

• Are fluent in Git and source-driven development — branching strategies, PR conventions, and collaborative code reviews aren't new concepts to you

• Have worked with Salesforce DX and CI/CD tooling like Copado, Gearset, Flosum, or GitHub Actions

• Hold any two of: Platform Developer I, Platform Developer II, or JavaScript Developer I

• Can explain governor limits, deployment strategy, and test coverage decisions to someone who isn't a developer

More awesome, if you have

• Experience on a Salesforce-native SaaS product with recurring, predictable release cycles

• Built enterprise-scale integrations or event-driven architectures

• Worked with CPQ, Marketing Cloud, MuleSoft, or Data Cloud

• Stood up engineering standards, release governance, or DevOps process from scratch

• A Data Architect, Security & Identity Architect, Agentforce Specialist, Data Cloud Consultant, or Platform App Builder certification