D365/Power Platform/Azure

D365/Power Platform/Azure – Washington, DC

Creative Information Technology Inc (CITI) is an esteemed IT enterprise renowned for its exceptional customer service and innovation. We serve both government and commercial sectors, offering a range of solutions such as Healthcare IT, Human Services, Credentialing, Cloud Computing, and Big Data Analytics. With clients in the US and abroad, we hold key contract vehicles including GSA IT Schedule 70, NIH CIO‑SP3, GSA Alliant, and DHS‑Eagle II. Join us in driving growth and seizing new business opportunities.

Role and Responsibilities

3.1 Solution and Platform Architecture

• Own and maintain the authoritative STAAND architecture: logical and physical data models, Dataverse table and relationship design, solution segmentation, environment strategy, and integration topology.
• Personally build in the platform — model‑driven app configuration, plug‑ins and custom APIs (C#/.NET), PCF controls, TypeScript/JavaScript client extensions, Power Fx, and plug‑in pipeline optimization.
• Establish and enforce architecture standards, design patterns, naming conventions, and technical debt registers across all modules and portals.
• Chair design authority review for significant changes; sign off on solution designs before build.
• Diagnose deep platform issues: performance degradation, API and service‑protection limits, plug‑in execution ordering, solution layering conflicts, storage growth, portal rendering.
• Maintain architecture artifacts sufficient to satisfy CCWIS review, federal audit, and District IT governance.

3.2 Cross‑Cloud Architecture: GCC and Commercial Azure

• Design, document, and harden the boundary between the GCC Dynamics/Power Platform tenant and Azure commercial‑cloud services.
• Define what data may traverse that boundary, in what form (de‑identified, tokenized, aggregated, or full record), under what authorization, and with what logging — including explicit architectural boundaries for protected data categories such as Medicaid Enrollment.
• Implement cross‑tenant , managed identities, service principals, Key Vault secret lifecycle, private networking, and API gateway patterns.
• Maintain a defensible position on data and FedRAMP authorization boundaries for every commercial‑cloud service in use, and present that position to auditors and federal reviewers.

3.3 AI and Agentic Development

• Serve as hands‑on technical lead for CFSA's AI capability, including CORA and its expansion into agentic workflows.
• Design, build, evaluate, and productionize agents in Azure AI Foundry and Copilot Studio: tool and function calling, orchestration and multi‑agent patterns, grounding and retrieval over Dataverse and document stores, prompt and context engineering, structured output, and human‑in‑the‑loop checkpoints.
• Own AI evaluation discipline: golden datasets, automated evals, groundedness and hallucination measurement, regression testing on model or prompt changes, latency and cost benchmarking, controlled rollout.
• Manage the AI model lifecycle — track model releases and deprecations, run comparative evaluation before adopting a new model, execute migrations without regression to worker‑facing quality.
• Implement responsible AI controls appropriate to a child welfare setting: content safety, PII/PHI handling, bias and fairness testing, explainability, audit logging of AI‑influenced actions, and clear framing of AI output as decision support rather than decision making.
• Support predictive and analytic capability aligned to agency mission priorities, ensuring models are validated, monitored for drift, and governed.
• Build reusable AI platform assets — prompt libraries, agent templates, evaluation harnesses, observability dashboards.

3.4 Application and Platform Security

• Own the security architecture of STAAND end to end; serve as technical counterpart to the agency ISSO, OCTO security, and District privacy officials.
• Apply and evidence compliance with OCTO IT policies (octo.dc.gov/page/it-policies), NIST SP 800‑53, FISMA, FedRAMP, HIPAA, 45 CFR 1355 (CCWIS), Title IV‑E confidentiality, and District data protection law including DC Code § 28-3851 et seq. breach notification obligations.
• Design and enforce least privilege: Dataverse business unit and role architecture, row/column‑level security, portal web roles and table permissions, privileged access management, sep