Marketing Specialist
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
- About the role: we can include description of the role and maybe company overview? The role description: "The Marketing & Communications Specialist plays a key role in helping keep Ames Construction’s marketing and communications work organized, aligned, and moving forward. This position combines strong project coordination with hands-on marketing and communications support, helping maintain team planning and systems, supporting key brand platforms and resources, and coordinating assigned initiatives. The ideal candidate is highly organized, proactive, and detail-oriented, with strong communication and teamwork skills and the ability to take ownership of specific phases of larger projects or standalone assignments from start to finish. This person is comfortable managing multiple priorities, coordinating across teams and vendors, learning new systems, and contributing ideas that improve how Marketing & Communications works."
That's about the role and ideal candidate. Could be placed under About the role.
- Responsibilities: The "Key Duties And Responsibilities" list bullet points. We'll put those under Responsibilities
with - each.
- Requirements: Might be similar to Qualifications? The posting has "Qualifications" section with bullet list of education, experience, skills. Could treat that as Qualifications. Requirements maybe could be same as Qualifications? But we need to avoid duplicate sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they gave examples of possible headings; we can choose to include only those with content. We have Qualifications content. We might not need a separate Requirements if it's same. However we could treat "Qualifications" as the qualifications section. The "Requirements" could be omitted if no distinct content. The posting includes "Qualifications" heading with bullet list. So we will output
Qualifications
with list.
- Skills: Could be extracted from qualifications: strong organizational, communication, proofreading, etc. But we already have them in qualifications list. Might be redundant. Better to not create a Skills section if it's just repeating. We'll omit Skills.
- Benefits: The posting has a "Total Rewards" paragraph describing base salary range, bonus, retirement benefits, health benefits, etc. That includes Pay and Benefits. We need to separate Pay and Benefits sections only if they have specific content. The posting says: "Base salary range is $70,000-$80,000 a year, which varies depending on many factors, including experience, skills, and knowledge. This role is eligible for a discretionary bonus. Ames offers generous retirement benefits, including Employee Stock Option Plan (ESOP) participation and a 401k match. Ames' non-craft health benefits package is designed so that our team members flourish, with medical, dental, and vision (all at one low premium), voluntary benefits, company holidays, and paid time off."
Thus we have Pay (salary range, bonus) and Benefits (retirement, health, etc.). We'll create two sections: Pay
and Benefits
. Provide the details in or
as appropriate. The instruction: Use - for any list of duties/requirements/benefits, and
for prose. For Pay, it's not a list but prose; we can use
. For Benefits, we could list items: retirement benefits (ESOP participation, 401k match), health benefits (medical, dental, vision at low premium), voluntary benefits, company holidays, paid time off. That's a list; we can use
- .
- Schedule: The posting includes "Working Conditions" with location, travel, office environment. That could be considered Schedule? Actually schedule refers to work schedule/hours. Not present. There's no explicit schedule info. So we should not create a Schedule section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we omit Schedule.
- Requirements: we might not need separate Requirements if we have Qualifications. But we could include Requirements as a section with the same content? That would be duplicate. Better to omit Requirements.
Thus final sections: About the role, Responsibilities, Qualifications, Pay, Benefits.
Check if any other content like "Location" etc. Could be part of About the role? Not needed.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract:
About the role: include the paragraph(s) describing the role and ideal candidate. Also maybe include the company description? The instruction says preserve ALL substantive information. The company description at start is substantive about Ames Construction. Should we include it? It could be part of About the role or maybe a separate section like "About the company". But we only allowed headings from list; we could put it under About the role as well. However About the role is supposed to be about the role, not company. But we can include both; it's still substantive. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid adding other content under those headings. So we can put company overview under About the role as introductory paragraph.
Thus About the role will contain:
- Ames Construction description (first paragraph)
- The role description paragraph(s)
- Ideal candidate paragraph.
We'll combine into maybe multiple
tags.
Responsibilities: list each duty.
Qualifications: list each bullet.
Pay: paragraph with salary range and bonus.
Benefits: list of retirement benefits, health benefits, voluntary benefits, company holidays, paid time off.
We must not include boilerplate like EEO, equal opportunity, etc. Remove those lines.
Also remove "Please see the Benefits section of our Careers page for more information." That's a reference; we can drop as it's not substantive? It's a reference to external; maybe we can drop as it's not substantive detail. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is more like a reference; could be considered navigation? It's not essential; we can drop.
Also remove "Ames Construction is an equal opportunity employer..." line.
Now produce HTML fragment.
We'll need to ensure proper nesting:
About the role
followed by ...
maybe multiple .
Then
Responsibilities
- ...
Then Qualifications
- ...
Then Pay
...
Then Benefits
- ...
Make sure not to include any extra text outside HTML.
Let's draft.
About the role content:
Paragraph 1: "Ames Construction has been building America for more than 60 years, and our people are the reason we continue to succeed. We are a full-service, heavy civil and industrial contractor building critical infrastructure, including highways, bridges, mines, dams, rail, and more. Our teams take on challenging projects that keep communities safe, supply chains moving, and the country connected. At Ames, we are Fueled by Family. That means we look out for one another, take pride in our work, and build strong relationships rooted in trust and respect. Guided by our core values of People, Team, Our Bond, Persistence, and Vision, we do what we say we will do, push through challenges, and deliver work we’re proud of. When you join Ames, you’re joining a company built for long-term success, where skilled people, strong teams, and disciplined execution come together to build careers and a better future."
Paragraph 2: "The Marketing & Communications Specialist plays a key role in helping keep Ames Construction’s marketing and communications work organized, aligned, and moving forward. This position combines strong project coordination with hands-on marketing and communications support, helping maintain team planning and systems, supporting key brand platforms and resources, and coordinating assigned initiatives."
Paragraph 3: "The ideal candidate is highly organized, proactive, and detail-oriented, with strong communication and teamwork skills and the ability to take ownership of specific phases of larger projects or standalone assignments from start to finish. This person is comfortable managing multiple priorities, coordinating across teams and vendors, learning new systems, and contributing ideas that improve how Marketing & Communications works."
We'll keep as separate tags.
Responsibilities list items (from "Key Duties And Responsibilities"):
- Maintain the Marketing & Communications planning calendar and support the team’s use of Asana, helping keep priorities, key dates, deliverables, and project information current and visible.
- Serve as a project coordinator for assigned Marketing & Communications initiatives, helping develop timelines, coordinate details and contributors, track deliverables and approvals, and keep work moving.
- Help administer Ames' digital asset management (DAM) platform, including asset organization, tagging, version control, and accessibility, and assist coworkers in locating and using brand assets.
- Support the development, publishing, and maintenance of select Ames intranet/SharePoint content and resources.
- Support the coordination and continued development of Ames-branded merchandise and materials, including apparel, promotional items, and print materials, coordinating with vendors and internal partners to improve offerings, processes, and the overall brand experience.
- Provide proofreading, formatting, and quality control support for communications and branded materials. Support the creation and adaptation of presentations, templates, and other branded materials as needed.
- Help source and organize photography, video, graphics, and other assets needed for communications, presentations, and creative projects. Support logistics and execution for Marketing & Communications campaigns, events, and other team initiatives.
- Support budget and vendor tracking related to assigned projects, platforms, and programs.
Note: Some items have two sentences combined; we keep as one
- .
Qualifications list:
- Bachelor’s or Associate degree in Communications, Marketing, Business, Project Management, or related field; equivalent relevant experience considered.
- 2–4 years of experience in marketing, communications, project coordination, or related field.
- Strong organizational and project coordination skills, with the ability to manage multiple priorities, details, and deadlines.
- Strong written and verbal communication skills with excellent proofreading skills and attention to detail.
- Ability to take ownership of assigned work, identify next steps, and proactively move work forward.
- Strong interpersonal skills and ability to work effectively with coworkers, leaders, creative partners, and external vendors.
- Proficiency in Microsoft Office applications, particularly PowerPoint.
- Experience with Asana or other project management platforms preferred; experience with digital asset management systems, SharePoint, or similar digital platforms is a plus.
- Comfortable learning new technology, systems, and processes.
- Proactive, resourceful, and collaborative approach.
- Ability to maintain confidentiality.
Pay paragraph:
"Base salary range is $70,000-$80,000 a year, which varies depending on many factors, including experience, skills, and knowledge. This role is
Qualifications
with list. - Skills: Could be extracted from qualifications: strong organizational, communication, proofreading, etc. But we already have them in qualifications list. Might be redundant. Better to not create a Skills section if it's just repeating. We'll omit Skills. - Benefits: The posting has a "Total Rewards" paragraph describing base salary range, bonus, retirement benefits, health benefits, etc. That includes Pay and Benefits. We need to separate Pay and Benefits sections only if they have specific content. The posting says: "Base salary range is $70,000-$80,000 a year, which varies depending on many factors, including experience, skills, and knowledge. This role is eligible for a discretionary bonus. Ames offers generous retirement benefits, including Employee Stock Option Plan (ESOP) participation and a 401k match. Ames' non-craft health benefits package is designed so that our team members flourish, with medical, dental, and vision (all at one low premium), voluntary benefits, company holidays, and paid time off." Thus we have Pay (salary range, bonus) and Benefits (retirement, health, etc.). We'll create two sections:Pay
andBenefits
. Provide the details inor
- as appropriate. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. For Pay, it's not a list but prose; we can use
. For Benefits, we could list items: retirement benefits (ESOP participation, 401k match), health benefits (medical, dental, vision at low premium), voluntary benefits, company holidays, paid time off. That's a list; we can use
- .
- Schedule: The posting includes "Working Conditions" with location, travel, office environment. That could be considered Schedule? Actually schedule refers to work schedule/hours. Not present. There's no explicit schedule info. So we should not create a Schedule section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we omit Schedule.
- Requirements: we might not need separate Requirements if we have Qualifications. But we could include Requirements as a section with the same content? That would be duplicate. Better to omit Requirements.
Thus final sections: About the role, Responsibilities, Qualifications, Pay, Benefits.
Check if any other content like "Location" etc. Could be part of About the role? Not needed.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract:
About the role: include the paragraph(s) describing the role and ideal candidate. Also maybe include the company description? The instruction says preserve ALL substantive information. The company description at start is substantive about Ames Construction. Should we include it? It could be part of About the role or maybe a separate section like "About the company". But we only allowed headings from list; we could put it under About the role as well. However About the role is supposed to be about the role, not company. But we can include both; it's still substantive. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid adding other content under those headings. So we can put company overview under About the role as introductory paragraph. Thus About the role will contain: - Ames Construction description (first paragraph) - The role description paragraph(s) - Ideal candidate paragraph. We'll combine into maybe multiple
tags. Responsibilities: list each duty. Qualifications: list each bullet. Pay: paragraph with salary range and bonus. Benefits: list of retirement benefits, health benefits, voluntary benefits, company holidays, paid time off. We must not include boilerplate like EEO, equal opportunity, etc. Remove those lines. Also remove "Please see the Benefits section of our Careers page for more information." That's a reference; we can drop as it's not substantive? It's a reference to external; maybe we can drop as it's not substantive detail. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is more like a reference; could be considered navigation? It's not essential; we can drop. Also remove "Ames Construction is an equal opportunity employer..." line. Now produce HTML fragment. We'll need to ensure proper nesting:
About the role
followed by...
maybe multiple. Then
Responsibilities
- ...
Qualifications
- ...
Pay
...
ThenBenefits
- ...
tags. Responsibilities list items (from "Key Duties And Responsibilities"): - Maintain the Marketing & Communications planning calendar and support the team’s use of Asana, helping keep priorities, key dates, deliverables, and project information current and visible. - Serve as a project coordinator for assigned Marketing & Communications initiatives, helping develop timelines, coordinate details and contributors, track deliverables and approvals, and keep work moving. - Help administer Ames' digital asset management (DAM) platform, including asset organization, tagging, version control, and accessibility, and assist coworkers in locating and using brand assets. - Support the development, publishing, and maintenance of select Ames intranet/SharePoint content and resources. - Support the coordination and continued development of Ames-branded merchandise and materials, including apparel, promotional items, and print materials, coordinating with vendors and internal partners to improve offerings, processes, and the overall brand experience. - Provide proofreading, formatting, and quality control support for communications and branded materials. Support the creation and adaptation of presentations, templates, and other branded materials as needed. - Help source and organize photography, video, graphics, and other assets needed for communications, presentations, and creative projects. Support logistics and execution for Marketing & Communications campaigns, events, and other team initiatives. - Support budget and vendor tracking related to assigned projects, platforms, and programs. Note: Some items have two sentences combined; we keep as one
- . Qualifications list: - Bachelor’s or Associate degree in Communications, Marketing, Business, Project Management, or related field; equivalent relevant experience considered. - 2–4 years of experience in marketing, communications, project coordination, or related field. - Strong organizational and project coordination skills, with the ability to manage multiple priorities, details, and deadlines. - Strong written and verbal communication skills with excellent proofreading skills and attention to detail. - Ability to take ownership of assigned work, identify next steps, and proactively move work forward. - Strong interpersonal skills and ability to work effectively with coworkers, leaders, creative partners, and external vendors. - Proficiency in Microsoft Office applications, particularly PowerPoint. - Experience with Asana or other project management platforms preferred; experience with digital asset management systems, SharePoint, or similar digital platforms is a plus. - Comfortable learning new technology, systems, and processes. - Proactive, resourceful, and collaborative approach. - Ability to maintain confidentiality. Pay paragraph: "Base salary range is $70,000-$80,000 a year, which varies depending on many factors, including experience, skills, and knowledge. This role is
- .
- Schedule: The posting includes "Working Conditions" with location, travel, office environment. That could be considered Schedule? Actually schedule refers to work schedule/hours. Not present. There's no explicit schedule info. So we should not create a Schedule section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we omit Schedule.
- Requirements: we might not need separate Requirements if we have Qualifications. But we could include Requirements as a section with the same content? That would be duplicate. Better to omit Requirements.
Thus final sections: About the role, Responsibilities, Qualifications, Pay, Benefits.
Check if any other content like "Location" etc. Could be part of About the role? Not needed.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract:
About the role: include the paragraph(s) describing the role and ideal candidate. Also maybe include the company description? The instruction says preserve ALL substantive information. The company description at start is substantive about Ames Construction. Should we include it? It could be part of About the role or maybe a separate section like "About the company". But we only allowed headings from list; we could put it under About the role as well. However About the role is supposed to be about the role, not company. But we can include both; it's still substantive. The instruction: "Use