Lead Developer - Microsoft Dynamics 365 Customer Insights

Position SummaryWe are seeking a hands-on Lead Developer to design and deliver a branded, interactive patient messaging solution using Microsoft Dynamics 365 Customer Insights - Journeys, Microsoft Dataverse, Azure Functions, and Twilio. The lead developer will own the core pro-code implementation, guide technical decisions, review code, and support the solution through integration testing, user acceptance testing, production deployment, and stabilization. Required platform experience: Candidates must have hands-on experience with Microsoft Dynamics 365 Marketing, now Customer Insights - Journeys, including real-time journeys. This requirement is mandatory. Key Responsibilities· Lead the detailed technical design and implementation across Customer Insights - Journeys, Dataverse, Azure Functions, and Twilio. · Review the current Customer Insights implementation, existing real -time journeys, integration points, session model, and deployment approach. · Develop Dataverse C# plugins that run within the sandbox execution model and follow platform performance, security, and tracing practices. · Define and implement Dataverse Custom APIs, including request and response parameters, plugin registration, validation, error handling, and downstream invocation patterns. · Build the Customer Insights custom -channel components required to send RCS messages, process delivery events, invoke triggers, and support journey branching. · Implement attribute change triggers and custom triggers that allow inbound patient responses to continue the appropriate real-time journey path. · Develop Azure Functions using the .NET isolated-worker model, dependency injection, configuration, logging, retry handling, and secure webhook processing. · Integrate Twilio Content Templates, RCS senders or sender pools, message status callbacks, inbound webhooks, and SMS fallback behavior. · Configure app registrations, managed identities, permissions, secrets or certificates, and secure service -to-service authentication between Azure, Dataverse, and Twilio-facing components. · Own solution packaging and deployment across development, test, and production environments, including managed and unmanaged solutions, environment variables, connection references, and deployment pipelines. · Provide technical leadership through code reviews, design walkthroughs, troubleshooting, and coordination with architecture, QA, business analysis, and client teams. · Support unit testing, end-to-end integration testing, regression testing, UAT defect resolution, production deployment, stabilization, and knowledge transfer. Required Technical Experience• Microsoft Dataverse and Power Platform pro-code development: Strong hands-on experience designing and developing Dataverse plugins in C# using the sandbox model, plugin execution context, tracing, secure and unsecure configuration, and appropriate synchronous or asynchronous execution patterns. • Dataverse Custom APIs: Proven experience defining Custom APIs and request and response parameters, registering plugin logic, handling validation and faults, and exposing operations for journey or integration workflows. • Power Platform solution lifecycle: Hands-on experience with managed and unmanaged solutions, dependency management, environment variables, connection references, solution packing and unpacking, source control, and repeatable deployment across environments. • Customer Insights - Journeys: Hands-on experience with the platform formerly known as Dynamics 365 Marketing, including real-time journeys, custom -channel framework, channels, custom triggers, attribute change triggers, journey branching, delivery reporting, and session or interaction data. • Azure Functions: Strong .NET and C# experience building Azure Functions with the isolated -worker model, dependency injection, configuration, telemetry, webhook endpoints, idempotency, retries, and exception handling. • Azure identity and security: Experience with Microsoft Entra ID app registrations, application permissions, managed identity, client credentials, certificate or secret management, and secure service -to-service authentication. • Twilio and messaging: Hands-on messaging integration experience with Twilio. Direct RCS Business Messaging experience is strongly preferred, including Content Templates, sender pools, status callbacks, inbound webhooks, opt-out handling, and SMS fallback. • Integration engineering: Experience designing resilient API and webhook integrations with correlation identifiers, structured logging, replay protection, idempotency, observability, and production support considerations. Preferred Experience· Healthcare, patient-engagement, or another privacy-sensitive messaging environment · Messaging consent, opt-out, short-code, deliverability, and carrier considerations · Azure DevOps or equivalent source-control and CI/CD practices for Power Platform and Azure workloads · Production monitoring and troubleshooting across Dataverse, Azure Functions, and external messaging providers