Enterprise AI Systems Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes: THE COMPANY (mission) maybe not needed as heading? Could be "About the role"? Actually "THE COMPANY" is description of company; could be considered "About the role"? But we have "ROLE AND RESPONSIBILITIES:" and "PERSONAL AND PROFESSIONAL QUALIFICATIONS:" and "EDUCATION:" and "JUUL LABS PERKS & BENEFITS:" and "SALARY RANGES:" and "LOCATIONS:" (maybe schedule? Not schedule). We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine: "About the role" could include company mission and role overview. "Responsibilities" from ROLE AND RESPONSIBILITIES. "Requirements" maybe from PERSONAL AND PROFESSIONAL QUALIFICATIONS (experience). "Qualifications" maybe education? Or we could treat "Qualifications" as education and certifications. "Skills" maybe technical skills list. "Benefits" from perks & benefits. "Pay" from salary ranges. "Schedule" not present; we should not include schedule if no content. We must not repeat job title as heading (not given). Must not include Job ID etc. Remove boilerplate like EEO etc. Also remove application instructions (none). Remove duplicated lines. We need to preserve all substantive information. So we need to include details: company mission, role ownership, admin tasks, content building, tracking consumption, platform uptime, MCP servers, LLM gateway, model selection, agentic workflows, AI workloads on AWS/GCP, code ownership, instrumentation, data handling, etc. Also qualifications: 5+ years experience, administering enterprise SaaS/AI tenant, working knowledge of LLMs, hands-on MCP, AWS/GCP, GitHub, Python/TS, security fundamentals, communication, nice-to-have items. Education: preferred bachelor degree or relevant experience. Benefits: list items. Pay: salary ranges per tier. Locations: maybe not needed as heading; could be included under About the role or maybe as a separate section? Not in allowed headings; we could include location info in About the role paragraph. But we must not invent sections. Could include location info in a paragraph under About the role. We must not include boilerplate like equal opportunity etc. So strip that. We must not include "Salary varies by role..." generic; but we have specific salary ranges per tier. The generic sentence may be considered boilerplate; we can drop it but keep the ranges. We must not include "Perform related duties as assigned" maybe generic but it's part of responsibilities; keep. We must not include "Nice to have:" list; that's part of qualifications; we can include as part of Qualifications or Skills. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we should make
  . For qualifications list, also
  . For benefits list,
  . For skills maybe also list. We need to use

  for prose. We must not create empty sections. Thus output something like:

  About the role

  Juul Labs' mission ...

  The role involves owning AI platforms end-to-end ...

  Location tiers ...

  Responsibilities

  • Administer our enterprise Claude, Gemini, OpenRouter, Cursor and NotebookLM tenants...
  ...

  Requirements

  • 5+ years in software, cloud, or platform engineering, including recent hands-on work building and running LLM-based systems.
  ...

  Qualifications

  • Preferred: bachelor degree in applicable field or relevant work experience.
  Maybe also Skills section: list technical skills: Python, TypeScript, AWS, GCP, MCP, LLM gateways, etc. Could be under Skills. But we already have qualifications covering many; we could separate Skills as separate heading. We need to avoid duplication. Let's decide: - About the role: company mission + brief role description. - Responsibilities: detailed list from ROLE AND RESPONSIBILITIES. - Requirements: experience requirements from PERSONAL AND PROFESSIONAL QUALIFICATIONS (the bullet points about experience). - Qualifications: education plus nice-to-have? Or maybe Qualifications: education + nice-to-have. - Skills: technical skills list (Python/TS, AWS/GCP, MCP, LLM gateways, GitHub, etc.) - Benefits: perks & benefits. - Pay: salary ranges. We must not include Schedule. Now we need to ensure we preserve all substantive information. Let's extract. Company mission paragraph: "THE COMPANY:Juul Labs's mission is to transition the world’s billion adult smokers away from combustible cigarettes, eliminate their use, and combat underage usage of our products. We have the opportunity to address one of the world’s most intractable challenges through a commitment to exceptional quality, research, design, and innovation. Backed by leading technology investors, we are committed to the same excellence when it comes to hiring great talent.We are a diverse team that is united by this common purpose and we are hiring the world’s best engineers, scientists, designers, product managers, operations experts, and customer service and business professionals. If the opportunity to build your career is compelling, read on for more details." We can condense but must preserve all substantive info; we can keep as prose. Role overview: from "ROLE AND RESPONSIBILITIES: You own these platforms end to end. What you build gets used across the whole company, and you decide how AI runs here rather than inheriting someone else's design." That's part of responsibilities but could be in About the role. Now responsibilities list: many bullet-like sentences separated by periods. We need to turn each into
  • . Let's parse: - Administer our enterprise Claude, Gemini, OpenRouter, Cursor and NotebookLM tenants. User provisioning, groups and roles, workspace configuration, and tenant security settings. - Build and maintain the content that makes those platforms useful: skills, prompts, projects, connectors, and the documentation behind them. - Drive adoption across 250 users and growing. - Track consumption and spend across all three platforms. Report on usage, find idle seats, and support the business-unit chargeback model. - Keep the platforms running. Availability monitoring, feature rollouts, user issue triage, and escalation ownership when something breaks. - Build and operate the MCP servers and gateways that connect these platforms to internal systems, with least-privilege access and full audit logging. - Run the LLM gateway that centralizes routing, authentication, rate limiting, logging, and policy enforcement across model providers. - Choose the right model for each workload, commercial or open-weight, based on cost, latency, capability, and how sensitive the data is. - Build agentic workflows and automations against internal APIs and tools, with the evaluation and guardrails to keep them predictable. - Architect and run AI workloads on AWS and GCP: compute, networking, IAM, secrets management, private connectivity, Bedrock, and Vertex AI. - Own the code in GitHub and write most of it yourself, mostly Python and TypeScript. Branch protection, access control, secret scanning, and Actions pipelines. - Instrument the stack for cost, performance, and security telemetry, and build the reporting that leadership and finance rely on. - Enforce data handling, retention, and access policy alongside Cybersecurity and AI Governance, and write the runbooks and standards behind it. - Perform related duties as assigned, within your scope of practice We'll make each as
  • . Now Requirements: from PERSONAL AND PROFESSIONAL QUALIFICATIONS bullet points (the first set before "Nice to have"). List: - 5+ years in software, cloud, or platform engineering, including recent hands-on work building and running LLM-based systems. - Experience administering an enterprise SaaS or AI tenant at scale: access management, configuration, cost control, and adoption. - Working knowledge of both commercial and open-weight LLMs, including prompt engineering, evaluation, retrieval, and agentic patterns. - Hands-on with Model Context Protocol (MCP), MCP gateways, or LLM gateways. Comparable API integration and middleware experience counts. - AWS and GCP architecture, including IAM, networking, secrets management, and managed AI services. - GitHub and standard engineering discipline: version control, code review, testing, CI/CD, and infrastructure as code. - Strong Python and/or JavaScript/TypeScript for building integrations, automations, and internal tooling. - Security and data governance fundamentals applied to AI work: least privilege, data classification, DLP, and auditability. - Able to explain technical work to executives, finance, and people who do not work in technology. We'll put these under Requirements. Now Qualifications: Education: "Preferred, bachelor degree in applicable field or relevant work experience". Also maybe "Nice to have" list could go under Qualifications or Skills. Let's put under Qualifications: Education plus Nice to have. Nice to have list: - Vertex AI or Amazon Bedrock - self-hosted open-weight model deployment - vector databases and RAG pipelines - Splunk or another SIEM - cloud cost management We'll include as
  • under Qualifications. Now Skills: maybe we can list technical skills not covered elsewhere: Python, TypeScript, AWS, GCP, MCP, LLM gateways, GitHub, etc. But many are already in Requirements. To avoid duplication, maybe we skip Skills section or combine with Requirements. But we need to follow instruction: prefer few substantive sections over many thin ones. Could omit Skills if its content is covered elsewhere. However we need to include all substantive info; if we omit Skills heading, we still have the info in Requirements. That's fine. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: from JUUL LABS PERKS & BENEFITS: - A place to grow your career. We’ll help you set big goals - and exceed them - People. Work with talented, committed and supportive teammates - Equity and performance bonuses. Every employee is a stakeholder in our success - Cell phone subsidy, commuter benefits and discounts on JUUL products - Excellent medical, dental and vision, disability, and life insurance, plus family support, wellness, legal, and employee assistance program benefits - 401(k) plan with company matching - Plus biannual discretionary performance bonuses We'll make each as
  • . Now Pay: Salary ranges per tier. We need to present them maybe as a list. We have: Tier 1 Locations: Greater New York City, and San Francisco Bay Area Tier 1 Range:: $165,000 USD - $206,000 USD Tier 2 Locations: Greater Boston, Washington DC Metropolitan Area, Seattle/Tacoma,Greater Sacramento, Southern California (Los Angeles/OC/San Diego, Riverside and Imperial counties) Tier 2 Range:: $150,000 USD - $187,000 USD Tier 3 Locations: Rest of New England, NY Capital District, Rest of New Jersey, GreaterPhiladelphia, Pittsburgh, Delaware, Rest of Maryland, Rest of Virginia, North Carolina,Atlanta, Miami-Fort Lauderdale-WPB, Chicagoland, Dallas, Houston, Austin,Minneapolis/St. Paul, Colorado, Phoenix, Las Vegas, Reno, Carson City NV., Portland Ore./VancouverWash., Rest of California, Hawaii Tier 3 Range:: $141,000 USD - $176,000 USD Tier 4 Locations: Rest of US including Alaska and Puerto Rico