CFSA - Senior Developer - D365/Power Platform/Azure

Benefits:

• Opportunity for advancement
• Training & development
• Wellness resources

CFSA requires a hands‑on Senior 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). STAAND is built on Microsoft Dynamics 365 and the Power Platform in a Government Community Cloud (GCC) tenant, with Azure services operating in Microsoft's commercial cloud. 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. This is a working lead role—the Resource is expected to be in the codebase daily.

3. Scope of Work and Responsibilities

3.1 Hands‑On Development

• Personally design and write complex work in the backlog: Dataverse plug‑ins and custom APIs in C#/.NET, PCF controls, TypeScript/JavaScript client extensions, complex Power Fx, Azure Functions and Logic Apps, and integration components.
• 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.

3.2 CI/CD, ALM, and Release Engineering

• 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.

3.3 Code Review and Engineering Quality

• 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.