> Markdown version of [/jobs/ext/3036468-chief-builder-distinguished-solution-engineer-maestro](https://www.wearedevelopers.com/jobs/ext/3036468-chief-builder-distinguished-solution-engineer-maestro). 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). --- # Chief Builder, Distinguished Solution Engineer, Maestro - **Company:** Salesforce Inc. - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Cloud Computing, Computer Programming, Metadata, Release Management, Salesforce.Com, Apex Code, Marketing Cloud - **Published:** September 23, 2026 - **Apply:** https://salesforce.wd12.myworkdayjobs.com/External_Career_Site/job/Missouri---Remote/Chief-Builder--Distinguished-Solution-Engineer--Maestro_JR360275-1 ## About the Role * Experience. 10+ years in solution engineering, technical architecture, forward deployed engineering, or professional services, including time at the most senior technical level in a field organization. * Platform mastery. Deep working knowledge of the Salesforce platform and its metadata: Apex, Flow, Lightning Web Components, the Metadata API, packaging, and release management. You know where the sharp edges are because you have been cut. * AI native building. You build with AI coding agents in your daily work and you have a clear view of where they are strong and where they need a human. * Enablement at scale. You have taken a capability from a handful of experts to thousands of practitioners, and you can show what changed in their output. * Field credibility. SEs, architects, and services leads take your call. You have earned that by building, not by presenting. * Communication. You can explain the same technical decision to an engineer, an executive, and a customer, and all three leave with the right understanding. * Travel. Willingness to travel as needed. * Preferred. Salesforce certifications at the architect level. Experience building or running a technical community or champions program. Experience across Marketing Cloud, Revenue Cloud, or Data 360. * Education. Degree or equivalent relevant experience required. Experience will be evaluated based on the core competencies for the role. ## Description * Own internal technical enablement. Design and run the enablement that makes SE, FDE, Professional Services, Success, and Partner technologists genuinely capable with the product. Not slideware. Hands on keyboard, measured by what they can build afterward. * Own the programming. Build the curriculum, certification path, office hours, build labs, and champions network that carry the capability across every region and every team. * Set the technical standard. Define what a good build looks like: tested, governed, reversible, explainable. Publish the reference patterns everyone else works from. * Build the reference library. Turn the best real work in the field into reusable references that any technologist can pick up and run with. * Be the proof in the room. Lead the hardest technical engagements and the most senior customer conversations. A CIO should be able to ask you why a change is safe and get a real answer. * Close the loop with Product. Bring back what the field actually hits: the gaps, the sharp edges, and the patterns worth building into the product. * Scale through others. Grow a network of technical leaders across the field who can run this without you in the room. ## Related Videos - [A Data Mesh needs Open Metadata](https://www.wearedevelopers.com/videos/505-a-data-mesh-needs-open-metadata) - [The AI-Native Engineering Org: What’s Real, What’s Hype, What’s Next](https://www.wearedevelopers.com/videos/100004-the-ai-native-engineering-org-what-s-real-what-s-hype-what-s-next) - [Crafting Custom Frameworks with Rust: A Deep Dive into Procedural Macros](https://www.wearedevelopers.com/videos/849-crafting-custom-frameworks-with-rust-a-deep-dive-into-procedural-macros) - [The Software Engineer 2030: From Coder To AI Orchestrator? - Patrick Schnell](https://www.wearedevelopers.com/videos/1825-the-software-engineer-2030-from-coder-to-ai-orchestrator-patrick-schnell) - [AI Won't Fix Your Engineering Culture](https://www.wearedevelopers.com/videos/100266-ai-won-t-fix-your-engineering-culture) - [Bringing Clarity to Event Streams: Enabling Analytics and AI Through Rich Metadata](https://www.wearedevelopers.com/videos/1616-bringing-clarity-to-event-streams-enabling-analytics-and-ai-through-rich-metadata) ## Related Articles - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Why developer experience matters](https://www.wearedevelopers.com/magazine/514-why-developer-experience-matters) - [What Makes WeAreDevelopers World Congress Different From Every Other Tech Event?](https://www.wearedevelopers.com/magazine/701-what-makes-wearedevelopers-world-congress-different-from-every-other-tech-event) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)