Azure AI PowerApps Developer – Full stack

About Ariana.Digital
Ariana.Digital is a team of entrepreneurial, energetic, and innovative digital professionals. We bring broad experience across industries and the digital ecosystem, helping organizations drive impact and sustainable growth. Our team thrives on diversity of backgrounds, skills, and experiences, and we value those who deliver tactical excellence along with a long-term strategic vision for our clients.

AI-video interview - required; W2 only ; 9 month extendible contract; remote with travel as required. US GC or citizen only.

What We Offer:
Flexible working arrangements
Resources and support for continuous growth

Azure Full-Stack Engineer
Engagement: W2 project talent through myndQ.ai
Reports to: Program Manager

Place of work: Remote + travel as required to contractor site. (Atlanta)

28 September 2026 – 27 June 2027 (nine months)

Effort: 40 hours week.

Clearance / suitability: Public Trust processing before any tenant access. No Government systems or data until onboarding, NDA/data clauses, suitability, training, and authorization are properly complete.

The work
Our public sector client is buying a modernized reporting application: landing and navigation, public vs. healthcare-provider branching, validation that helps finish a complete report, in-page help, phone and desktop, English and Spanish parity for public instructions. Production stays in govcloud-managed Azure.

The Azure Full-Stack lead owns the application UI, API, and gov-cloud Azure integration.
You implement from Government-controlled schemas, interfaces, identity, and approval gates. You do not invent the hosting service, database, queue, API shape, or upload mechanism. Kickoff supplies those. A thin adapter contains that uncertainty.

Stack :

Public site - PowerApp Service or Container Apps | TypeScript/React; C# / ASP.NET Core; Playwright, axe, xUnit; Bicep; Copilot Cowork + Copilot Studio Work IQ; GraphIQ MCP; Entra / PIV | Microsoft Graph (C#); SharePoint or Dataverse as the content store || Security | Entra, PIV staff sign-in, managed identities, FIPS | Entra CBA or govcloud federation; directed logs || API integration | REST adapter or named queue/file | C#, OpenAPI, idempotent receipts |
Alternate paths exist (Static Web Apps + Functions; Power Apps + Dataverse; SharePoint Lists UI; Service Bus or file drop). Power Pages for the form. Production remains government-managed Azure.

What you own
Application UI and API
- Accessible UI from UX/HCD specs: landing, branching steps, client validation, content integration, surveys, performance.- Server APIs: branch rules, authorization, validation, upload policy, throttling, correlation IDs, output mapping.- Repeat every integrity-relevant browser check on the server.- Typed contracts between UI and API. Accessible errors agreed with UX.- Performance budget for page load ≤ 3 seconds; assets on gov Azure; no third-party analytics that ship PHI.
Canonical model and adapter
- Versioned state machine and branch matrix. A person cannot be forced through the other path’s required fields.- Field rules, completeness assistance, and review-step checks. No chatbot diagnosing an adverse event.- Canonical report model and adapter to the Government-identified interface: idempotent submit, retries, receipts, reconciliation, failed items to gov-approved handling.- Logs for reconciliation without unnecessary narrative, PHI, or PII.
gov Azure, identity, and content
- Deploy only to gov-approved Azure with reproducible IaC, environment separation, managed identities, approved secrets, Entra/PIV, least privilege, encryption, and gov-directed logging.- No hardcoded subscriptions, tenants, resource IDs, secrets, endpoints, or feature states.- App reads only published content via Graph or Dataverse API with a managed identity. Public reporters never authenticate to Copilot, SharePoint, Work IQ, or MCP.- GraphIQ MCP may draft and stage FAQ, tooltip, label, list, field-definition, and branch-matrix updates. It cannot publish, cannot change application/adapter/IaC source, and cannot read reports, PHI, or submitter PII.- Code, tests, IaC, and engine changes use Government-approved IDEs only (OpenAI Codex, Cursor, Claude Code, or equivalent after a revised AI Use Card). Not MCP. Zero touch on gov production data and the gov production environment.
Uploads
- Phase 1: gov-approved medical-record and vaccine-docume…