AI Enablement & Implementation Specialist

We need to output HTML fragment with 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. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove "How to apply" etc. Also remove "What you will receive" maybe that's Benefits? Actually "What you will receive" is benefits. So we need to map content. Let's parse the posting. First line: "Full-time · Remote within the United States · $110,000–$140,000 annual base salary · Occasional travel to New York". That's schedule? Actually schedule: remote, occasional travel. Pay: salary range. So we have Pay and Schedule sections. Then "The opportunity Altitude 7 is a specialist AI consultancy..." That's about the role. Could be About the role. Then "What you will do" bullet list: responsibilities. Then "What we are looking for": qualifications/requirements/skills. Then "What will make you stand out": maybe additional qualifications or skills. Then "What success looks like": maybe expectations, could be responsibilities or qualifications. Then "What you will receive": benefits. Then "How to apply": application instructions -> remove. Then "Selected candidates will complete a live conversation...": also application instructions -> remove. Then "AI tools may help us...": also remove. Then "We provide reasonable accommodations...": EEO -> remove. Then "Altitude 7 is an equal opportunity employer.": remove. We need to preserve all substantive info: so we need to include details about role, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We must not create sections with filler like "commensurate with experience". Not present. We need to decide which sections to include. We have: - About the role: description of Altitude 7 and role. - Responsibilities: bullet list under "What you will do". - Requirements: maybe "What we are looking for" includes requirements. - Qualifications: maybe overlapping with requirements; but we can combine? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple but prefer few substantive sections over many thin ones. So we need to decide which sections have distinct content. We could have: About the role: description. Responsibilities: bullet list. Requirements: combine "What we are looking for" and "What will make you stand out" and "What success looks like" maybe as qualifications/skills. But we need to separate Requirements, Qualifications, Skills if they have distinct content. Let's extract content: "What we are looking for" bullet list: - Demonstrated experience building working AI agents, automations, or LLM-enabled applications—not only completing tutorials. - Practical fluency with Claude Code, Codex, or comparable agent-building tools. - A strong foundation in computer science, software engineering, data science, or equivalent demonstrated technical ability. - Clear, confident written and spoken communication. - The ability to lead a client conversation, listen carefully, think on your feet, and explain technical tradeoffs in plain English. - Strong judgment, curiosity, reliability, and comfort working in a fast-moving environment. - Availability to make Altitude 7 your primary professional commitment and work consistently during US business hours. - Authorization to work in the United States. - Willingness to travel occasionally to New York for client engagements. - Finance, economics, accounting, investment research, or financial-services experience is a meaningful advantage. - You do not need decades of industry experience, but concepts such as earnings reports, sell-side research, investment workflows, risk, and compliance should either be familiar or learnable quickly. That's a mix of requirements and qualifications. "What will make you stand out": - You have built something real and can show us how it works. - You can explain the problem, the architecture, what failed, how you tested it, and what you would change next. - You understand that a useful agent is more than a prompt: it needs permissions, evaluation, monitoring, error handling, and an appropriate human review process. - You may be an experienced practitioner or an unusually capable earlier-career candidate. - Demonstrated ability, learning velocity, communication, and ownership matter more than tenure or pedigree. That's more about desirable traits. "What success looks like" bullet list: - Build and document contained agents with decreasing supervision. - Diagnose failures and make thoughtful reliability improvements. - Create polished demonstrations, implementation materials, and user guides. - Explain Claude and Codex workflows confidently to sophisticated non-technical users. - Support client discovery, training, and straightforward implementations. - Take meaningful ownership of delivery so the founder is not the sole technical translator or client-facing operator. That's expectations for first 90 days, could be considered responsibilities or performance goals. We could treat "What success looks like" as part of Responsibilities or maybe as Qualifications? It's more about early performance expectations. Given instruction to prefer few substantive sections, we could combine Requirements, Qualifications, Skills into one section maybe "Requirements & Qualifications". But headings are predefined; we could still include multiple if they have content. However we must not create sections with filler. If we split, each must have substantive content. We could have: - About the role - Responsibilities (What you will do) - Requirements (What we are looking for) - Qualifications (What will make you stand out + What success looks like) - Benefits (What you will receive) - Pay (salary range) - Schedule (Remote within US, occasional travel to NY) That seems reasonable. Check if any content duplicated: Ensure we don't repeat. Now we need to strip out application instructions etc. Let's craft HTML. We'll use

for each section heading. Inside each section, we will put

for prose,

• for lists. We need to preserve all substantive info: ensure we don't lose any detail. Let's extract the About the role paragraph: "Altitude 7 is a specialist AI consultancy helping hedge funds and investment-management firms turn AI from an experiment into practical systems their teams can use. We are hiring an AI Enablement & Implementation Specialist who can both build and communicate: someone who lives in Claude, Claude Code, Codex, and the rapidly evolving agent ecosystem; can turn an ambiguous business problem into a working system; and can explain that system clearly to investment professionals. This is a hands-on role working directly with Altitude 7's founder. You will contribute to agent development, client discovery, testing, documentation, implementation, and training. The role is remote within the United States, with occasional travel to New York for client delivery." Note: The remote/travel part also appears in schedule; we might not duplicate. But we can keep it in About the role as it's part of description. However schedule section will also mention remote and occasional travel. To avoid duplication, maybe we should not repeat. But instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we remove from About the role, we lose that detail. But we could keep it in About the role and also mention in Schedule? That would be duplication. Better to keep it only in Schedule? But About the role includes other details about role; we could keep the remote/travel in Schedule only and remove from About the role to avoid duplication. However the About the role paragraph currently includes that sentence. If we remove it, we are summarizing away detail (removing). The instruction says do NOT invent or summarize away detail. So we must keep that detail somewhere. We could keep it in About the role and not duplicate in Schedule; but Schedule section needs to convey remote and occasional travel. If we don't include it there, we lose schedule detail. But we could still include schedule details but maybe we can phrase schedule as "Remote within the United States; occasional travel to New York for client delivery." That's same sentence. If we include it in both sections, it's duplication but not summarizing away. Duplication is allowed? The instruction says remove duplicated lines. It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should avoid duplicated lines. So we need to avoid repeating the exact same sentence. We could keep the detail in one place only. Which section is more appropriate? The schedule section is specifically for schedule info; the About the role is more about role description. The remote/travel is schedule info, so better to put it in Schedule and remove from About the role. But then we are removing that sentence from About the role, which is a line. Is that considered summarizing away detail? It's removing a line that is about schedule; but we still preserve the detail in Schedule section. So overall detail is preserved, just relocated. That seems acceptable as we are not summarizing away; we are moving it to appropriate section. The instruction about duplicated lines likely refers to identical lines appearing multiple times in the posting; we can deduplicate by keeping one copy. So we can remove the remote/travel sentence from About the role and keep it in Schedule. Thus About the role paragraph will be: "Altitude 7 is a specialist AI consultancy helping hedge funds and investment-management firms turn AI from an experiment into practical systems their teams can use. We are hiring an AI Enablement & Implementation Specialist who can both build and communicate: someone who lives in Claude, Claude Code, Codex, and the rapidly evolving agent ecosystem; can turn an ambiguous business problem into a working system; and can explain that system clearly to investment professionals. This is a hands-on role working directly with Altitude 7's founder. You will contribute to agent development, client discovery, testing, documentation, implementation, and training." Now Responsibilities: bullet list from "What you will do". Let's extract each bullet: - Build, test, deploy, and maintain practical AI agents and workflow automations. - Translate client workflows into clear technical requirements and implementation plans. - Use language-model APIs, Python, integrations, MCP, retrieval systems, and modern agent frameworks to create reliable solutions. - Evaluate outputs, investigate failures, improve reliability, and document controls and operating procedures. - Prepare and deliver practical training on Claude, ChatGPT, Claude Code, Codex, and agent-based workflows. - Communicate directly with clients, including investment managers and their research, operations, technology, and compliance teams. - Consider security, permissions, monitoring, auditability, compliance, and the blast radius of failures before systems are deployed. - Keep Altitude 7's demonstrations, training, and implementation practices current as the technology changes. We need to keep each as
• . Now Requirements: from "What we are looking for". We'll list each bullet. - Demonstrated experience building working AI agents, automations, or LLM-enabled applications—not only completing tutorials. - Practical fluency with Claude Code, Codex, or comparable agent-building tools. - A strong foundation in computer science, software engineering, data science, or equivalent demonstrated technical ability. - Clear, confident written and spoken communication. - The ability to lead a client conversation, listen carefully, think on your feet, and explain technical tradeoffs in plain English. - Strong judgment, curiosity, reliability, and comfort working in a fast-moving environment. - Availability to make Altitude 7 your primary professional commitment and work consistently during US business hours. - Authorization to work in the United States. - Willingness to travel occasionally to New York for client engagements. - Finance, economics, accounting, investment research, or financial-services experience is a meaningful advantage. - You do not need decades of industry experience, but concepts such as earnings reports, sell-side research, investment workflows, risk, and compliance should either be familiar or learnable quickly. Now Qualifications: from "What will make you stand out" and "What success looks like". We could combine them. Let's list bullets from "What will make you stand out": - You have built something real and can show us how it works. - You can explain the problem, the architecture, what failed, how you tested it, and what you would change next. - You understand that a useful agent is more than a prompt: it needs permissions, evaluation