Accounting Assistant

HDR · Greater Houston · 1 mo ago

On-siteConsultingFull-time

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Let's parse the posting. Content: - Intro paragraph about HDR culture, mission, etc. Could be "About the role"? Actually "About the role" could be description of role. The posting includes description of role: "As part of our Architecture practice at HDR, you’ll contribute to the design and delivery of spaces and experiences..." That's about the role. Also later: "In the role of Accounting Assistant, we'll count on you to: Assist with project budgeting, invoicing and monthly status reports Assist with project coordination of document control, development and tracking of decision logs, action items, client and team meetings and organization and production of deliverables Perform other duties as needed". That's responsibilities. - Preferred Qualifications: Bachelor's degree in Accounting, Experience supervising other financial professionals beneficial. - Required Qualifications: High School diploma or equivalent, Strong attention to detail, manage multiple projects independently, An attitude and commitment to being an active participant of our employee-owned culture is a must. - There's also "What We Believe", "Our Commitment", "Employee Network Groups", etc. Those are more about company culture, could be "About the role"? But they are not specific to role. Might be considered "About the role"? Probably not. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content for them. We have: - About the role: we have description of role (the paragraph about Architecture practice and the role of Accounting Assistant). Could be considered "About the role". We'll include that. - Responsibilities: list of duties (Assist with project budgeting...). We'll put as

. - Requirements: maybe combine Required Qualifications? The instruction includes Requirements and Qualifications separate headings. Usually Requirements = required qualifications, Qualifications = preferred? But they gave both. We'll treat "Requirements" as required qualifications, and "Qualifications" as preferred qualifications. Or we could combine. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. - Skills: maybe not explicitly listed. There's "Strong attention to detail, manage multiple projects independently". That's a skill. Could be placed under Skills. But we also have "Experience supervising other financial professionals beneficial" under Preferred Qualifications. Might be considered Skills. However we already have Qualifications section for preferred qualifications. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So we could combine Required and Preferred into Qualifications? But they gave separate headings as examples; we can choose to include only those with content. We have content for Required Qualifications and Preferred Qualifications. Could make two sections: Requirements (required) and Qualifications (preferred). That seems appropriate. - Skills: Not explicitly separate; we could omit. - Benefits, Pay, Schedule: The posting includes "Schedule:Full-time" under metadata. That's schedule info. So we can include Schedule section with "Full-time". Also there is no explicit Benefits or Pay. So we omit those. - Also there is "Primary Location:United States-Texas-Dallas Other Locations:United States-Texas-Houston". That's location metadata; we could fold into a short
maybe under About the role? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short paragraph after About the role maybe. But we need to preserve ALL substantive information; location is substantive? It's location info. Could be included as a short p. We also have "Industry:Architecture", "BusinessClass:Marketing and Admin", "Job Posting:Sep 21, 2026". Those are metadata; we can fold into a short p or drop. Probably include a short p with location and posting date. We must remove boilerplate: EEO, etc. Remove the lines about Affirmative Action, etc. Now construct HTML. Structure:
About the role

At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? ... (the paragraph about architecture practice and role). Then maybe include location and posting date in a short p after? But we need to preserve all substantive info; we could add a p: "Primary Location: United States-Texas-Dallas; Other Locations: United States-Texas-Houston. Industry: Architecture. Job Posting: Sep 21, 2026." That's okay. Then
Responsibilities
- Assist with project budgeting, invoicing and monthly status reports
- Assist with project coordination of document control, development and tracking of decision logs, action items, client and team meetings and organization and production of deliverables
- Perform other duties as needed
Then
Requirements
- High School diploma or equivalent
- Strong attention to detail
- Ability to manage multiple projects independently
- Attitude and commitment to being an active participant of our employee-owned culture is a must
Then
Qualifications
- Bachelor's degree in Accounting
- Experience supervising other financial professionals (beneficial)
Then
Schedule

Full-time
We should not include Benefits, Pay. Check for any repeated lines: we removed duplicates. Check for boilerplate: removed EEO lines. Check for any "What We Believe" etc. Not included; that's okay as it's generic company culture not specific to role. Might be considered part of About the role? But we already have a long paragraph; we could incorporate some of that? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "What We Believe" and "Our Commitment" and Employee Network Groups are substantive about company culture. Should we include them? They are not role-specific but still substantive. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include only role-specific sections; we could include a section like "About HDR" but not in the list of headings. The allowed headings are limited to those examples. So we cannot create a custom heading like "About HDR". We must use only those headings. So we must fit that content into one of those headings. The best fit is "About the role" maybe extended to include company culture. That seems acceptable. Thus we can expand the About the role paragraph to include the culture statements. Let's craft About the role paragraph: At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? We believe architecture is more than designing buildings, it’s about providing solutions to societal challenges and creating stronger, more vibrant communities. As part of our Architecture practice at HDR, you’ll contribute to the design and delivery of spaces and experiences that advance community well-being around the world. From healing environments and learning spaces to research labs and civic landmarks and infrastructure, your work will directly influence how individuals experience the world around them. We bring together architects, planners, designers, and technical experts to solve complex design challenges with creativity, curiosity, and collaboration. From championing design excellence with an emphasis on resilience and sustainability to pioneering innovative building technologies, your contributions will leave a lasting impact on the built environment. This isn’t just a job, it’s a chance to drive meaningful change and help define the future of our communities. In the role of Accounting Assistant, we'll count on you to: Assist with project budgeting, invoicing and monthly status reports; Assist with project coordination of document control, development and tracking of decision logs, action items, client and team meetings and organization and production of deliverables; Perform other duties as needed. But we already have Responsibilities separate; we might not want to duplicate responsibilities in About the role. However the instruction says preserve ALL substantive information; we can keep responsibilities in both places? That would be duplication. Better to keep responsibilities only in Responsibilities section, and About the role includes the descriptive paragraphs about HDR, architecture practice, impact, etc., but not the duty list. The duty list is responsibilities. So we should not repeat them. Thus About the role paragraph will be the introductory culture and architecture description, ending before "In the role of Accounting Assistant, we'll count on you to:". Let's extract that: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: 'https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. We believe architecture is more than designing buildings, it’s about providing solutions to societal challenges and creating stronger, more vibrant communities. As part of our Architecture practice at HDR, you’ll contribute to the design and delivery of spaces and experiences that advance community well-being around the world. From healing environments and learning spaces to research labs and civic landmarks and infrastructure, your work will directly influence how individuals experience the world around them. We bring together architects, planners, designers, and technical experts to solve complex design challenges with creativity, curiosity, and collaboration. From championing design excellence with an emphasis on resilience and sustainability to pioneering innovative building technologies, your contributions will leave a lasting impact on the built environment. This isn’t just a job, it’s a chance to drive meaningful change and help define the future of our communities." We should remove the link maybe? It's a URL; we can keep as plain text? Probably okay to keep as part of sentence. But we might drop the "Watch Our Story: 'https://www.hdrinc.com/our-story'" as it's a link; but it's substantive? It's a reference; we could keep as plain text. However it's not essential; but we can keep. Now after that, we have Responsibilities section. Now Required Qualifications section. Now Preferred Qualifications (Qualifications) section. Now Schedule section. Add location and posting date maybe as a short p after About the role? Could be placed in a p after About the role before Responsibilities. That would be minor metadata; we can include. Let's craft final HTML. Be careful to not include any markdown fences. Output:
About the role

At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: 'https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to

Accounting Assistant

About the role

Responsibilities

Requirements

Qualifications

Schedule

About the role

Similar jobs