Google Cloud Platform Solution Architect

Role Google Cloud Platform Solution lead — hands-on (designs and builds)
Team Google Cloud Center of Excellence — regulated support
Location U.S. — secure vendor-operated site (hybrid: on-site + remote)

Reports to Delivery Lead / Engagement Lead
The role
You are the technical owner of how support is designed and delivered for a Google Cloud Center of Excellence handling regulated workloads. You architect the operating model — how cases are classified and routed, how AI-assisted tooling fits the lifecycle, how autonomy is earned and governed, and how regulated data is segregated and audited. Then you stay hands-on: you build reference implementations, prove out the hard technical patterns, and take the escalations no one else can crack.
This is deliberately not a whiteboard-only role. You design the system and you can operate it — troubleshoot a P1, write the runbook, wire up the tooling, and show engineers how it’s done. Your credibility comes from doing, not just diagramming.
What you’ll do — design & own
• Architect the support operating model — the specialization shards, case routing, severity handling (P1–P4), and how the case lifecycle (intake → classify → triage → KB → HITL → resolve → capture) works end to end.
• Design the regulatory architecture — how FedRAMP, CJIS, IAL3, ITAR and IRS-1075 controls are enforced: data segregation, role-based access, the human-only guardrail on regulated cases, and the audit evidence each regime requires.
• Own the AI-assisted support design — how Gemini-native classification, retrieval, and drafting fit the lifecycle, how autonomy is earned and revoked, and where the human must always hold sign-off.
• Map the solution to Google’s requirements — the native tooling (Vector, Looker), the VOVO secure-site model, BeyondCorp zero-trust access, and the FMR/TRT/CES measurement approach.
• Set the technical standards the delivery team builds and resolves against, and evolve them as the operation matures toward higher automation.
What you’ll do — hands-on
• Build reference implementations and tooling — prove the patterns work before the team adopts them; wire up integrations, retrieval, and automation.
• Take the hardest escalations — the P1s and complex cases that need deep Google Cloud Platform troubleshooting across networking, IAM, data & analytics, Vertex AI, and platform services.
• Author the seed knowledge — write and sign the runbooks that bootstrap the knowledge base, and set the bar for what “good” looks like.
• Coach through doing — pair with engineers on live cases, review their toughest tickets, and lift the pod’s technical depth.
What you bring — required
• U.S. citizenship and willingness to undergo adjudication/certification for regulated-data access.
• 7+ years in cloud engineering, cloud support, or solution architecture — with real, recent hands-on depth (you still build and troubleshoot, not just advise).
• Deep Google Cloud Platform expertise across networking, IAM, compute, and at least two of: data & analytics (BigQuery), ML/Vertex AI, security operations, platform. Professional-level Google Cloud Platform certification strongly preferred.
• Regulated / compliance architecture experience — you have designed or operated within FedRAMP, CJIS, ITAR, IRS-1075, HIPAA, PCI, or similar, and can explain how the controls are enforced, not just named.
• Support / operations architecture — you have designed how a support or operations function runs at scale (routing, severity, SLAs, escalation, knowledge).
• Incident leadership — you can own a P1 war-room, drive resolution under pressure, and communicate to customers and executives.
• Clear technical writing — you produce designs, runbooks, and standards others can follow.
Nice to have
• Experience with AI-assisted or agentic support tooling, Gemini, or LLM-in-the-loop workflows.
• Scripting / automation (Python, Go, Bash) and infrastructure-as-code.
• Prior work standing up a vendor-operated secure facility, or under BeyondCorp / zero-trust.
• Experience transitioning a support function from an incumbent with zero service degradation.
What success looks like in 90 days
• The support operating model and regulatory architecture are designed, documented, and agreed with the delivery team.
• Reference implementations and seed runbooks exist, and engineers are building against your standards.
• You are cleared for regulated-case handling and have personally resolved at least one hard escalation or P1