Senior Developer - D365/Power Platform/Azure

GoIntellects Inc.; Washington (District of Columbia); Hybrid; USD 110,000 - 160,000; Full time

Benefits offered by this job

Flexible work from home options

Job summary

GoIntellects Inc. is seeking a hands-on Senior Developer to build, release, and support STAAND on Dynamics 365 and Power Platform in a Washington, DC government context.

The role emphasizes daily coding, CI/CD ownership, ALM, and close collaboration with staff to meet needs. The ideal candidate will design and implement Dataverse plugins, TypeScript/JavaScript client code, Azure Functions, and integration components, while ensuring quality through tests, monitoring, and proactive production

Responsibilities

• Hands-on design and implementation of Dataverse plug-ins, APIs, and PCF controls.
• Own CI/CD, ALM, and release pipelines in Azure DevOps for multiple environments.
• Enforce coding standards, security, performance, and test coverage in code reviews.
• Provide production support, monitoring, and root-cause analysis for defects.
• Engage with stakeholders, run sprint demos, and support UAT and change communications.

Job description

Senior Developer - D365/Power Platform/Azure-Long-Term Contract (Government) Position

Title: Senior Developer - D365/Power Platform/Azure

Worksite Address: Washington, DC

Interviews: Both Webcam and In Person

Short Description

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

Complete Description

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

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 client leadership on delivery status, risk, and trade-offs in plain language.

Flexible work from home options available.