Engineer Administrator
Integra · Houston, TX · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO etc. Must preserve all substantive info.
We need to parse the posting.
Content:
Location: Houston, TX Department: DEPENG, DEPADM
"The Opportunity" paragraph: description of role.
Then "What you will do?" list of duties.
Then "Required Qualifications" list.
Then "How We Support You" describing benefits.
Then "Come build with us" description of company.
Then "Equal Opportunity Statement" (boilerplate to remove).
We need sections: About the role (maybe from The Opportunity). Responsibilities (What you will do?). Requirements (maybe Required Qualifications). Qualifications (maybe education/experience? but we have Required Qualifications already). Skills (maybe proficiency in MS Office etc). Benefits (How We Support You). Pay (not mentioned explicitly; only "Competitive pay with incentive opportunities" is mentioned in benefits paragraph. That is pay info. So we can include Pay section with that sentence. Schedule: not mentioned. So omit Schedule.
We must not create sections with filler like "not specified". So only include sections with real content.
We need to use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO etc. Must preserve all substantive info.
We need to parse the posting.
Content:
Location: Houston, TX Department: DEPENG, DEPADM
"The Opportunity" paragraph: description of role.
Then "What you will do?" list of duties.
Then "Required Qualifications" list.
Then "How We Support You" describing benefits.
Then "Come build with us" description of company.
Then "Equal Opportunity Statement" (boilerplate to remove).
We need sections: About the role (maybe from The Opportunity). Responsibilities (What you will do?). Requirements (maybe Required Qualifications). Qualifications (maybe education/experience? but we have Required Qualifications already). Skills (maybe proficiency in MS Office etc). Benefits (How We Support You). Pay (not mentioned explicitly; only "Competitive pay with incentive opportunities" is mentioned in benefits paragraph. That is pay info. So we can include Pay section with that sentence. Schedule: not mentioned. So omit Schedule.
We must not create sections with filler like "not specified". So only include sections with real content.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail.
We need to extract details.
Let's break down.
Location and Department: Should we include? It's metadata; could be placed in a short
maybe under About the role? 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/department in a short paragraph maybe under About the role or separate? Probably include as a short
after heading? But they said "fold minor metadata into a short
or drop it." So we can include a short
with location and department.
Now sections:
About the role: The Opportunity paragraph(s). There are multiple sentences: "The Engineering Administrator provides administrative and operational support to the Engineering team by coordinating documentation, tracking projects, maintaining engineering records, and assisting with cross-functional communication. This role is responsible for ensuring engineering documentation, reports, drawings, and project information are accurate, organized, and maintained in accordance with company procedures. The Engineering Administrator serves as a key contributor for Engineering. This role helps keep projects running smoothly by providing structured administrative support that helps streamline engineering operations and allows engineers and project managers to concentrate on project execution and technical decision-making."
We can put that as
under About the role.
Responsibilities: The list after "What you will do?" It's a series of sentences each starting with a verb. Could be turned into
- . Must preserve all details.
List items:
- Provide administrative support to the Engineering department and engineering leadership.
- Maintain engineering documentation, including drawings, specifications, procedures, manuals, and revision histories.
- Coordinate document control activities, including engineering change notices (ECNs), engineering change orders (ECOs), and document revisions.
- Track engineering projects, action items, and deliverables to ensure deadlines are met.
- Prepare reports, presentations, meeting agendas, and meeting minutes.
- Schedule meetings, coordinate calendars, and organize project reviews.
- Assist with maintaining Bills of Materials (BOMs) within the ERP and Product Lifecycle Management (PLM) systems.
- Process and distribute engineering documentation to internal departments and external partners.
- Support product development by organizing project files and maintaining engineering databases.
- Coordinate approvals for engineering documentation and workflow processes.
- Maintain engineering records in accordance with company quality management procedures.
- Assist with supplier documentation, technical data requests, and engineering correspondence.
- Track prototype builds, testing documentation, and project milestones.
- Generate reports and metrics related to engineering activities and document status.
- Assist with onboarding new engineering employees by coordinating training records, system access, and department resources.
- Support continuous improvement initiatives by identifying opportunities to improve administrative and document management processes.
- Perform other administrative duties as assigned.
We need to keep all details.
Requirements: The "Required Qualifications" section includes bullet-like sentences. Could be turned into list.
List:
- 3+ years of administrative experience supporting engineering, manufacturing, construction, or technical teams.
- Experience working with engineering documentation and revision control.
- Experience coordinating multiple projects and priorities in a fast-paced environment.
- Experience with ERP, PLM, or document management systems preferred.
- Experience in manufacturing, industrial, construction, or data center environments is a plus.
- Associate degree in Business Administration, Engineering Technology, Project Management, or a related field preferred.
- Equivalent combination of education and experience will be considered.
- Proficient in Microsoft Office Suite, particularly Excel, Word, Outlook, and PowerPoint.
- Experience with SharePoint, Autodesk Vault, SolidWorks PDM, Windchill, or similar document management systems is preferred.
- Working knowledge of ERP systems such as SAP, Oracle, Epicor, or Microsoft Dynamics is preferred.
- Ability to maintain confidentiality with engineering and business information.
- Strong customer service mindset with the ability to work effectively across departments.
- Ability to identify process improvements and implement administrative efficiencies.
We could split into Requirements and Qualifications and Skills. But we have many overlapping. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have "Required Qualifications" which includes experience, education, skills. Could split: Requirements (experience), Qualifications (education), Skills (technical proficiencies). But we must not create sections with filler. We need to ensure each section has real specific content.
We could do:
- Requirements: experience items (3+ years admin experience, experience with engineering documentation, coordinating multiple projects, experience with ERP/PLM/document management systems preferred, experience in manufacturing etc).
- Qualifications: education items (Associate degree preferred, equivalent combination considered).
- Skills: proficiency in MS Office, experience with SharePoint etc, working knowledge of ERP, ability to maintain confidentiality, strong customer service, ability to identify process improvements.
But we need to check if any of these become vague like "preferred" etc. That's still specific content.
We must not repeat content across sections; but we can split as long as we preserve all info.
Let's extract each bullet and assign.
Original list:
1. 3+ years of administrative experience supporting engineering, manufacturing, construction, or technical teams. -> Requirements (experience)
2. Experience working with engineering documentation and revision control. -> Requirements
3. Experience coordinating multiple projects and priorities in a fast-paced environment. -> Requirements
4. Experience with ERP, PLM, or document management systems preferred. -> Requirements (or Skills) but it's experience; we can put under Requirements.
5. Experience in manufacturing, industrial, construction, or data center environments is a plus. -> Requirements
6. Associate degree in Business Administration, Engineering Technology, Project Management, or a related field preferred. -> Qualifications (education)
7. Equivalent combination of education and experience will be considered. -> Qualifications (education/experience)
8. Proficient in Microsoft Office Suite, particularly Excel, Word, Outlook, and PowerPoint. -> Skills
9. Experience with SharePoint, Autodesk Vault, SolidWorks PDM, Windchill, or similar document management systems is preferred. -> Skills (or Requirements) but it's experience with specific systems; could be Skills.
10. Working knowledge of ERP systems such as SAP, Oracle, Epicor, or Microsoft Dynamics is preferred. -> Skills
11. Ability to maintain confidentiality with engineering and business information. -> Skills (or Requirements) but it's ability; could be Skills.
12. Strong customer service mindset with the ability to work effectively across departments. -> Skills
13. Ability to identify process improvements and implement administrative efficiencies. -> Skills
We could also have a separate "Skills" section for items 8-13.
Now Benefits: from "How We Support You" paragraph. It includes several bullet-like sentences but not formatted as list. We need to turn into
- for any list of benefits. So we need to extract each benefit.
Paragraph:
"We believe your best work happens when you feel supported - professionally, personally, and financially. That’s why we offer a range of benefits designed to help you thrive, stay healthy, and plan for the future.
Performance-driven rewards – Competitive pay with incentive opportunities that recognize your results and contributions.
Comprehensive healthcare – Medical, dental, and vision coverage that supports you and your family’s total well-being.
Security and peace of mind – Life and disability insurance programs that provide protection when it matters most.
Flexible benefits options – A variety of voluntary benefits so you can personalize coverage to fit your needs.
Time to recharge – Generous paid time off to relax, travel, and maintain a healthy work-life balance.
Investing in your growth – Education assistance and tuition support to help you build skills and advance your career.
Planning for the future – Retirement and savings programs that help you achieve long-term financial confidence."
We can make each as
- .
Pay section: The posting mentions "Competitive pay with incentive opportunities" inside benefits. But we also have a Pay section heading possible. Since we have pay info, we could create a Pay section with that sentence. However the benefits paragraph already includes pay as a bullet. The instruction: "Prefer a few substantive sections over many thin ones." We could keep pay inside Benefits, but we also have a Benefits section. The Pay section would be thin if we separate just that sentence. Better to incorporate pay into Benefits. But we have a Benefits heading; we can include pay as one of the benefit items. So we don't need separate Pay section.
Schedule: not mentioned, omit.
Now "Come build with us" description of company: This is substantive info about company. Could be placed under About the role? Or maybe a separate section like "About the company". But headings list does not include About the company; only About the role, Responsibilities, etc. We could incorporate it into About the role as additional paragraph, or we could create a separate section like "About the company" but not in allowed headings. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should fit company description into About the role or maybe as a short paragraph under About the role. The About the role currently is about the role; we could add company description as another paragraph under About the role, but that might mix. However we could also create a section "About the company" but not in list; risk of being considered not allowed. Safer to incorporate into About the role as additional paragraph after the role description.
Thus About the role will have two paragraphs: role description and company description.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
... role description ...
... company description ...
Responsibilities
- ... each duty ...
...
Requirements
- ... experience items ...
...
Qualifications
- ... education items ...
...
Skills
- ... skill items ...
...
Benefits
- ... benefit items ...
...
We must ensure
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. We need to extract details. Let's break down. Location and Department: Should we include? It's metadata; could be placed in a short
maybe under About the role? 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/department in a short paragraph maybe under About the role or separate? Probably include as a short
after heading? But they said "fold minor metadata into a short
or drop it." So we can include a short
with location and department. Now sections: About the role: The Opportunity paragraph(s). There are multiple sentences: "The Engineering Administrator provides administrative and operational support to the Engineering team by coordinating documentation, tracking projects, maintaining engineering records, and assisting with cross-functional communication. This role is responsible for ensuring engineering documentation, reports, drawings, and project information are accurate, organized, and maintained in accordance with company procedures. The Engineering Administrator serves as a key contributor for Engineering. This role helps keep projects running smoothly by providing structured administrative support that helps streamline engineering operations and allows engineers and project managers to concentrate on project execution and technical decision-making." We can put that as
under About the role. Responsibilities: The list after "What you will do?" It's a series of sentences each starting with a verb. Could be turned into
- . Must preserve all details.
List items:
- Provide administrative support to the Engineering department and engineering leadership.
- Maintain engineering documentation, including drawings, specifications, procedures, manuals, and revision histories.
- Coordinate document control activities, including engineering change notices (ECNs), engineering change orders (ECOs), and document revisions.
- Track engineering projects, action items, and deliverables to ensure deadlines are met.
- Prepare reports, presentations, meeting agendas, and meeting minutes.
- Schedule meetings, coordinate calendars, and organize project reviews.
- Assist with maintaining Bills of Materials (BOMs) within the ERP and Product Lifecycle Management (PLM) systems.
- Process and distribute engineering documentation to internal departments and external partners.
- Support product development by organizing project files and maintaining engineering databases.
- Coordinate approvals for engineering documentation and workflow processes.
- Maintain engineering records in accordance with company quality management procedures.
- Assist with supplier documentation, technical data requests, and engineering correspondence.
- Track prototype builds, testing documentation, and project milestones.
- Generate reports and metrics related to engineering activities and document status.
- Assist with onboarding new engineering employees by coordinating training records, system access, and department resources.
- Support continuous improvement initiatives by identifying opportunities to improve administrative and document management processes.
- Perform other administrative duties as assigned.
We need to keep all details.
Requirements: The "Required Qualifications" section includes bullet-like sentences. Could be turned into list.
List:
- 3+ years of administrative experience supporting engineering, manufacturing, construction, or technical teams.
- Experience working with engineering documentation and revision control.
- Experience coordinating multiple projects and priorities in a fast-paced environment.
- Experience with ERP, PLM, or document management systems preferred.
- Experience in manufacturing, industrial, construction, or data center environments is a plus.
- Associate degree in Business Administration, Engineering Technology, Project Management, or a related field preferred.
- Equivalent combination of education and experience will be considered.
- Proficient in Microsoft Office Suite, particularly Excel, Word, Outlook, and PowerPoint.
- Experience with SharePoint, Autodesk Vault, SolidWorks PDM, Windchill, or similar document management systems is preferred.
- Working knowledge of ERP systems such as SAP, Oracle, Epicor, or Microsoft Dynamics is preferred.
- Ability to maintain confidentiality with engineering and business information.
- Strong customer service mindset with the ability to work effectively across departments.
- Ability to identify process improvements and implement administrative efficiencies.
We could split into Requirements and Qualifications and Skills. But we have many overlapping. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have "Required Qualifications" which includes experience, education, skills. Could split: Requirements (experience), Qualifications (education), Skills (technical proficiencies). But we must not create sections with filler. We need to ensure each section has real specific content.
We could do:
- Requirements: experience items (3+ years admin experience, experience with engineering documentation, coordinating multiple projects, experience with ERP/PLM/document management systems preferred, experience in manufacturing etc).
- Qualifications: education items (Associate degree preferred, equivalent combination considered).
- Skills: proficiency in MS Office, experience with SharePoint etc, working knowledge of ERP, ability to maintain confidentiality, strong customer service, ability to identify process improvements.
But we need to check if any of these become vague like "preferred" etc. That's still specific content.
We must not repeat content across sections; but we can split as long as we preserve all info.
Let's extract each bullet and assign.
Original list:
1. 3+ years of administrative experience supporting engineering, manufacturing, construction, or technical teams. -> Requirements (experience)
2. Experience working with engineering documentation and revision control. -> Requirements
3. Experience coordinating multiple projects and priorities in a fast-paced environment. -> Requirements
4. Experience with ERP, PLM, or document management systems preferred. -> Requirements (or Skills) but it's experience; we can put under Requirements.
5. Experience in manufacturing, industrial, construction, or data center environments is a plus. -> Requirements
6. Associate degree in Business Administration, Engineering Technology, Project Management, or a related field preferred. -> Qualifications (education)
7. Equivalent combination of education and experience will be considered. -> Qualifications (education/experience)
8. Proficient in Microsoft Office Suite, particularly Excel, Word, Outlook, and PowerPoint. -> Skills
9. Experience with SharePoint, Autodesk Vault, SolidWorks PDM, Windchill, or similar document management systems is preferred. -> Skills (or Requirements) but it's experience with specific systems; could be Skills.
10. Working knowledge of ERP systems such as SAP, Oracle, Epicor, or Microsoft Dynamics is preferred. -> Skills
11. Ability to maintain confidentiality with engineering and business information. -> Skills (or Requirements) but it's ability; could be Skills.
12. Strong customer service mindset with the ability to work effectively across departments. -> Skills
13. Ability to identify process improvements and implement administrative efficiencies. -> Skills
We could also have a separate "Skills" section for items 8-13.
Now Benefits: from "How We Support You" paragraph. It includes several bullet-like sentences but not formatted as list. We need to turn into
- for any list of benefits. So we need to extract each benefit. Paragraph: "We believe your best work happens when you feel supported - professionally, personally, and financially. That’s why we offer a range of benefits designed to help you thrive, stay healthy, and plan for the future. Performance-driven rewards – Competitive pay with incentive opportunities that recognize your results and contributions. Comprehensive healthcare – Medical, dental, and vision coverage that supports you and your family’s total well-being. Security and peace of mind – Life and disability insurance programs that provide protection when it matters most. Flexible benefits options – A variety of voluntary benefits so you can personalize coverage to fit your needs. Time to recharge – Generous paid time off to relax, travel, and maintain a healthy work-life balance. Investing in your growth – Education assistance and tuition support to help you build skills and advance your career. Planning for the future – Retirement and savings programs that help you achieve long-term financial confidence." We can make each as
- .
Pay section: The posting mentions "Competitive pay with incentive opportunities" inside benefits. But we also have a Pay section heading possible. Since we have pay info, we could create a Pay section with that sentence. However the benefits paragraph already includes pay as a bullet. The instruction: "Prefer a few substantive sections over many thin ones." We could keep pay inside Benefits, but we also have a Benefits section. The Pay section would be thin if we separate just that sentence. Better to incorporate pay into Benefits. But we have a Benefits heading; we can include pay as one of the benefit items. So we don't need separate Pay section.
Schedule: not mentioned, omit.
Now "Come build with us" description of company: This is substantive info about company. Could be placed under About the role? Or maybe a separate section like "About the company". But headings list does not include About the company; only About the role, Responsibilities, etc. We could incorporate it into About the role as additional paragraph, or we could create a separate section like "About the company" but not in allowed headings. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should fit company description into About the role or maybe as a short paragraph under About the role. The About the role currently is about the role; we could add company description as another paragraph under About the role, but that might mix. However we could also create a section "About the company" but not in list; risk of being considered not allowed. Safer to incorporate into About the role as additional paragraph after the role description. Thus About the role will have two paragraphs: role description and company description. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce:
About the role
... role description ...
... company description ...
Responsibilities
- ... each duty ... ...
Requirements
- ... experience items ... ...
Qualifications
- ... education items ... ...
Skills
- ... skill items ... ...
Benefits
- ... benefit items ... ...
- . Must preserve all details.
List items:
- Provide administrative support to the Engineering department and engineering leadership.
- Maintain engineering documentation, including drawings, specifications, procedures, manuals, and revision histories.
- Coordinate document control activities, including engineering change notices (ECNs), engineering change orders (ECOs), and document revisions.
- Track engineering projects, action items, and deliverables to ensure deadlines are met.
- Prepare reports, presentations, meeting agendas, and meeting minutes.
- Schedule meetings, coordinate calendars, and organize project reviews.
- Assist with maintaining Bills of Materials (BOMs) within the ERP and Product Lifecycle Management (PLM) systems.
- Process and distribute engineering documentation to internal departments and external partners.
- Support product development by organizing project files and maintaining engineering databases.
- Coordinate approvals for engineering documentation and workflow processes.
- Maintain engineering records in accordance with company quality management procedures.
- Assist with supplier documentation, technical data requests, and engineering correspondence.
- Track prototype builds, testing documentation, and project milestones.
- Generate reports and metrics related to engineering activities and document status.
- Assist with onboarding new engineering employees by coordinating training records, system access, and department resources.
- Support continuous improvement initiatives by identifying opportunities to improve administrative and document management processes.
- Perform other administrative duties as assigned.
We need to keep all details.
Requirements: The "Required Qualifications" section includes bullet-like sentences. Could be turned into list.
List:
- 3+ years of administrative experience supporting engineering, manufacturing, construction, or technical teams.
- Experience working with engineering documentation and revision control.
- Experience coordinating multiple projects and priorities in a fast-paced environment.
- Experience with ERP, PLM, or document management systems preferred.
- Experience in manufacturing, industrial, construction, or data center environments is a plus.
- Associate degree in Business Administration, Engineering Technology, Project Management, or a related field preferred.
- Equivalent combination of education and experience will be considered.
- Proficient in Microsoft Office Suite, particularly Excel, Word, Outlook, and PowerPoint.
- Experience with SharePoint, Autodesk Vault, SolidWorks PDM, Windchill, or similar document management systems is preferred.
- Working knowledge of ERP systems such as SAP, Oracle, Epicor, or Microsoft Dynamics is preferred.
- Ability to maintain confidentiality with engineering and business information.
- Strong customer service mindset with the ability to work effectively across departments.
- Ability to identify process improvements and implement administrative efficiencies.
We could split into Requirements and Qualifications and Skills. But we have many overlapping. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have "Required Qualifications" which includes experience, education, skills. Could split: Requirements (experience), Qualifications (education), Skills (technical proficiencies). But we must not create sections with filler. We need to ensure each section has real specific content.
We could do:
- Requirements: experience items (3+ years admin experience, experience with engineering documentation, coordinating multiple projects, experience with ERP/PLM/document management systems preferred, experience in manufacturing etc).
- Qualifications: education items (Associate degree preferred, equivalent combination considered).
- Skills: proficiency in MS Office, experience with SharePoint etc, working knowledge of ERP, ability to maintain confidentiality, strong customer service, ability to identify process improvements.
But we need to check if any of these become vague like "preferred" etc. That's still specific content.
We must not repeat content across sections; but we can split as long as we preserve all info.
Let's extract each bullet and assign.
Original list:
1. 3+ years of administrative experience supporting engineering, manufacturing, construction, or technical teams. -> Requirements (experience)
2. Experience working with engineering documentation and revision control. -> Requirements
3. Experience coordinating multiple projects and priorities in a fast-paced environment. -> Requirements
4. Experience with ERP, PLM, or document management systems preferred. -> Requirements (or Skills) but it's experience; we can put under Requirements.
5. Experience in manufacturing, industrial, construction, or data center environments is a plus. -> Requirements
6. Associate degree in Business Administration, Engineering Technology, Project Management, or a related field preferred. -> Qualifications (education)
7. Equivalent combination of education and experience will be considered. -> Qualifications (education/experience)
8. Proficient in Microsoft Office Suite, particularly Excel, Word, Outlook, and PowerPoint. -> Skills
9. Experience with SharePoint, Autodesk Vault, SolidWorks PDM, Windchill, or similar document management systems is preferred. -> Skills (or Requirements) but it's experience with specific systems; could be Skills.
10. Working knowledge of ERP systems such as SAP, Oracle, Epicor, or Microsoft Dynamics is preferred. -> Skills
11. Ability to maintain confidentiality with engineering and business information. -> Skills (or Requirements) but it's ability; could be Skills.
12. Strong customer service mindset with the ability to work effectively across departments. -> Skills
13. Ability to identify process improvements and implement administrative efficiencies. -> Skills
We could also have a separate "Skills" section for items 8-13.
Now Benefits: from "How We Support You" paragraph. It includes several bullet-like sentences but not formatted as list. We need to turn into