Principal AI Architect

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: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove EEO statements etc. We need to parse the posting. Content: - Intro about SecurityScorecard (company description). This is not a section heading; we can include as a paragraph maybe under "About the role"? Actually "About the role" heading is present. The company description could be part of "About the role" or maybe we can include as a paragraph before sections? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have headings for those sections if content exists. The company description is not under any of those headings; but we could include it under "About the role" as part of that section's prose. The "About the role" heading is present in the posting: "About the Role:" then description. So we will create

About the role

and include the description (the paragraph about the role). Also we might include the company description as part of that? Probably not needed; but we can include it as a paragraph before the heading? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. It doesn't forbid other paragraphs outside sections. But likely they expect sections only. However we can include a brief intro paragraph before sections? Might be okay but safer to include company description under "About the role" as part of that section's content. Now identify sections: - About the role: we have description after "About the Role:" includes paragraphs about role responsibilities, reporting, etc. We'll capture that. - Responsibilities: there is a "What You'll Do" bullet list. That's responsibilities. - Requirements: there is "Required Qualifications:" list. - Qualifications: there is "Preferred Qualifications:" list. - Skills: maybe not explicitly listed; but we could infer from Required Qualifications includes skills. However we should only create a Skills section if posting has real specific content for it. There's no separate "Skills" heading. So we omit Skills. - Benefits: there is "Benefits:" paragraph with details. - Pay: there is "The estimated total compensation range for this position is $240,000 - $300,000 (base plus bonus)." Also mention base plus bonus, equity, etc. So we have pay info. - Schedule: not mentioned. No schedule info. So omit Schedule. Also there is "Our Tech Stack" section. Not in the list of allowed headings; but we could maybe include under "Qualifications" or "Skills"? But we should not create new headings not in list. 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 likely they want only those. However we could incorporate tech stack into Qualifications or Responsibilities? Might be better to include as a paragraph under "Qualifications" maybe as part of "Preferred Qualifications"? But the tech stack is separate. Could we treat it as part of "Qualifications"? The instruction: "Prefer a few substantive sections over many thin ones." So we could add a section "Tech Stack" but not in allowed list; risk. Better to incorporate into "Qualifications" or "Responsibilities". Since it's about the environment, maybe include under "Qualifications" as a paragraph. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep tech stack details somewhere. We could add a

Tech Stack

but that deviates from allowed headings. However the instruction 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 exclusive list. So we can use other headings if needed, as long as they are

. But they also say "Prefer a few substantive sections over many thin ones." So we could add a Tech Stack section if it's substantive. It is substantive. So we can include

Tech Stack

. That seems okay. But we must not create sections with filler. Tech stack has real content. Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Tech Stack, Benefits, Pay. We must not include Schedule. Now we need to extract content precisely. Let's copy relevant text. About the role: after "About the Role:" we have: "SecurityScorecard is hiring a Principal Software Architect to lead the system design of our agentic AI capabilities and serve as a technical anchor for engineering teams building the next generation of our platform. This is an individual contributor role reporting to the Chief Architect, alongside a Front-end Architect and a Data-focused Architect, and partnering closely with engineering leadership, Product, and Data Science. We're looking for someone who can go deep technically and also move a room: an architect whose designs get adopted because they're well-reasoned and well-communicated, not just handed down. You will lead the system design for how agentic features are built, integrated, and operated reliably at production scale, working in close partnership with our Data Science team, who bring the model and ML depth. Your focus is the system: orchestration, state and memory, tool boundaries, failure semantics, and how all of it composes with the wider platform. Like the rest of our architecture function, you'll prototype to prove out decisions rather than implement full solutions, and you'll set direction through Technical Design Reviews (TDRs), and standards. Deep data-engineering specialization isn't required, but you should be comfortable reasoning about data flows, storage decisions, and how agentic systems consume and act on data." That's the about role. Now Responsibilities: "What You'll Do" bullet list: - Own the system design for our agentic capabilities: orchestration, context and state, tool boundaries, and reliability patterns for non-deterministic systems - Write the TDRs, design docs, and standards that set architectural direction for agentic work across teams - Prototype to validate architectural decisions before teams commit to them at scale - Partner with Data Science so that agent and model work composes cleanly with existing platform services, from APIs and event streaming through to storage - Review TDRs from across engineering, giving teams substantive feedback on architecture and risk, not only on AI work - Build consensus across engineering teams and get them genuinely aligned, not merely compliant - Help drive the shift to AI-assisted and agentic development across engineering, shaping how engineers design, review, and iterate in an AI-native workflow - Mentor senior and staff engineers on agentic system design and measurably elevate the technical bar - Communicate architectural decisions and their trade-offs clearly to executives and customers Now Required Qualifications list: - 10+ years of software engineering experience, including significant time as a senior, staff, or principal-level architect or technical lead designing production systems - Deep expertise in distributed systems: service boundaries, consistency models, event-driven architecture, API design (REST; gRPC familiarity a plus), and operating systems reliably at scale - Hands-on experience building, prototyping, and architecting agentic or LLM-powered systems in production, not just demos: agent loop design, context engineering, MCP and tool/function-calling integration, RAG architectures, memory and state management, and reliability and guardrail patterns for non-deterministic systems - Working knowledge of data engineering fundamentals, including data modeling, pipeline design, and streaming vs. batch, sufficient to make informed architectural calls without deep specialization in the domain - A track record of influence without authority: presenting a technical direction to skeptical engineers and earning genuine buy-in, and giving rigorous design review feedback on systems you didn't build yourself - Strong technical writing and mentorship: TDRs, design docs, and decision records that teams can act on without hand-holding, plus a history of raising the technical bar around you - Ability to communicate complex architectural decisions clearly to executives and customers - Comfort operating as a senior individual contributor, driving outcomes through prototyping and technical credibility Preferred Qualifications list: - Familiarity with multi-agent orchestration patterns (supervisor and sub-agent architectures, agent handoffs), which our use cases are likely to grow toward - Experience with our stack or comparable technologies: Node.js/TypeScript, PostgreSQL, ClickHouse, Kafka, AWS, Kubernetes - Experience leading AI-assisted or agentic development adoption across an engineering organization; given the scope of this work at SecurityScorecard, this carries significant weight - Experience partnering closely with data science or ML teams on productionizing their work - Cybersecurity industry background Tech Stack paragraph: "Our Tech Stack Our platform runs on Node.js and TypeScript, with a React Microfrontend Architecture and PostgreSQL and ClickHouse for storage. We use Kafka for event streaming, and our infrastructure runs on AWS with Kubernetes, Terraform, Helm, and ArgoCD. We are actively expanding our AI/ML infrastructure. You do not need to have used every tool here, but you should be comfortable reasoning across a stack of this kind and making principled architectural trade-offs within it." Benefits paragraph: "Benefits: Specific to each country, we offer a competitive salary, stock options, Health benefits, and unlimited PTO, parental leave, tuition reimbursements, and much more! The estimated total compensation range for this position is $240,000 - $300,000 (base plus bonus). Actual compensation for the position is based on a variety of factors, including, but not limited to affordability, skills, qualifications and experience, and may vary from the range. In addition to base salary, employees may also be eligible for annual performance-based incentive compensation awards and equity, among other company benefits." Wait that includes compensation also. Actually the Benefits paragraph includes compensation range. But we also have a separate Pay section maybe. The instruction: Benefits and Pay separate. The posting lumps compensation in Benefits. We need to separate: Benefits (salary, stock options, health benefits, unlimited PTO, parental leave, tuition reimbursements, etc.) and Pay (estimated total compensation range $240k-$300k base plus bonus, plus performance-based incentive, equity). We'll extract. Thus Benefits: "Specific to each country, we offer a competitive salary, stock options, Health benefits, and unlimited PTO, parental leave, tuition reimbursements, and much more!" (maybe also mention other benefits). We'll keep that. Pay: "The estimated total compensation range for this position is $240,000 - $300,000 (base plus bonus). Actual compensation for the position is based on a variety of factors, including, but not limited to affordability, skills, qualifications and experience, and may vary from the range. In addition to base salary, employees may also be eligible for annual performance-based incentive compensation awards and equity, among other company benefits." Now we need to ensure we don't include boilerplate: EEO statements, etc. Remove all that. Now produce HTML. Structure:

About the role

... (the paragraph)

Responsibilities

• ... each bullet
...

Requirements

... required qualifications

Qualifications

... preferred qualifications

Tech Stack

... tech stack paragraph

Benefits

... benefits paragraph