D365 Solutions Architect
Ambient Enterprises, Remote, California
What you need
- A track record of Dynamics 365 Sales, Field Service, or Business Central solutions you personally designed, with diagrams and decision records other people built from, and examples you can walk through in detail.
- At least one production system you supported long after go-live, including what broke and what you changed because of it.
- Deep Dataverse knowledge: data modeling, security roles, business rules, plugins, and Power Automate.
- Integration design experience across Dynamics 365 apps such as Field Service, and with Business Central or another ERP, including error handling, duplicate prevention, and monitoring.
- ALM experience: managed and unmanaged solutions, environment strategy, and source-controlled deployment pipelines.
- Working experience with Git and GitHub, including branching, pull requests, code review, and deployment pipelines.
- Hands-on development in C# plugins, JavaScript web resources, and Power Automate, strong enough to build and fix production code, not only review it.
- Working knowledge of AI development tools such as GitHub Copilot or Claude Code, with the judgment to review and correct what they produce.
- Clear communication with non-technical leaders, with examples of explaining a technical tradeoff to a business leader and changing a decision because of it.
- Examples of improvements you proposed and built that nobody asked for, and what happened.
Nice to have
- Experience consolidating acquired companies onto a shared platform.
- Microsoft partner or consulting experience, combined with time owning a system in-house.
- Experience setting up architecture governance, such as decision records or a review board.
Estimated compensation: $150-170k/yr. with flexibility based on experience and skills.
Solution Design
- Turn business requests into designs a developer can build without guessing, covering data model, security, and environment promotion.
- Write technical specifications for larger stories before build starts and review them with the developers who will help build them.
- Review designs and pull requests from developers and partners, and explain the feedback so people learn from it.
- Build plugins, flows, and integration code directly, and step in on development when the team is stretched or a problem needs senior hands.