Principal Threat Architect, AI-Era Detection & Response
TrendAI · Austin, Texas Metropolitan Area · 1 mo ago
Art & CreativeFull-time
We need to output only HTML fragment, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We need to parse the job posting.
First, there is a description: "TrendAI™, the global AI security leader..." This is about the company. Not a section heading.
Then "About The Team" - that could be "About the role"? Actually "About The Team" is a section. The instruction says use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We need to parse the job posting.
First, there is a description: "TrendAI™, the global AI security leader..." This is about the company. Not a section heading.
Then "About The Team" - that could be "About the role"? Actually "About The Team" is a section. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map "About The Team" to "About the role"? The heading text should be exactly as given? Probably we should use the heading from posting: "About The Team". But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those standard headings, but we can also use the actual heading if it matches. Safer to use the exact heading from posting: "About The Team". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Means we should use those headings when appropriate. If posting has "About The Team", we could treat that as "About the role". But maybe better to follow the posting's headings: "About The Team", "The Role", "Key Responsibilities", "Minimum Qualifications", "Preferred Qualifications", "What We Offer You". Also there is "Be Passionate..." etc but that's fluff.
We need to avoid repeating job title as heading. The job title is "Principal Threat Architect". Not present as heading.
We need to include sections only when posting has real specific content.
Let's extract content:
- About The Team: description of Security Research & Development group, frontier of AI-era cyber defense, etc. That's substantive.
- The Role: description of role, responsibilities overview.
- Key Responsibilities: list of bullet points (Threat & technology research, Architecture & capability design, Prototyping & experimentation, Research-to-production bridge, Technical leadership, Communication & influence). Those are specific.
- Minimum Qualifications: list of bullet points (Bachelor's degree..., 8+ years..., Proven track record..., Hands-on experience..., Working familiarity..., Experience in a research..., Proficiency..., Strong written..., Must be legally authorized...). Those are specific.
- Preferred Qualifications: list (Master's..., Direct experience..., Experience building..., Hands-on experience..., Proficiency..., Familiarity..., Publication..., Experience within...). Those are specific.
- What We Offer You: list of benefits (Comprehensive medical..., Life insurance..., Short & Long Term Disability..., Pre-partum..., Mental Health..., Adoption Assistance..., Wellness Incentive..., Pet Insurance..., 401(k) with company match..., Paid Time Off..., 14 Annual Holidays..., Tuition Assistance..., Employee Resource Groups...). Also mention competitive compensation with bonus opportunity, work-life balance, team activities, etc. Also note "This position does not offer sponsorship..." That's a note about visa sponsorship; could be considered part of "What We Offer You" or separate. But it's a restriction, not a benefit. Might be better to include as a note under "What We Offer You" or separate section like "Important Notes". But instruction says only use those headings; we could include a short paragraph under "What We Offer You" that includes that note.
We also have "Be Passionate..." etc which is fluff; we can ignore.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statements repeated twice; we should remove those.
Also "At TrendAI, we embrace change..." etc is fluff but maybe not boilerplate; but it's generic. Might be considered boilerplate; but it's not EEO. It's a value statement. Could keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The value statement is not those; we could keep but it's not under a heading. It appears after the EEO statements. Might be considered fluff but not prohibited. Safer to omit if not under a heading. We'll only output sections we have.
Thus we will output:
About The Team
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those standard headings, but we can also use the actual heading if it matches. Safer to use the exact heading from posting: "About The Team". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Means we should use those headings when appropriate. If posting has "About The Team", we could treat that as "About the role". But maybe better to follow the posting's headings: "About The Team", "The Role", "Key Responsibilities", "Minimum Qualifications", "Preferred Qualifications", "What We Offer You". Also there is "Be Passionate..." etc but that's fluff.
We need to avoid repeating job title as heading. The job title is "Principal Threat Architect". Not present as heading.
We need to include sections only when posting has real specific content.
Let's extract content:
- About The Team: description of Security Research & Development group, frontier of AI-era cyber defense, etc. That's substantive.
- The Role: description of role, responsibilities overview.
- Key Responsibilities: list of bullet points (Threat & technology research, Architecture & capability design, Prototyping & experimentation, Research-to-production bridge, Technical leadership, Communication & influence). Those are specific.
- Minimum Qualifications: list of bullet points (Bachelor's degree..., 8+ years..., Proven track record..., Hands-on experience..., Working familiarity..., Experience in a research..., Proficiency..., Strong written..., Must be legally authorized...). Those are specific.
- Preferred Qualifications: list (Master's..., Direct experience..., Experience building..., Hands-on experience..., Proficiency..., Familiarity..., Publication..., Experience within...). Those are specific.
- What We Offer You: list of benefits (Comprehensive medical..., Life insurance..., Short & Long Term Disability..., Pre-partum..., Mental Health..., Adoption Assistance..., Wellness Incentive..., Pet Insurance..., 401(k) with company match..., Paid Time Off..., 14 Annual Holidays..., Tuition Assistance..., Employee Resource Groups...). Also mention competitive compensation with bonus opportunity, work-life balance, team activities, etc. Also note "This position does not offer sponsorship..." That's a note about visa sponsorship; could be considered part of "What We Offer You" or separate. But it's a restriction, not a benefit. Might be better to include as a note under "What We Offer You" or separate section like "Important Notes". But instruction says only use those headings; we could include a short paragraph under "What We Offer You" that includes that note.
We also have "Be Passionate..." etc which is fluff; we can ignore.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statements repeated twice; we should remove those.
Also "At TrendAI, we embrace change..." etc is fluff but maybe not boilerplate; but it's generic. Might be considered boilerplate; but it's not EEO. It's a value statement. Could keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The value statement is not those; we could keep but it's not under a heading. It appears after the EEO statements. Might be considered fluff but not prohibited. Safer to omit if not under a heading. We'll only output sections we have.
Thus we will output:
About The Team
About The Team
...content...
The Role
...content...
Key Responsibilities
- ... each bullet...
Minimum Qualifications
- ... each bullet...
Preferred Qualifications
- ... each bullet...
What We Offer You
- ... each benefit...
We offer competitive compensation with bonus opportunity tied to company performance, along with room to enhance your skills through ongoing learning and broad technological opportunities. Achieving work-life balance is a priority, complemented by team activities, fostering an environment rooted in equity, inclusion, and collaboration, that is reflected in both our culture and our work. This position does not offer sponsorship for work permit applications or renewals, either now or in the future. Candidates must be authorized to work in the U.S. without the need for employment-based visa sponsorship, both currently and moving forward. The company will not sponsor applicants for U.S. work visa status for this role (including, but not limited to, H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT, or any other employment-based visa).
We need to ensure we don't include headings like Pay, Schedule, Benefits, Skills unless we have content. We have Benefits covered under What We Offer You. No explicit Pay or Schedule. So we omit those. We must not repeat job title as heading. Not present. We must not put Job ID/requisition numbers as headings; none present. We must preserve ALL substantive information; do not invent or summarize away detail. Need to keep all details from each bullet. Let's extract exact text. About The Team paragraph: "Our Security Research & Development group sits at the frontier of AI-era cyber defense. We study how attackers are beginning to weaponize artificial intelligence, how AI is reshaping detection and response, and what durable capabilities defenders will need over the next several years. We are not a day-to-day operations team. Our charter is to research, prototype, and design the core capabilities that will anchor our platform and our customers' defenses for the next generation." We should keep that exactly. The Role paragraph: "We are seeking a Principal Threat Architect to research the frontier of AI-era threats and defensive technologies and to design the core detection-and-response capabilities that will anchor our platform for the next several years. This is a senior individual-contributor role at the intersection of threat research and systems architecture. You will study emerging threats and newly viable technologies, prototype and validate novel defensive approaches, and converge open-ended research into durable, production-grade operational architecture. You will work across disciplines — threat intelligence, detection engineering, AI/ML, and platform engineering — to translate what you learn into foundational capabilities rather than point solutions. Success in this role means the architecture you design today is still the foundation defenders build on years from now." We keep that. Key Responsibilities bullet points as given: - "Threat & technology research. Research the evolving AI-era threat landscape — including AI-enabled attacks and threats to AI systems themselves (e.g., prompt injection, model misuse, data leakage) — and translate findings into defensive strategy." - "Architecture & capability design. Design new threat operational architecture: scalable, robust detection-and-response systems that integrate with existing security tooling, data pipelines, and analyst workflows." - "Prototyping & experimentation. Envision, build, and validate prototypes that demonstrate the feasibility and impact of novel defensive approaches; converge open-ended research into concrete, supportable specifications." - "Research-to-production bridge. Partner with detection engineering, data science, and platform teams to transition prototypes from early-stage design into durable, production-grade capabilities." - "Technical leadership. Provide principal-level technical leadership on core design decisions and trade-offs; set direction that peers and adjacent teams build upon." - "Communication & influence. Communicate complex research and architectural direction clearly to technical and non-technical audiences, including leadership; contribute to thought leadership as appropriate." We need to keep punctuation exactly. Minimum Qualifications bullet points: - "Bachelor's degree in computer science, engineering, or a related technical field, or equivalent practical experience." - "8+ years in cybersecurity, with demonstrable depth in threat detection and response." - "Proven track record designing and delivering complex technical systems from concept through production deployment." - "Hands-on experience architecting scalable systems that integrate with existing security tooling and operational workflows." - "Working familiarity with AI/ML concepts and their application to threat detection, prevention, or response, including awareness of AI-specific threats and frameworks such as MITRE ATT&CK." - "Experience in a research, R&D, or emerging-technologies function, with a demonstrated ability to take ambiguous, open-ended problems and converge them into concrete specifications." - "Proficiency in at least one production programming language (e.g., Python)." - "Strong written and verbal communication, including conveying complex technical concepts to varied audiences." - "Must be legally authorized to work in the United States." Preferred Qualifications bullet points: - "Master's in computer science, machine learning, or a security-related discipline." - "Direct experience with AI/ML security — securing ML/GenAI models, adversarial ML, or defending against AI-enabled attacks — aligned with frameworks such as the OWASP Top 10 for LLMs." - "Experience building or operating detection-and-response platforms (EDR / XDR / MDR, SIEM, SOAR) or agentic SOC architectures." - "Hands-on experience with large-scale data-processing systems and modern distributed architectures." - "Proficiency in systems languages such as C/C++ or Rust in addition to Python." - "Familiarity with cloud security across AWS, Azure, or GCP and with hybrid/multi-cloud environments." - "Publication, patent, or conference-presentation record in threat research or applied AI security." - "Experience within a vendor CTO office, security research lab, or comparable innovation function." What We Offer You bullet points (benefits): - "Comprehensive medical, dental and vision insurance" - "Life insurance" - "Short & Long Term Disability" - "Pre-partum, maternity, parental and medical leave" - "Mental Health Wellness Program" - "Adoption Assistance" - "Wellness Incentive" - "Pet Insurance" - "401(k) with company match" - "Paid Time Off" - "14 Annual Holidays" - "Tuition Assistance" - "Employee Resource Groups" We also have sentence: "We offer competitive compensation with bonus opportunity tied to company performance, along with room to enhance your skills through ongoing learning and broad technological opportunities. Achieving work-life balance is a priority, complemented by team activities, fostering an environment rooted in equity, inclusion, and collaboration, that is reflected in both our culture and our work." This is not a bullet but prose; we can put as. Then the visa sponsorship note: "This position does not offer sponsorship for work permit applications or renewals, either now or in the future. Candidates must be authorized to work in the U.S. without the need for employment-based visa sponsorship, both currently and moving forward. The company will not sponsor applicants for U.S. work visa status for this role (including, but not limited to, H-1B, L-1, TN, O-1, E-3, H-1B1, F-1,