Senior Google Cloud Architect

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Employment Eligibility Statement: "Due to specific project and client requirements, this position is open to U.S. Citizens and U.S. Lawful Permanent Residents (Green Card holders). Sponsorship is not available at this time. Danta Technologies evaluates all candidates in compliance with the Immigration and Nationality Act (INA) and EEOC guidelines. All hiring decisions are made without regard to race, color, religion, sex, gender identity, sexual orientation, national origin, age, disability, veteran status, or any other protected characteristic." - Title: Senior Google Cloud Architect - GCP & AI (10+ Years of Exp) (we don't repeat as heading) - Location: Milpitas, CA - Onsite - Primary Skill: GKE Cluster & TPU Configuration - Job Description: "Seeking a Senior Google Cloud Architect with strong GCP and AI/ML expertise to lead enterprise cloud modernization and GenAI initiatives." - Required Skills: bullet list: - 6+ years of hands-on GCP experience. - Strong expertise in GKE, Kubernetes, and TPU configuration. - GCP: GCE, GKE, Cloud Run, VPC, Load Balancing, Cloud Storage, Cloud SQL, BigQuery, Pub/Sub, IAM, Monitoring & Logging. - Vertex AI, Gemini, Vertex AI Studio, AI/ML and MLOps. - Strong GenAI, LLM, RAG, Vector DB, Prompt Engineering, AI Agents experience. - Python mandatory; Java/Go preferred. - Terraform, Docker, CI/CD, GitHub/GitLab, Cloud Build. - Experience designing enterprise cloud architectures, migrations, security, governance, and modernization. - Strong communication and technical leadership skills. - Preferred: Google Professional Cloud Architect / ML Engineer certification and semiconductor, manufacturing, or Hi-Tech experience - Notes: "- All qualified applicants will receive consideration for employment without regard to race, color, religion, religious creed, sex, national origin, ancestry, age, physical or mental disability, medical condition, genetic information, military and veteran status, marital status, pregnancy, gender, gender expression, gender identity, sexual orientation, or any other characteristic protected by local law, regulation, or ordinance." - Benefits: "Danta offers a compensation package to all W2 employees that are competitive in the industry. It consists of competitive pay, the option to elect healthcare insurance (Dental, Medical, Vision), Major holidays and Paid sick leave as per state law. The rate/ Salary range is dependent on numerous factors including Qualification, Experience and Location." - #ZR (maybe a tag, ignore) We need to decide sections. We have eligibility statement (maybe part of About the role? Could be a short paragraph). Could be "About the role" or "Eligibility". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have real content. We have: - About the role: could include job description and location/primary skill. - Responsibilities: maybe not explicit; job description mentions leading enterprise cloud modernization and GenAI initiatives. Could be considered responsibilities. - Requirements: required skills list. - Qualifications: maybe preferred certification and experience. - Skills: maybe list of technical skills (but we already have required skills). Could combine. - Benefits: we have benefits description. - Pay: not specific; only says competitive pay dependent on factors. That's vague; we should not create Pay section unless posting actually states them. It says "competitive pay" but no range. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (healthcare, holidays, sick leave). So Benefits section is okay. Pay section: we have only "competitive pay" but no specifics; that might be considered filler? It says "competitive pay" is a statement but not a specific range. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive pay" is somewhat vague but it's stated. However it's not a specific number; but it's still a statement. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is competitive pay. So we could include a Pay section with that statement. But we also have Benefits section that includes healthcare etc. Might be better to combine Pay and Benefits into a single "Compensation and Benefits" but headings are fixed. We could create a Benefits section and include the pay statement inside it as prose. However the instruction says to use headings for Benefits, Pay, Schedule separately. If we put pay inside Benefits, we might be missing a Pay heading. But we could still create a Pay section with the statement "competitive pay, dependent on qualification, experience, location." That is not filler; it's actual content. So we can include Pay section. Schedule: not mentioned (onsite). Location says Onsite but not schedule (e.g., full-time). Not given. So we should not create Schedule section. Now we need to eliminate boilerplate: EEO statements, eligibility statement maybe not boilerplate? It's specific to citizenship requirement. That's substantive. We should keep it. We also have Notes about non-discrimination; that's boilerplate EEO. Should remove. We have "All qualified applicants will receive consideration for employment without regard to ..." that's also EEO boilerplate; remove. We have "Danta Technologies evaluates all candidates in compliance with the Immigration and Nationality Act (INA) and EEOC guidelines." That's part of eligibility statement; keep? It's about compliance; maybe keep as part of eligibility. We need to preserve all substantive information: eligibility, location, primary skill, job description, required skills, preferred, benefits, pay statement. We need to format using

  headings,

  • for lists,

    for prose. We need to decide which headings to use. Potential sections: - About the role: could include location, primary skill, job description paragraph. - Responsibilities: maybe the job description includes leading enterprise cloud modernization and GenAI initiatives; we could treat that as responsibilities. - Requirements: required skills list. - Qualifications: preferred certification and experience. - Skills: maybe we could combine required skills and preferred into Skills? But we already have Requirements and Qualifications. Could also have Skills section for technical skills list (like GCP services, languages, tools). However that would duplicate. Better to follow instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's six sections. Let's extract content for each. About the role: - Location: Milpitas, CA - Onsite - Primary Skill: GKE Cluster & TPU Configuration - Job Description: Seeking a Senior Google Cloud Architect with strong GCP and AI/ML expertise to lead enterprise cloud modernization and GenAI initiatives. We could combine into a paragraph. Responsibilities: - Lead enterprise cloud modernization and GenAI initiatives (maybe also designing enterprise cloud architectures, migrations, security, governance, modernization). Actually those are in required skills. But responsibilities could be: leading enterprise cloud modernization and GenAI initiatives, designing enterprise cloud architectures, migrations, security, governance, and modernization. However those are also in required skills. Might be overlapping. But we can keep responsibilities as the high-level duty: lead enterprise cloud modernization and GenAI initiatives. Requirements (required skills): List each bullet. Qualifications (preferred): - Google Professional Cloud Architect / ML Engineer certification - Semiconductor, manufacturing, or Hi-Tech experience Benefits: - Competitive pay (maybe we put in Pay) - Option to elect healthcare insurance (Dental, Medical, Vision) - Major holidays - Paid sick leave as per state law Pay: - Competitive pay, dependent on qualification, experience, location. We need to ensure we don't create filler. The pay statement is specific enough. Now we need to remove duplicated lines: The eligibility statement includes EEOC guidelines; we keep that part but not the later EEO boilerplate. We also need to remove the line "All qualified applicants will receive consideration for employment without regard to ..." (duplicate). Remove. Also remove the note about "#ZR". Remove. Now produce HTML. Structure:

    About the role

    Location: Milpitas, CA - Onsite. Primary Skill: GKE Cluster & TPU Configuration. Seeking a Senior Google Cloud Architect with strong GCP and AI/ML expertise to lead enterprise cloud modernization and GenAI initiatives.

    Responsibilities

    Lead enterprise cloud modernization and GenAI initiatives, including designing enterprise cloud architectures, migrations, security, governance, and modernization.

    Requirements

    • 6+ years of hands-on GCP experience.
    • Strong expertise in GKE, Kubernetes, and TPU configuration.
    • GCP: GCE, GKE, Cloud Run, VPC, Load Balancing, Cloud Storage, Cloud SQL, BigQuery, Pub/Sub, IAM, Monitoring & Logging.
    • Vertex AI, Gemini, Vertex AI Studio, AI/ML and MLOps.
    • Strong GenAI, LLM, RAG, Vector DB, Prompt Engineering, AI Agents experience.
    • Python mandatory; Java/Go preferred.
    • Terraform, Docker, CI/CD, GitHub/GitLab, Cloud Build.
    • Experience designing enterprise cloud architectures, migrations, security, governance, and modernization.
    • Strong communication and technical leadership skills.

    Qualifications

    • Google Professional Cloud Architect / ML Engineer certification (preferred).
    • Semiconductor, manufacturing, or Hi-Tech experience (preferred).

    Benefits

    • Option to elect healthcare insurance (Dental, Medical, Vision).
    • Major holidays.
    • Paid sick leave as per state law.

    Pay

    Competitive pay, dependent on qualification, experience, and location.

    We also need to include eligibility statement about citizenship. Where to put? Could be part of About the role as a separate paragraph. Or we could add a section "Eligibility". But headings list does not include Eligibility; but we could still add a heading if we have real content. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications,