Lead Developer- Dynamics CRM
Role Descriptions: Lead Developer- Dynamics CRMLocation : Montvale, NJDuration: 6+ monthsEssential Skills: Lead Developer- Dynamics CRMDesirable Skills:Keyword:Skills: Digital : Microsoft Dynamics 365 CRM TechnicalExperience Required: 10 & AboveDevelopment Lead**PLEASE DO NOT SUBMIT DUPLICATES FROM 49978-1**Microsoft Dynamics 365 CE/CRM Technical LeadRole: ProCode DeveloperRequired Skills & Experience• 5-10+ years in software engineering with strong Python (async, typing, packaging, testing) and API development.• 2-4+ years building GenAI/LLM solutions (Azure OpenAI/Foundry), including prompt engineering, tool/function calling, and retrieval patterns. (Learning/Docs alignment via Microsoft Learn & internal enablement.)• Hands-on with Azure services used in AI apps: Azure AI Foundry, Azure OpenAI, Azure AI Search, Azure Functions, Key Vault, Event Grid/Service Bus, Storage, App Service/Container Apps.• Practical experience with agentic frameworks (e.g., Semantic Kernel, LangGraph, or AutoGen).• Familiarity with vector databases, embeddings, chunking strategies, and evaluation/guardrail techniques.• Proficiency with Git, DevOps pipelines, and observability (App Insights/Log Analytics).• ---Nice to Have• Experience with PCF/Power Platform extensions to surface agents in business apps, or Teams/Copilot Studio action integration when relevant to the use case. (Enterprise agent go-to-market references.)• Exposure to prompt flow, evaluation harnesses, A/B testing, and model benchmarking in Foundry.• Knowledge of RAI tooling (e.g., NeMo Guardrails or platform safety configs) and enterprise AI compliance processes.Education & Certifications• Bachelor's in Computer Science/Engineering (or equivalent experience).• Certifications (nice-to-have): Azure AI Engineer/Developer, Azure Data/Architect, PL-400/PL-600 (if working adjacent to Dynamics/Power Platform).Behavioral Competencies• Product mindset with focus on business value, reliability, and safety.• Excellent collaboration and communication across architecture, security, and delivery teams.• Bias for automation, documentation, and re-use; comfortable in agile, multi-stream programs