Principal Architect (Remote)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, scam warning, application instructions. Must preserve all substantive info. We need to parse the posting. First line: "Who You Are" then description of candidate. That seems like "Desired skills and experience" maybe. Then "About The Role" heading. Then responsibilities etc. Then "Desired skills and experience:" list. Then "A Little About Us" (company description). Then "Some of Our Benefits" list. Then NYC Pay Transparency Law salary range. Then EEO etc (remove). Also "Complete ongoing security awareness training..." that's part of responsibilities? It appears under "Other duties as assigned." Actually after "Other duties as assigned." there is "Business Impact & Measurement" then "Leadership Expectations" then "Desired skills and experience:" then "A Little About Us" then "Some of Our Benefits" then salary then EEO. We need to decide sections: About the role (we have that heading). Responsibilities (we have many bullet-like paragraphs under "Other responsibilities include:" and then list of responsibilities). Could combine responsibilities and maybe "Business Impact & Measurement" and "Leadership Expectations" as part of responsibilities or separate sections? The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Qualifications/Skills (maybe combine Desired skills and experience), Benefits, Pay. Schedule not present, so omit. We must not create sections with placeholder text. So we need to ensure each section has substantive content. Let's extract content. About the role: The paragraph after "About The Role" up to before "Other responsibilities include:"? Actually the text: "About The RoleThe Principal Architect is a senior client-facing technology leader responsible for helping Myriad360's clients understand, prioritize, and navigate major technology shifts while connecting those priorities to practical business outcomes. The Principal Architect operates at the intersection of technology strategy, executive advisory, account development, and solution orchestration. This role works closely with Account Executives, Client Solution Architects, Specialists, Practice leaders, Professional Services, Managed Services, and strategic technology partners to deepen executive relationships, shape strategic opportunities, and expand Myriad360's relevance within key accounts. Unlike a CSA, who typically leads broad technical discovery and orchestrates active pursuits, the Principal Architect is focused on executive-level technology strategy, thought leadership, account influence, and long-range opportunity creation. Must be based in the United States." That is the About the role content. Then "Other responsibilities include:" then list of responsibilities broken into subheadings: Executive Client Advisory, Strategic Account Development, Technology Strategy & Thought Leadership, Opportunity Creation & Expansion, Cross-Functional Solution Orchestration, CSA & Sales Enablement, OEM & Ecosystem Engagement, Voice of the Client, Business Impact & Measurement, Leadership Expectations? Actually after Voice of the Client there is "Business Impact & Measurement" then "Leadership Expectations". Then "Desired skills and experience:" list. We could treat all those as responsibilities (including business impact and leadership expectations). Or we could split into Responsibilities and Qualifications. Since we want few sections, maybe: About the role, Responsibilities (covering all duty paragraphs), Qualifications (desired skills and experience), Benefits, Pay. We must not include "A Little About Us" as a section unless we decide to include it as About the company? Not required; we can drop it as boilerplate? It's substantive but not required sections; we could incorporate into About the role? Probably better to omit as not requested heading. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit company description. Benefits: list under "Some of Our Benefits". Include those bullet points. Pay: salary range from NYC Pay Transparency Law: base salary range $250,000-350,000, plus opportunities for profit-sharing bonus and/or commission. Also note compensation in other geographies may vary. We'll include that. Schedule: not present, omit. Now we need to format using

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, desired skills, benefits, pay. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must drop the EEO paragraph at end, also maybe "Complete ongoing security awareness training and comply with company policies to the requirements section. Identify and escalate security risks..." That is part of responsibilities? It appears after "Other duties as assigned." Actually it's a sentence: "Complete ongoing security awareness training and comply with company policies to the requirements section. Identify and escalate security risks to the appropriate Executive Leadership Team member and actively contribute to remediation efforts." This seems like a responsibility (security compliance). We should keep it as part of responsibilities. Also "Other duties as assigned." is a generic phrase; we might keep it? It's not substantive; maybe we can drop as filler? It's a line but not detailed. Might be considered boilerplate; but it's part of responsibilities. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Other duties as assigned." is generic but not necessarily boilerplate; but could be considered filler. I'd keep it as part of responsibilities but maybe we can drop because it's not specific. Safer to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." "Other duties as assigned." is not substantive detail; it's a placeholder. I'd drop it. Now we need to structure responsibilities as a list. The responsibilities have headings like Executive Client Advisory, etc. We could make each a

• with subheadings? But we need to use
  • for any list of duties/requirements/benefits. So we can make a
    where each
    • contains a heading (maybe ) and then description. That's acceptable. We must not invent headings like

      etc. Only

      for section headings. Inside

      we can use plain text or . Let's extract each responsibility block: 1. Executive Client Advisory - Serve as a trusted technology advisor to CIOs, CTOs, CISOs, infrastructure leaders, and other senior client stakeholders. - Lead executive-level conversations around technology strategy, transformation priorities, risk, modernization, and emerging technology. - Help clients translate complex technology shifts into practical business decisions. - Facilitate executive workshops, strategy sessions, roadmap discussions, and innovation briefings. - Build long-term relationships that extend beyond individual products, projects, or vendors. 2. Strategic Account Development - Partner with Account Executives and CSAs to identify where executive engagement can materially expand the client relationship. - Support strategic account planning by helping identify technology priorities, executive initiatives, transformation programs, organizational challenges, competitive threats, technical debt, and whitespace opportunities. - Help move client conversations from tactical purchases toward multi-year strategic relationships. - Create new opportunities by introducing ideas, perspectives, and solutions the client may not yet be considering. 3. Technology Strategy & Thought Leadership - Maintain strong awareness of major enterprise technology trends and translate them into relevant client conversations. - Provide thought leadership across Enterprise AI, AI infrastructure, RAG and agentic AI, data center modernization, networking, cybersecurity, hybrid cloud, automation and observability, platform engineering, Managed Services, Enterprise Service Management, and operating-model transformation. - Develop clear points of view on where technologies are headed and how they may affect client strategy. - Represent Myriad360 in executive briefings, client events, industry panels, technology summits, webinars, and partner engagements. 4. Opportunity Creation & Expansion - Help identify strategic opportunities before they become formal projects or RFPs. - Partner with Sales and CSA leadership to turn executive conversations into actionable opportunities. - Connect strategic client initiatives to Myriad360 capabilities across advisory, infrastructure, security, cloud, AI, Professional Services, Managed Services, and Field Services. - Help broaden opportunities beyond an initial technology request by considering the complete client lifecycle. 5. Cross-Functional Solution Orchestration - Work closely with CSAs to ensure executive strategy translates into technical discovery and execution. - Bring together appropriate Specialists, Practice leaders, Professional Services, Managed Services, and partners for strategic opportunities. - Avoid becoming the technical owner for every pursuit; instead, help ensure the right expertise is engaged. - Support complex, multi-practice opportunities where executive context and technical strategy are critical to success. 6. CSA & Sales Enablement - Help CSAs and Sales teams elevate client conversations beyond products and features. - Coach teams on executive communication, technology storytelling, business outcome alignment, strategic discovery, opportunity creation, whiteboarding, and workshop facilitation. - Share repeatable client insights, market trends, and strategic plays across the organization. - Help build confidence among technical teams in engaging senior client executives. 7. OEM & Ecosystem Engagement - Build strong relationships with CTOs, Chief Architects, Field CTOs, and technical executives across strategic OEM partners. - Bring OEM insights, roadmaps, and innovation into relevant client conversations. - Help identify where Myriad360 can create differentiated joint solutions with strategic partners. - Participate in executive briefings and joint account strategy where appropriate. 8. Voice of the Client - Bring market and client feedback back into Myriad360 leadership. - Identify recurring client challenges, emerging needs, and gaps in Myriad360's capabilities. - Help influence service development, practice strategy, technology investment, partner strategy, enablement priorities, and the Managed Services roadmap. - Provide leadership with a practical field perspective on where client demand is moving. - Complete ongoing security awareness training and comply with company policies to the requirements section. Identify and escalate security risks to the appropriate Executive Leadership Team member and actively contribute to remediation efforts. 9. Business Impact & Measurement - The Principal Architect should have meaningful business accountability without becoming a traditional quota-carrying overlay. - Success should be measured through strategic influence and the business outcomes created from executive engagement. - Executive client relationships created or expanded - Strategic account engagement - Executive workshops and advisory sessions - Opportunities proactively created - Influenced pipeline - Opportunity expansion - Cross-practice opportunity creation - Professional Services and Managed Services attach - Strategic account penetration - Executive sponsorship within major accounts - Client retention and expansion - OEM executive relationships - Thought leadership contributions - Client feedback and market intelligence - Enablement and coaching impact across Sales and CSA teams Note: Some of those are phrases without verbs; they are bullet points under Business Impact & Measurement. We'll keep them as list items. 10. Leadership Expectations - Operate comfortably with CIO, CTO, CISO, and senior technology executives. - Communicate complex technology in clear business language. - Build trust without relying on a sales pitch. - Be intellectually curious across multiple technology domains. - Have enough technical depth to establish credibility while knowing when to bring in deeper expertise. - Ask strong questions and listen before prescribing solutions. - Lead with empathy and seek to understand the client's business and operating environment. - Think across organizational silos and technology practices. - Connect strategy to execution. - Create opportunities rather than wait for them. - Influence without formal authority. - Represent Myriad360 with credibility internally, externally, and across the partner ecosystem. - Model a One Team mindset across Sales, Pre-Sales, Services, PMO, Delivery, and the broader Myriad360 / Advizex organization. Now Desired skills and experience list: - 15+ years of experience in enterprise technology, consulting, solution architecture, technology strategy, systems integration, or related roles