Stakeholder Management Lead – TDIS & Strategic Initiatives

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Job Title: Stakeholder Management Lead – TDIS & Strategic Initiatives Agency Texas A&M Engineering Department Civil Engineering (but we don't output title as heading). - Job Location: College Station, Texas. - Job Type: Staff. - Proposed Minimum Salary: Commensurate (no specific number) -> we should NOT create Pay section because it's not specific (commensurate with experience). According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Here salary is "Commencement"? It says "Proposed Minimum Salary Commensurate". That's not a specific amount, it's vague. So we should not include Pay section. - Schedule: Not mentioned. So no Schedule. - Benefits: The posting includes a paragraph: "Texas A&M Engineering provides an outstanding benefits package including but not limited to: ..." then lists many benefits. So we can include Benefits section with that list. - About the role: There's a "Job Description Purpose:" paragraph describing purpose. Also "Why work for Texas A&M Engineering?" paragraph describing who we are. Could be About the role or About the department. We need to decide sections. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. Let's extract: About the role: Could be the "Why work for Texas A&M Engineering?" and "Job Description Purpose:" maybe also "About Civil Engineering". But "About Civil Engineering" is more about department. Might fit under About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role containing description of role and purpose. Could also include "About Civil Engineering" as part of About the role? Might be okay. Responsibilities: list bullet points. Requirements: "What we need: Bachelor’s degree in related field. An equivalent combination of education and experience may be considered. Seven years of related experience." Qualifications: "What is helpful: 7–10 years of progressively responsible experience in areas such as public-sector partnerships, emergency management, technology/data implementation, stakeholder management, program/project management, or a related field." Skills: Not explicitly listed but could be implied from responsibilities and qualifications. However we should not create a Skills section unless there is explicit content. The posting does not have a separate skills list. So we should omit Skills. Benefits: as described. Pay: Not specific -> omit. Schedule: not mentioned -> omit. We also need to include location and job type maybe as a short

under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and job type in a short paragraph maybe under About the role or at top. We must preserve all substantive information. So we need to include location, job type, maybe department (Civil Engineering). Also mention that it's Staff. We need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the "Helpful Applicant Information Required Materials for Application:" etc. Also remove "Compensation Philosophy:" etc? That's maybe substantive? It's about compensation philosophy but not specific pay. Might be considered boilerplate? It's generic statement. Might be considered boilerplate; but it's not about specific benefits. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Compensation philosophy is not exactly those, but could be considered generic. However it's substantive about compensation philosophy. Might keep? But we have no Pay section; we could include it under Benefits? Not exactly. Might be safer to omit as it's not specific benefit. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep compensation philosophy if it's substantive. However it's generic but still part of posting. The rule about Pay section: only create if posting actually states them. Compensation philosophy is not a pay figure, but it's still about compensation. Could be included in a

under About the role or maybe a separate section? There's no specific heading for compensation philosophy. Could fold into Benefits? Not exactly. Might be okay to include as a paragraph under About the role. But we need to avoid duplication: there is also "Compensation Philosophy: Recruit and retain high-performing workforce through competitive compensation and career development including career pathing, coaching and skills development. Offer total rewards, flexible benefits, professional development, performance recognition and work-life balance. Ensure resources are readily available and utilized to attract and retain the highest quality researchers, faculty, and staff." This is somewhat similar to benefits description but more generic. Could be considered boilerplate. I'd lean to omit because it's not specific benefit details. Also need to remove "Employment Eligibility Verification", "All positions are security-sensitive", "Equal Opportunity/Veterans/Disability Employer." Those are EEO/legal boilerplate, remove. Also remove "Helpful Applicant Information Required Materials for Application:" etc. Also remove "Work Location: Main Campus – College Station, TX." but we need location; we can keep location in a short p. Now let's craft HTML. We'll start with a

for metadata: Job Location: College Station, Texas. Job Type: Staff. Department: Civil Engineering (maybe). Or we can incorporate into About the role. Then

About the role

with paragraphs: Why work for Texas A&M Engineering? (the who we are paragraph) and Job Description Purpose paragraph. Also maybe include About Civil Engineering paragraph? That is about department mission; could be included under About the role as well. We need to preserve all substantive info: The "Who we are" paragraph about Engineering history, mission, TEES, etc. That's substantive. The "Job Description Purpose:" paragraph about stakeholder adoption strategies etc. The "About Civil Engineering" paragraph about mission of Zachry Department. We'll include those as separate

under About the role. Then

Responsibilities

with

• each responsibility. Responsibilities list from posting: - Developing and executing stakeholder adoption strategies. - Managing relationships with emergency management agencies, state and local government partners, nonprofits, VOADs, philanthropic and community organizations. - Recruiting and onboarding users - Providing training and implementation support; and helping organizations integrate TDIS and TDIS AI into their operational workflows. - Serve as a bridge between external stakeholders and IDRT’s technical and research teams by identifying adoption barriers, translating user needs into actionable requirements, and helping inform future platform development. Note there is a missing period after "users". We'll keep as is. Then

  Requirements

  with

  maybe bullet? It's not a list but we can put as

  . Could also make

  but not required. We'll use

  . Content: Bachelor’s degree in related field. An equivalent combination of education and experience may be considered. Seven years of related experience. Then

  Qualifications

  with

  : What is helpful: 7–10 years of progressively responsible experience in areas such as public-sector partnerships, emergency management, technology/data implementation, stakeholder management, program/project management, or a related field. Then

  Benefits

  with
  • each benefit. Benefits list: - Competitive medical insurance benefits through Blue Cross and Blue Shield of Texas and Prescription coverage by Express Scripts. - Options for Vision, Dental, Life, and Long-Term Disability insurance. - A defined benefit retirement plan with the Teacher Retirement System of Texas (TRS) with 8.25% employer contribution. - Additional Voluntary Retirement Programs: Tax Deferred Account 403(b) and a Deferred Compensation Program 457(b). - Flexible spending account options for medical and childcare expenses - Generous paid time off with holidays, vacation and sick leave. - Robust free training access through LinkedIn Learning plus professional development opportunities. - Tuition assistance and Educational release time to further your academic pursuits. - Access to Engineer Your Wellness programs that provide opportunities for employees to engage in health and fitness. - Wellness release time offered to employees to promote work/life balance. Note there is a missing period after "expenses". We'll keep. We should not include "Texas A&M Engineering provides an outstanding benefits package including but not limited to:" as heading; just list. Now ensure we didn't include any boilerplate. Check for duplicated lines: The responsibilities list had some duplication? Not really. Now produce HTML fragment. We need to output only HTML, no markdown fences. Let's construct:

    Job Location: College Station, Texas. Job Type: Staff. Department: Civil Engineering.

    About the role

    Why work for Texas A&M Engineering? Engineering has been part of Texas A&M University since its opening in 1876 as the Agricultural and Mechanical College of Texas. Today, the College of Engineering is the largest college on the College Station campus with more than 25,000 engineering students enrolled in 15 departments. Its mission is to serve Texas, the nation and the global community by providing engineering graduates who are well-founded in engineering fundamentals, instilled with the highest standards of professional and ethical behavior, and prepared to meet the complex technical challenges of society. As the research arm of Engineering, the Texas A&M Engineering Experiment Station (TEES) is a state agency within the Texas A&M University System with a mission to improve lives through basic and applied engineering research, workforce development and technology transition. Our collaborations with industry, academia and government provide cutting-edge solutions to global technical challenges. We are deeply committed to recruiting and retaining a talented workforce that embraces our core values of Respect, Excellence, Leadership, Loyalty, Integrity, and Service, by offering competitive salaries, an array of benefits, an extensive support network, and above all, an enriching and highly collaborative working community that is deeply passionate about our vision for higher education, research, and public service.

    Job Description Purpose: The Project Manager III would have primary responsibility for developing and executing stakeholder adoption strategies; managing relationships with emergency management agencies, state and local government partners, nonprofits, VOADs, philanthropic and community organizations; recruiting and onboarding users; providing training and implementation support; and helping organizations integrate TDIS and TDIS AI into their operational workflows. The position would also serve as a bridge between external stakeholders and IDRT’s technical and research teams by identifying adoption barriers, translating user needs into actionable requirements, and helping inform future platform development.

    About Civil Engineering The mission of the Zachry Department of Civil and Environmental Engineering at Texas A&M University is to prepare our graduates to become professional engineers and leaders in the engineering profession by providing our students with a solid education that will enable them to integrate fundamental scientific engineering principles and that will couple with the latest technological advances to facilitate the development of their problem-solving skills. Additionally, the department provides opportunities for educational enhancement through meaningful interactions with the profession. In summary, we expect our graduates to be fully prepared for life-long learning experiences that will strengthen their abilities to successfully and effectively solve the complex engineering problems facing society.

    Responsibilities

    • Developing and executing stakeholder adoption strategies.
    • Managing relationships with emergency management agencies, state and local government partners, nonprofits, VOADs, philanthropic and community organizations.
    • Recruiting and onboarding users
    • Providing training