Raider Immersion Intern - Team Lead
for each heading only if there is real content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Job Title: Raider Immersion Intern - Team Lead (but not used as heading)
- Department: Center for Civics, Culture, and Workforce Development
- Job Summary/Basic Function: Under general direction, the Team Lead will oversee a multidisciplinary student team (undergraduate and graduate) working on an open-source, industry-sponsored project as part of the Raider Immersion Program. The Team Lead serves as a primary liaison between Wright State University, the sponsoring organization(s), the Technical Strategist, and the Center for Civics, Culture and Workforce Development. The project supports the sponsoring organization(s) in the design and development of solutions aligned with the project's scope and objectives. The Team Lead is responsible for ensuring successful project delivery, managing team operations, and facilitating collaboration among stakeholders.
- Minimum Qualifications: Enrollment at Wright State University (undergraduate or graduate level). Applicants must be U.S. citizens to meet federal contract requirements. Demonstrated leadership experience in academic, technical, or project settings. Experience or coursework in project management, administration, or technical disciplines. Strong organizational and communication skills. Ability to manage multiple priorities and coordinate across diverse technical domains.
- Preferred Qualifications: Experience working with multidisciplinary teams. Technical proficiency in one or more of the following areas: Scripting/programming (Python preferred). User interface design / development. Communicating with software APIs. Data analysis and modeling.
- Essential Functions And Percent Of Time: list with percentages.
We need to decide sections: About the role (maybe job summary), Responsibilities (essential functions), Requirements (minimum qualifications), Qualifications (maybe preferred?), Skills (maybe technical proficiency?), Benefits, Pay, Schedule.
We have no explicit Benefits, Pay, Schedule info. There's Position FTE: 70% (that's schedule? maybe part-time). Minimum Annual Or Hourly Rate Salary Band: UC HINTN (not a clear number). That's vague; we should not create Pay or Schedule sections unless posting actually states them. It says "Minimum Annual Or Hourly Rate Salary Band: UC HINTN". That's not a specific number; it's a band placeholder. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay or Schedule sections because they are not specific. However, we have Position FTE: 70% which indicates part-time schedule. That could be considered schedule info. But is it specific? It says Position FTE: 70% (i.e., 70% full-time). That is specific enough? It's a percentage. Might be considered schedule. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Position FTE: 70% which is schedule-related. So we could include a Schedule section with that info. However, we need to avoid filler like "varies". 70% is specific. So we can include Schedule.
Benefits: none stated. So omit Benefits.
Pay: Salary band UC HINTN is vague; not a specific number; likely placeholder. So omit Pay.
Thus sections: About the role (job summary), Responsibilities (essential functions with percentages), Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe technical proficiency list), Schedule (FTE 70%). Could also combine Requirements and Qualifications? But we have separate headings allowed. We'll include them if content.
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.
Let's extract details precisely.
About the role: The job summary paragraph. We'll put that in
.
Responsibilities: Essential Functions And Percent Of Time list:
- Project Delivery and Oversight - (30%)
Ensure timely and successful completion of all project deliverables.
Lead, mentor, and coordinate a team of student interns (bachelor's and master's level) across engineering and technical domains
Oversee onboarding, timecard management, and administrative functions for all team members.
Support training for team members as needed for project tools, methods, and software.
- Technical Leadership & Problem Solving - (30%)
Guide the team in understanding and implementing the technical requirements
Ensure the solution is user-friendly, with clear documentation and support for future enhancements.
- Coordination & Communication - (30%)
Serve as the primary point of contact between the student team, Technical Strategist, and sponsoring agency representatives, and the Center for Civics, Culture and Workforce Development.
Coordinate with the Technical Strategist to clarify technical requirements, project scope, and deliverables.
Facilitate communication and feedback loops with sponsoring agency, including scheduling and documenting meetings.
Monitor progress, manage risks, and implement corrective actions.
- Administrative Functions - (10%)
Manage documentation, reporting, and compliance records for the project.
Ensure all administrative processes (onboarding, payroll, training records) are completed accurately and on time.
We need to preserve the percentages and bullet points. Use
- for each duty? Could have nested lists? Probably each main function as
- with sub-bullets? But rule: Use
- for any list of duties/requirements/benefits. Could treat each bullet as
- . For sub-items we could also use
- inside. That's okay.
Requirements: Minimum Qualifications list:
- Enrollment at Wright State University (undergraduate or graduate level).
- Applicants must be U.S. citizens to meet federal contract requirements.
- Demonstrated leadership experience in academic, technical, or project settings.
- Experience or coursework in project management, administration, or technical disciplines.
- Strong organizational and communication skills.
- Ability to manage multiple priorities and coordinate across diverse technical domains.
Qualifications: Preferred Qualifications list:
- Experience working with multidisciplinary teams.
- Technical proficiency in one or more of the following areas:
- Scripting/programming (Python preferred).
- User interface design / development.
- Communicating with software APIs.
- Data analysis and modeling.
Skills: Could be derived from technical proficiency list; but we already have that under Preferred Qualifications. Could create Skills section for those technical proficiencies. However, we must not duplicate content? The rule says preserve ALL substantive information; do not invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could put technical proficiency under Skills, and keep Preferred Qualifications as other preferred qualifications (experience working with multidisciplinary teams). But the posting lumps them together under Preferred Qualifications. We could split: Preferred Qualifications (experience working with multidisciplinary teams) and Skills (technical proficiency). That seems reasonable and preserves all info.
Schedule: Position FTE: 70% (maybe also mention it's part-time). We'll put that in
.
Now ensure we don't include boilerplate: EEO statement, Faculty Rank or Job Title, Job Category, Department (maybe we keep Department as part of About the role? The posting includes Department: Center for Civics, Culture, and Workforce Development. That's substantive. Should we include it? It's not under headings but we can include in About the role paragraph. The rule: preserve ALL substantive information. So we should include Department somewhere. Could add a sentence: "Department: Center for Civics, Culture, and Workforce Development." Or incorporate into About the role.
Also Position FTE: 70% we already used.
Also Minimum Annual Or Hourly Rate Salary Band: UC HINTN we are omitting as vague.
Also EEO number etc omitted.
Also Special Instructions to Applicants (First Consideration Date, Closing Date, link) - those are application instructions; we must remove application instructions per rule. So drop those.
Also Copyright etc removed.
Now craft HTML.
Structure:
About the role
Under general direction, the Team Lead will oversee a multidisciplinary student team (undergraduate and graduate) working on an open-source, industry-sponsored project as part of the Raider Immersion Program. The Team Lead serves as a primary liaison between Wright State University, the sponsoring organization(s), the Technical Strategist, and the Center for Civics, Culture and Workforce Development. The project supports the sponsoring organization(s) in the design and development of solutions aligned with the project's scope and objectives. The Team Lead is responsible for ensuring successful project delivery, managing team operations, and facilitating collaboration among stakeholders. Department: Center for Civics, Culture, and Workforce Development.
Responsibilities
- Project Delivery and Oversight - (30%)
- Ensure timely and successful completion of all project deliverables.
- Lead, mentor, and coordinate a team of student interns (bachelor's and master's level) across engineering and technical domains.
- Oversee onboarding, timecard management, and administrative functions for all team members.
- Support training for team members as needed for project tools, methods, and software.
- Technical Leadership & Problem Solving - (30%)
- Guide the team in understanding and implementing the technical requirements.
- Ensure the solution is user-friendly, with clear documentation and support for future enhancements.
- Coordination & Communication - (30%)
- Serve as the primary point of contact between the student team, Technical Strategist, and sponsoring agency representatives, and the Center for Civics, Culture and Workforce Development.
- Coordinate with the Technical Strategist to clarify technical requirements, project scope, and deliverables.
- Facilitate communication and feedback loops with sponsoring agency, including scheduling and documenting meetings.
- Monitor progress, manage risks, and implement corrective actions.
- Administrative Functions - (10%)
- Manage documentation, reporting, and compliance records for the project.
- Ensure all administrative processes (onboarding, payroll, training records) are completed accurately and on time.
Requirements
- Enrollment at Wright State University (undergraduate or graduate level).
- Applicants must be U.S. citizens to meet federal contract requirements.
- Demonstrated leadership experience in academic, technical, or project settings.
- Experience or coursework in project management, administration, or technical disciplines.
- Strong organizational and communication skills.
- Ability to manage multiple priorities and coordinate across diverse technical domains.
Qualifications
- Experience working with multidisciplinary teams.
Skills
- Technical proficiency in one or more of the following areas:
- Scripting/programming (Python preferred).
- User interface design / development.
- Communicating with software APIs.
- Data analysis and modeling.
Schedule
Position FTE: 70% (part-time).
Check: Did we preserve all substantive info? We included Department, job summary, responsibilities with percentages, minimum qualifications, preferred qualification (experience working with multidisciplinary teams), technical proficiency as skills, schedule FTE. We omitted salary band (v
. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details precisely. About the role: The job summary paragraph. We'll put that in
. Responsibilities: Essential Functions And Percent Of Time list: - Project Delivery and Oversight - (30%) Ensure timely and successful completion of all project deliverables. Lead, mentor, and coordinate a team of student interns (bachelor's and master's level) across engineering and technical domains Oversee onboarding, timecard management, and administrative functions for all team members. Support training for team members as needed for project tools, methods, and software. - Technical Leadership & Problem Solving - (30%) Guide the team in understanding and implementing the technical requirements Ensure the solution is user-friendly, with clear documentation and support for future enhancements. - Coordination & Communication - (30%) Serve as the primary point of contact between the student team, Technical Strategist, and sponsoring agency representatives, and the Center for Civics, Culture and Workforce Development. Coordinate with the Technical Strategist to clarify technical requirements, project scope, and deliverables. Facilitate communication and feedback loops with sponsoring agency, including scheduling and documenting meetings. Monitor progress, manage risks, and implement corrective actions. - Administrative Functions - (10%) Manage documentation, reporting, and compliance records for the project. Ensure all administrative processes (onboarding, payroll, training records) are completed accurately and on time. We need to preserve the percentages and bullet points. Use
- for each duty? Could have nested lists? Probably each main function as
- with sub-bullets? But rule: Use
- for any list of duties/requirements/benefits. Could treat each bullet as
- . For sub-items we could also use
- inside. That's okay.
Requirements: Minimum Qualifications list:
- Enrollment at Wright State University (undergraduate or graduate level).
- Applicants must be U.S. citizens to meet federal contract requirements.
- Demonstrated leadership experience in academic, technical, or project settings.
- Experience or coursework in project management, administration, or technical disciplines.
- Strong organizational and communication skills.
- Ability to manage multiple priorities and coordinate across diverse technical domains.
Qualifications: Preferred Qualifications list:
- Experience working with multidisciplinary teams.
- Technical proficiency in one or more of the following areas:
- Scripting/programming (Python preferred).
- User interface design / development.
- Communicating with software APIs.
- Data analysis and modeling.
Skills: Could be derived from technical proficiency list; but we already have that under Preferred Qualifications. Could create Skills section for those technical proficiencies. However, we must not duplicate content? The rule says preserve ALL substantive information; do not invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could put technical proficiency under Skills, and keep Preferred Qualifications as other preferred qualifications (experience working with multidisciplinary teams). But the posting lumps them together under Preferred Qualifications. We could split: Preferred Qualifications (experience working with multidisciplinary teams) and Skills (technical proficiency). That seems reasonable and preserves all info.
Schedule: Position FTE: 70% (maybe also mention it's part-time). We'll put that in
. Now ensure we don't include boilerplate: EEO statement, Faculty Rank or Job Title, Job Category, Department (maybe we keep Department as part of About the role? The posting includes Department: Center for Civics, Culture, and Workforce Development. That's substantive. Should we include it? It's not under headings but we can include in About the role paragraph. The rule: preserve ALL substantive information. So we should include Department somewhere. Could add a sentence: "Department: Center for Civics, Culture, and Workforce Development." Or incorporate into About the role. Also Position FTE: 70% we already used. Also Minimum Annual Or Hourly Rate Salary Band: UC HINTN we are omitting as vague. Also EEO number etc omitted. Also Special Instructions to Applicants (First Consideration Date, Closing Date, link) - those are application instructions; we must remove application instructions per rule. So drop those. Also Copyright etc removed. Now craft HTML. Structure:
About the role
Under general direction, the Team Lead will oversee a multidisciplinary student team (undergraduate and graduate) working on an open-source, industry-sponsored project as part of the Raider Immersion Program. The Team Lead serves as a primary liaison between Wright State University, the sponsoring organization(s), the Technical Strategist, and the Center for Civics, Culture and Workforce Development. The project supports the sponsoring organization(s) in the design and development of solutions aligned with the project's scope and objectives. The Team Lead is responsible for ensuring successful project delivery, managing team operations, and facilitating collaboration among stakeholders. Department: Center for Civics, Culture, and Workforce Development.
Responsibilities
- Project Delivery and Oversight - (30%)
- Ensure timely and successful completion of all project deliverables.
- Lead, mentor, and coordinate a team of student interns (bachelor's and master's level) across engineering and technical domains.
- Oversee onboarding, timecard management, and administrative functions for all team members.
- Support training for team members as needed for project tools, methods, and software.
- Technical Leadership & Problem Solving - (30%)
- Guide the team in understanding and implementing the technical requirements.
- Ensure the solution is user-friendly, with clear documentation and support for future enhancements.
- Coordination & Communication - (30%)
- Serve as the primary point of contact between the student team, Technical Strategist, and sponsoring agency representatives, and the Center for Civics, Culture and Workforce Development.
- Coordinate with the Technical Strategist to clarify technical requirements, project scope, and deliverables.
- Facilitate communication and feedback loops with sponsoring agency, including scheduling and documenting meetings.
- Monitor progress, manage risks, and implement corrective actions.
- Administrative Functions - (10%)
- Manage documentation, reporting, and compliance records for the project.
- Ensure all administrative processes (onboarding, payroll, training records) are completed accurately and on time.
Requirements
- Enrollment at Wright State University (undergraduate or graduate level).
- Applicants must be U.S. citizens to meet federal contract requirements.
- Demonstrated leadership experience in academic, technical, or project settings.
- Experience or coursework in project management, administration, or technical disciplines.
- Strong organizational and communication skills.
- Ability to manage multiple priorities and coordinate across diverse technical domains.
Qualifications
- Experience working with multidisciplinary teams.
Skills
- Technical proficiency in one or more of the following areas:
- Scripting/programming (Python preferred).
- User interface design / development.
- Communicating with software APIs.
- Data analysis and modeling.
Schedule
Position FTE: 70% (part-time).
Check: Did we preserve all substantive info? We included Department, job summary, responsibilities with percentages, minimum qualifications, preferred qualification (experience working with multidisciplinary teams), technical proficiency as skills, schedule FTE. We omitted salary band (v - Project Delivery and Oversight - (30%)
- inside. That's okay.
Requirements: Minimum Qualifications list:
- Enrollment at Wright State University (undergraduate or graduate level).
- Applicants must be U.S. citizens to meet federal contract requirements.
- Demonstrated leadership experience in academic, technical, or project settings.
- Experience or coursework in project management, administration, or technical disciplines.
- Strong organizational and communication skills.
- Ability to manage multiple priorities and coordinate across diverse technical domains.
Qualifications: Preferred Qualifications list:
- Experience working with multidisciplinary teams.
- Technical proficiency in one or more of the following areas:
- Scripting/programming (Python preferred).
- User interface design / development.
- Communicating with software APIs.
- Data analysis and modeling.
Skills: Could be derived from technical proficiency list; but we already have that under Preferred Qualifications. Could create Skills section for those technical proficiencies. However, we must not duplicate content? The rule says preserve ALL substantive information; do not invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could put technical proficiency under Skills, and keep Preferred Qualifications as other preferred qualifications (experience working with multidisciplinary teams). But the posting lumps them together under Preferred Qualifications. We could split: Preferred Qualifications (experience working with multidisciplinary teams) and Skills (technical proficiency). That seems reasonable and preserves all info.
Schedule: Position FTE: 70% (maybe also mention it's part-time). We'll put that in