Vice President of Engineering, Architecture

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 as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - Intro about CreatorIQ (company description) maybe belongs in About the role? Actually "About the role" could be description of role. The posting includes: "Vice President of Engineering, Architecture This is a hands-on executive leadership role..." So we can put that under About the role. - Responsibilities: bullet list under "In this role, you’ll get to:" with subheadings: Technology Strategy & Execution, Platform & Infrastructure Consolidation, Leadership & Cultural Impact. Each has bullet points. - Requirements/Qualifications: "Who you are and what you’ll need for this position:" list of criteria. - Skills: maybe part of requirements? Could separate but we can include under Skills if there are specific skills listed: e.g., expertise in distributed systems, cloud-native, etc. But we can combine. - Benefits: "Compensation, benefits, and beyond: We understand that a comprehensive benefits package plays a significant role..." but no specifics given besides compensation range later. No explicit benefits listed. So we should not create Benefits section unless specific content. There's mention "review our benefits and perks" but no detail. So we omit Benefits. - Pay: Compensation Range: $250K - $280K. That's specific. So include Pay section. - Schedule: Not mentioned. No schedule info. So omit. - Also maybe include "About the company" but not required. The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Possibly also include a short paragraph for company description under About the role? Might be okay. We must not invent or summarize away detail. Must preserve all substantive info. So we need to include all bullet points exactly as given, not summarizing. Let's extract: About the role: The paragraph(s) describing role: "Vice President of Engineering, Architecture This is a hands-on executive leadership role for a proven technology leader who has successfully scaled complex SaaS platforms through both technical transformation and organizational growth. You’ll own the company’s architectural vision and strategy—consolidating systems, defining core frameworks, and establishing a foundation for sustainable velocity and innovation. This is not a role for a theoretical strategist; you’ll be an active individual contributor who can move seamlessly between long-term vision and hands-on technical execution. This role leads with influence, it is not a people management role." Also maybe include the mission statement? That's more about company. Could be part of About the role? Probably not needed. We'll keep role description. Responsibilities: Under "In this role, you’ll get to:" we have three categories each with bullet points. Let's list them exactly: Technology Strategy & Execution - Define and drive a 1–3 year global architecture roadmap that delivers on scalability, security, resilience, and performance. - Lead the unification and modernization of systems—reducing complexity and enabling a coherent platform architecture. - Establish and champion core architectural principles, frameworks, and patterns to guide engineering excellence. - Evaluate, select, and introduce best-in-class technologies and tooling that accelerate developer productivity. - Partner with the CTO to align architecture strategy with business priorities and product evolution. Platform & Infrastructure Consolidation - Oversee re-architecture and modernization initiatives that consolidate legacy or disparate platforms into a unified technical foundation. - Drive alignment across multiple product lines and services to create a seamless, scalable ecosystem. - Lead the unification of data and event-driven infrastructure, ensuring maintainability, security, and global performance. - Balance standardization with team autonomy—establishing frameworks that scale without stifling innovation. Leadership & Cultural Impact - Lead and develop a global team of architects and senior engineers across the US, EU, and other distributed regions. - Foster a culture of technical excellence, accountability, and psychological safety—where engineers are empowered to innovate and deliver impact. - Collaborate cross-functionally with Product, DevOps, and Security to ensure architecture supports business goals and operational efficiency. - Mentor senior technical leaders and architects, developing deep bench strength across the organization. - Communicate complex technical decisions clearly and persuasively to executive stakeholders and non-technical audiences. Requirements / Qualifications: The list under "Who you are and what you’ll need for this position:" includes: - 10+ years in technology leadership roles, including 3+ years in architecture or platform strategy at scale. - Demonstrated success in scaling and consolidating multi-product or post-M&A SaaS platforms. - Deep expertise in distributed systems, modern SaaS architecture, and database design. - Experience leading and influencing teams of 50+ engineers and architects globally. - Proven track record driving system migrations, refactoring, or platform unification initiatives. - Expertise in cloud-native architectures (AWS, GCP, or Azure) and event-driven or microservices ecosystems. - Strong technical judgment in balancing polyglot environments with standardization. - Experience in compliance-heavy industries (finance, healthtech, adtech, or similar) is a plus. - Exceptional communication skills with the ability to influence at all levels—from engineering teams to the boardroom. Also there is a motivational paragraph about confidence etc. That's not a requirement; we can omit as it's encouragement. Skills: Could be derived from requirements but we could separate: maybe list technical skills: distributed systems, SaaS architecture, database design, cloud-native (AWS/GCP/Azure), event-driven/microservices, polyglot environments, etc. But we already have them in requirements. To avoid duplication, we could put them under Skills if we want. However instruction: Prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they have separate headings allowed. We could include both Requirements and Qualifications as separate if they have distinct content. The list seems to be both requirements and qualifications; there is no separate qualifications list. So we could just have Requirements section and maybe omit Qualifications. Or we could have Requirements and Qualifications both with same content? That would be duplication. Better to have one section, maybe Requirements, and skip Qualifications. But the instruction says use headings for those categories if they have real specific content. We have content for Requirements (the list). We don't have separate Qualifications content beyond that. So we can omit Qualifications heading. Skills: Could we extract skills from the list? The list includes expertise etc. That could be considered skills. But we already have them in Requirements. To avoid thin sections, we could just have Requirements and maybe Skills combined? But we need to follow headings list; we can include Skills if we have specific skill statements not already covered. The list includes: Deep expertise in distributed systems, modern SaaS architecture, and database design. Experience leading and influencing teams... Expertise in cloud-native architectures... Strong technical judgment... Experience in compliance-heavy industries... Exceptional communication skills. Those are skills. So we could put them under Skills. But then Requirements would be maybe the years of experience etc. However the list mixes both. To avoid duplication, we could split: Requirements: years of experience, success scaling, leading teams, track record, etc. Skills: expertise in distributed systems, SaaS architecture, database design, cloud-native, event-driven/microservices, polyglot, compliance industries, communication. But that's splitting the same list; risk of losing some nuance but still preserving all info. It's okay as long as we don't omit any. Let's decide: We'll have Requirements (experience-based) and Skills (technical/communication). We'll ensure we keep all items. Requirements items: - 10+ years in technology leadership roles, including 3+ years in architecture or platform strategy at scale. - Demonstrated success in scaling and consolidating multi-product or post-M&A SaaS platforms. - Experience leading and influencing teams of 50+ engineers and architects globally. - Proven track record driving system migrations, refactoring, or platform unification initiatives. Skills items: - Deep expertise in distributed systems, modern SaaS architecture, and database design. - Expertise in cloud-native architectures (AWS, GCP, or Azure) and event-driven or microservices ecosystems. - Strong technical judgment in balancing polyglot environments with standardization. - Experience in compliance-heavy industries (finance, healthtech, adtech, or similar) is a plus. - Exceptional communication skills with the ability to influence at all levels—from engineering teams to the boardroom. That covers all. Now Benefits: we have none specific, so omit. Pay: Compensation Range: $250K - $280K. Schedule: none. Now About the role: we need to include the description. Also maybe include the company intro? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The company intro at start: "CreatorIQ is the operating system for creator-led growth trusted by more than 1,300 global brands and agencies. We’re on a mission to make businesses more human, and humans more impactful. We operate by our values — be intentional, pursue excellence every day, embrace the journey together, and be a good human — every day. CreatorIQ has earned the title of best companies to work for in multiple programs, including BuiltIn LA and NY. It’s been named a Fastest-Growing Company in North America on the Deloitte Technology Fast 500™ for four years, was named a leader in IDC MarketScape: Worldwide Influencer Marketing Platforms for Large Enterprises in 2025, was named a Leader by The Forrester New Wave™: Influencer Marketing Solutions, and has been consistently recognized by G2 as a Leader, and is rated 5 stars on Influencer MarketingHub. We operate in a flexible work model that combines both in-person and remote work to boost collaboration, enhance innovation, and adapt to individual work styles. We're seeking passionate, innovative minds to join our journey. Be a part of our dynamic team and let's transform the industry together!" That's substantive info about company and work model. Should we include it? The heading "About the role" is for role description, but we could also include company overview under About the role? Might be okay but could be considered not role-specific. However we have no other heading for company info. The instruction says use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid including other content under About the role beyond role description. It says use

for section headings (e.g. About the role, Responsibilities...). So we can have About the role heading and include both company overview and role description. That preserves all substantive info. Thus About the role will contain paragraphs: company description, mission, values, awards, flexible work model, seeking passionate minds, then role description. We must not repeat job title as a heading. The job title appears earlier; we won't repeat. Now we need to output HTML fragment only, no markdown fences. We'll structure:

About the role

... (multiple paragraphs maybe). We'll keep each paragraph as

. Then

Responsibilities

• ... but we have subheadings inside responsibilities. The instruction: Use
  • for any list of duties/requirements/benefits. It didn't forbid using headings inside list? Probably we can keep the subheadings as or maybe as

    but not allowed? Only headings allowed are those specific ones. So we should not add other headings. We can incorporate subheadings as bold text within

    . That's okay. Thus for each category we can have

    Technology Strategy & Execution: then a nested

    for its items? But nested lists are still
    • . That's fine