D365 Solutions Architect

Ambient Enterprises•Remote, California, CA
•$150,000 - $170,000•Remote

About The Position

Ambient Enterprises is seeking a D365 Solutions Architect to design solutions across Dynamics 365 Sales, Field Service, and Business Central, including their integrations. The role determines how solutions are built and ensures the development team implements them accordingly. It reports to the Enterprise Solutions Architect and works closely with sales, service, and finance leaders. The role is accountable for solution design, integration architecture and reliability, commission and credit-split data, acquisition onboarding, and architecture standards and governance. It sits within IT and follows IT architecture, security, and change standards. Most of the week is spent on design and review, alongside hands-on development and providing senior technical support when needed. This is a senior individual-contributor role with no direct reports. The position is remote within the United States.

Requirements

  • Demonstrated experience personally designing Dynamics 365 Sales, Field Service, or Business Central solutions, with diagrams and decision records others have used to build solutions; able to explain examples in detail.
  • Experience supporting at least one production system long after go-live, including explaining what broke and what was changed as a result.
  • Deep Dataverse knowledge, including data modeling, security roles, business rules, plugins, and Power Automate.
  • Experience designing integrations across Dynamics 365 applications, such as Field Service, and with Business Central or another ERP, including error handling, duplicate prevention, and monitoring.
  • Application lifecycle management experience with 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 C# plugin, JavaScript web resource, and Power Automate development skills sufficient to build and fix production code, not just review it.
  • Working knowledge of AI development tools such as GitHub Copilot or Claude Code, and judgment to review and correct their output.
  • Clear communication with non-technical leaders, including examples of explaining technical tradeoffs and changing a business decision as a result.
  • Examples of self-initiated improvements that were built and their outcomes.

Nice To Haves

  • Experience consolidating acquired companies onto a shared platform.
  • Microsoft partner or consulting experience combined with experience owning a system in-house.
  • Experience establishing architecture governance, such as decision records or a review board.

Responsibilities

  • Translate business requests into build-ready designs covering data models, security, and environment promotion.
  • Write technical specifications for larger stories and review them with the developers who will build them.
  • Review designs and pull requests from developers and partners, explaining feedback to help them learn.
  • Build plugins, flows, and integration code, and step into development when the team is stretched or a problem requires senior support.
  • Document integrations across Sales, Field Service, and Business Central, including an owner, current data-flow diagram, and decision record for integrations carrying production risk.
  • Design integrations to handle retries without duplicates, deletions, delta synchronization, and failed messages.
  • Set up integration monitoring and alerts directed to a named owner.
  • Work with department leaders to understand their needs before proposing solutions.
  • Explain cost and risk tradeoffs and push back with reasons when a request is not worth its cost.
  • Assess acquired companies' systems against Ambient's architecture, including fit-gap analysis and identifying the system of record for each entity.
  • Plan data migration, deduplication, and cutover for acquired companies, and create a repeatable onboarding playbook.
  • Present architecture decision records to the architecture board and maintain records of decisions.
  • Keep Architecture and Development Standards current, including guidance on the team's use of AI tools.
  • Help the team use AI development tools effectively and review their output appropriately.
  • Evaluate and pilot improved development approaches, then share successful ones with the team.
  • Set the release approach for Sales and Field Service solutions, including solution layering, environments, and pipelines.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service