Enterprise Solutions Architect

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - About Artos: description. That's like "About the role"? Actually "About Artos" is company description. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description about Artos and the role? The "About Artos" is company overview. Could fit under "About the role". We'll include that. - The Role: description of role. Could be part of responsibilities? Actually "The Role" is overview. Could be part of "About the role". We'll combine. - What You'll Do: list of duties. That's responsibilities. - What We're Looking For: list of requirements (10+ years experience etc). That's qualifications/requirements. - Nice to Have: could be skills or qualifications? Could be "Skills" or "Qualifications". We'll treat as "Skills" maybe. - Other Information: includes work environment, in-person, likes matcha KitKats etc. That's not really benefits/pay/schedule. Could be "Benefits"? Not really. It's more like "Other". Might be omitted if not fitting categories. The instruction: include a section ONLY when posting has real, specific content for it. So we need to see if there is content for Benefits, Pay, Schedule. There's none. So we omit those sections. We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we must avoid duplication. The categories overlap. We need to decide which sections to include based on content. We have: - About the role/company: we have description. - Responsibilities: "What You'll Do" bullet points. - Requirements: "What We're Looking For" bullet points (10+ years experience etc). That's qualifications. - Nice to Have: could be "Skills" or "Qualifications". Could be separate "Skills" section. We could combine Requirements and Qualifications into one? But instruction says we can have multiple sections; we should prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section called "Requirements". And Nice to Have could be "Preferred Qualifications" but we don't have that heading. Could put under "Skills". But we have limited headings list; we can use Skills for nice-to-have. Thus sections:

About the role

: include About Artos and The Role description.

Responsibilities

: list from What You'll Do.

Requirements

: list from What We're Looking For (mandatory).

Skills

: list from Nice to Have. We must not include Benefits, Pay, Schedule. We need to format lists with

• . For prose, use

  . We must preserve all substantive information, not invent or summarize away detail. So we need to keep each bullet exactly as in text, maybe rephrase? Must not invent or summarize away detail. So we should copy the bullet points verbatim (or close). Ensure we don't lose any detail. Let's extract bullets. From "What You'll Do:": - Own Customer Technical Relationships - Serve as the primary technical partner for our largest enterprise customers. - Build trusted relationships with IT, architecture, security, infrastructure, and business leaders. - Lead technical discovery, architecture reviews, and planning discussions. - Understand customer systems and how Artos fits within their broader technology ecosystem. - Architect & Expand Solutions - Design approaches for integrating and deploying Artos in complex enterprise environments. - Advise customers on system architecture, APIs, authentication, networking, data flows, and integrations. - Identify new technical use cases and opportunities to expand Artos across customer organizations. - Partner with Engineering and Product to turn customer needs into technical solutions. - Lead Customer Initiatives - Own technical coordination of deployments, integrations, upgrades, and new initiatives. - Manage customer commitments, timelines, dependencies, SLAs, and technical requirements. - Coordinate validation, documentation, and compliance activities - Identify blockers and bring in the right internal experts to resolve them. - Help Build the Function - Develop repeatable approaches for enterprise deployments and technical customer engagement. - Help define how Solutions Architecture scales as Artos grows. - Potentially help build and lead a broader Solutions Architecture team over time. We need to preserve all. Could flatten into a single list? But better to keep sub-bullets? The instruction: use

  • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep simple list items each line. Could combine main headings as part of li text. We'll produce each bullet as
  • with the text. We must not lose any detail: include all sub-bullets. Now "What We're Looking For:" bullets: - 10+ years of experience in Solutions Architecture, Enterprise Architecture, Customer Engineering, or similar roles. - Experience working with complex enterprise software environments - Strong understanding of system architecture, APIs, authentication, networking, integrations, and distributed systems. - Experience owning technical relationships with large enterprise customers. - Ability to work effectively with everyone from engineers to executive stakeholders. - Experience supporting both pre-sales technical conversations and post-sale deployments. - Comfortable operating in a startup environment where processes are still being built. Now "Nice to Have:" bullets: - Pharmaceutical or life sciences experience. - GxP or similar regulated/compliance experience. - Startup or small-company experience. - Previous software engineering or hands-on technical background. - Experience building or leading Solutions Architecture or Solutions Engineering teams. Now "Other Information:" includes: - Very comfortable working in a fast-paced and intense startup environment - Willing to work in-person in our office in Mission Bay 4-5 days/week - Likes matcha KitKats, believes every LLM prompt is just Schrödinger’s cat waiting to be observed, and knows too many random facts about the Mongol postal system This is not benefits/pay/schedule. Could be considered "Other" but we don't have a heading for that. Could we put under "Skills"? Not really. Could we create a section "Additional Information"? Not in allowed headings. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those categories. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't explicitly forbid other headings, but we should stick to those given. The "Other Information" doesn't fit any of those categories. Could we incorporate into "About the role" or "Skills"? The first two bullets about environment and in-person could be considered "Schedule"? Actually schedule: in-person 4-5 days/week is schedule info. That could go under Schedule heading. The instruction: include Schedule section only if posting actually states them. It does state "Willing to work in-person in our office in Mission Bay 4-5 days/week". That's schedule info. So we can create a Schedule section with that bullet. The other bullet about "Very comfortable working in a fast-paced and intense startup environment" could be part of Requirements or Skills? Could be part of Requirements (comfortable operating in startup environment already listed). It's similar. The last bullet about likes matcha KitKats etc is fun fact, not relevant to job; could be omitted as boilerplate? It's not cookie/navigation/legal/EEO etc. It's personal fun facts. Might be considered irrelevant but not boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's just fun personal info. Should we keep? It's substantive information about the candidate's preferences? It's not a job requirement. It's more like "Other Information". Could be considered not needed. But we could include under "Skills"? Not really. Might be considered filler. I'd lean to omit it as it's not relevant to job. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive? It's about the candidate's personal likes, not job-related. Might be considered not substantive for the job. But it's still in posting. Hard to decide. I'd keep it maybe under a section "Additional Information" but not allowed. Could we put under "About the role" as a fun note? Might be weird. Better to follow instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The fun fact is specific content, not filler. So we need a section for it. But we don't have a heading for fun facts. Could we use "Skills"? Not appropriate. Could we use "Qualifications"? Not appropriate. Could we use "Requirements"? Not appropriate. Could we use "Benefits"? Not appropriate. Could we use "Pay"? Not appropriate. Could we use "Schedule"? Not appropriate. Thus maybe we should not create a section for it, and instead drop it as it's not fitting any allowed heading and might be considered filler? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove fun facts. But also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we cannot map to allowed headings, maybe we should omit it because we cannot create a heading not in the list? The instruction didn't forbid other headings, but gave examples. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we could create other headings if needed. But to be safe, we could create a heading "Other Information" and include those bullets. However, the instruction says "include a section ONLY when the posting has real, specific content for it". That would be satisfied. So we can add

    Other Information

    with list. But the examples didn't include Other Information, but it's not prohibited. I'd go ahead and add Other Information section to preserve that content. Thus sections: About the role, Responsibilities, Requirements, Skills, Schedule, Other Information. But we already have Requirements (mandatory) and Skills (nice-to-have). We also have Schedule from the in-person bullet. We also have Other Information for the fun fact and maybe the fast-paced environment bullet (though that is similar to requirement). We could incorporate fast-paced environment into Requirements (already there). So we can drop that duplicate. Let's extract schedule bullet: "Willing to work in-person in our office in Mission Bay 4-5 days/week". That's schedule. Now Other Information: "Likes matcha KitKats, believes every LLM prompt is just Schrödinger’s cat waiting to be observed, and knows too many random facts about the Mongol postal system". Also maybe "Very comfortable working in a fast-paced and intense startup environment" but we already have similar in Requirements. We'll keep only the fun fact. Now we need to ensure we don't duplicate content. Let's craft HTML. We'll start with

    About the role

    ... combine About Artos and The Role description.

    About Artos: "At Artos