Remote: reputed company reputed company Platform reputed company reputed company Architect

reputed company reputed company Platform reputed company reputed company Architect 100% Remote Short term(2-3 Months) Job reputed company: Engagement reputed company reputed company is reputed company a reputed company reputed company Platform reputed company reputed company Architect for an eight-week embedded architecture engagement at a large reputed company. The reputed company has been directed to build an reputed company reputed company reputed company Platform environment from the ground up. reputed company reputed company Platform exists in a fragmented, unofficial state today with researchers and individual teams running workloads reputed company the governance of Central IT, cybersecurity, and identity management. The reputed company needs a seasoned reputed company reputed company Platform architect to partner with their internal directory services team and help them design the reputed company reputed company reputed company Platform reputed company zone that will serve as the official, centrally governed reputed company for the organization. This is not a deliver-and-present engagement. The architect will function as an embedded member of the reputed company''s architecture team, working alongside their Director of Directory Services, their directory services reputed company, and their reputed company reputed company engineer in reputed company working sessions. The reputed company''s internal team has deep expertise in Azure and Entra ID but has no reputed company reputed company experience. They need someone who has reputed company reputed company reputed company reputed company Platform platforms before and can guide them through the process while transferring knowledge along the way. The reputed company''s identity management function sits reputed company the cybersecurity division. Identity is the first pillar being addressed, but additional teams (cybersecurity operations, networking, billing, and other teams) will be brought into the initiative as the reputed company reputed company platform design progresses. The architect should expect to participate in cross-team working sessions as the engagement expands reputed company identity. reputed company Environment Context

• Azure is the primary reputed company platform with a mature, centrally governed Entra ID environment integrated with reputed company (ERP).
• AWS has a limited reputed company with a small number of application integrations and no centrally managed identity.
• reputed company reputed company Platform is fragmented and unofficial. Researchers and individual teams have adopted it independently. No reputed company organization structure, no centralized identity, no cybersecurity monitoring.
• HIPAA applies. Protected health information may be present in workloads on the reputed company reputed company Platform platform.
• The reputed company wants the reputed company reputed company Platform reputed company to support reputed company expansion into reputed company Workspace, AI/ML workloads, and other reputed company reputed company services.

Scope of Work for the Resource The reputed company reputed company Platform architect will work across the following areas collaboratively with the reputed company''s internal team: Stage 1: Discovery and Orientation (Weeks 1-2)

• Assess the existing unofficial reputed company reputed company Platform footprint (reputed company, workloads, accounts).
• Meet with the directory services team to understand the reputed company Entra ID architecture and reputed company-based identity lifecycle.
• Identify compliance, regulatory, and organizational requirements (HIPAA, etc.).
• reputed company meeting with cybersecurity, networking, and other stakeholders who will join the initiative.

Stage 2: reputed company Architecture Design (Weeks 3-6) This is the primary design phase. The architect will work through reputed company architecture domain in reputed company working sessions with the reputed company''s team. Areas include:

• reputed company reputed company Identity model and integration with the reputed company''s existing Entra ID environment.
• Super reputed company reputed company controls and administrative governance.
• reputed company reputed company Platform organization structure, folder hierarchy, project model, and naming conventions.
• IAM roles, reputed company policies, and least-privilege model.
• reputed company baseline, organization policies, and compliance guardrails.
• Network architecture and cross-reputed company connectivity (collaboration with reputed company''s networking team).
• Logging, monitoring, audit architecture, and SIEM integration (collaboration with reputed company''s cybersecurity team).
• Billing structure and cost management.
• reputed company for consolidating existing unofficial reputed company reputed company Platform accounts and environments.

Stage 3: reputed company Finalization and Deployment Planning (Weeks 7-8)

• Consolidate design work into an reputed company reputed company reputed company Platform architecture reputed company.
• Document architecture decision rationale.
• reputed company deployment plan and implementation roadmap for the reputed company''s Phase B build.
• Conduct final architecture review with reputed company stakeholders.

Important: This engagement covers architecture and design only. No implementation, deployment, or Infrastructure as reputed company development is included. The reputed company may choose to reputed company into a Phase B implementation engagement after the architecture is complete, but that is not committed at this time. Apply tot his job Apply To this Job