Project Coordinator
Aston Carter · Dallas, TX · 1 mo ago
RemoteRemoteOTHR$33–$38/hrContract
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. No Job ID etc. Remove boilerplate.
We need to parse the job description.
Key sections:
- About the role: The first paragraph after job title: "The Project Coordinator supports complex, high-revenue engineering and architectural projects by managing contracts, proposals, financial tracking, and project documentation. This role prepares and reviews key project documents, monitors financial performance, and serves as a central liaison between project managers, internal teams, suppliers, and clients to ensure projects adhere to contract requirements and achieve strong financial outcomes."
That is about the role.
- Responsibilities: list of bullet points under "Responsibilities". We'll capture each bullet.
- Essential Skills: list of required skills/experience. Could be under Requirements or Qualifications. The posting has "Essential Skills" and "Additional Skills & Qualifications". We can combine into Requirements/Qualifications. But we need to decide headings: maybe "Requirements" for essential skills, "Qualifications" for additional? Or just one "Requirements". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple if content exists.
We have:
- Essential Skills: list of at least 2 years experience items, plus proficiency etc.
- Additional Skills & Qualifications: list of desirable items.
We could put "Requirements" for essential skills (mandatory) and "Qualifications" for additional (preferred). Or combine into "Skills". But we have also a separate "Skills" heading possible.
We also have Pay And Benefits section: includes pay range and benefits list.
Work Environment: includes remote, time zones, tools.
Job Type & Location: Contract to Hire based out of Dallas, TX. But location is not remote? Actually says fully remote but Job Type & Location says based out of Dallas, TX. Might be metadata; we can incorporate into a short paragraph maybe under About the role or Work Environment. But we should not create heading for Job Type & Location unless we have content. Could fold into a paragraph under About the role or Work Environment.
Application Deadline: not needed (application instructions). Remove.
About Aston Carter: company description; could be considered boilerplate? It's not required but could be considered "About the company". Not in allowed headings list but we could put under "About the role"? Probably better to omit as it's company boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Aston Carter" is not exactly those but could be considered company overview; not required to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep substantive info about the company? It's not directly about the role but could be considered relevant. However typical job posting includes company overview; we might keep it under a heading like "About the Company" but not in allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create other headings. We could incorporate company info into About the role paragraph? Might be okay to add a short paragraph about the employer under About the role? But the instruction says About the role heading for section headings (e.g. About the role...). So we can put company description under About the role? Might be stretching.
Better to keep only role-related content; company description may be considered not essential to the role but still substantive. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. But we lack a heading for it; we could put it under About the role as a paragraph after role description. That seems acceptable.
Now Pay And Benefits: we have pay range and benefits list. So we need a Pay section (maybe also Benefits). The instruction: Prefer a few substantive sections over many thin ones. Could combine Pay and Benefits under one heading "Pay and Benefits"? But allowed headings list includes Pay and Benefits separately. We could create both if content exists. We have pay range and benefits list. So we can have
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. No Job ID etc. Remove boilerplate.
We need to parse the job description.
Key sections:
- About the role: The first paragraph after job title: "The Project Coordinator supports complex, high-revenue engineering and architectural projects by managing contracts, proposals, financial tracking, and project documentation. This role prepares and reviews key project documents, monitors financial performance, and serves as a central liaison between project managers, internal teams, suppliers, and clients to ensure projects adhere to contract requirements and achieve strong financial outcomes."
That is about the role.
- Responsibilities: list of bullet points under "Responsibilities". We'll capture each bullet.
- Essential Skills: list of required skills/experience. Could be under Requirements or Qualifications. The posting has "Essential Skills" and "Additional Skills & Qualifications". We can combine into Requirements/Qualifications. But we need to decide headings: maybe "Requirements" for essential skills, "Qualifications" for additional? Or just one "Requirements". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple if content exists.
We have:
- Essential Skills: list of at least 2 years experience items, plus proficiency etc.
- Additional Skills & Qualifications: list of desirable items.
We could put "Requirements" for essential skills (mandatory) and "Qualifications" for additional (preferred). Or combine into "Skills". But we have also a separate "Skills" heading possible.
We also have Pay And Benefits section: includes pay range and benefits list.
Work Environment: includes remote, time zones, tools.
Job Type & Location: Contract to Hire based out of Dallas, TX. But location is not remote? Actually says fully remote but Job Type & Location says based out of Dallas, TX. Might be metadata; we can incorporate into a short paragraph maybe under About the role or Work Environment. But we should not create heading for Job Type & Location unless we have content. Could fold into a paragraph under About the role or Work Environment.
Application Deadline: not needed (application instructions). Remove.
About Aston Carter: company description; could be considered boilerplate? It's not required but could be considered "About the company". Not in allowed headings list but we could put under "About the role"? Probably better to omit as it's company boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Aston Carter" is not exactly those but could be considered company overview; not required to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep substantive info about the company? It's not directly about the role but could be considered relevant. However typical job posting includes company overview; we might keep it under a heading like "About the Company" but not in allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create other headings. We could incorporate company info into About the role paragraph? Might be okay to add a short paragraph about the employer under About the role? But the instruction says About the role heading for section headings (e.g. About the role...). So we can put company description under About the role? Might be stretching.
Better to keep only role-related content; company description may be considered not essential to the role but still substantive. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. But we lack a heading for it; we could put it under About the role as a paragraph after role description. That seems acceptable.
Now Pay And Benefits: we have pay range and benefits list. So we need a Pay section (maybe also Benefits). The instruction: Prefer a few substantive sections over many thin ones. Could combine Pay and Benefits under one heading "Pay and Benefits"? But allowed headings list includes Pay and Benefits separately. We could create both if content exists. We have pay range and benefits list. So we can have Pay
with pay range paragraph, and Benefits
with list.
Schedule: we have work environment mentions time zones (Eastern, Central, Mountain) to align with core business hours. That's schedule info. So we can create Schedule section.
Now we need to output only HTML fragment, no /, no markdown.
Let's extract content.
About the role paragraph: combine first paragraph and maybe company description? Let's keep role description only under About the role. Then maybe add a short paragraph about employer under same heading? Could be okay.
Responsibilities: list each bullet.
Essential Skills: list each bullet under Requirements.
Additional Skills & Qualifications: list each bullet under Qualifications.
Skills: maybe we could have a Skills heading for technical proficiencies (Excel, Deltek, etc.) but those are already in Essential Skills. Could skip separate Skills heading.
Pay: paragraph with pay range.
Benefits: list of benefits.
Schedule: paragraph about time zones and remote.
Work Environment: maybe we could incorporate into Schedule or About the role. But we have details about remote, tools, time zones. We already have Schedule for time zones. Work Environment could be under About the role or maybe we create a Work Environment heading? Not in allowed list but we could put under About the role. Let's incorporate work environment details into About the role or Schedule.
Better: About the role includes role description; Work Environment could be separate but not in allowed list. So we can add a paragraph under About the role covering work environment details (remote, tools, time zones). Then Schedule maybe not needed. But we have schedule info about time zones; we could include that in About the role as well. However the instruction: prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits. That's six sections. Schedule maybe redundant if we include time zones in About the role.
Let's decide: We'll include About the role (including role description, work environment, remote, tools, time zones). Responsibilities, Requirements (essential skills), Qualifications (additional skills), Pay, Benefits.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now extract specifics.
About the role paragraph: "The Project Coordinator supports complex, high-revenue engineering and architectural projects by managing contracts, proposals, financial tracking, and project documentation. This role prepares and reviews key project documents, monitors financial performance, and serves as a central liaison between project managers, internal teams, suppliers, and clients to ensure projects adhere to contract requirements and achieve strong financial outcomes."
Add work environment: "This is a fully remote position supporting engineering and architectural projects for a large, high-revenue organization. The role operates within a professional, collaborative culture where team members report high satisfaction with their work environment. You will work closely with project managers and Business Operations teams using tools such as Microsoft Excel, Deltek, BST, Oracle, and potentially Deltek Vantagepoint. The position requires working from locations within Eastern, Central, or Mountain time zones to align with core business hours and project team schedules. The work is primarily computer-based, focusing on contract management, financial analysis, and project coordination in a structured yet supportive environment."
Add job type location: "This is a Contract to Hire position based out of Dallas, TX." Could be included.
Now Responsibilities list: need to capture each bullet exactly.
Let's list them:
- Prepare fee proposal templates, draft contracts, and subcontracts for review, ensuring accuracy and alignment with project requirements.
- Review contracts and subcontracts to confirm that projects adhere to contract language, terms, and conditions throughout the project lifecycle.
- Issue and track project amendment documentation, including change orders, and coordinate reviews and approvals with relevant stakeholders.
- Develop Work Breakdown Structures (WBS) and Project Authorization forms, including detailed budgets and client invoicing requirements.
- Assist project managers with the processing of subconsultant invoices through the project accounting system, ensuring timely and accurate payment.
- Monitor project financials, including variance, revenue, budgets, and work in progress (WIP), and follow up on revenue variance issues to support revenue recovery.
- Participate in resolving project financial issues by collaborating with project managers and Business Operations teams.
- Serve as a liaison between internal staff, suppliers, and clients, communicating effectively on behalf of project managers to support smooth project execution.
- Conduct pre-bill reviews with project managers as necessary to validate billing accuracy and compliance with contract terms.
- Participate in monthly project review meetings and collaborate with Business Operations teams to assess project performance.
- Assist Business Operations with analysis of project budget performance and provide recommendations to improve financial outcomes.
- Support the creation and maintenance of proposal templates and other project documentation to standardize and streamline project initiation processes.
Now Essential Skills (requirements):
- At least 2 years of experience drafting contracts and subcontracts.
- At least 2 years of experience preparing proposal templates for professional services projects.
- At least 2 years of experience managing and processing change orders.
- At least 2 years of experience working closely with project managers on active projects.
- Experience working for an engineering or architectural firm with revenue over $150 million.
- Strong ability to review and interpret contracts and subcontracts to ensure compliance.
- Proficiency in creating pivot tables and using VLOOKUP functions in Microsoft Excel.
- Proficiency with project accounting or enterprise systems such as Deltek, BST, or Oracle.
- Experience with contract, invoicing, and change order processes within a project environment.
- Ability to develop and manage proposals and proposal templates in alignment with organizational standards.
Now Additional Skills & Qualifications (qualifications):
- Experience with Deltek Vantagepoint is highly desirable.
- 2 or more years of experience working on FDOT or Florida-based projects is a plus.
- Experience in coordinating projects within engineering or architectural firms is beneficial.
- Strong analytical skills with the ability to evaluate project budget performance and recommend improvements.
- Excellent communication and interpersonal skills to effectively liaise between internal teams, suppliers, and clients.
- Detail-oriented approach to managing documentation, financial data, and contract requirements.
- Ability to work independently in a remote environment while maintaining strong collaboration with project managers and Business Operations teams.
Now Pay: "The pay range for this position is $33.00 - $38.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors."
We could keep that paragraph.
Now Benefits list: bullet list:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
Now ensure we don't include boilerplate like "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's somewhat generic but still substantive? It's about benefits eligibility. Could include as a sentence before list. But it's somewhat generic; still maybe keep. However the instruction: prefer few substantive sections over many thin ones. Could include a short paragraph about benefits eligibility then list.
We'll include a brief sentence: "Eligibility requirements apply to some benefits and may depend on job classification and length of employment. Benefits are subject to change." Then list.
Now we need to output HTML.
Structure:
About the role
... (combined paragraphs)
Responsibilities
- ...