Senior Microsoft Dynamics 365 / Power Platform / Azure Developer

HRUCKUS; Washington (District of Columbia); Hybrid; USD 132,000 - 141,000; Full time

Job summary

HRUCKUS is seeking a Senior Microsoft Dynamics 365 / Power Platform / Azure Developer for a hybrid assignment in Washington, DC. The role involves building, releasing, and operating the CCWIS system, STAAND, and closely working with CFSA staff to ensure operational readiness.

You will own CI/CD, Power Platform ALM, and code quality gates; engage with social workers and partners; manage production support and release processes; and drive architectural decisions across DevOps pipelines and Azure

Qualifications

• Bachelor's degree in CS or related field.
• 10+ years progressive software development experience.
• 6+ years Dynamics 365 CE / Dataverse / Power Platform development.
• 5+ years C#/.NET plug‑in and custom API development for Dataverse.
• Technical lead role over a development team (min. 3 developers).
• Azure DevOps pipeline authoring and ownership (YAML, multi‑stage).
• Power Platform ALM — solution layering, environment variables, connection references, deployments.
• Pull request review as designated merge authority on a protected branch.
• Production support ownership with defined severity tiers and SLAs.
• Automated testing — unit, integration, UI regression for D365 solutions.
• Power Pages / portal development including web roles and table permissions.
• Secure development practices — secrets management, PII/PHI handling.
• Operating a live system through MS biannual release waves.

Responsibilities

• Build and maintain integrations across GCC/commercial boundary.
• Optimize platform performance and API usage.
• Implement portal functionality across six external portals.
• Build automated test coverage for code and interfaces.
• Own Azure DevOps YAML build and release pipelines.
• Manage branching, versioning, and release cadence.
• Maintain environment strategy and security/compliance checks.
• Automate infrastructure provisioning (Bicep/ARM or Terraform).
• Plan and execute releases with notes and runbooks.
• Lead reviews and mentor CFSA staff on best practices.

Skills

Dynamics 365

Power Platform

Dataverse

C#/.NET

Azure DevOps

CI/CD

Azure

GCC Government Cloud

Education

Bachelor's degree in Computer Science / Software Engineering / Information Systems / Data Science or related

Tools

Azure DevOps

Power Platform ALM

Bicep/Terraform

Job description

Veteran Firm Seeking a Senior Microsoft Dynamics 365 / Power Platform / Azure Developer for a Hybrid Assignment in Washington, DC

My name is Stephen Hrutka, and I lead a Veteran-owned consulting firm in Washington, DC, focused on strategic sourcing, supply chain, and IT Staffing.

We want to fill a Senior Microsoft Dynamics 365 / Power Platform / Azure Developer role for the Child and Family Services Agency (CFSA) in the DC Government.

The ideal candidate is a DMV resident with 10+ years of progressive software development, 6+ years of hands‑on Dynamics 365/Power Platform development, and expertise in C#/.NET plug‑ins and Azure DevOps. Experience with Government cloud delivery (GCC) and infrastructure as code (Bicep/Terraform) is highly desired.

Executive Summary:

HRUCKUS is looking for an experienced Senior Microsoft Dynamics 365 / Power Platform / Azure Developer to build, release, and operate STAAND (Stronger Together Against Abuse and Neglect in DC), the District's federally certified Comprehensive Child Welfare Information System (CCWIS).

Position Description:

The Resource will personally write complex code, own CI/CD and Power Platform ALM end to end, gate quality through pull request review, run the production support and release process, and engage directly with social workers, supervisors, private agency partners, and the CFSA training organization to ensure delivery meets real operational needs.

Position Responsibilities:

• Build and maintain integrations across the GCC/commercial boundary, including retry, idempotency, dead-letter handling, and reconciliation logic.
• Optimize platform performance: plug‑in execution ordering and depth, query and FetchXML tuning, batching against API and service‑protection limits, portal page and cache behavior, and form/view load times.
• Implement portal functionality across six external portals, including web roles, table permissions, and external‑user authentication flows.
• Build and maintain automated test coverage — unit tests for plug‑ins and custom code, integration tests for interfaces, and UI regression suites.
• Produce prototypes and spikes to de‑risk design decisions before entering the sprint backlog.
• Refactor and retire technical debt on a defined cadence.
• Own the Azure DevOps YAML build and release pipelines, Power Platform Build Tools tasks, solution export/pack/unpack, environment variables, connection references, and automated deployment across Dev, Test, UAT, Train, and Production.
• Own branching and merge strategy, versioning scheme, and release train cadence; keep all solutions and code under source control with no manual production changes.
• Maintain environment strategy and hygiene with the Architect: refresh cadence, data masking for lower environments, managed environment policies, DLP policy alignment, and capacity monitoring.
• Integrate quality gates into the pipeline: static analysis, Power Platform solution checker, dependency and secret scanning, test execution, and enforced failure thresholds.
• Automate infrastructure provisioning for Azure components (Bicep/ARM or Terraform) so environments are reproducible.
• Plan and execute releases: release notes, deployment runbooks, rollback plans, go/no‑go criteria, and post‑deployment verification.
• Execute Dynamics 365 biannual release wave and monthly Power Platform update readiness: early‑access testing, deprecation remediation, and regression validation against the Architect’s impact plan.
• Continuously reduce release cycle time, deployment failure rate, and manual deployment steps; report DORA‑style metrics.
• Serve as primary reviewer and merge authority for pull requests into protected branches.
• Enforce coding standards, security requirements, performance patterns, and test coverage thresholds; reject work with specific, actionable findings.
• Maintain the definition of done, PR checklist, and code review SLA so review does not become a bottleneck.
• Review specifically for security defects: injection, insecure deserialization, hardcoded secrets, unsafe portal permissions, and unsafe handling of PII/PHI.
• Review AI‑related changes — prompt modifications, agent tool scoping, grounding source changes — against the Architect’s evaluation framework before merge.
• Mentor CFSA staff and other contract developers through review; treat review as a capability‑transfer mechanism.
• Own triage, diagnosis, and resolution of production defects across modules and portals; drive root cause analysis and permanent fixes.
• Maintain monitoring, alerting, and observability: Application Insights, Azure Monitor, Dataverse audit and plug‑in trace logs, portal telemetry, and integration failure dashboards.
• Operate to defined severity tiers and response/resolution targets; provide hyper‑care coverage following each release.
• Participate in escalation rotation for critical production incidents, including outside core hours as required.
• Monitor capacity, storage growth, license and API consumption, and Azure spend; flag trends before they become constraints.
• Maintain and exercise backup, restore, and disaster recovery procedures; validate RTO/RPO periodically.
• Keep runbooks, known‑error records, and support documentation current.
• Work directly with social workers, supervisors, private agency partners, resource development specialists, and fiscal staff to understand requests before building.
• Facilitate requirements refinement and story elaboration sessions; translate practice language into buildable, testable acceptance criteria.
• Run demos at end of sprint and before release; collect and act on feedback.
• Plan and support User Acceptance Testing; triage defects during UAT and provide go/no‑go recommendation.
• Partner with the training organization on release notes, tip sheets, training calendar alignment, and change communications.
• Serve as the technical point of contact for the super‑user community and the STAAND help desk escalation path.
• Brief the District Program Manager and CFSA leadership on delivery status, risk, and trade‑offs in plain language.

Required Qualifications:

• Bachelor's degree in Computer Science, Software Engineering, Information Systems, Data Science, or a closely related technical discipline (16 years)
• Progressive software development experience (10 years)
• Hands‑on Dynamics 365 CE / Dataverse / Power Platform development (6 years)
• C#/.NET plug‑in and custom API development for Dataverse (5 years)
• Technical lead role over a development team (min. 3 developers) (4 years)
• Azure DevOps pipeline authoring and ownership (YAML, multi‑stage) (4 years)
• Power Platform ALM — solution layering, environment variables, connection references, managed deployments (4 years)
• Pull request review as designated merge authority on a protected branch (4 years)
• Production support ownership with defined severity tiers and SLAs (4 years)
• Azure development — Functions, Logic Apps, API Management, Service Bus, Key Vault (4 years)
• Direct engagement with non‑technical business users for requirements and UAT (4 years)
• Automated testing — unit, integration, and UI regression for D365 solutions (3 years)
• Power Pages / portal development including web roles and table permissions (3 years)
• Secure development practice — code‑level security review, secrets management, PII/PHI handling (3 years)
• Operating a live system through Microsoft biannual release waves (2 years)
• Bachelor's degree in Computer Science, Software Engineering, Information Systems, Data Science, or a closely related technical discipline

The target annual salary is $131,600.00 - $141,000.00