Jobs · Design · Missouri

Structural Engineer II

Clayco · St Louis, MO · 2 wk ago
On-siteDesign$8.1/hrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate. We need to parse the posting. Content: - About Us (company description) - maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" maybe summarizing description of role? The posting includes "The Role We Want You For" and "Scope of Responsibility" and "The Specifics of the Role". We can combine into sections: About the role (maybe a paragraph summarizing role), Responsibilities (list of duties), Requirements (education/experience), Qualifications (maybe similar to requirements?), Skills (list of skills), Benefits (list), Pay (maybe not given specifics; they have compensation paragraph but not a range; they say salary range considers factors... no specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated (Discretionary Annual Bonus..., Comprehensive Benefits Package...). So Benefits section is okay. Pay: they have a paragraph about compensation but no specific numbers or range; they say "The salary range for this position considers a wide range of factors...". That's not a specific figure; it's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT include Pay section because it's not specific. Schedule: not mentioned. So omit. Qualifications: maybe we can treat Requirements as qualifications? The posting has "Requirements" heading with bullet list? Actually they have "RequirementsAssociate’s degree...". That's a paragraph. Also they have "Some Things You Should Know" etc. We could treat "Requirements" as a section. Also "Qualifications" maybe not separate; we could combine. But we need to follow instruction: Use headings for those categories if content exists. We have content for Requirements (education, experience). We have content for Skills (list of skills like Revit, Navisworks, etc). We have Benefits. We have About the role (maybe a paragraph summarizing role). We have Responsibilities (list of duties). Let's extract. Let's parse sections: About Us: company description - maybe not needed as a heading; but we could include as part of About the role? Probably not. The instruction says use headings for sections like About the role, Responsibilities, etc. So we can create About the role paragraph summarizing the role description from "The Role We Want You For", "Scope of Responsibility", "The Specifics of the Role". We'll combine into a paragraph. Responsibilities: list of duties from "Scope of Responsibility" and "The Specifics of the Role". We'll extract bullet points. Requirements: education/experience from "Requirements" paragraph. Qualifications: maybe we can treat as same as Requirements? But we could also include "Some Things You Should Know" as qualifications? Not sure. Safer to not create Qualifications if no distinct content. We'll skip. Skills: list of skills from "The Specifics of the Role": Uses Revit Structures effectively, Ability to use Navisworks effectively a plus, Good knowledge of how construction documents are put together, Creates conceptual structural models..., Incorporates standard notes..., Manages and incorporates electronic or paper redlines..., Takes complete ownership..., Highly focused on quality..., Highly proficient in checking his/her own work..., Able to mentor junior designers..., Trained in Autodesk Revit Structure..., Motivated and Self Starter..., Positive and team oriented attitude, Communicates well... We'll put these as
  • . Benefits: list from "BenefitsDiscretionary Annual Bonus: Subject to company and individual performance.Comprehensive Benefits Package Including: Medical, dental and vision plans, 401k, PTO and paid company holidays, employee assistance program, flexible spending accounts, life insurance, disability coverage, learning & development programs and more!" We'll parse into bullet points. Pay: not specific, skip. Schedule: none. We must not include boilerplate like About Us, About LJC, etc. Also remove duplicated lines, cookie/navigation/legal/EEO etc. Not present. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include. For About the role paragraph, we need to include the substance from those sections but not omit details. We'll need to write a paragraph that captures the role description: Structural Designer II will work with in-house Development, Architecture, and Construction teams to provide Structural Design and Quality Assurance on industrial projects for nationwide clients. This role is for St. Louis office, on-site. Works closely with more experienced engineers and designers to assist in development of deliverables. Expected to execute work on one or more intermediate level tasks simultaneously as delegated by Lead or Sr. Designer. May delegate basic tasks to Entry-Level Designers and provide oversight. Able to work self-sufficiently most of the time and understands basics of communicating effectively with engineers and other disciplines. That's from Scope of Responsibility. Then The Specifics of the Role list of duties. We'll incorporate those as responsibilities list, not in About the role paragraph. So About the role paragraph can be a high-level summary: The Structural Designer II will work with in-house Development, Architecture, and Construction teams to provide Structural Design and Quality Assurance on industrial (distribution, manufacturing, food and beverage, cold storage) projects for nationwide clients. This is an on-site position based in the St. Louis office. That seems fine and retains substantive info. Now Responsibilities: we need to list duties from Scope of Responsibility and The Specifics of the Role. But we must avoid duplication. Let's list: - Work closely with more experienced engineers and designers to assist in the development of deliverables. - Execute work on one or more intermediate level tasks simultaneously as delegated by the Lead or Sr. Designer. - Delegate basic and fundamental tasks to Entry-Level Designers and provide oversight of their work. - Work self-sufficiently most of the time and understand basics of communicating effectively with engineers and other disciplines involved in the project. - Use Revit Structures effectively. - Ability to use Navisworks effectively (a plus). - Good knowledge of how construction documents are put together. - Create conceptual structural models based on verbal direction or rough sketches from engineers or other designers. - Incorporate standard notes and details for use in the construction documents. - Manage and incorporate electronic or paper redlines from the Structural Engineer using established workflows. - Take complete ownership of their portion of the structural scope, reliably working to meet schedule, budget, and quality requirements. - Be highly focused on quality, ensuring conformance with established structural standards, project standards, and project delivery processes. - Be highly proficient in checking his/her own work and coordinating work with related disciplines to avoid clashes. - Mentor junior designers by assisting with finding answers to technical questions and concerns. - Be trained in Autodesk Revit Structure (Architectural/Structural design in 3D modeling). - Be motivated and self‑starter, pay attention to details, and be willing to learn other disciplines if needed. - Maintain a positive and team‑oriented attitude. - Communicate well with team members and consultants. That seems comprehensive. Now Requirements: from "RequirementsAssociate’s degree in Computer Aided Drafting and Design or similar technical degree. (or 3+ years of experience utilizing BIM software)2-5 years of experience required, in an operating company or design firm setting." We need to format as list maybe. We'll put as
    • Associate’s degree in Computer Aided Drafting and Design or similar technical degree (or 3+ years of experience utilizing BIM software)
    • 2‑5 years of experience required, in an operating company or design firm setting
    Now Benefits: list items. - Discretionary Annual Bonus: Subject to company and individual performance. - Comprehensive Benefits Package Including: - Medical, dental and vision plans - 401k - PTO and paid company holidays - Employee assistance program - Flexible spending accounts - Life insurance - Disability coverage - Learning & development programs and more We'll format as
    • Discretionary Annual Bonus: Subject to company and individual performance.
    • Comprehensive Benefits Package Including:
      • Medical, dental and vision plans
      • ... etc. But nested lists maybe okay. Simpler: just list each benefit as separate
      • . We'll include the bonus as one, then each benefit. Thus: - Discretionary Annual Bonus: Subject to company and individual performance. - Medical, dental and vision plans - 401k - PTO and paid company holidays - Employee assistance program - Flexible spending accounts - Life insurance - Disability coverage - Learning & development programs and more Now we need to output only HTML fragment, no /, no markdown. We'll produce:

        About the role

        ...

        Responsibilities

          ...

        Requirements

          ...

        Skills

          ...

        Benefits

          ...
        We should not include Qualifications, Pay, Schedule. Check for any repeated content: Ensure we didn't miss any substantive info like "The Role We Want You For" includes "This role is for the our St. Louis office, and is an on-site position." We included that in About the role. Also "Some Things You Should Know" includes bullet points: "Our clients and projects are nationwide.", "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 is substantive info; we should include somewhere. Where? Could be part of About the role or maybe a separate section like "About the company" but we are not supposed to add headings unless real specific content. We could incorporate these details into About the role paragraph or maybe a separate

        About the company

        but not in allowed list. The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings for those sections if we have them. It doesn't say we cannot add other headings, but better to stick to those. We could incorporate the "Some Things You Should Know" into About the role paragraph as additional details. Thus About the role paragraph can be expanded: The Structural Designer II will work with in-house Development, Architecture, and Construction teams to provide Structural Design and Quality Assurance on industrial (distribution, manufacturing, food and beverage, cold storage) projects for nationwide clients. This is an on-site position based in the St. Louis office. Clayco’s clients and projects are nationwide; the firm offers a collaborative design‑build approach not found elsewhere, works on creative, complex, award‑winning, high‑profile jobs, and operates at a fast pace. That captures the "Some Things You Should Know" points. Now ensure we didn't lose any other substantive info: The "About Us" and "About LJC" descriptions are company overview; we may not need to include as they are not role-specific. The instruction says preserve ALL substantive information; but does that mean we must include all info from posting, even company overview? It says "Preserve ALL substantive information; do NOT invent or summarize away detail."

Similar jobs

Structural Engineer II

Lake Superior ConsultingCranberry Township, PA· 1 mo ago
Engineering$78k–$94k/yrapply on jobs.lsconsulting.com

Structural Engineer II

OceaneeringHanover, MD· 2 mo ago
Engineering$75k–$112k/yrapply on ebfr.fa.us2.oraclecloud.com

Structural Engineer II

Hargrove Engineers & ConstructorsCleveland, OH· 3 mo ago
Engineeringapply on hargroveepc.wd12.myworkdayjobs.com