AI-Consultant / Architect

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Include only sections with real content. We have job summary, responsibilities, requirements, what we offer (benefits, pay). Also travel up to 30% maybe schedule? Travel is not schedule but could be under Schedule? Probably not. Pay: target compensation $250K-280K USD. Benefits: list of benefits. Also maybe "Organizational Alignment" not needed. "Success Criteria" maybe not needed. "What we offer" includes benefits and pay. We'll create sections: About the role (maybe from Job Summary). Responsibilities (Role & Responsibilities). Requirements (Job Requirements). Benefits (What we offer benefits list). Pay (Target compensation). Possibly Schedule: travel up to 30% could be considered schedule? But schedule usually about work hours, remote, etc. There's mention remote-friendly organization, but not explicit schedule. Might not include Schedule if not explicit. We'll include Travel under Responsibilities maybe as a bullet. But we can also add a Schedule section with travel up to 30% and remote-friendly. However instruction: only include section if posting has real specific content. Travel is mentioned under Responsibilities: "Travel up to 30% to support customer engagements". That's a responsibility, not schedule. Remote-friendly organization is under What we offer? Actually it's in What we offer list: "A remote-friendly organization, with colleagues working remotely either part or full-time". That's a benefit/condition. Could be under Benefits or maybe under Schedule? Probably better to put under Benefits as a bullet. We'll keep Benefits section includes list of benefits including remote-friendly, parking, etc. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract. Job Summary paragraph: "The AI Consultant / Architect is the senior technical authority within SoftwareOne’s AI advisory practice in North America. This role is responsible for translating AI ambition into production-grade, governed, and commercially viable architectures that can be successfully delivered at scale. The role defines end-to-end AI solution architecture across generative AI, agentic systems, and traditional ML, ensuring technical feasibility, cost awareness, governance, and delivery readiness. It acts as the key technical advisor to customer technology leadership, shaping solution design decisions and ensuring that architectures are defensible, scalable, and aligned with enterprise standards. In addition to delivery-focused architecture work, this role helps define reference architectures, technical standards, and reusable patterns that guide the evolution of the AI advisory practice. SoftwareOne is an AI‑forward company. We actively use AI across our business to improve productivity, decision‑making, and outcomes - and we are intentional about hiring people who are curious, hands-on, actively apply AI, and lead by example as technology continues to evolve." That's About the role. Responsibilities bullet list: from "Role & Responsibilities". We'll list each bullet. - Own end-to-end solution architecture for AI engagements spanning deterministic automation, traditional ML, and generative / agentic AI. - Design for the full lifecycle — data pipelines, model selection, integration, orchestration, evaluation, and monitoring. - Make and document the build-vs-buy and model-selection decisions, with the trade-offs made explicit for the customer. - Lead AI strategy, readiness, and use-case discovery workshops with customer business and technology leadership. - Produce architecture blueprints, roadmaps, and business cases that connect technical design to measurable business outcomes. - Give account and delivery teams a credible technical narrative that supports pipeline and protects delivery. - Embed AI governance and risk management into every design — aligned to NIST AI RMF, the EU AI Act, and SR 11-7 where applicable. - Account for cloud and inference economics (FinOps) so solutions are affordable to run, not just to build. - Assess and communicate blast-radius risk, data exposure, and model failure modes before they reach production. - Mentor consultants and solution engineers, raising the technical bar across the practice. - Capture patterns and lessons from each engagement so the practice compounds its expertise over time. - Travel up to 30% to support customer engagements, workshops, and architecture advisory sessions. Requirements bullet list: from "Job Requirements". We'll list. - Demonstrated experience using AI in a practical, applied way — such as improving workflows, automating tasks, enabling better decision‑making, or increasing impact in prior roles. (Note: does not require deep technical expertise) - Proven experience architecting and delivering AI / ML solutions in enterprise or services environments. - Deep, hands-on knowledge of generative AI — LLMs, RAG, agentic systems — alongside traditional ML and data engineering. - Strong cloud architecture skills across at least one major hyperscaler (Azure, AWS, or GCP). - Working fluency in AI governance and risk frameworks (NIST AI RMF, EU AI Act, SR 11-7) and in cloud cost / FinOps dynamics. - Excellent communication and influencing skills; able to move between a boardroom and a build session. - Entrepreneurial, accountable, and client-driven. - Aligned to SoftwareOne’s IMPACT values. Benefits list: from "What we offer". We'll extract bullet points. - Generous pay with bonus structure (quarterly or bi-annual depending on the role) - Independent environment without a lot of red tape where you are empowered to make decisions - Substantial benefits package that includes: - Full suite of medical coverage with A+ carriers, Dental, and Vision with strong employer contributions plus additional voluntary coverage available for Pets, Identity Theft Protection, Accident & Critical Illness - 401k program with employer matching 50% up to the first 10% of employee’s contributions - Wellness plan that includes credits to premiums and employer contributions towards the savings plan of your choice - Access to EAP and concierge services plus pre-paid legal at no cost - Abundant time off that includes paid holidays, floating holidays, your birthday off, a volunteer day, and discretionary time off (DTO) - Employee stock purchase plan - Learning and development opportunities galore, tuition reimbursement, and much more! - Specific to Nashville and Milwaukee-based office employees: company-paid parking - Winning culture, inclusive environment, and friendly people all over the world - A remote-friendly organization, with colleagues working remotely either part or full-time Pay: "Target compensation for this role will be $250K - 280K USD (mix of base salary and bonus). Actual offers may be higher or lower than this range and will be determined based on a variety of factors, including (but not limited to) candidates’ qualifications, experience, education, and work location." We'll put that under Pay section. We should not include "Job Summary" heading; we used About the role. We must not repeat job title as heading. Good. We must not include Job ID etc. We must not include boilerplate like "The preceding job profile has been designed..." etc. Remove that. Also remove "Success Criteria", "Organizational Alignment". Remove "Company description" maybe? It's substantive but not under headings we have; we could include as About the company? Not requested headings. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says prefer few substantive sections. Could include "Company description" but not in list. Safer to omit. We must output only HTML fragment. Let's craft. Structure:

About the role

...summary...

Responsibilities

• ...
...

Requirements

...

Benefits

...

Pay

Target compensation for this role will be $250K - 280K USD (mix of base salary and bonus). Actual offers may be higher or lower than this range and will be determined based on a variety of factors, including (but not limited to) candidates’ qualifications, experience, education, and work location.

We might also include Schedule? Not needed. Make sure to preserve all substantive info: we included travel under responsibilities, remote-friendly under benefits, company-paid parking under benefits, etc. Check we didn't miss any substantive info: "Independent environment without a lot of red tape where you are empowered to make decisions" is under benefits (we included as bullet). "Winning culture, inclusive environment, and friendly people all over the world" included. "Learning and development opportunities galore, tuition reimbursement, and much more!" included. We omitted "Generous pay with bonus structure (quarterly or bi-annual depending on the role)" because we have Pay section; but we could also include that under Benefits as bullet? But we already have Pay section covering compensation; we could still include that bullet under Benefits as part of benefits package. However to avoid duplication, we could keep it under Benefits as bullet about bonus structure. But Pay section already mentions target compensation; we could keep both. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that bullet about generous pay with bonus structure. However we also have Pay section with target compensation. It's okay to have both; they are not duplicate but complementary. We'll include bullet under Benefits: "Generous pay with bonus structure (quarterly or bi-annual depending on the role)". And Pay section will give the range. Check we didn't miss "Substantial benefits package that includes:" we already have bullet list. Now ensure we didn't include any boilerplate like "We are not able to consider candidates residing in the state of Hawaii currently." That's substantive? It's a restriction; should we include? It's a requirement/location restriction. It's substantive. Should we include under Requirements maybe as a note. The instruction: preserve ALL substantive information. So we need to include that. Where to put? Could be under Requirements as a bullet: "We are not able to consider candidates residing in the state of Hawaii currently." Or under About the role? Probably under Requirements as a note. Also "Company description" maybe substantive but not under headings; we could omit as not requested but it's substantive. However instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid adding extra sections not in list, but we should avoid thin sections. Company description is a paragraph; we could add an "About the company" section with h3? Not in list but could be okay. However they gave examples of headings; they didn't say you cannot use others, but they said use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings for sections; but we could also add other headings if needed. Safer to stick to those headings. So we may drop company description. But we must preserve ALL substantive information; dropping company description would lose info. However maybe they consider company description not essential for the job posting? It's still substantive. But the instruction says "Prefer a few substantive sections over many thin ones." Could we incorporate company description into About the role? It's about the company, not the role. Could add a paragraph after About the role? Might be okay to add a separate

after About the role before Responsibilities? That would be extra content not under a heading, but still preserved. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs outside headings. So we can keep a paragraph about company after About the role without a heading. That preserves info. Thus we will keep About the role paragraph (job summary). Then maybe a paragraph about company description (the paragraph after "Job Summary" maybe not needed). Actually the company description