Three years inside a major insurer's Salesforce org
Apex, Visualforce, LWC and Aura development for Mercury General in Los Angeles, with REST API integrations and asynchronous processing, held to a test coverage bar above the platform minimum.
- Practice
- Salesforce development · Insurance
- Period
- Jan 2019 to Mar 2022
- Client rating
- 5.0 out of 5
Complex requirements, solved in the room
The role began where most enterprise Salesforce work does: understanding requirements complex enough that no one person held the whole picture, and joining the brainstorming sessions where the solution actually got decided.
On an insurer's org, a change is rarely local. Every proposal had to be weighed against what it would do to the rest of the platform.
What was built
Development spanned the full platform surface across three years.
- Apex classes and controller classes written against SFDC governor limits
- Visualforce pages, plus LWC and Aura components
- Integrations using REST APIs
- Asynchronous processing for the work that could not run inline
- Apex triggers with bulkification assumed, not retrofitted
Coverage as a standing bar, not a release scramble
Test coverage was held above 75% and maintained at that level through every enhancement, with unit tests prepared as part of the work rather than assembled at deployment.
That distinction is the whole difference. Coverage written to pass a deployment gate tells you nothing; coverage written alongside the feature is what makes the next change safe.
Outcome
Three years and three months on one insurer's org, across development, integration and release discipline, with the coverage bar never dropping below 75%.
Have a similar problem?
Book a free 30 minute audit. We map what is broken, what it costs you and what the fix takes.
