Gl Accountant
Aston Carter · St Louis, MO · 1 mo ago
On-siteAccounting$35–$40/hrContract
We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real specific content. Must not include boilerplate like EEO, legal, etc. Must remove application instructions, cookie/navigation/legal/EEO, duplicated lines. Must preserve all substantive information.
We need to parse the job description.
Key sections:
- About the role (maybe "General Ledger Accountant plays a key role...") That's a paragraph describing role.
- Responsibilities: list of duties.
- Essential Skills (maybe "Essential Skills" heading). Could be considered "Requirements" or "Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map.
We have "Essential Skills" list (1-7 years experience etc). Also "Additional Skills & Qualifications". Could combine into Qualifications/Skills.
We have "Work Environment" description.
We have "Job Type & Location": Contract position based out of Saint Louis, MO.
We have "Pay And Benefits": pay range $35-40/hr, benefits list.
We have "Workplace Type": fully onsite position in Saint Louis, MO.
We have "Application Deadline": anticipated to close on Sep 28, 2026. This is maybe metadata; but we can include as a short paragraph maybe under a heading? Not required but we can include as a short p.
We have "About Aston Carter": company description; maybe we can include as a short paragraph under "About the company" but not required heading; but we can include as a paragraph.
We must remove boilerplate: EEO, equal opportunity, accommodation, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI, etc.
Also remove duplicated lines.
We must not create sections with filler like "commensurate with experience". Not needed.
We need to output only HTML fragment, no html/body tags, no markdown fences.
Let's decide sections:
-
About the role
with paragraph describing role. -Responsibilities
with- list.
-
Qualifications
maybe combine Essential Skills and Additional Skills & Qualifications into a list. -Work Environment
paragraph. -Job Type and Location
paragraph. -Pay and Benefits
with pay range paragraph and benefits list. -Workplace Type
paragraph (maybe redundant with Job Type & Location; but we can combine? The instruction says prefer few substantive sections over many thin ones. Could combine Job Type & Location and Workplace Type into one section "Job Details". But we have headings list includes Schedule, Pay, Benefits. Not required to use all. We could make a section "Job Details" but not in allowed headings? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings if appropriate, but better to stick to those. We could map: - About the role - Responsibilities - Qualifications (covers Essential Skills & Additional Skills) - Benefits (maybe include Pay within Benefits? But we have separate Pay heading allowed. Could do Pay and Benefits combined under Benefits? But we have Pay heading allowed; we could do Pay and Benefits separate. - Work Environment maybe not in list but could be "Requirements"? Not exactly. Could use "Work Environment" as a heading though not in examples but allowed? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. We could incorporate Work Environment into About the role or Responsibilities? Probably better to have a section "Work Environment" but it's not in list; risk. However the instruction says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also use other headings if needed? The examples are just examples; not exclusive. I'd keep Work Environment as its own heading; it's substantive. Similarly Job Type & Location could be under "Schedule"? Not exactly. Could be under "Job Type & Location" but not in list. Might be okay. Given the instruction to prefer few substantive sections over many thin ones, we could combine some. Let's think: We have: - About the role (paragraph) - Responsibilities (list) - Qualifications/Skills (list) - Work Environment (paragraph) - Job Type & Location (paragraph) - Pay and Benefits (pay range paragraph + benefits list) - Workplace Type (maybe same as Job Type & Location, could merge) - Application Deadline (maybe minor metadata, could be short p under About the role or separate small section not required; but we could drop as minor metadata? It's substantive but could be folded into a short p under About the role? Might be okay. - About Aston Carter (company description) could be folded into About the role or separate short p. We need to preserve all substantive information; we can't drop details like pay range, benefits list, job type, location, work environment, etc. We can combine Job Type & Location and Workplace Type into one paragraph under a heading "Job Details". But we don't have that heading in examples; but we could use "Job Type & Location" as heading (makes sense). Workplace Type is essentially same info (fully onsite). Could be included in same paragraph. Thus sections: - About the role - Responsibilities - Qualifications (or Skills) - Work Environment - Job Type & Location (including workplace type) - Pay and Benefits - Application Deadline (maybe as a short p under About the role? But we can make its own small section "Application Timeline". Not in examples but okay.) - About Aston Carter (maybe as "About the Company"). But to keep few sections, we could merge About Aston Carter and Application Deadline into a short paragraph under About the role? Might lose some detail but still preserve. The instruction says preserve ALL substantive information; we can embed them in paragraphs. Thus final sections:
About the role
... include role description, plus company description and application deadline maybe.
Responsibilities
- ...
Qualifications
- ...
Work Environment
...
Job Type & Location
...
Pay and Benefits
Pay range: $35.00 - $40.00/hr.
- ... benefits list
- . Now Qualifications: combine Essential Skills and Additional Skills & Qualifications. Essential Skills list (numbered 1-7): "1–7 years of accounting experience with a focus on general ledger activities. Solid understanding of general ledger structures, including cost centers, entities, and account coding. Hands-on experience inputting, preparing, and posting journal entries, including manual and correcting entries. Experience performing month-end close processes and account reconciliations. Proficiency in reconciling subledgers to the general ledger, identifying variances, and tracing them to source transactions. Strong Excel skills, including building reconciliation workbooks from scratch, using pivot tables, and applying VLOOKUP or XLOOKUP functions. Ability to join tables in Excel based on consistent data sets to support data analysis and reconciliation. Capability to troubleshoot journal entry and batch import errors, interpret system messages, and resolve or escalate issues effectively." Additional Skills & Qualifications: "Experience working in a large organization with complex financial structures. Exposure to business warehouse (BW) or similar financial reporting and data tools. Ability to create and manage a SharePoint site or similar shared repository to facilitate information sharing within the accounting team. Strong analytical mindset with a desire to dig into issues and identify root causes rather than only flagging discrepancies. Attention to detail and commitment to maintaining accurate and reliable financial records. Effective communication skills to collaborate with colleagues and explain reconciliation findings and journal entry issues." We can combine into a single list (no numbering). Ensure we don't duplicate. Now Work Environment paragraph: "This role is based in a professional office setting within a large organization. You will work on-site Monday through Friday during regular business hours. The environment offers a modern, well-appointed office and access to financial systems and tools, including Excel and potentially business warehouse (BW) reporting solutions. Collaboration with other accounting and finance team members is an integral part of the role, with shared resources managed through platforms such as SharePoint." Job Type & Location paragraph: "This is a Contract position based out of Saint Louis, MO. This is a fully onsite position in Saint Louis, MO." We could combine: "This is a Contract position based out of Saint Louis, MO. The role is fully onsite." Pay and Benefits