Lighthouse Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes "Job Description" then description. We need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, immigration sponsorship, etc. Also remove navigation/legal etc. Must preserve all substantive info. We need to parse content: - Intro: "We are Omnissa! ..." This is about company. Could be "About the role"? Actually "About the role" heading maybe for description of role. The intro includes company description and "What is the opportunity?" then description of Lighthouse Architect. So we could put that under

About the role

with paragraphs. - Responsibilities: The "Key Responsibilities" section with sub-bullets. We need to output

• for each duty. Probably each bullet point under subheadings? The content includes subheadings like Customer Engagement & Advisory, Solution Architecture & Technical Leadership, Delivery & Execution Support, Customer Success, Adoption & Value Realization, Internal Collaboration & Enablement. Those are subheadings but we are not required to output subheadings; we can just list responsibilities as list items. However we need to preserve all substantive info; we could keep subheadings as inside li? But spec says use
  • for any list of duties/requirements/benefits, and

    for prose. It doesn't forbid other tags inside li. We could include subheadings as inside li. That seems okay. - Requirements/Qualifications/Skills: The "What will you bring to Omnissa?" section lists experience etc. Also "Preferred Qualifications". Also "Success in This Role Looks Like" maybe could be under Qualifications? But we need sections: Requirements, Qualifications, Skills. We need to decide where to put each piece. We have: - 8+ years of experience in technical consulting, solution architecture, or enterprise IT roles. - Strong background in designing and supporting complex enterprise solutions. - Experience working directly with customers in advisory or pre/post-sales technical roles. - Ability to explain complex technical concepts to both technical and non-technical audiences. - Proven ability to operate independently with executive-level customers. - Strong problem-solving, communication, and relationship management skills. These could be Requirements or Qualifications. Then "Preferred Qualifications": list: - Experience supporting large, complex enterprise accounts. - Familiarity with modern enterprise architectures (cloud, identity, security, endpoint, virtualization, integrations, etc.). - Experience influencing technical decisions without direct authority. - Prior experience in Customer Success, Architecture, or Professional Services organizations. Also "Success in This Role Looks Like" is more about outcomes; could be under Qualifications or maybe separate but we don't have a heading for that. Could be placed under Qualifications as well. We also have Benefits: "In addition to competitive compensation, Omnissa offers a variety of benefits such as employee ownership, health insurance, 401k with matching contributions, disability insurance, paid-time off, growth opportunities, and more." Pay: "Compensation: The typical base salary for this role is between USD $159,412 - 332,125 per year and it may be eligible for participation in a corporate bonus program. Actual compensation offer may vary from posted hiring range based upon geographic location, work experience, education, skill level, or other relevant factors." Schedule: Not mentioned. Location: USA, Location Type: Remote, Travel Expectations: None. That could be considered Schedule? Not exactly. There's no schedule info like full-time, part-time, hours. So we should not create Schedule section because no specific content. We should not create Benefits section unless posting actually states them. It does state benefits list, so we include Benefits. We should not create Pay section unless posting actually states them. It does state compensation range, so include Pay. We should not create Schedule section because no schedule info. We need to avoid boilerplate: EEO, immigration sponsorship, etc. Remove those paragraphs. We need to preserve all substantive info: company description, role description, responsibilities, qualifications, preferred qualifications, success criteria, location, travel expectations, compensation, benefits. We need to output only HTML fragment, no /, no markdown. Let's structure:

    About the role

    We are Omnissa! Omnissa is the first AI-driven digital work platform, built to support flexible, secure, work-from anywhere experiences. We integrate industry-leading solutions—including Unified Endpoint Management, Virtual Apps and Desktops, Digital Employee Experience, and Security & Compliance—into a seamless, autonomous workspace that adapts to how people work. Our platform boosts employee engagement while optimizing IT operations, security, and cost. Guided by our Core Values—Act in Alignment, Build Trust, Foster Inclusiveness, Drive Efficiency, and Maximize Customer Value—we’re growing rapidly and committed to delivering meaningful impact. If you're passionate about shaping the future of work, we’d love to hear from you.

    The Lighthouse Architect is a senior, customer-facing technical advisor responsible for helping enterprise customers design, implement, and operationalize solutions that drive long-term success and value realization. Acting as a trusted partner, the Lighthouse Architect bridges business objectives and technical execution, providing architectural guidance, risk mitigation, and ongoing optimization throughout the customer lifecycle. This role is hands-on, consultative, and highly collaborative—working closely with customers, internal product and engineering teams, sales, and delivery partners to ensure successful outcomes and sustained customer confidence.

    Then Responsibilities:

    Responsibilities

    • Customer Engagement & Advisory: Serve as a trusted technical advisor for assigned strategic customers. Understand customer business goals, technical environments, and success criteria. Translate customer requirements into practical, scalable architecture recommendations. Build long-term relationships with customer technical and business stakeholders. Partner with account teams to align technical strategy to renewal, adoption, and expansion goals—maintaining a strong value narrative with customer leaders.
    • Solution Architecture & Technical Leadership: Design, validate, and evolve solution architectures aligned to best practices and customer objectives. Lead technical discovery, architecture reviews, and design workshops. Provide guidance on deployment models, integrations, scalability, performance, and security. Identify technical risks early and drive mitigation strategies.
    • Delivery & Execution Support: Partner with implementation teams, partners, and customer resources during onboarding and major initiatives. Provide oversight and technical direction without necessarily owning day-to-day project management. Support complex troubleshooting and act as an escalation point for architectural issues. Validate solutions against desired outcomes and architectural intent.
    • Customer Success, Adoption & Value Realization: Proactively drive customer outcomes by increasing adoption and effective usage of current entitlements, ensuring customers realize measurable value from the solutions they already own. Identify and remove adoption or consumption blockers (process, technical, or organizational), partnering with customer stakeholders and internal teams to accelerate progress. Translate customer objectives into a practical adoption roadmap (milestones, success criteria, operational readiness) that supports renewal health and long-term stickiness. Spot and qualify expansion opportunities by connecting customer initiatives and emerging use cases to additional solution capabilities, and coordinate with account teams to pursue growth paths responsibly.
    • Internal Collaboration & Enablement: Collaborate with Sales, Customer Success, Product, Support, and Engineering teams. Provide customer feedback to influence product direction and roadmap alignment. Share patterns, lessons learned, and best practices across the Lighthouse team. Contribute to internal documentation, enablement content, and architectural standards.
    Then Requirements/Qualifications/Skills. We need to decide headings. Could combine Requirements and Qualifications? But spec says use headings for those categories if content exists. We have both required and preferred qualifications. We could make:

    Requirements

    • 8+ years of experience in technical consulting, solution architecture, or enterprise IT roles.
    • Strong background in designing and supporting complex enterprise solutions.
    • Experience working directly with customers in advisory or pre/post-sales technical roles.
    • Ability to explain complex technical concepts to both technical and non-technical audiences.
    • Proven ability to operate independently with executive-level customers.
    • Strong problem-solving, communication, and relationship management skills.

    Preferred Qualifications

    • Experience supporting large, complex enterprise accounts.
    • Familiarity with modern enterprise architectures (cloud, identity, security, endpoint, virtualization, integrations, etc.).
    • Experience influencing technical decisions without direct authority.
    • Prior experience in Customer Success, Architecture, or Professional Services organizations.
    We could also include "Success in This Role Looks Like" maybe under Qualifications or as a separate section? There's no heading for that but we could treat as Qualifications? It's more about outcomes; maybe we could add a

    Success Indicators

    but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. "Success in This Role Looks Like" could go under Qualifications (maybe as part of Qualifications). Or we could add a

    Qualifications

    and include both required and preferred plus success indicators. But we already used Requirements and Preferred Qualifications headings. The spec says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. It also says "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one

    Qualifications

    and include both required and preferred plus success indicators. But we also have Skills maybe separate. However the "What will you bring to Omnissa?" includes skills like problem-solving, communication, relationship management. Those could be Skills. Thus we could have:

    Requirements

    for the mandatory experience items.

    Skills

    for abilities like explaining concepts, problem-solving, communication, relationship management.

    Qualifications

    for preferred qualifications and success indicators. But we need to avoid too many thin sections. Maybe better:

    Requirements

    for mandatory experience;

    Qualifications

    for preferred qualifications and success indicators;

    Skills

    for abilities. Let's decide. We have mandatory experience items (8+ years, strong background, experience working directly with customers). Those are requirements. Skills: Ability to explain complex technical concepts, proven ability to operate independently with executive-level customers, strong problem-solving, communication, relationship management skills. Preferred qualifications: experience supporting large accounts, familiarity with modern enterprise architectures, experience influencing technical decisions without direct authority, prior experience in Customer Success, Architecture, or Professional Services organizations. Success in This Role Looks Like: could be placed under Qualifications as well (maybe as a paragraph). But we could also add a

    under Qualifications. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Qualifications, Benefits, Pay. We must not create Schedule. Now ensure we preserve location and travel expectations. Where to put? Could be under About the role as a paragraph? Or maybe under Qualifications? Not really. Could add a short

    after About the role: "Location: USA (Remote). Travel Expectations: None." That is substantive info. We'll include that as a paragraph under About the role or separate? Probably after the role description