Sr. Manager, Frontend Engineering

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements/Qualifications (What You Bring), Benefits (What We Offer), Pay (Compensation), maybe Schedule? Not present. Also maybe "Additional Information" includes Work Environment, Location, Travel - could be part of Benefits? But we should only include sections with real content. The posting includes "About Interos.ai" description; but we should not repeat job title as heading. The page already shows it. We should not include "About Interos.ai" as a section heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when the posting has real, specific content for it. The posting includes "About Interos.ai" which is company overview, not necessarily a required section. Could we include it under "About the role"? The "About The Role" heading is present. So we should have an

About the role

with content from that section (the paragraph after "About The Role"). Then "What You'll Do" => Responsibilities. Then "What You Bring" => Requirements/Qualifications (maybe combine). Could also have Skills but we can just use Requirements. Then "What We Offer" => Benefits. Then "Compensation" => Pay. We also have "Additional Information" with Work Environment, Location, Travel. Could be part of Benefits? But it's not benefits exactly. Could be its own section? Not in the list of allowed headings but we could maybe treat as "Additional Information" but instruction says use those example headings; not required to stick strictly but likely they expect those headings. However we can include a section for "Work Environment" if we want but not in list. Safer to stick to allowed headings. The additional info could be folded into Benefits or maybe omitted? But we must preserve ALL substantive information; cannot drop. So we need to include that info somewhere. Could add a

Additional Information

though not in list but maybe acceptable. The instruction: "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. So we can add other headings as needed. But better to follow the spirit: include sections for the main categories. Additional info could be part of Benefits or maybe a separate "Work Environment" heading. I'll add a section "Work Environment" as

Work Environment

to keep info. Also we have "OUR CORE VALUES" - could be part of Benefits? It's substantive. Could be its own section "Core Values". Might be okay. We need to remove boilerplate: EEO, accessibility, etc. Remove equal opportunity employer, accessibility & accommodations lines. Also remove "Additional Information Work Environment, Location, and Travel:"? We'll keep the content but not the heading label? We'll keep content. We must not repeat job title as heading. So no

SR. MANAGER, FRONTEND ENGINEERING

. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment, no /, no markdown fences. Let's extract content. About Interos.ai: paragraph describing company. Should we include? It's substantive. Could be part of "About the role"? But there is already "About The Role" section separate. The "About Interos.ai" is company overview; we could include it under "About the role" or separate "About Interos.ai". Since we have "About the role" heading, we could put company overview there as well? But the instruction: "About the role" heading for section headings. The posting has "About The Role" heading. So we should put the content under that heading. The "About Interos.ai" could be placed before that as a general intro; but we could also include it under "About the role" as part of the role description? Might be okay to include it there. However we must preserve all substantive information; we can include it as a paragraph under About the role. Let's parse sections: - About Interos.ai (company description) - About The Role (role description) - What You'll Do (responsibilities) - What You Bring (requirements) - BONUS POINTS FOR (bonus qualifications) - What We Offer (benefits) - OUR CORE VALUES (values) - Additional Information (Work Environment, Location, Travel) - Compensation (Base Salary Range, Variable Compensation, Equity) We need to decide headings. We could have:

About the role

containing company description + role description.

Responsibilities

containing What You'll Do.

Requirements

containing What You Bring + BONUS POINTS FOR (maybe as a list).

Benefits

containing What We Offer.

Core Values

containing OUR CORE VALUES.

Work Environment

containing Additional Information.

Pay

containing Compensation. We must not include empty sections. Now extract content precisely. About Interos.ai paragraph: "interos.ai is the standard for supply chain risk intelligence. Our Resilience platform, powered by an 11B buyer-supplier knowledge graph and 250M+ businesses scored across six risk factors, Cyber, Catastrophic, ESG, Restrictions, Geopolitical, and Finance, is run by Fortune 1000 market leaders and trusted by major Federal departments. As the only AI-powered SaaS platform that comprehensively assesses risk across these domains, interos.ai helps customers understand their exposure through our proprietary iScore® and assists both real-time and anticipatory opportunities to mitigate supply chain risk. Our second-generation platform, iQ, is the industry's first fully productized predictive analytics platform for supply chain risk. iQ orchestrates ERP and Resilience platform insights to deliver AI-driven suggestions for supply chain risk management, helping organizations quantify financial exposure, stay ahead of geopolitical volatility and shifting tariffs, and communicate risk in the language CFOs use every day. We are not afraid to challenge conventions, explore new ideas, and iterate quickly. Our work is meaningful, the problems are complex, and the pace requires focus, curiosity, and adaptability. We are looking for people who are humble in how they collaborate, hungry to succeed, and smart in how they work. People who thrive here are energized by broad exposure, comfortable navigating ambiguity, open to feedback, proactive in taking ownership, and motivated by making a real impact." About The Role paragraph: "interos.ai is hiring a Senior Manager, Frontend Engineering to lead the team behind the interface of our Resilience and iQ platforms, the tools that help Fortune 1000 companies and federal agencies see supply chain risk before it becomes a headline. You will own the technical direction and day to day leadership of a team of React and TypeScript engineers, balancing hands-on technical judgment with people leadership. This is a high-visibility role: your team's work is the first thing every customer touches, and the quality of that experience shapes how the world's most complex organizations trust us with their risk data. You will partner closely with Product, Design, and Backend Engineering to turn roadmap priorities into a frontend that is fast, accessible, and easy to use." What You'll Do bullet list: - Own the technical vision and architecture for interos.ai's frontend systems, keeping our React and TypeScript codebase scalable as the iQ and Resilience platforms grow - Lead, hire, and develop a team of frontend engineers, setting the bar for code quality, delivery, and craft - Partner with Product, Design, and Backend Engineering leadership to translate roadmap priorities into a clear frontend delivery plan - Drive architectural decisions on component design, state management, and application performance across the platform - Establish and evolve engineering standards, code review practices, and testing strategy using tools such as Jest and Cypress - Monitor and improve application performance and reliability using tools such as Datadog, Lighthouse, and Chrome DevTools - Champion accessibility and responsive design as core requirements across every release - Build a culture of ownership and mentorship, running effective sprint planning, retrospectives, and 1:1s - Manage team capacity, prioritization, and cross-functional dependencies to keep delivery predictable - Partner with Talent Acquisition on hiring plans and interview loops for frontend roles What You Bring bullet list: - 10+ years of experience in frontend software development, with a strong track record shipping production web applications, or equivalent experience - 5+ years of experience directly managing a team of frontend engineers, including hiring, performance management, and career development - Experience with React and TypeScript in production, along with strong fundamentals in HTML, CSS, and modern JavaScript - Experience architecting frontend systems that scale across multiple teams or a complex product surface - Experience with CI/CD pipelines and observability tooling such as Datadog - Experience building and scaling SaaS products, ideally in a startup or fast-growing company environment - Experience with responsive design, cross-browser compatibility, and testing frameworks such as Jest or Cypress - Strong communication skills, with experience partnering across product, design, and backend engineering BONUS POINTS FOR bullet list: - Familiarity with Snowflake or GraphQL - Experience with performance optimization and accessibility best practices at scale - Experience with cloud platforms such as AWS, Azure, or Google Cloud - Background in cybersecurity, risk, or supply chain technology - Experience mentoring other engineering managers or technical leads What We Offer bullet list: - Comprehensive health, dental, and vision insurance - 401(k) with employer match - Flexible Time Off (FTO) + 10 paid holidays - Opportunity to help shape an early, fast-growing market - A flexible, remote-first work environment that empowers you to perform at your best, wherever you are - An incredible culture built on trust, accountability, and collaboration across time zones and teams OUR CORE VALUES bullet list (with descriptions): - Technical Skill: We hold a performance-driven standard across everything we build and deliver. We value depth of expertise, strong judgment, and the ability to turn complex challenges into clear, effective solutions. - Will: We show up hungry, humble, and smart. We take ownership, seek growth, and elevate one another through curiosity, accountability, and collaboration. - Thrill: We stay connected and bring energy to the work. Meaningful relationships and celebrating wins together fuel great outcomes. Additional Information paragraph: "Work Environment, Location, and Travel: This role can be remote-first within the United States, with optional access to our Arlington, VA HQ. Occasional travel may be required for team summits, customer engagements, or industry events." Compensation paragraph: "Compensation: Base Salary Range: $180,000 - $230,000 USD (depending on experience and location) Variable Compensation: Eligible for annual performance bonus Equity: Stock options included as part of total compensation package" We need to output HTML with

headings and

• for lists,

  for prose. We must not include any boilerplate like EEO, accessibility, etc. Already removed. Now construct HTML. We'll start with

  About the role

  then include company description and role description as maybe two

  paragraphs. Then

  Responsibilities

  with
  list. Then

  Requirements

  with
  list for What You Bring, then maybe a separate

  Bonus Qualifications

  but we could incorporate under Requirements as a sublist? Better to have separate heading for Bonus Points? The instruction allows any heading; we could add

  Bonus Qualifications

  . But we might combine into Requirements with a note. However to preserve all info, we can have a separate