Technical Writer Intern
General Dynamics Mission Systems · Manassas, VA · 1 mo ago
On-siteWriting$27.5/hrInternship
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, etc). Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: "Target salary range: USD $27.50/Hr. - USD $27.50/Hr." That's a specific pay figure, though it's same min and max. It says "Target salary range: USD $27.50/Hr. - USD $27.50/Hr." That is a pay statement. So we can include a Pay section with that info. Also schedule: "WORKPLACE OPTIONS: This position is on-site 100%." That's schedule info (on-site). So we can include Schedule section. Benefits: The posting mentions "In addition to receiving a competitive wage, the Administration Intern will enhance their skill set..." and later "We offer highly competitive benefits and pride ourselves in being a great place to work..." but no specific benefits listed. There's no explicit benefits list like health, 401k, etc. So we should not create a Benefits section unless there is specific content. The phrase "We offer highly competitive benefits" is vague, not specific. According to rule: 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. The benefits statement is vague but still states they offer benefits. However it's not a list. Might be considered filler? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they offer benefits, but not specifics. Might be okay to include a Benefits section with that statement? But they said "Prefer a few substantive sections over many thin ones." The benefits statement is thin. Might be better to omit Benefits section. Let's see if there is any other benefit info: "In addition to receiving a competitive wage, the Administration Intern will enhance their skill set by working among a talented and technically accomplished group of colleagues. Interns will also enjoy a flexible work environment where contributions are recognized and rewarded." That's more about work environment, not benefits. So we can omit Benefits.
Now sections we have: Responsibilities, Qualifications (maybe Basic Qualifications), Skills (Required Experience And Skills, Optional/Preferred Experience And Skills), About the role (maybe the overview). Also we have "Company Overview" which could be About the role or About the company. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We need to preserve all substantive info. Let's extract:
Basic Qualifications:
- Candidates should demonstrate a thorough understanding of business principles.
- Administrative Interns must be actively enrolled in an accredited degree program with a preference in a related field.
- Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information.
- Due to the nature of work performed within our facilities, U.S. citizenship is required.
Responsibilities:
- REPRESENTATIVE DUTIES AND TASKS: Apply your classroom-learned skills to a program supporting the defense of our country.
- GDMS has an immediate opening for an Administration Intern (Technical Writing focus) to join our team.
- The position provides an opportunity to enhance the performance and profitability of an organization that supports some of our nation's fundamental defense services.
- The selected candidate will work with collaborative teams on various projects of the GDMS organization and its clients.
- In addition to receiving a competitive wage, the Administration Intern will enhance their skill set by working among a talented and technically accomplished group of colleagues.
- Interns will also enjoy a flexible work environment where contributions are recognized and rewarded.
- Job Duties/Responsibilities:
- Write and edit technical documentation in various formats (e.g., .doc, .PDF, HTML, and XML/SGML-tagged IETMs).
- Able to comply with military specifications and technical documentation requirements.
- Maintain established technical documentation lifecycle, to include review cycles and hardware and/or software update cycles.
- Create supporting graphics (e.g., functional block diagrams) in various formats (e.g., .JPEG, .PNG, etc.) to support documentation functional descriptions and procedures.
- Perform quality assurance to ensure technical and grammatical accuracy of documentation.
- Collaborate with Subject Matter Experts (SMEs) during development and editing to ensure technical accuracy of documentation.
Required Experience And Skills (Preferred):
- Preferred English major.
- Proficient with Microsoft Office products (including, but not limited to: Word, Excel, PowerPoint, and Teams).
- Ability to research unfamiliar technology well enough to describe and summarize for an end-user; must be comfortable asking questions and collaborating with Subject Matter Experts.
- Excellent oral and written communication skills.
- Meticulous attention to detail.
Optional/Preferred Experience And Skills:
- Experience using an XML editor (e.g., XMLSpy, Arbortext).
- Familiarity with basic graphic design principles.
- Understanding of a repository-based content management system (e.g., TortoiseSVN).
WHAT YOU'LL EXPERIENCE:
- Technologies that aren’t just top-notch, they’re often top-secret
- A team of bold thinkers committed to exploring what’s next
- Opportunities to gain new knowledge - as it’s discovered
WORKPLACE OPTIONS:
- This position is on-site 100%.
- While on-site, you will be a part of the Manassas, VA facility.
Target salary range: USD $27.50/Hr. - USD $27.50/Hr. (This estimate represents the typical salary range for this position based on experience and other factors (geographic location, etc.). Actual pay may vary.)
Company Overview:
- General Dynamics Mission Systems (GDMS) engineers a diverse portfolio of high technology solutions, products and services that enable customers to successfully execute missions across all domains of operation.
- With a global team of 12,000+ top professionals, we partner with the best in industry to expand the bounds of innovation in the defense and scientific arenas.
- Given the nature of our work and who we are, we value trust, honesty, alignment and transparency.
- We offer highly competitive benefits and pride ourselves in being a great place to work with a shared sense of purpose.
- You will also enjoy a flexible work environment where contributions are recognized and rewarded.
- If who we are and what we do resonates with you, we invite you to join our high-performance team!
We need to remove boilerplate: Equal Opportunity Employer etc. Also remove "This job posting will remain open until the position is filled." (application instruction). Also remove "Due to the nature of work performed within our facilities, U.S. citizenship is required." that's substantive, keep.
Now structure:
We could have sections:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, etc). Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: "Target salary range: USD $27.50/Hr. - USD $27.50/Hr." That's a specific pay figure, though it's same min and max. It says "Target salary range: USD $27.50/Hr. - USD $27.50/Hr." That is a pay statement. So we can include a Pay section with that info. Also schedule: "WORKPLACE OPTIONS: This position is on-site 100%." That's schedule info (on-site). So we can include Schedule section. Benefits: The posting mentions "In addition to receiving a competitive wage, the Administration Intern will enhance their skill set..." and later "We offer highly competitive benefits and pride ourselves in being a great place to work..." but no specific benefits listed. There's no explicit benefits list like health, 401k, etc. So we should not create a Benefits section unless there is specific content. The phrase "We offer highly competitive benefits" is vague, not specific. According to rule: 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. The benefits statement is vague but still states they offer benefits. However it's not a list. Might be considered filler? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they offer benefits, but not specifics. Might be okay to include a Benefits section with that statement? But they said "Prefer a few substantive sections over many thin ones." The benefits statement is thin. Might be better to omit Benefits section. Let's see if there is any other benefit info: "In addition to receiving a competitive wage, the Administration Intern will enhance their skill set by working among a talented and technically accomplished group of colleagues. Interns will also enjoy a flexible work environment where contributions are recognized and rewarded." That's more about work environment, not benefits. So we can omit Benefits.
Now sections we have: Responsibilities, Qualifications (maybe Basic Qualifications), Skills (Required Experience And Skills, Optional/Preferred Experience And Skills), About the role (maybe the overview). Also we have "Company Overview" which could be About the role or About the company. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We need to preserve all substantive info. Let's extract:
Basic Qualifications:
- Candidates should demonstrate a thorough understanding of business principles.
- Administrative Interns must be actively enrolled in an accredited degree program with a preference in a related field.
- Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information.
- Due to the nature of work performed within our facilities, U.S. citizenship is required.
Responsibilities:
- REPRESENTATIVE DUTIES AND TASKS: Apply your classroom-learned skills to a program supporting the defense of our country.
- GDMS has an immediate opening for an Administration Intern (Technical Writing focus) to join our team.
- The position provides an opportunity to enhance the performance and profitability of an organization that supports some of our nation's fundamental defense services.
- The selected candidate will work with collaborative teams on various projects of the GDMS organization and its clients.
- In addition to receiving a competitive wage, the Administration Intern will enhance their skill set by working among a talented and technically accomplished group of colleagues.
- Interns will also enjoy a flexible work environment where contributions are recognized and rewarded.
- Job Duties/Responsibilities:
- Write and edit technical documentation in various formats (e.g., .doc, .PDF, HTML, and XML/SGML-tagged IETMs).
- Able to comply with military specifications and technical documentation requirements.
- Maintain established technical documentation lifecycle, to include review cycles and hardware and/or software update cycles.
- Create supporting graphics (e.g., functional block diagrams) in various formats (e.g., .JPEG, .PNG, etc.) to support documentation functional descriptions and procedures.
- Perform quality assurance to ensure technical and grammatical accuracy of documentation.
- Collaborate with Subject Matter Experts (SMEs) during development and editing to ensure technical accuracy of documentation.
Required Experience And Skills (Preferred):
- Preferred English major.
- Proficient with Microsoft Office products (including, but not limited to: Word, Excel, PowerPoint, and Teams).
- Ability to research unfamiliar technology well enough to describe and summarize for an end-user; must be comfortable asking questions and collaborating with Subject Matter Experts.
- Excellent oral and written communication skills.
- Meticulous attention to detail.
Optional/Preferred Experience And Skills:
- Experience using an XML editor (e.g., XMLSpy, Arbortext).
- Familiarity with basic graphic design principles.
- Understanding of a repository-based content management system (e.g., TortoiseSVN).
WHAT YOU'LL EXPERIENCE:
- Technologies that aren’t just top-notch, they’re often top-secret
- A team of bold thinkers committed to exploring what’s next
- Opportunities to gain new knowledge - as it’s discovered
WORKPLACE OPTIONS:
- This position is on-site 100%.
- While on-site, you will be a part of the Manassas, VA facility.
Target salary range: USD $27.50/Hr. - USD $27.50/Hr. (This estimate represents the typical salary range for this position based on experience and other factors (geographic location, etc.). Actual pay may vary.)
Company Overview:
- General Dynamics Mission Systems (GDMS) engineers a diverse portfolio of high technology solutions, products and services that enable customers to successfully execute missions across all domains of operation.
- With a global team of 12,000+ top professionals, we partner with the best in industry to expand the bounds of innovation in the defense and scientific arenas.
- Given the nature of our work and who we are, we value trust, honesty, alignment and transparency.
- We offer highly competitive benefits and pride ourselves in being a great place to work with a shared sense of purpose.
- You will also enjoy a flexible work environment where contributions are recognized and rewarded.
- If who we are and what we do resonates with you, we invite you to join our high-performance team!
We need to remove boilerplate: Equal Opportunity Employer etc. Also remove "This job posting will remain open until the position is filled." (application instruction). Also remove "Due to the nature of work performed within our facilities, U.S. citizenship is required." that's substantive, keep.
Now structure:
We could have sections:
About the role
(maybe combine company overview and role description). But we have separate "About the role" and "Company Overview". The instruction list includes About the role as a possible heading. We could put role description there (the opening paragraphs about the internship). Then maybe another section for Company Overview? Not in list. Could treat company overview as About the role? Or we could add a section "About the company" but not in allowed headings. Better to stick to allowed headings. So we can put role description under About the role, and maybe put company overview under About the role as well, or we could omit a separate company overview section. But we must preserve all substantive info; we can include company overview content inside About the role section as prose.
Alternatively, we could create a section "About the role" for the role description, and another section "Company Overview" not in list but maybe we shouldn't. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive list? 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 limit to those. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Qualifications, Skills, Pay, Schedule. Possibly Requirements (maybe same as Qualifications). But we have Basic Qualifications; we could put that under Qualifications. Requirements maybe not needed.
We have Required Experience And Skills and Optional/Preferred Experience And Skills; those could go under Skills.
We have WHAT YOU'LL EXPERIENCE maybe could go under About the role or Skills? It's more about experience; could be part of About the role.
We have WORKPLACE OPTIONS (schedule) -> Schedule.
We have Target salary range -> Pay.
We have Basic Qualifications -> Qualifications.
We have Responsibilities -> Responsibilities.
We have company overview and role description -> About the role.
Thus we will output:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should limit to those. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Qualifications, Skills, Pay, Schedule. Possibly Requirements (maybe same as Qualifications). But we have Basic Qualifications; we could put that under Qualifications. Requirements maybe not needed.
We have Required Experience And Skills and Optional/Preferred Experience And Skills; those could go under Skills.
We have WHAT YOU'LL EXPERIENCE maybe could go under About the role or Skills? It's more about experience; could be part of About the role.
We have WORKPLACE OPTIONS (schedule) -> Schedule.
We have Target salary range -> Pay.
We have Basic Qualifications -> Qualifications.
We have Responsibilities -> Responsibilities.
We have company overview and role description -> About the role.
Thus we will output:
About the role
... (combined role description and company overview)
Responsibilities
- ... each duty
Qualifications
- ... each qualification
Skills
- ... required skills
- ... optional/preferred skills
- for any list. Could have two separate
- sections, each preceded by a
- for any list of duties/requirements/benefits, and
for prose. So we can have a
preceding each list to describe. Thus:
Required Skills:
- ...
Preferred Skills:
- ...
Pay
Target salary range: USD $27.50/Hr. - USD $27.50/Hr. (This estimate represents the typical salary range for this position based on experience and other factors (geographic location, etc.). Actual pay may vary.)
Schedule
This position is on-site 100%. While on-site, you will be a part of the Manassas, VA facility.
We must ensure we don't repeat any boilerplate. Also we need to preserve all substantive info from the posting. Let's verify we captured everything. From Basic Qualifications: - thorough understanding of business principles. - actively enrolled in an accredited degree program with a preference in a related field. - subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information. - U.S. citizenship is required. We captured those. From Responsibilities: - Apply your classroom-learned skills to a program supporting the defense of our country. - GDMS has an immediate opening for an Administration Intern (Technical Writing focus) to join our team. - The position provides an opportunity to enhance the performance and profitability of an organization that supports some of our nation's fundamental defense services. - The selected candidate will work with collaborative teams on various projects of the GDMS organization and its clients. - In addition to receiving a competitive wage, the Administration Intern
heading? But we cannot add extra headings not allowed. Could just make one list with all items, but we need to differentiate required vs optional. Could keep as separate lists with a preceding
like "Required Skills:" and "Preferred Skills:" but that's not a heading; it's okay as prose. The rule: Use
- for any list of duties/requirements/benefits, and