Director, Information Technology - Connected Insurance Platforms
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Why USAA?" maybe considered intro but could be part of About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections with those headings only if there is real specific content. We need to decide which sections to include.
We have content: About the role: could be the introductory paragraph about USAA mission and the opportunity description. That seems appropriate.
Responsibilities: corresponds to "What You'll Do" list.
Requirements/Qualifications/Skills: The posting has "What You Have" (requirements) and "What Sets You Apart" (preferred qualifications). Could split into Requirements (mandatory) and Qualifications (preferred) or Skills. We need to decide.
We have Pay: compensation range given.
Benefits: described.
Schedule: "We offer a flexible work environment that requires an individual to be in the office 4 days per week. This position can be based in one of the following locations: San Antonio, TX, or Plano, TX. Relocation assistance is not available for this position." That's schedule/location info. So we can put Schedule section.
We must not include sections with filler like "commensurate with experience". We have actual content.
We must not repeat job title. Not include "Why USAA?" as heading; we can incorporate that into About the role paragraph.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove duplicated lines: In "What You'll Do" there is a duplicated line: "Builds and oversees a team of employees for assigned functional area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities." appears twice. We should keep only one instance.
Also there is duplicated "Builds and oversees a team of employees for assigned technology support area..." and later again similar. We need to deduplicate.
We need to keep all substantive info but remove duplicates.
Let's extract content.
Intro: "Why USAA? At USAA, our mission is to empower our members to achieve financial security through highly competitive products, exceptional service and trusted advice. We seek to be the #1 choice for the military community and their families. Embrace a fulfilling career at USAA, where our core values – honesty, integrity, loyalty and service – define how we treat each other and our members. Be part of what truly makes us special and impactful. We are proud to support active-duty military spouses. USAA roles may offer remote or hybrid flexibility for active-duty military spouses consistent with applicable policy and business needs."
Then "The Opportunity USAA is seeking a Director, Information Technology to lead the strategy, delivery, and evolution of telematics technology capabilities supporting Auto and Property & Casualty Insurance. This leader will drive the development of scalable cloud-based data platforms, telematics products, and strategic partnerships that transform driving behavior and connected vehicle data into meaningful business outcomes. The ideal candidate brings deep experience in insurance technology, telematics ecosystems, and modern data platforms, combined with a passion for innovation, talent development, and delivering member value. As a technology leader, you will partner across engineering, product, data science, and business teams to advance usage-based insurance and telematics capabilities. You will help shape the future of connected insurance by leveraging cloud technologies, advanced analytics, and strategic industry partnerships to improve pricing, risk assessment, claims insights, and member experience."
Then "We offer a flexible work environment that requires an individual to be in the office 4 days per week. This position can be based in one of the following locations: San Antonio, TX, or Plano, TX. Relocation assistance is not available for this position."
Then "What You'll Do" list.
Then "What You Have" list.
Then "What Sets You Apart" list.
Then compensation range.
Then benefits description.
We need to map to sections:
About the role: combine Why USAA? + The Opportunity + maybe location/flexibility? But location/flexibility could go to Schedule. We'll keep About the role as mission/intro and opportunity description.
Responsibilities: What You'll Do (deduplicated).
Requirements: What You Have (mandatory). Could also include "What Sets You Apart" as Qualifications or Skills. We'll make Qualifications section for preferred qualifications.
Skills: maybe combine some skills from both? But we can keep Skills optional; but we need to avoid thin sections. Perhaps we can put Skills as part of Qualifications. But instruction says we can use those headings; we should only include sections with real specific content. We have content for Requirements (What You Have) and Qualifications (What Sets You Apart). We could also have Skills if we extract skill statements, but maybe better to just have Requirements and Qualifications.
Pay: compensation range.
Benefits: benefits description.
Schedule: work environment, location, relocation.
We must not include sections like "About the role" if we don't have content; we do.
Now we need to format.
We'll produce:
About the role
... (combined intro)
Responsibilities
- ... each duty
Requirements
- ... each requirement
Qualifications
- ... each preferred qualification
Benefits
... benefits paragraph
Pay
... compensation range paragraph
Schedule
... schedule/location paragraph
We need to ensure we don't include any boilerplate like "USAA does not provide visa sponsorship..." that's maybe part of Requirements? Actually it's a note about visa sponsorship; could be considered a requirement but it's a restriction. Should we include? It's substantive info about visa sponsorship. It's not a typical requirement but it's a condition. We could include it under Requirements as a note. However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship notice is not exactly EEO but could be considered a legal restriction. Not sure. The posting includes: "USAA does not provide visa sponsorship for this role. Please do not apply for this role if at any time (now or in the future) you will need immigration support (i.e., H-1B, TN, STEM OPT Training Plans, etc.)." This is a legal restriction; maybe we should keep it as part of Requirements or a separate note. It's substantive. I'd include it under Requirements as a bullet.
Also there is a line: "Compensation: USAA has an effective process for assessing market data and establishing ranges to ensure we remain competitive. You are paid within the salary range based on your experience and market data of the position. The actual salary for this role may vary by location. Employees may be eligible for pay incentives based on overall corporate and individual performance and at the discretion of the USAA Board of Directors." That's more detail about compensation; we can include in Pay section.
Also there is a line: "The above description reflects the details considered necessary to describe the principal functions of the job and should not be construed as a detailed description of all the work requirements that may be performed in the job." That's boilerplate; we should remove.
Also "Applications for this position are accepted on an ongoing basis, this posting will remain open until the position is filled. Thus, interested candidates are encouraged to apply the same day they view this posting." That's application instruction; remove.
Also "USAA is an Equal Opportunity Employer..." remove.
Now we need to deduplicate responsibilities list.
Let's extract responsibilities list from the posting:
"Responsible for developing, maintaining, testing, and monitoring an internal control environment, including preventative and detective controls, to effectively manage risks.
Builds and oversees a team of employees for assigned technology support area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities.
Oversees efforts in establishing documentation standards and quality assurance methodologies for technology support functions and ensure adherence to standards across teams.
Accountable for the identification, research, and analysis of end to end business, processes, and technology support opportunities.
Develops and oversees metrics for technology support capabilities and/or processes (KPIs, KRIs, etc.).
Creates a multi-year plan to operationalize a technology support strategy, with key milestones, deliverables, and realization targets.
Oversees the creation and execution of departmental budgets and forecasts for applicable technology support function.
Oversees the availability management of technology solutions / domains by applying strong change and incident management practices.
Works across multiple functional areas and influences future business strategy to be able to best utilize available technology support functions as well as future ones.
Stays abreast of industry trends and understands the direction of applicable technology support capabilities and ensures technology environment is agile enough to change quickly to support.
Builds successful stakeholder relationships with other IT and business leaders by developing a clear understanding of business needs, acting as a trusted advisor, and ensuring cost-effective delivery of technology support services to meet those needs.
Participates in the development of 3rd Party vendors strategy and provides oversight to ensure achievement of technology support objectives.
May provide oversight of vendor management activities including service agreements, staff augmentation and technology contracts.
Builds and oversees a team of employees for assigned functional area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities.
Ensures risks associated with business activities are effectively identified, measured, monitored, and controlled in accordance with risk and compliance policies and procedures."
Duplicate: "Builds and oversees a team of employees for assigned technology support area..." and later "Builds and oversees a team of employees for assigned functional area..." They are similar but not identical; one says technology support area, other says functional area. Might be considered distinct but both about team building. Could keep both? The instruction says remove duplicated lines. These are not exact duplicates but similar. Safer to keep both? Might be considered duplicated content. I'd keep only one generic: "Builds and oversees a team of employees for assigned area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities." But we risk losing nuance. However the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines means exact duplicates. The two lines are not exact duplicates; they differ in "technology support area" vs "functional area". So we can keep both.
Now requirements list:
"Bachelor's degree; OR 4 additional years of related experience beyond the minimum required may be substituted in lieu of a degree.
8+ years of experience in a technology function within Software Engineering, Application Development, Data Engineering, or Infrastructure environments.
Experience designing, building, and scaling cloud-based data platforms that ingest and process high-volume data streams using AWS, Azure, or GCP.
Experience partnering with insurance telematics providers (e.g., Arity, Cambridge Mobile Telematics (CMT), Octo) and/or vehicle OEMs.
Experience leading technology solutions through the full software development lifecycle, including requirements, design, development, testing, implementation, and support.
Strong technical knowledge across one or more domains including Application
- for any list of duties/requirements/benefits. For prose use
. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove duplicated lines: In "What You'll Do" there is a duplicated line: "Builds and oversees a team of employees for assigned functional area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities." appears twice. We should keep only one instance. Also there is duplicated "Builds and oversees a team of employees for assigned technology support area..." and later again similar. We need to deduplicate. We need to keep all substantive info but remove duplicates. Let's extract content. Intro: "Why USAA? At USAA, our mission is to empower our members to achieve financial security through highly competitive products, exceptional service and trusted advice. We seek to be the #1 choice for the military community and their families. Embrace a fulfilling career at USAA, where our core values – honesty, integrity, loyalty and service – define how we treat each other and our members. Be part of what truly makes us special and impactful. We are proud to support active-duty military spouses. USAA roles may offer remote or hybrid flexibility for active-duty military spouses consistent with applicable policy and business needs." Then "The Opportunity USAA is seeking a Director, Information Technology to lead the strategy, delivery, and evolution of telematics technology capabilities supporting Auto and Property & Casualty Insurance. This leader will drive the development of scalable cloud-based data platforms, telematics products, and strategic partnerships that transform driving behavior and connected vehicle data into meaningful business outcomes. The ideal candidate brings deep experience in insurance technology, telematics ecosystems, and modern data platforms, combined with a passion for innovation, talent development, and delivering member value. As a technology leader, you will partner across engineering, product, data science, and business teams to advance usage-based insurance and telematics capabilities. You will help shape the future of connected insurance by leveraging cloud technologies, advanced analytics, and strategic industry partnerships to improve pricing, risk assessment, claims insights, and member experience." Then "We offer a flexible work environment that requires an individual to be in the office 4 days per week. This position can be based in one of the following locations: San Antonio, TX, or Plano, TX. Relocation assistance is not available for this position." Then "What You'll Do" list. Then "What You Have" list. Then "What Sets You Apart" list. Then compensation range. Then benefits description. We need to map to sections: About the role: combine Why USAA? + The Opportunity + maybe location/flexibility? But location/flexibility could go to Schedule. We'll keep About the role as mission/intro and opportunity description. Responsibilities: What You'll Do (deduplicated). Requirements: What You Have (mandatory). Could also include "What Sets You Apart" as Qualifications or Skills. We'll make Qualifications section for preferred qualifications. Skills: maybe combine some skills from both? But we can keep Skills optional; but we need to avoid thin sections. Perhaps we can put Skills as part of Qualifications. But instruction says we can use those headings; we should only include sections with real specific content. We have content for Requirements (What You Have) and Qualifications (What Sets You Apart). We could also have Skills if we extract skill statements, but maybe better to just have Requirements and Qualifications. Pay: compensation range. Benefits: benefits description. Schedule: work environment, location, relocation. We must not include sections like "About the role" if we don't have content; we do. Now we need to format. We'll produce:
About the role
... (combined intro)
Responsibilities
- ... each duty
Requirements
- ... each requirement
Qualifications
- ... each preferred qualification
Benefits
... benefits paragraph
Pay
... compensation range paragraph
Schedule
... schedule/location paragraph
We need to ensure we don't include any boilerplate like "USAA does not provide visa sponsorship..." that's maybe part of Requirements? Actually it's a note about visa sponsorship; could be considered a requirement but it's a restriction. Should we include? It's substantive info about visa sponsorship. It's not a typical requirement but it's a condition. We could include it under Requirements as a note. However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship notice is not exactly EEO but could be considered a legal restriction. Not sure. The posting includes: "USAA does not provide visa sponsorship for this role. Please do not apply for this role if at any time (now or in the future) you will need immigration support (i.e., H-1B, TN, STEM OPT Training Plans, etc.)." This is a legal restriction; maybe we should keep it as part of Requirements or a separate note. It's substantive. I'd include it under Requirements as a bullet. Also there is a line: "Compensation: USAA has an effective process for assessing market data and establishing ranges to ensure we remain competitive. You are paid within the salary range based on your experience and market data of the position. The actual salary for this role may vary by location. Employees may be eligible for pay incentives based on overall corporate and individual performance and at the discretion of the USAA Board of Directors." That's more detail about compensation; we can include in Pay section. Also there is a line: "The above description reflects the details considered necessary to describe the principal functions of the job and should not be construed as a detailed description of all the work requirements that may be performed in the job." That's boilerplate; we should remove. Also "Applications for this position are accepted on an ongoing basis, this posting will remain open until the position is filled. Thus, interested candidates are encouraged to apply the same day they view this posting." That's application instruction; remove. Also "USAA is an Equal Opportunity Employer..." remove. Now we need to deduplicate responsibilities list. Let's extract responsibilities list from the posting: "Responsible for developing, maintaining, testing, and monitoring an internal control environment, including preventative and detective controls, to effectively manage risks. Builds and oversees a team of employees for assigned technology support area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities. Oversees efforts in establishing documentation standards and quality assurance methodologies for technology support functions and ensure adherence to standards across teams. Accountable for the identification, research, and analysis of end to end business, processes, and technology support opportunities. Develops and oversees metrics for technology support capabilities and/or processes (KPIs, KRIs, etc.). Creates a multi-year plan to operationalize a technology support strategy, with key milestones, deliverables, and realization targets. Oversees the creation and execution of departmental budgets and forecasts for applicable technology support function. Oversees the availability management of technology solutions / domains by applying strong change and incident management practices. Works across multiple functional areas and influences future business strategy to be able to best utilize available technology support functions as well as future ones. Stays abreast of industry trends and understands the direction of applicable technology support capabilities and ensures technology environment is agile enough to change quickly to support. Builds successful stakeholder relationships with other IT and business leaders by developing a clear understanding of business needs, acting as a trusted advisor, and ensuring cost-effective delivery of technology support services to meet those needs. Participates in the development of 3rd Party vendors strategy and provides oversight to ensure achievement of technology support objectives. May provide oversight of vendor management activities including service agreements, staff augmentation and technology contracts. Builds and oversees a team of employees for assigned functional area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities. Ensures risks associated with business activities are effectively identified, measured, monitored, and controlled in accordance with risk and compliance policies and procedures." Duplicate: "Builds and oversees a team of employees for assigned technology support area..." and later "Builds and oversees a team of employees for assigned functional area..." They are similar but not identical; one says technology support area, other says functional area. Might be considered distinct but both about team building. Could keep both? The instruction says remove duplicated lines. These are not exact duplicates but similar. Safer to keep both? Might be considered duplicated content. I'd keep only one generic: "Builds and oversees a team of employees for assigned area through ongoing execution of recruiting, development, retention, coaching and support, performance management, and managerial activities." But we risk losing nuance. However the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines means exact duplicates. The two lines are not exact duplicates; they differ in "technology support area" vs "functional area". So we can keep both. Now requirements list: "Bachelor's degree; OR 4 additional years of related experience beyond the minimum required may be substituted in lieu of a degree. 8+ years of experience in a technology function within Software Engineering, Application Development, Data Engineering, or Infrastructure environments. Experience designing, building, and scaling cloud-based data platforms that ingest and process high-volume data streams using AWS, Azure, or GCP. Experience partnering with insurance telematics providers (e.g., Arity, Cambridge Mobile Telematics (CMT), Octo) and/or vehicle OEMs. Experience leading technology solutions through the full software development lifecycle, including requirements, design, development, testing, implementation, and support. Strong technical knowledge across one or more domains including Application