Document Control Admin
Ducommun Incorporated · Huntsville, AR · 1 mo ago
On-siteAdministrativeFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the job posting.
Key sections:
- About the role? The posting includes "Provide/Create and Update internal documentation for production, test, quality and shipping. Maintain the latest information by confirming/updating the system for accuracy so that Ducommun can purchasing the correct piece parts, build, test, inspect and ship the unit to meet the customers requirements. Provide support within the department and assist with special projects. Provide support to all departments as needed." That's responsibilities.
- Who are we? That's about company description. Could be "About the company" but not required heading list includes "About the role". We could use "About the role" for responsibilities? Actually "About the role" is for description of role. Could also use "Responsibilities". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings.
We need to include sections only if there is real content.
We have:
- Responsibilities: many bullet-like sentences.
- Requirements: "Must have basic Microsoft Office skills, including e-mail, Word, and Excel skills. May be required to navigate the Internet efficiently and effectively. Able to learn and navigate: Adobe, Photoshop, PLM, Baan and Fox-Pro. Ability to retain and understand requirements for the different customers. Able to work with a high level of accuracy. Problem-solving and prioritization skills. Ability to read & interpret various customer drawing packages."
- Qualifications: "High School diploma required; associate’s degree preferred. 1-2 years relevant experience preferred"
- Skills: maybe overlapping with requirements. Could combine.
- Benefits: "Excellent company culture – as recognized by Newsweek’s Top 100 Most Loved Workplaces Clean and climate controlled working environment Opportunity for career growth Great benefits including paid vacation and sick time, 401K match, Employee Stock Purchase Program, annual bonus plan, and tuition reimbursement"
- Pay: Not mentioned. So we should NOT create Pay section.
- Schedule: Not mentioned. So no Schedule.
- About the role: Could be a brief summary: "Provide/Create and Update internal documentation for production, test, quality and shipping..." That's essentially responsibilities. Might be better to have "About the role" as a short paragraph summarizing the role, and then "Responsibilities" as a list.
But we must not repeat content. We can split: "About the role" short prose, then "Responsibilities" list.
We need to preserve all substantive information. So we need to include all details from the posting.
Let's extract all substantive info:
From first paragraph:
- Provide/Create and Update internal documentation for production, test, quality and shipping.
- Maintain the latest information by confirming/updating the system for accuracy so that Ducommun can purchasing the correct piece parts, build, test, inspect and ship the unit to meet the customers requirements.
- Provide support within the department and assist with special projects.
- Provide support to all departments as needed.
Company description:
- Founded in 1849, Ducommun is the oldest company in California.
- Starting as a hardware supply store during the California Gold Rush and eventually assisted in the birth of the aerospace industry in Southern California by providing aircraft aluminum to early aerospace pioneers like Lindbergh, Douglas and Lockheed.
- Today Ducommun is a global provider of innovative manufacturing solutions for customers in the aerospace, defense and industrial markets.
- We specialize in electronic and structural systems, producing complex products and components for commercial aircraft platforms, mission-critical military and space programs, and sophisticated industrial applications.
- Our Facility in Huntsville, AR manufactures state-of-the-art circuit boards for Aerospace and Defense.
Why Ducommun? (benefits/culture):
- Excellent company culture – as recognized by Newsweek’s Top 100 Most Loved Workplaces
- Clean and climate controlled working environment
- Opportunity for career growth
- Great benefits including paid vacation and sick time, 401K match, Employee Stock Purchase Program, annual bonus plan, and tuition reimbursement
Job Summary (maybe "General data entry..."):
- General data entry.
- Organize/Priortize task and workflow.
- Research requirements/specificatons for understanding details to be accurate.
- Process customer (Change Impacts) and internal changes (DAN Requests).
- Enter, retrieve and analyze various information.
- Create Bills of Materials in PLM.
- Create and Update Documents in PLM, examples are: Process Sheets, Wire List Tubing List, Torque List, As Built List, Etc.
- Create/Update Routers in Baan, Issue Routers confirming accurate revisions update as required per effectivies listed on DANs.
- Update internal documents as required per Customer, Production, Engineering, and QA requested changes.
- Confirm all requested changes are per the customers documentation for correct build of the assembly.
- Request any missing documation called out by the requirement.
- Issue DANs and update documents per the DAN in PLM and the Shared Drive.
- Stay organized within your own workload.
- Maintain project files and schedules.
- Adhere to “General Requirements of Team Members.”
- Perform other assignments as required
- Provide assistance to Engineers.
- Interact with other departments.
- Research and resolve discrepancies when it arises in all departments.
Required Skills And Qualifications:
- Must have basic Microsoft Office skills, including e-mail, Word, and Excel skills.
- May be required to navigate the Internet efficiently and effectively.
- Able to learn and naviagate: Adobe, Photoshop, PLM, Baan and Fox-Pro.
- Ability to retain and understand requirements for the different customers.
- Able to work with a high level of accuracy.
- Problem-solving and prioritization skills.
- Ability to read & interpret various customer drawing packages.
Required Experience And Education:
- High School diploma required; associate’s degree preferred.
- 1-2 years relevant experience preferred
Equal Opportunity Employer Veterans/Disabled (boilerplate to remove)
Address: 403 LaBarge Avenue Huntsville, Arkansas, 72740 United States (metadata, can be short p)
We need to remove EEO boilerplate.
We need to avoid duplication: Some sentences repeated? Not many.
Now decide sections.
Potential sections:
- About the role (short paragraph summarizing role)
- Responsibilities (list of duties)
- Requirements (skills)
- Qualifications (education/experience)
- Benefits (company culture and benefits)
- About the company (maybe not in list but could be "About Ducommun" but not required heading list; we could incorporate into "About the role" or separate "About the company". The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use those for section headings (e.g. ...). It might be okay to add other headings but better to stick to those. We could put company description under "About the role" or maybe under a separate "About Ducommun" but that's not in list. Safer to incorporate into "About the role" or maybe a separate "About the company" but risk being considered extra heading. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples, not exclusive. But to be safe, we can stick to those.
We have content for About the role (role description), Responsibilities (detailed duties), Requirements (skills), Qualifications (education/experience), Benefits (culture/benefits). No Pay, Schedule.
We could also have a short "About Ducommun" but maybe we can put company description under "About the role" as part of role context. However the role description is about duties; company description is separate. Could we put under "About the role" a paragraph that includes both role and company? Might be mixing but acceptable.
Alternatively we could have "About the role" for role summary, and then "Responsibilities" for detailed duties. Then we could have "About Ducommun" as a separate heading but not in the list; risk. I'd rather include company description in a short paragraph under "About the role" or maybe under a separate "About Ducommun" but risk being considered unnecessary heading. The instruction says "Prefer a few substantive sections over many thin ones." So we should combine where possible.
Thus we can have:
About the role
Provide/Create and Update internal documentation for production, test, quality and shipping. Maintain the latest information by confirming/updating the system for accuracy so that Ducommun can purchase the correct piece parts, build, test, inspect and ship the unit to meet customer requirements. Provide support within the department and assist with special projects. Provide support to all departments as needed.
Then maybe a separate About Ducommun
but we risk extra heading. Could we incorporate company description into About the role? Might be odd but we can add a second paragraph after the role description: "Ducommun, founded in 1849, is the oldest company in California..." etc. That would be part of About the role section. That seems okay.
Then Responsibilities: list of duties from Job Summary etc.
Then Requirements: list of skills.
Then Qualifications: education/experience.
Then Benefits: list of benefits/culture.
We must not repeat content. Ensure we include all details.
Let's extract details for each section.
About the role paragraph: combine first paragraph and company description.
First paragraph: "Provide/Create and Update internal documentation for production, test, quality and shipping. Maintain the latest information by confirming/updating the system for accuracy so that Ducommun can purchasing the correct piece parts, build, test, inspect and ship the unit to meet the customers requirements. Provide support within the department and assist with special projects. Provide support to all departments as needed."
Note: there is a grammar error "purchasing" should be "purchase". We must preserve substantive information, not correct grammar? We should preserve as is? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must keep exact wording, but we should not change meaning. Slight grammar fix might be considered altering? Safer to keep original wording. However "Ducommun can purchasing" is ungrammatical but it's substantive. We'll keep it.
Company description: "Founded in 1849, Ducommun is the oldest company in California. Starting as a hardware supply store during the California Gold Rush and eventually assisted in the birth of the aerospace industry in Southern California by providing aircraft aluminum to early aerospace pioneers like Lindbergh, Douglas and Lockheed. Today Ducommun is a global provider of innovative manufacturing solutions for customers in the aerospace, defense and industrial markets. We specialize in electronic and structural systems, producing complex products and components for commercial aircraft platforms, mission-critical military and space programs, and sophisticated industrial applications. Our Facility in Huntsville, AR manufactures state-of-the-art circuit boards for Aerospace and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the job posting. Key sections: - About the role? The posting includes "Provide/Create and Update internal documentation for production, test, quality and shipping. Maintain the latest information by confirming/updating the system for accuracy so that Ducommun can purchasing the correct piece parts, build, test, inspect and ship the unit to meet the customers requirements. Provide support within the department and assist with special projects. Provide support to all departments as needed." That's responsibilities. - Who are we? That's about company description. Could be "About the company" but not required heading list includes "About the role". We could use "About the role" for responsibilities? Actually "About the role" is for description of role. Could also use "Responsibilities". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings.
We need to include sections only if there is real content.
We have:
- Responsibilities: many bullet-like sentences.
- Requirements: "Must have basic Microsoft Office skills, including e-mail, Word, and Excel skills. May be required to navigate the Internet efficiently and effectively. Able to learn and navigate: Adobe, Photoshop, PLM, Baan and Fox-Pro. Ability to retain and understand requirements for the different customers. Able to work with a high level of accuracy. Problem-solving and prioritization skills. Ability to read & interpret various customer drawing packages."
- Qualifications: "High School diploma required; associate’s degree preferred. 1-2 years relevant experience preferred"
- Skills: maybe overlapping with requirements. Could combine.
- Benefits: "Excellent company culture – as recognized by Newsweek’s Top 100 Most Loved Workplaces Clean and climate controlled working environment Opportunity for career growth Great benefits including paid vacation and sick time, 401K match, Employee Stock Purchase Program, annual bonus plan, and tuition reimbursement"
- Pay: Not mentioned. So we should NOT create Pay section.
- Schedule: Not mentioned. So no Schedule.
- About the role: Could be a brief summary: "Provide/Create and Update internal documentation for production, test, quality and shipping..." That's essentially responsibilities. Might be better to have "About the role" as a short paragraph summarizing the role, and then "Responsibilities" as a list.
But we must not repeat content. We can split: "About the role" short prose, then "Responsibilities" list.
We need to preserve all substantive information. So we need to include all details from the posting.
Let's extract all substantive info:
From first paragraph:
- Provide/Create and Update internal documentation for production, test, quality and shipping.
- Maintain the latest information by confirming/updating the system for accuracy so that Ducommun can purchasing the correct piece parts, build, test, inspect and ship the unit to meet the customers requirements.
- Provide support within the department and assist with special projects.
- Provide support to all departments as needed.
Company description:
- Founded in 1849, Ducommun is the oldest company in California.
- Starting as a hardware supply store during the California Gold Rush and eventually assisted in the birth of the aerospace industry in Southern California by providing aircraft aluminum to early aerospace pioneers like Lindbergh, Douglas and Lockheed.
- Today Ducommun is a global provider of innovative manufacturing solutions for customers in the aerospace, defense and industrial markets.
- We specialize in electronic and structural systems, producing complex products and components for commercial aircraft platforms, mission-critical military and space programs, and sophisticated industrial applications.
- Our Facility in Huntsville, AR manufactures state-of-the-art circuit boards for Aerospace and Defense.
Why Ducommun? (benefits/culture):
- Excellent company culture – as recognized by Newsweek’s Top 100 Most Loved Workplaces
- Clean and climate controlled working environment
- Opportunity for career growth
- Great benefits including paid vacation and sick time, 401K match, Employee Stock Purchase Program, annual bonus plan, and tuition reimbursement
Job Summary (maybe "General data entry..."):
- General data entry.
- Organize/Priortize task and workflow.
- Research requirements/specificatons for understanding details to be accurate.
- Process customer (Change Impacts) and internal changes (DAN Requests).
- Enter, retrieve and analyze various information.
- Create Bills of Materials in PLM.
- Create and Update Documents in PLM, examples are: Process Sheets, Wire List Tubing List, Torque List, As Built List, Etc.
- Create/Update Routers in Baan, Issue Routers confirming accurate revisions update as required per effectivies listed on DANs.
- Update internal documents as required per Customer, Production, Engineering, and QA requested changes.
- Confirm all requested changes are per the customers documentation for correct build of the assembly.
- Request any missing documation called out by the requirement.
- Issue DANs and update documents per the DAN in PLM and the Shared Drive.
- Stay organized within your own workload.
- Maintain project files and schedules.
- Adhere to “General Requirements of Team Members.”
- Perform other assignments as required
- Provide assistance to Engineers.
- Interact with other departments.
- Research and resolve discrepancies when it arises in all departments.
Required Skills And Qualifications:
- Must have basic Microsoft Office skills, including e-mail, Word, and Excel skills.
- May be required to navigate the Internet efficiently and effectively.
- Able to learn and naviagate: Adobe, Photoshop, PLM, Baan and Fox-Pro.
- Ability to retain and understand requirements for the different customers.
- Able to work with a high level of accuracy.
- Problem-solving and prioritization skills.
- Ability to read & interpret various customer drawing packages.
Required Experience And Education:
- High School diploma required; associate’s degree preferred.
- 1-2 years relevant experience preferred
Equal Opportunity Employer Veterans/Disabled (boilerplate to remove)
Address: 403 LaBarge Avenue Huntsville, Arkansas, 72740 United States (metadata, can be short p)
We need to remove EEO boilerplate.
We need to avoid duplication: Some sentences repeated? Not many.
Now decide sections.
Potential sections:
- About the role (short paragraph summarizing role)
- Responsibilities (list of duties)
- Requirements (skills)
- Qualifications (education/experience)
- Benefits (company culture and benefits)
- About the company (maybe not in list but could be "About Ducommun" but not required heading list; we could incorporate into "About the role" or separate "About the company". The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use those for section headings (e.g. ...). It might be okay to add other headings but better to stick to those. We could put company description under "About the role" or maybe under a separate "About Ducommun" but that's not in list. Safer to incorporate into "About the role" or maybe a separate "About the company" but risk being considered extra heading. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples, not exclusive. But to be safe, we can stick to those.
We have content for About the role (role description), Responsibilities (detailed duties), Requirements (skills), Qualifications (education/experience), Benefits (culture/benefits). No Pay, Schedule.
We could also have a short "About Ducommun" but maybe we can put company description under "About the role" as part of role context. However the role description is about duties; company description is separate. Could we put under "About the role" a paragraph that includes both role and company? Might be mixing but acceptable.
Alternatively we could have "About the role" for role summary, and then "Responsibilities" for detailed duties. Then we could have "About Ducommun" as a separate heading but not in the list; risk. I'd rather include company description in a short paragraph under "About the role" or maybe under a separate "About Ducommun" but risk being considered unnecessary heading. The instruction says "Prefer a few substantive sections over many thin ones." So we should combine where possible.
Thus we can have:
About the role
About the role
Provide/Create and Update internal documentation for production, test, quality and shipping. Maintain the latest information by confirming/updating the system for accuracy so that Ducommun can purchase the correct piece parts, build, test, inspect and ship the unit to meet customer requirements. Provide support within the department and assist with special projects. Provide support to all departments as needed.
Then maybe a separate