Senior Solution Architect - Part-Time

#

Domain

What it covers

1

Feature-to-Platform Mapping

Every feature placed in PWA, Power Pages, Model-Driven Apps, or split. Justified in Architecture Decision Records.

2

CC↔GCC Bridge (APIM)

The single security-critical integration layer between Commercial Cloud workloads and RP's GCC back-office. Policies, versioning, caching, audit.

3

Data Architecture

Source-of-truth assignment per data element. OASIS read-only. Dataverse for eService records. PDPA classification, retention, lifecycle.

4

Identity Architecture

Entra ID tenant design. 3-role RBAC with business units. Token flows across PWA, Power Pages, Power Apps. Conditional access.

5

Non-Functional Architecture

SLA, performance budgets, RTO/RPO, accessibility (WCAG 2.1 AA), observability, scaling rules. NFR document part of the contract.

6

Release Strategy

Rolling release model. Feature flags. Blue-green via slot swap. VAPT per release. Parallel run with SNApp.

7

Reusable Component Library

SGDS rendered three ways: PWA native, Power Pages CDN, Power Apps PCF wrap. Version coordination. RP self-sufficiency post-handover.

8

Compliance Architecture

VAPT scope and remediation. ShipHats integration. WOGAA telemetry. IM8 alignment. SGDS Masthead and accessibility.

3. Must-Have Technical Skills

Eachitem below is essential. Generic 'Azure experience' or 'Power Platformexperience' is not enough. We are looking for measurable depth in the specifictools this project will use.

Skill area

Depth required

Azure architecture

Production-deep. VNet design, private endpoints, APIM policies in XML, App Service slot-swap, Front Door routing, Key Vault rotation, ExpressRoute peering. Must draw the topology from memory.

Power Platform architecture

Knows the limits, gotchas and tipping points. Dataverse quotas. Power Automate connector throttles. Power Pages caching. PCF iframe constraints. ALM patterns. Has shipped 2+ production solutions.

Frontend / PWA architecture

Understands bundle size budgets, service worker strategies, MSAL token flows, performance trade-offs. Can challenge a frontend lead on why first paint is 4 seconds.

Identity & access (Entra ID)

OAuth 2.0, OpenID Connect, SAML, PKCE, JWT validation, token lifecycle, scope and consent, conditional access. Reads Entra ID app manifests fluently.

Integration patterns

API gateway, BFF, CQRS, event-driven, sync vs async, retry and idempotency, circuit breakers, dead-letter queues. Picks the right pattern per use case.

Security architecture

Zero trust, defense in depth, threat modelling (STRIDE), data classification, encryption-at-rest vs in-transit, secrets management, audit logging.

Data architecture

Source-of-truth assignment, master vs transactional data, schema evolution, archive strategy, GDPR/PDPA. For RP, must design around a read-only OASIS — no data migration.

DevSecOps

Azure DevOps pipelines, ShipHats gates (SCA / SAST / DAST / secrets scanning), Infrastructure-as-Code (Bicep or Terraform), environment promotion, rollback strategies.

GovTech compliance

IM8, WOGAA, SGDS, VAPT process, IDSC approval flow, ShipHats onboarding. Separates a commercial architect from a government-ready architect.

4. Soft Skills (Equally Essential)

Theseseparate an architect who looks good on paper from one who actually moves theproject forward.

•      Abilityto say "no" with reasons. Defends architectural decisions in front ofdevelopers and clients without hand-waving authority.

•      Abilityto push back on the client when their decision creates a downstream problem —without sounding like a refusal.

•      Facilitationskill. Architecture happens in workshops. Stays the calmest, most patientperson in the room when stakeholders disagree.

•      Documentationdiscipline. Every decision documented as an Architecture Decision Record (ADR).RP staff inheriting the system in year 3 should read these without needing toask anyone.

•      Translationbetween technical and business. Explains why a technical choice matters interms of cost, time, or risk — not jargon.

•      Comfortwith ambiguity. RP's discovery is still in progress; requirements will emergeduring delivery. Designs for change, not fixed scope.

5. Certifications

Certificationsare not the goal — capability is. But for this combined PWA + Power Platform +Azure + Government profile, these signal real depth. Candidates holding bothPL-600 and AZ-305 are rare and worth interviewing on sight.

Certification

What it signals

Priority

PL-600 — Power Platform Solution Architect Expert

Gold-standard cert for this exact role. Functional, technical, and architectural depth on Power Platform.

Strongly preferred

AZ-305 — Designing Microsoft Azure Infrastructure Solutions

Architect-level Azure cert. Covers networking, identity, data, security.

Strongly preferred

PL-400 — Power Platform Developer Associate

Hands-on developer credential. Proves coding-level understanding.

Preferred

AZ-700 — Azure Network Engineer Associate

Networking depth — VNets, private endpoints, ExpressRoute, firewall. Important for the CC↔GCC bridge.

Nice-to-have

6. Experience Requirements

•      8+ yearsof solution architecture experience. Senior level minimum. Principal levelideal.

•      Hasshipped at least 2 government-grade or regulated-industry systems to productionin Singapore.

•      Haspersonally architected at least one Power Platform deployment of meaningfulscale — multiple Power Pages sites, multiple Model-Driven Apps, integratedDataverse, proper ALM.

•      Haspersonally architected at least one production Azure deployment with VNet,private endpoints, APIM, App Service, Key Vault, and Entra ID integration.

•      Familiarwith at least one of: ShipHats, WOGAA onboarding, IM8, IDSC approval. Multipleis better.

•      Hasworked through at least 2 VAPT cycles end-to-end — scope, triage, remediation,retest.

•      Hasfacilitated client workshops with mixed business and technical stakeholders.Not just attended — facilitated.

•      Comfortablewith both agile (modern product) and waterfall (legacy government) delivery —knows when to use each.