Senior Developer

Digerati Systems Inc.; Washington (District of Columbia); Hybrid; USD 140,000 - 190,000; Full time

Job summary

CFSA seeks a hands‑on Senior Developer to build, release, and operate STAAND on Dynamics 365 and Power Platform. You will own CI/CD, ALM end-to-end, perform quality reviews, provide production support, and collaborate directly with social workers and CFSA staff daily.

The role requires leading a development team, mentoring staff, and ensuring security and performance across multicloud components within GCC infrastructure.

Qualifications

• .
• .

Responsibilities

• Build and maintain integrations across GCC/commercial boundary with retry/idempotency handling.
• Own CI/CD, ALM, and release engineering for Dynamics 365 and Power Platform.

Skills

C#/.NET

Dataverse

Power Platform

Azure DevOps

CI/CD

ALM

Security reviews

GCC/GCCH

Education

Bachelor's degree in CS/SE/IS/Data Science

Tools

Bicep/ARM

Terraform

Power BI

GitHub Actions

Dataverse tooling

Azure DevOps

Job description

Candidate must be local to DMV (DC, Maryland & Virginia).

Hybrid position.

Agency is asking for online OR in person interview.

Skill

Required / Desired

Amount

of Experience

Candidate Years of Experience

Bachelor's degree in Computer Science, Software Engineering, Information Systems, Data Science, or a closely related technical discipline

Required

16

Years

Required

10

Years

Required

6

Years

C#/.NET plug-in and custom API development for Dataverse

Required

5

Years

Required

4

Years

Technical lead role over a development team (min. 3 developers)

Required

4

Years

Azure DevOps pipeline authoring and ownership (YAML, multi-stage)

Required

4

Years

Power Platform ALM — solution layering, environment variables, connection references, managed deployments

Required

4

Years

Pull request review as designated merge authority on a protected branch

Required

4

Years

Production support ownership with defined severity tiers and SLAs

Required

4

Years

Required

4

Years

Automated testing — unit, integration, and UI regression for D365 solutions

Required

3

Years

Power Pages / portal development including web roles and table permissions

Required

3

Years

Operating a live system through Microsoft biannual release waves

Required

2

Years

Direct engagement with non-technical business users for requirements and UAT

Required

4

Years

Secure development practice — code-level security review, secrets management, PII/PHI handling

Required

3

Years

Government cloud delivery — GCC, GCC High, or Azure Government

2

Years

Infrastructure as code — Bicep, ARM, or Terraform

2

Years

1

Years

Data and reporting — Power BI, Fabric, Synapse, Data Factory

3

Years

Mentoring and capability transfer to government staff

3

Years

Required

Required

Microsoft Certified: Dynamics 365 Customer Service (MB-230) or Sales Functional Consultant (MB-210)

Microsoft Certified: Azure Security Engineer Associate (AZ-500)

GitHub Actions or GitHub Advanced Security certification

ITIL 4 Foundation

Candidate must be local to DMV (DC, Maryland & Virginia).

Hybrid position.

Agency is asking for online OR in person interview.

CFSA seeks a hands‑on Senior Developer to build, release, and support STAAND on Dynamics 365 and Power Platform. Duties include daily coding, CI/CD and ALM ownership, quality reviews, production support, and direct collaboration with staff to meet needs.

1. Summary

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

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.

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.

3.4 Production Support and Solution Health

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

3.5 Customer and Stakeholder Engagement

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.