Procore Support Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - About Us: description of Clayco. Could be "About the role"? Actually "About Us" is company description. Might be considered "About the role"? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe summarizing role description), Responsibilities (list of duties), Requirements (list of requirements), Qualifications (maybe same as requirements?), Skills (maybe list of skills), Benefits (list of benefits), Pay (if present), Schedule (if present). We need to include only sections with real content. Let's extract: - About Us: description of Clayco. Could be placed under "About the role"? Actually "About the role" is about the role, not company. But we could treat "About Us" as "About the role"? Might be better to have "About the role" summarizing the role description: "We are looking for an experienced Procore Support Engineer to join our team based in St. Louis, MO. The Procore Support Engineer plays a key role..." That's from "The Role We Want You For". So we can put that under About the role. - Responsibilities: list of duties under "The Specifics of The Role". Those bullet points: Provide day-to-day administration..., Support end users..., Monitor system performance..., Assist with updates..., Employ process standardization..., Develop and maintain internal documentation..., Collaborate with functional area leaders..., Participate in quality assurance checks..., Support the Procore Support Manager..., Support the delivery of reference materials., Serve as a Procore subject matter expert..., Gather feedback..., Assist in the evaluation and testing..., Support process improvement initiatives... We can list those as

  • . - Requirements: list under "Requirements". Those bullet points: Experience supporting construction technology systems..., Solid understanding..., Strong analytical..., Self-motivated..., Excellent communication..., Capacity to produce clear..., Proven ability..., Familiarity..., Experience supporting..., Exposure to... We can list as
    • . - Qualifications: maybe same as requirements? Could combine? But we need separate sections only if content distinct. The posting has "Requirements" and also "Some Things You Should Know" (some extra info). Also "Why Clayco?" (benefits/recognition). Also "Benefits" section. Also "Compensation" (Pay). Also maybe "Schedule"? Not present. We need to decide sections: - About the role: from "The Role We Want You For" paragraph. - Responsibilities: from "The Specifics of The Role" bullet list. - Requirements: from "Requirements" bullet list. - Benefits: from "Benefits" paragraph (list of benefits). It includes "Discretionary Annual Bonus: Subject to company and individual performance" and "Comprehensive Benefits Package Including: Medical, dental and vision plans, 401k, generous PTO and paid company holidays, employee assistance program, flexible spending accounts, life insurance, disability coverage, learning & development programs and more!" So we can list as
      • . - Pay: from "Compensation" paragraph. It says: "The salary range for this position considers a wide range of factors in making compensation decisions including but not limited to: Education, qualifications, skills, training, experience, certifications, internal equity, and location. Compensation decisions are dependent on the facts and circumstances of each case." This is vague, no actual numbers. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation but not a specific range. It says "The salary range for this position considers a wide range of factors..." but does not give actual numbers. Is that considered stating them? It mentions salary range but not actual numbers. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation discussion but not a specific range. Might be considered stating them? It says "The salary range for this position considers a wide range of factors..." which is generic. It does not give a range. I'd argue it's not concrete enough to create a Pay section. Safer to omit Pay section. - Schedule: not present. - Qualifications: maybe we could treat "Some Things You Should Know" as Qualifications? Actually that section includes: "No other builder can offer the collaborative design-build approach that Clayco does. We work on creative, complex, award-winning, high-profile jobs. The pace is fast! This position is classified as a safety-sensitive role in accordance with applicable state and federal laws. Candidates selected for this position will be subject to a comprehensive background check, which includes mandatory drug testing." That's more about role specifics, maybe could be "Qualifications" or "Additional Info". But we already have Requirements. Could create a section "Qualifications" for those points? However they are not qualifications but role specifics. Might be better to include them under "About the role" or as a separate section "Additional Information". But instruction only lists certain headings; we can still use other headings? It says use

        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 put the safety-sensitive info under "Requirements" maybe? But it's not a requirement. Could put under "About the role" as extra prose. - Skills: not explicitly listed separate; could be derived from requirements but we might not need a separate Skills section if we already have Requirements. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one? But we have separate headings for Requirements and Skills. If we don't have distinct skills list, we could omit Skills section. Thus final sections: About the role, Responsibilities, Requirements, Benefits. We need to preserve all substantive information. Let's extract each piece. About the role: combine "The Role We Want You For" paragraph and maybe also "About Us"? Actually About Us is company description, not role. But we could include company description under About the role? Might be considered "About the role" includes company context. The instruction: About the role heading example. We'll include both the company overview and role description? Might be too much but preserves info. However "About Us" is separate heading in original; we could treat that as "About the role"? Might be okay. Let's craft About the role paragraph: Combine Clayco description and role overview. Clayco description: "Clayco is a full-service, turnkey real estate development, master planning, architecture, engineering, and construction firm that safely delivers clients across North America the highest quality solutions on time, on budget, and above and beyond expectations. With $8.1 billion in revenue for 2025, Clayco specializes in the 'art and science of building,' providing fast track, efficient solutions for mission critical, industrial, life sciences, power & energy, aviation, commercial, institutional, residential and sports & entertainment related building projects." Role overview: "We are looking for an experienced Procore Support Engineer to join our team based in St. Louis, MO. The Procore Support Engineer plays a key role in supporting the launch, maintenance, and ongoing operational consistency of Procore across the enterprise. This position is part of a centralized Procore Support Team responsible for managing multiple Procore instances to support the Clayco enterprise, ensuring seamless administration, user support, and alignment with enterprise processes and standards. The ideal candidate is highly collaborative, detail-oriented, and experienced in Procore, and more generally, construction technology systems. They will work closely with project teams, internal stakeholders, and system administrators to ensure Procore is effectively utilized, continuously improved, and fully supported across the organization." We can combine into a few paragraphs. Responsibilities: list each bullet from "The Specifics of The Role". Let's extract them exactly: - Provide day-to-day administration of Procore, including user permission maintenance, tool configuration, integration variance reporting, and troubleshooting. - Support end users through ticket resolution, technical and process guidance, and escalation management. - Monitor system performance, oversee maintenance cycles, and coordinate with Procore support as needed. - Assist with updates, new feature evaluation, maintenance releases, and rollout planning. - Employ process standardization through tool configuration, ensuring consistent Procore usage enterprise-wide that support Clayco SOPs. - Develop and maintain internal documentation including SOPs, work instructions, and other support materials. - Collaborate with functional area leaders to align Procore configurations with business requirements and workflows. - Participate in quality assurance checks to ensure governance compliance across all Procore instances. - Support the Procore Support Manager in delivering enterprise-wide communication around Procore education resources, updates, and best practices. - Support the delivery of reference materials. - Serve as a Procore subject matter expert during onboarding, project mobilizations, and major system releases. - Gather feedback from end users, identify trends, and recommend enhancements to improve system usability and operational alignment. - Assist in the evaluation and testing of new Procore features. - Support process improvement initiatives that elevate user experience and drive consistent, enterprise-wide tool adoption. We need to preserve all; ensure no duplication. Requirements: list each bullet from "Requirements": - Experience supporting construction technology systems, with Procore strongly preferred. - Solid understanding of construction management processes and the financial workflows that support project planning and execution. - Strong analytical and troubleshooting skills. - Self-motivated with the ability to work independently and collaborate effectively within a team. - Excellent communication and customer service skills. - Capacity to produce clear, structured technical documentation. - Proven ability to manage multiple priorities in a fast-paced operational environment. - Prior experience administering Procore or similar PMIS (Kahua, Prolog, e-Builder, ProjectSite) - Familiarity with enterprise software governance models. - Experience supporting a multi-instance or large-scale software deployment. - Exposure to training development, change management, or process improvement disciplines. Benefits: list from "Benefits": - Discretionary Annual Bonus: Subject to company and individual performance - Comprehensive Benefits Package Including: Medical, dental and vision plans, 401k, generous PTO and paid company holidays, employee assistance program, flexible spending accounts, life insurance, disability coverage, learning & development programs and more! We could split into items: Discretionary Annual Bonus, Medical, dental and vision plans, 401k, generous PTO and paid company holidays, employee assistance program, flexible spending accounts, life insurance, disability coverage, learning & development programs. But the text says "Comprehensive Benefits Package Including: ..." So we can list each item. We'll create

        • for each. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

          About the role

          ... paragraphs ...

          Responsibilities

          • ...
          ...

          Requirements