Senior Front End Engineer
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — none present. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Why Join Us" maybe? It's not a required heading but could be considered a section if there is real content. The posting includes "Why Join Us" and "What We Offer You". Those are sections with content. We need to include sections only when posting has real, specific content. "Why Join Us" includes description: "Work on high-visibility web properties...". That's substantive. "What We Offer You" includes benefits list. So we should include sections: About The Role, Responsibilities, Qualifications, Why Join Us, What We Offer You (Benefits). Possibly also "Success Profile" is a section with content. Should we include? It's a list of traits. It's substantive. Could be its own section. The instruction: Prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real, specific content. We have many sections: About The Role, Responsibilities, Qualifications, Success Profile, Why Join Us, What We Offer You. Could combine some? But they are distinct headings in original. We should follow original headings as they appear: About The Role, Responsibilities, Qualifications, Success Profile, Why Join Us, What We Offer You. Also maybe "Location" but that's minor metadata; we can fold into a short
maybe after About The Role? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short paragraph after the heading? But we should not create a heading for Location. Probably we can include location in a
after About The Role heading? However About The Role heading is already used; we can add a
after it containing location? But the About The Role section already has prose; we could add location as part of that paragraph. But we must preserve ALL substantive information; location is substantive? It's location: Austin, TX (Hybrid). That's important. We'll include it in a
after About The Role heading maybe before responsibilities? But the About The Role heading currently is followed by prose describing role. We could insert location as a separate
before responsibilities? The instruction: use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. So we can have multiple
under a heading. So we can have About The Role heading, then a
containing the location sentence, then another
with the role description. That seems okay.
Now we need to strip boilerplate: The sections like "At TrendAI™, the global AI security leader..." is introductory fluff; maybe we can keep as part of About The Role? Actually that is before About The Role heading. It's generic company description. Might be considered boilerplate? It's not a heading; it's prose before the heading. Should we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This intro is not boilerplate per se, but it's generic marketing fluff. However it's substantive? It describes company mission. Might be okay to keep as a
before any heading? But we have no heading for that; we could just start with About The Role heading and incorporate that intro into About The Role paragraph? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that intro somewhere. Could place it as a
before the first heading? But we cannot have stray text outside of sections? The output is just HTML fragment; we can have leading
before first heading. That's fine.
But we need to avoid duplication: The intro repeats some of the later content? Not exactly.
Let's extract sections:
Intro paragraph: "TrendAI™, the global AI security leader and enterprise business unit of Trend Micro, empowers organizations with full AI visibility and consolidated security that inspires confidence, drives innovation, and eliminates risk. At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future. AI Fearlessly. Location: Austin, TX (Hybrid)"
We can keep that as a
maybe with location included.
Then About The Role heading:
About The Role
Then prose: "TrendAI is looking for a Senior Front End Engineer to help build and evolve the websites that represent our global brand, including trendaisecurity.com and trendmicro.com. You'll work primarily on the front end of a Sanity CMS architecture, partnering with marketing, design, sales, and growth stakeholders to ship continuous improvements to content-driven web experiences. You should be comfortable or excited to learn headless CMS platforms, writing production frontend code, integrating with internal and external platforms, and using AI tools to accelerate your and your team's productivity. We are looking for someone who handles change well, treats process as something to improve rather than defend, and sees highly collaborative AI-assisted development as a normal part of how teams work now."
That's the About The Role content.
Then Responsibilities heading: Responsibilities
Then list items: each sentence starting with a verb. We'll make - for each.
List:
- Design, build, and maintain front-end applications and marketing sites on Sanity CMS, shipping changes end-to-end on medium-to-large sites, from content schema through rendered page.
- Partner with marketing, content, and SEO/GEO stakeholders to turn business and content needs into scalable, maintainable frontend architecture for global teams.
- Build reusable components, templates, and tooling that let authors and other non-engineers create and manage content confidently and safely.
- Own performance, accessibility, and technical SEO/AI-crawler readiness across our web properties.
- Integrate with third-party services and APIs (analytics, marketing automation, personalization) from the frontend as part of the broader web ecosystem.
- Use AI-assisted development tools (Claude Code, Copilot, or internal tooling) as a standard part of your workflow for prototyping, code review, refactoring, and documentation.
- Take part in an agile team: sprint planning, code review, retros, and ongoing process improvement.
- Adapt as priorities, tooling, or requirements shift. This is a fast-moving environment, and comfort with ambiguity matters as much as technical depth.
- Collaborate with design, product marketing, and other teams.
Note: Some items have two sentences; we can keep as one li.
Then Qualifications heading:
Qualifications
List:
- 5+ years of professional front-end web development experience.
- Hands-on production experience with Sanity CMS (or a comparable headless/structured-content CMS like Contentful, Contentstack, or Storyblok that uses GraphQL), with a willingness to go deep on Sanity and its GROQ query language specifically.
- Strong proficiency in TypeScript and a component-based frontend framework (React, Astro, Next.js, or similar).
- Solid understanding of frontend architecture: server-side rendering or static generation, component design, state management, and build tooling.
- Experience working in agile/scrum environments with iterative delivery and shifting priorities.
- Real, everyday use of AI coding tools in an engineering workflow, not just passing familiarity.
- Strong collaboration and communication skills, and comfort working directly with non-engineering stakeholders like marketing and content teams.
- Bachelor's degree in Computer Science, Engineering, or equivalent practical experience.
Then Success Profile heading: Success Profile
List:
- Owns ambiguity and changes well, without needing every requirement locked down up front.
- Genuinely interested in getting better at AI-assisted development, not just tolerating it.
- Collaborative by default. Sees marketing, production, editorial, and growth partners as co-owners of the web experience.
- Pragmatic: balances technical craft with the pace of a marketing-driven web team.
Then Why Join Us heading: Why Join Us
Prose: "Work on high-visibility web properties for a global cybersecurity leader going through a major brand evolution (TrendAI). Join a small, close-knit team where your technical decisions shape how millions of visitors experience the brand, with real room to bring in modern tooling and better ways of working."
Then What We Offer You heading: What We Offer You
We need to turn benefits list into - . The benefits list:
- 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
Also there is a paragraph before list: "You're important to us. What matters to you, matters to us too. Trend Micro provides benefit options for you and your family." That's prose; we can put as a
under the heading before the list.
Then after list there is paragraph: "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." That's also prose; we can add another
after list.
Then there is "Be Passionate. Be Innovative. Be a Trender." That's a tagline; maybe we can include as a
after the previous paragraph? It's not a heading; we can keep as a
.
Then there is visa sponsorship statement: "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)." This is important substantive info; we should keep it. Where to place? Could be its own section? Not a heading in original. Could be a
after the Be Passionate paragraph. It's not boilerplate; it's a requirement. We'll keep as a
.
Then there is diversity statement: "At Trend Micro, we embrace change, empower people, and encourage innovation in a connected world. Our diversity and multicultural workforce are key contributing factors to our success across the globe. Trend Micro provides equal employment opportunity for all applicants and employees. Trend Micro does not unlawfully discriminate on the basis of race, color, religion, sex, pregnancy and childbirth or related medical conditions, national origin, ancestry, age, physical or mental disability, medical condition, family care leave status, veteran status, marital status, sexual orientation, or gender identity." This is EEO boilerplate; instruction says remove EEO/equal-opportunity boilerplate. So we should remove that entire paragraph.
Also earlier there is "TrendAI™, the
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — none present. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Why Join Us" maybe? It's not a required heading but could be considered a section if there is real content. The posting includes "Why Join Us" and "What We Offer You". Those are sections with content. We need to include sections only when posting has real, specific content. "Why Join Us" includes description: "Work on high-visibility web properties...". That's substantive. "What We Offer You" includes benefits list. So we should include sections: About The Role, Responsibilities, Qualifications, Why Join Us, What We Offer You (Benefits). Possibly also "Success Profile" is a section with content. Should we include? It's a list of traits. It's substantive. Could be its own section. The instruction: Prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real, specific content. We have many sections: About The Role, Responsibilities, Qualifications, Success Profile, Why Join Us, What We Offer You. Could combine some? But they are distinct headings in original. We should follow original headings as they appear: About The Role, Responsibilities, Qualifications, Success Profile, Why Join Us, What We Offer You. Also maybe "Location" but that's minor metadata; we can fold into a short
maybe after About The Role? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short paragraph after the heading? But we should not create a heading for Location. Probably we can include location in a
after About The Role heading? However About The Role heading is already used; we can add a
after it containing location? But the About The Role section already has prose; we could add location as part of that paragraph. But we must preserve ALL substantive information; location is substantive? It's location: Austin, TX (Hybrid). That's important. We'll include it in a
after About The Role heading maybe before responsibilities? But the About The Role heading currently is followed by prose describing role. We could insert location as a separate
before responsibilities? The instruction: use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. So we can have multiple
under a heading. So we can have About The Role heading, then a
containing the location sentence, then another
with the role description. That seems okay.
Now we need to strip boilerplate: The sections like "At TrendAI™, the global AI security leader..." is introductory fluff; maybe we can keep as part of About The Role? Actually that is before About The Role heading. It's generic company description. Might be considered boilerplate? It's not a heading; it's prose before the heading. Should we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This intro is not boilerplate per se, but it's generic marketing fluff. However it's substantive? It describes company mission. Might be okay to keep as a
before any heading? But we have no heading for that; we could just start with About The Role heading and incorporate that intro into About The Role paragraph? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that intro somewhere. Could place it as a
before the first heading? But we cannot have stray text outside of sections? The output is just HTML fragment; we can have leading
before first heading. That's fine.
But we need to avoid duplication: The intro repeats some of the later content? Not exactly.
Let's extract sections:
Intro paragraph: "TrendAI™, the global AI security leader and enterprise business unit of Trend Micro, empowers organizations with full AI visibility and consolidated security that inspires confidence, drives innovation, and eliminates risk. At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future. AI Fearlessly. Location: Austin, TX (Hybrid)"
We can keep that as a
maybe with location included.
Then About The Role heading:
About The Role
Then prose: "TrendAI is looking for a Senior Front End Engineer to help build and evolve the websites that represent our global brand, including trendaisecurity.com and trendmicro.com. You'll work primarily on the front end of a Sanity CMS architecture, partnering with marketing, design, sales, and growth stakeholders to ship continuous improvements to content-driven web experiences. You should be comfortable or excited to learn headless CMS platforms, writing production frontend code, integrating with internal and external platforms, and using AI tools to accelerate your and your team's productivity. We are looking for someone who handles change well, treats process as something to improve rather than defend, and sees highly collaborative AI-assisted development as a normal part of how teams work now."
That's the About The Role content.
Then Responsibilities heading: Responsibilities
Then list items: each sentence starting with a verb. We'll make - for each.
List:
- Design, build, and maintain front-end applications and marketing sites on Sanity CMS, shipping changes end-to-end on medium-to-large sites, from content schema through rendered page.
- Partner with marketing, content, and SEO/GEO stakeholders to turn business and content needs into scalable, maintainable frontend architecture for global teams.
- Build reusable components, templates, and tooling that let authors and other non-engineers create and manage content confidently and safely.
- Own performance, accessibility, and technical SEO/AI-crawler readiness across our web properties.
- Integrate with third-party services and APIs (analytics, marketing automation, personalization) from the frontend as part of the broader web ecosystem.
- Use AI-assisted development tools (Claude Code, Copilot, or internal tooling) as a standard part of your workflow for prototyping, code review, refactoring, and documentation.
- Take part in an agile team: sprint planning, code review, retros, and ongoing process improvement.
- Adapt as priorities, tooling, or requirements shift. This is a fast-moving environment, and comfort with ambiguity matters as much as technical depth.
- Collaborate with design, product marketing, and other teams.
Note: Some items have two sentences; we can keep as one li.
Then Qualifications heading:
Qualifications
List:
- 5+ years of professional front-end web development experience.
- Hands-on production experience with Sanity CMS (or a comparable headless/structured-content CMS like Contentful, Contentstack, or Storyblok that uses GraphQL), with a willingness to go deep on Sanity and its GROQ query language specifically.
- Strong proficiency in TypeScript and a component-based frontend framework (React, Astro, Next.js, or similar).
- Solid understanding of frontend architecture: server-side rendering or static generation, component design, state management, and build tooling.
- Experience working in agile/scrum environments with iterative delivery and shifting priorities.
- Real, everyday use of AI coding tools in an engineering workflow, not just passing familiarity.
- Strong collaboration and communication skills, and comfort working directly with non-engineering stakeholders like marketing and content teams.
- Bachelor's degree in Computer Science, Engineering, or equivalent practical experience.
Then Success Profile heading: Success Profile
List:
- Owns ambiguity and changes well, without needing every requirement locked down up front.
- Genuinely interested in getting better at AI-assisted development, not just tolerating it.
- Collaborative by default. Sees marketing, production, editorial, and growth partners as co-owners of the web experience.
- Pragmatic: balances technical craft with the pace of a marketing-driven web team.
Then Why Join Us heading: Why Join Us
Prose: "Work on high-visibility web properties for a global cybersecurity leader going through a major brand evolution (TrendAI). Join a small, close-knit team where your technical decisions shape how millions of visitors experience the brand, with real room to bring in modern tooling and better ways of working."
Then What We Offer You heading: What We Offer You
We need to turn benefits list into - . The benefits list:
- 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
Also there is a paragraph before list: "You're important to us. What matters to you, matters to us too. Trend Micro provides benefit options for you and your family." That's prose; we can put as a
under the heading before the list.
Then after list there is paragraph: "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." That's also prose; we can add another
after list.
Then there is "Be Passionate. Be Innovative. Be a Trender." That's a tagline; maybe we can include as a
after the previous paragraph? It's not a heading; we can keep as a
.
Then there is visa sponsorship statement: "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)." This is important substantive info; we should keep it. Where to place? Could be its own section? Not a heading in original. Could be a
after the Be Passionate paragraph. It's not boilerplate; it's a requirement. We'll keep as a
.
Then there is diversity statement: "At Trend Micro, we embrace change, empower people, and encourage innovation in a connected world. Our diversity and multicultural workforce are key contributing factors to our success across the globe. Trend Micro provides equal employment opportunity for all applicants and employees. Trend Micro does not unlawfully discriminate on the basis of race, color, religion, sex, pregnancy and childbirth or related medical conditions, national origin, ancestry, age, physical or mental disability, medical condition, family care leave status, veteran status, marital status, sexual orientation, or gender identity." This is EEO boilerplate; instruction says remove EEO/equal-opportunity boilerplate. So we should remove that entire paragraph.
Also earlier there is "TrendAI™, the
for prose. So we can have multiple
under a heading. So we can have About The Role heading, then a
containing the location sentence, then another
with the role description. That seems okay. Now we need to strip boilerplate: The sections like "At TrendAI™, the global AI security leader..." is introductory fluff; maybe we can keep as part of About The Role? Actually that is before About The Role heading. It's generic company description. Might be considered boilerplate? It's not a heading; it's prose before the heading. Should we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This intro is not boilerplate per se, but it's generic marketing fluff. However it's substantive? It describes company mission. Might be okay to keep as a
before any heading? But we have no heading for that; we could just start with About The Role heading and incorporate that intro into About The Role paragraph? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that intro somewhere. Could place it as a
before the first heading? But we cannot have stray text outside of sections? The output is just HTML fragment; we can have leading
before first heading. That's fine. But we need to avoid duplication: The intro repeats some of the later content? Not exactly. Let's extract sections: Intro paragraph: "TrendAI™, the global AI security leader and enterprise business unit of Trend Micro, empowers organizations with full AI visibility and consolidated security that inspires confidence, drives innovation, and eliminates risk. At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future. AI Fearlessly. Location: Austin, TX (Hybrid)" We can keep that as a
maybe with location included. Then About The Role heading:
About The Role
Then prose: "TrendAI is looking for a Senior Front End Engineer to help build and evolve the websites that represent our global brand, including trendaisecurity.com and trendmicro.com. You'll work primarily on the front end of a Sanity CMS architecture, partnering with marketing, design, sales, and growth stakeholders to ship continuous improvements to content-driven web experiences. You should be comfortable or excited to learn headless CMS platforms, writing production frontend code, integrating with internal and external platforms, and using AI tools to accelerate your and your team's productivity. We are looking for someone who handles change well, treats process as something to improve rather than defend, and sees highly collaborative AI-assisted development as a normal part of how teams work now." That's the About The Role content. Then Responsibilities heading:Responsibilities
Then list items: each sentence starting with a verb. We'll make- for each.
List:
- Design, build, and maintain front-end applications and marketing sites on Sanity CMS, shipping changes end-to-end on medium-to-large sites, from content schema through rendered page.
- Partner with marketing, content, and SEO/GEO stakeholders to turn business and content needs into scalable, maintainable frontend architecture for global teams.
- Build reusable components, templates, and tooling that let authors and other non-engineers create and manage content confidently and safely.
- Own performance, accessibility, and technical SEO/AI-crawler readiness across our web properties.
- Integrate with third-party services and APIs (analytics, marketing automation, personalization) from the frontend as part of the broader web ecosystem.
- Use AI-assisted development tools (Claude Code, Copilot, or internal tooling) as a standard part of your workflow for prototyping, code review, refactoring, and documentation.
- Take part in an agile team: sprint planning, code review, retros, and ongoing process improvement.
- Adapt as priorities, tooling, or requirements shift. This is a fast-moving environment, and comfort with ambiguity matters as much as technical depth.
- Collaborate with design, product marketing, and other teams.
Note: Some items have two sentences; we can keep as one li.
Then Qualifications heading:
Qualifications
List: - 5+ years of professional front-end web development experience. - Hands-on production experience with Sanity CMS (or a comparable headless/structured-content CMS like Contentful, Contentstack, or Storyblok that uses GraphQL), with a willingness to go deep on Sanity and its GROQ query language specifically. - Strong proficiency in TypeScript and a component-based frontend framework (React, Astro, Next.js, or similar). - Solid understanding of frontend architecture: server-side rendering or static generation, component design, state management, and build tooling. - Experience working in agile/scrum environments with iterative delivery and shifting priorities. - Real, everyday use of AI coding tools in an engineering workflow, not just passing familiarity. - Strong collaboration and communication skills, and comfort working directly with non-engineering stakeholders like marketing and content teams. - Bachelor's degree in Computer Science, Engineering, or equivalent practical experience. Then Success Profile heading:Success Profile
List: - Owns ambiguity and changes well, without needing every requirement locked down up front. - Genuinely interested in getting better at AI-assisted development, not just tolerating it. - Collaborative by default. Sees marketing, production, editorial, and growth partners as co-owners of the web experience. - Pragmatic: balances technical craft with the pace of a marketing-driven web team. Then Why Join Us heading:Why Join Us
Prose: "Work on high-visibility web properties for a global cybersecurity leader going through a major brand evolution (TrendAI). Join a small, close-knit team where your technical decisions shape how millions of visitors experience the brand, with real room to bring in modern tooling and better ways of working." Then What We Offer You heading:What We Offer You
We need to turn benefits list into- . The benefits list:
- 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
Also there is a paragraph before list: "You're important to us. What matters to you, matters to us too. Trend Micro provides benefit options for you and your family." That's prose; we can put as a
under the heading before the list. Then after list there is paragraph: "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." That's also prose; we can add another
after list. Then there is "Be Passionate. Be Innovative. Be a Trender." That's a tagline; maybe we can include as a
after the previous paragraph? It's not a heading; we can keep as a
. Then there is visa sponsorship statement: "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)." This is important substantive info; we should keep it. Where to place? Could be its own section? Not a heading in original. Could be a
after the Be Passionate paragraph. It's not boilerplate; it's a requirement. We'll keep as a
. Then there is diversity statement: "At Trend Micro, we embrace change, empower people, and encourage innovation in a connected world. Our diversity and multicultural workforce are key contributing factors to our success across the globe. Trend Micro provides equal employment opportunity for all applicants and employees. Trend Micro does not unlawfully discriminate on the basis of race, color, religion, sex, pregnancy and childbirth or related medical conditions, national origin, ancestry, age, physical or mental disability, medical condition, family care leave status, veteran status, marital status, sexual orientation, or gender identity." This is EEO boilerplate; instruction says remove EEO/equal-opportunity boilerplate. So we should remove that entire paragraph. Also earlier there is "TrendAI™, the
- . The benefits list:
- 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
Also there is a paragraph before list: "You're important to us. What matters to you, matters to us too. Trend Micro provides benefit options for you and your family." That's prose; we can put as a