Enterprise AI Systems Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: THE COMPANY, ROLE AND RESPONSIBILITIES, PERSONAL AND PROFESSIONAL QUALIFICATIONS, EDUCATION, JUUL LABS PERKS & BENEFITS, SALARY RANGES, LOCATIONS. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt headings to match content: maybe "About the company", "Responsibilities", "Qualifications", "Education", "Benefits", "Pay", "Location". However instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. We need to include a section only when posting has real, specific content for it. So we need to map. - About the role: Could be THE COMPANY description? Actually "About the role" maybe corresponds to THE COMPANY? But we have "THE COMPANY" describing mission. Could treat as About the role? Might be better to use "About the company" but instruction says use those examples; we can still use "About the role" as heading for company overview. It's okay. - Responsibilities: from ROLE AND RESPONSIBILITIES. - Requirements/Qualifications: from PERSONAL AND PROFESSIONAL QUALIFICATIONS (maybe combine). Could have both Requirements and Qualifications sections. But we should avoid thin sections. Could combine into Qualifications. - Skills: maybe from qualifications list? Could be separate but we can embed. - Benefits: from JUUL LABS PERKS & BENEFITS. - Pay: from SALARY RANGES. - Schedule: not present, so omit. - Location: from LOCATIONS (maybe not in list but we can add as separate heading? Not in examples but we could still include? The instruction says use those headings as examples, but we can add others if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could include Location as a heading maybe not in list but still okay. However they said "include a section ONLY when the posting has real, specific content for it". So we can include Location. We must not repeat job title as heading (not present). Do not put Job ID etc. Remove boilerplate: EEO etc. Remove duplicated lines. Remove application instructions (none). Remove cookie/navigation/legal etc. We need to preserve all substantive information. Let's extract content. THE COMPANY paragraph: "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'll keep that. ROLE AND RESPONSIBILITIES: long bullet-like sentences. We need to convert to

• for any list of duties/requirements/benefits. So we should split each duty into list items. Let's parse responsibilities sentences: - 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. - 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 bullet a
• . PERSONAL AND PROFESSIONAL QUALIFICATIONS: list of qualifications. - 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. - Nice to have: Vertex AI or Amazon Bedrock, self-hosted open-weight model deployment, vector databases and RAG pipelines, Splunk or another SIEM, and cloud cost management. We'll make each bullet a
• . The "Nice to have:" could be a separate subsection maybe but we can keep as list item. EDUCATION: "Preferred, bachelor degree in applicable field or relevant work experience". We'll make a

  . JUUL LABS PERKS & BENEFITS: list. - 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 bullet a

• . SALARY RANGES: includes text and ranges. We need to preserve all substantive information. The paragraph: "Salary varies by role, level and location, and is dependent on the cost of labor in a given geographic region among other factors. These ranges may be modified at any time." Then locations and tiers with ranges. We'll present maybe a

  for the intro, then a

  for each tier? Could be a list. LOCATIONS: list of tiers with locations and ranges. We need to preserve all. We'll output maybe a

  Pay and include the salary details. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits. We should not create Schedule. Now produce HTML fragment. We'll start with

  About the role

  then

  THE COMPANY content

  . Then

  Responsibilities

  with li. Then

  Qualifications

  with li (including nice to have maybe as separate li). Then

  Education

  Preferred, bachelor degree in applicable field or relevant work experience

  . Then

  Benefits

  with li. Then

  Pay

  Salary varies by role, level and location, and is dependent on the cost of labor in a given geographic region among other factors. These ranges may be modified at any time.

  then maybe
  for tiers. We need to include locations and ranges. Could be under Pay or separate Location section. Since we have location details, we could add

  Location

  with list. But instruction examples didn't include Location but we can still include. It's not prohibited. We'll include. Thus:

  Location

  with li for each tier. We need to preserve all location text. Let's extract location details: "LOCATIONS:Tier 1 Locations: Greater New York City, and San Francisco Bay AreaTier 2 Locations: Greater Boston, Washington DC Metropolitan Area, Seattle/Tacoma,Greater Sacramento, Southern California (Los Angeles/OC/San Diego, Riverside and Imperial counties)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, HawaiiTier 4 Locations: Rest of US including Alaska and Puerto RicoTier 1 Range:: $165,000 USD - $206,000 USDTier 2 Range:: $150,000 USD - $187,000 USDTier 3 Range:: $141,000 USD - $176,000 USDTier 4 Range:: $126,000 USD - $157,000 USD" We need to format nicely. We'll create list items: - Tier 1 Locations: Greater New York City, and San Francisco Bay Area – Range: $165,000 – $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) – Range: $150,000 – $187,000 USD - Tier 3 Locations: Rest of New England, NY Capital District, Rest of New Jersey, Greater Philadelphia, 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./Vancouver Wash., Rest of California, Hawaii – Range: $141,000 – $