Designer - Structural
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include. The posting includes:
- Description (intro paragraph about role, location, etc.)
- About Martin/Martin, Inc. (company description)
- The Team (team description)
- Responsibilities (list)
- Requirements (list with required and desired)
- Working Conditions, Skills, And Abilities (list)
- Compensation (salary range, bonus, base salary review)
- Perks & Benefits (list)
- Professional Development (list)
We should not include sections like "About the role" if we already have description; but we could have a section "About the role" for the description paragraph. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It suggests we can use those headings if content exists. We need to decide which headings to use.
We have description content: could be placed under
About the role
with a .
We have company info: maybe not needed as separate heading; could be part of About the role? But we could also include a section "About Martin/Martin, Inc." but not in the list of allowed headings. 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 those as examples. Probably we should stick to those headings where applicable. Could also include "About the company" but not required. Safer to include only those headings that match content.
Thus sections:
- About the role (description paragraph)
- Responsibilities (list)
- Requirements (list)
- Working Conditions, Skills, And Abilities (maybe combine as Skills? Could be "Skills" heading)
- Pay (compensation)
- Benefits (perks & benefits)
- Professional Development (maybe under "Benefits"? but it's separate; we could include as "Professional Development" heading though not in examples but allowed? 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 suggests we can use those. However "Professional Development" is not in list; but we could incorporate into Benefits or Skills? Might be better to include as its own heading if content exists; but risk violating instruction? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates examples, not exhaustive list. So we can use other headings as needed. Probably fine.
We must not include empty sections. All have content.
We need to remove boilerplate: EEO, etc. Also remove duplicated lines: there is a Salary Description line at end duplicate of compensation; we should keep only one.
We need to preserve all substantive information.
Let's extract content.
Description paragraph: "Martin/Martin, Inc. is looking for a Building Information Modeling (BIM) Designer to join our Structural Engineering Group in our Denver, Colorado office. This position will provide opportunities to work on a variety of structures throughout Front Range of Colorado and nationally in markets such as healthcare, commercial office, sports and entertainment and education. A typical work week can include BIM 3D model development, project setup, drafting of 2D and 3D details, 3D model coordination and site visits working directly with a team of engineers. We operate in a dynamic environment and strive to support a culture that is collaborative, innovative, and creative. We encourage an environment of continuous learning through in-house training and mentoring programs. Additionally, each project presents unique challenges and opportunities to learn and grow as a Designer. The successful candidate will develop expertise in a broad range of BIM skills, demonstrate a willingness to learn, work as part of a team, and produce high-quality designs for our clients."
About Martin/Martin, Inc.: "Martin/Martin, Inc. is a civil, structural, and investigative consulting engineering firm, headquartered in the Denver area, built on experience and industry leadership cultivated since the 1940s. Our engineered solutions are developed through a culture of integrity, service, creativity, and quality for the benefit of our clients and the community. With ten office locations and a staff of 400+, Martin/Martin engineers have project experience in all 50 states and on all seven continents. (Yes, even Antarctica!) View our 2025 Year in Review here."
The Team: "Our structural engineering teams provide custom solutions for new constructions and expansions, with a strong record in notable projects like Coors Field, the Alice L. Walton School of Medicine, and Harborcenter."
We could combine About Martin/Martin and The Team into a single "About the company" section, but we have no heading for that. Could put under About the role? Might be okay to include as separate About the Company
. But instruction didn't forbid. I'd include as About the Company
with two paragraphs.
Responsibilities: list items:
- Develops complex models and drafts complex details
- Models and drafts without explicit redline and sometimes with only verbal direction
- Writes narratives for model and drawing revisions
- Manages production of the contract documents
- Manages downloading/uploading/cloud publishing and maintenance of linked files
- Checks drawings for adherence to department’s modeling/drafting standards
- Communicates with department, company, and client personnel in a professional manner
- Leads or trains lower-level and less experienced staff
- Represents design team at model coordination meetings
Requirements: Required list:
- Advanced knowledge of department’s modeling/drafting software (Revit) and standards
- Advanced knowledge of structural components and systems being designed and how they are constructed
- Advanced knowledge of drawing layout and assembly
- Able to assist project managers in estimating time for budgeting of modeling/drafting tasks
- Demonstrated effective verbal, organizational, and written skills
- Highly proficient in modeling systems and components
- Highly proficient in creating details, plans, drawing sets, and construction packages
- Must be eligible to work for any employer in the United States, without the need for visa sponsorship now or in the future.
- Ability to work in the Denver, Colorado area.
- Relocation reimbursement may be provided, depending on the role and job function.
Desired:
- 2-year Associate’s Degree in a related field
- Develops models from client’s models and is skilled in development of associated drawings
- Addresses coordination issues between disciplines with minimal direction
We could combine required and desired into one list, maybe separate subheadings? But we can just list all items; maybe separate with
indicating required vs desired. But we need to preserve all info. Could do two
with headings Required:
etc. However instruction says use - for any list of duties/requirements/benefits. It doesn't forbid headings inside. We'll do
Required:
... then Desired:
...
Working Conditions, Skills, And Abilities: list:
- Move inside or outside the office and on non-ADA accessible construction sites
- Remain stationary for long periods of time
- Repetitive movement on tasks such as using a keyboard or mouse
- Carry, ascend, and descend a ladder
- Identify color
- Read, communicate, and document in English
- Determine and exchange accurate information
- Occasionally move or hold equipment weighing up to 50 pounds
Compensation: includes:
- Base Salary: For individuals hired in Colorado, a reasonable estimate of the current range for this role is $90,000 to $98,000 annually.
- Base Salary Review: This role is eligible to participate in Martin/Martin’s annual base salary increase review process.
- Annual Bonus: This role is eligible to participate in a discretionary annual bonus program.
- Base salary review and increases, in addition to annual bonuses, are dependent on various factors, including a hired individual’s job-level and annual company performance.
Also there is a Salary Description line duplicate: "$90,000 - $98,000 / Year". We'll keep only one.
Perks & Benefits list:
- Medical/Dental/Vision, including plans with 100% (employee-only) coverage
- Minimum 3 weeks Paid Time Off (PTO) and 9-observed company holidays annually
- Hybrid Work Schedule
- Annual Wellness Subsidy
- Sabbatical
- 401(k) Plan Company Match
- Annual Profit Sharing (when appropriate)
- Extensive Employee Events (outings, picnics, golf, and ski days)
- Committee and Community Involvement
Professional Development:
- Martin/Martin provides ongoing internal continuing education, training, and mentorship, reimbursement for PE/SE licenses, and encouraged active participation in professional organizations.
We could format as - ... but it's a single sentence; could be
. But instruction says use
- for any list of duties/requirements/benefits. This is a list? It's a single item; we could still use
- . Or just
. Safer to use
for prose.
Now we need to output HTML fragment only.
We'll structure:
About the role
...
About the Company
...
...
(Team)
Responsibilities
...
Requirements
Required:
...
Desired:
...
Working Conditions, Skills, and Abilities
...
Pay
Base Salary: For individuals hired in Colorado, a reasonable estimate of the current range for this role is $90,000 to $98,000 annually.
Base Salary Review: This role is eligible to participate in Martin/Martin’s annual base salary increase review process.
Annual Bonus: This role is eligible to participate in a discretionary annual bonus program.
Base salary review and increases, in addition to annual bonuses, are dependent on various factors, including a hired individual’s job-level and annual company performance.
Benefits
...
Professional Development
Martin/Martin provides ongoing internal continuing education,
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include. The posting includes: - Description (intro paragraph about role, location, etc.) - About Martin/Martin, Inc. (company description) - The Team (team description) - Responsibilities (list) - Requirements (list with required and desired) - Working Conditions, Skills, And Abilities (list) - Compensation (salary range, bonus, base salary review) - Perks & Benefits (list) - Professional Development (list) We should not include sections like "About the role" if we already have description; but we could have a section "About the role" for the description paragraph. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It suggests we can use those headings if content exists. We need to decide which headings to use. We have description content: could be placed under
About the role
with a. We have company info: maybe not needed as separate heading; could be part of About the role? But we could also include a section "About Martin/Martin, Inc." but not in the list of allowed headings. 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 those as examples. Probably we should stick to those headings where applicable. Could also include "About the company" but not required. Safer to include only those headings that match content.
Thus sections:
- About the role (description paragraph)
- Responsibilities (list)
- Requirements (list)
- Working Conditions, Skills, And Abilities (maybe combine as Skills? Could be "Skills" heading)
- Pay (compensation)
- Benefits (perks & benefits)
- Professional Development (maybe under "Benefits"? but it's separate; we could include as "Professional Development" heading though not in examples but allowed? 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 suggests we can use those. However "Professional Development" is not in list; but we could incorporate into Benefits or Skills? Might be better to include as its own heading if content exists; but risk violating instruction? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates examples, not exhaustive list. So we can use other headings as needed. Probably fine.
We must not include empty sections. All have content.
We need to remove boilerplate: EEO, etc. Also remove duplicated lines: there is a Salary Description line at end duplicate of compensation; we should keep only one.
We need to preserve all substantive information.
Let's extract content.
Description paragraph: "Martin/Martin, Inc. is looking for a Building Information Modeling (BIM) Designer to join our Structural Engineering Group in our Denver, Colorado office. This position will provide opportunities to work on a variety of structures throughout Front Range of Colorado and nationally in markets such as healthcare, commercial office, sports and entertainment and education. A typical work week can include BIM 3D model development, project setup, drafting of 2D and 3D details, 3D model coordination and site visits working directly with a team of engineers. We operate in a dynamic environment and strive to support a culture that is collaborative, innovative, and creative. We encourage an environment of continuous learning through in-house training and mentoring programs. Additionally, each project presents unique challenges and opportunities to learn and grow as a Designer. The successful candidate will develop expertise in a broad range of BIM skills, demonstrate a willingness to learn, work as part of a team, and produce high-quality designs for our clients."
About Martin/Martin, Inc.: "Martin/Martin, Inc. is a civil, structural, and investigative consulting engineering firm, headquartered in the Denver area, built on experience and industry leadership cultivated since the 1940s. Our engineered solutions are developed through a culture of integrity, service, creativity, and quality for the benefit of our clients and the community. With ten office locations and a staff of 400+, Martin/Martin engineers have project experience in all 50 states and on all seven continents. (Yes, even Antarctica!) View our 2025 Year in Review here."
The Team: "Our structural engineering teams provide custom solutions for new constructions and expansions, with a strong record in notable projects like Coors Field, the Alice L. Walton School of Medicine, and Harborcenter."
We could combine About Martin/Martin and The Team into a single "About the company" section, but we have no heading for that. Could put under About the role? Might be okay to include as separate About the Company
. But instruction didn't forbid. I'd include as About the Company
with two paragraphs.
Responsibilities: list items:
- Develops complex models and drafts complex details
- Models and drafts without explicit redline and sometimes with only verbal direction
- Writes narratives for model and drawing revisions
- Manages production of the contract documents
- Manages downloading/uploading/cloud publishing and maintenance of linked files
- Checks drawings for adherence to department’s modeling/drafting standards
- Communicates with department, company, and client personnel in a professional manner
- Leads or trains lower-level and less experienced staff
- Represents design team at model coordination meetings
Requirements: Required list:
- Advanced knowledge of department’s modeling/drafting software (Revit) and standards
- Advanced knowledge of structural components and systems being designed and how they are constructed
- Advanced knowledge of drawing layout and assembly
- Able to assist project managers in estimating time for budgeting of modeling/drafting tasks
- Demonstrated effective verbal, organizational, and written skills
- Highly proficient in modeling systems and components
- Highly proficient in creating details, plans, drawing sets, and construction packages
- Must be eligible to work for any employer in the United States, without the need for visa sponsorship now or in the future.
- Ability to work in the Denver, Colorado area.
- Relocation reimbursement may be provided, depending on the role and job function.
Desired:
- 2-year Associate’s Degree in a related field
- Develops models from client’s models and is skilled in development of associated drawings
- Addresses coordination issues between disciplines with minimal direction
We could combine required and desired into one list, maybe separate subheadings? But we can just list all items; maybe separate with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates examples, not exhaustive list. So we can use other headings as needed. Probably fine.
We must not include empty sections. All have content.
We need to remove boilerplate: EEO, etc. Also remove duplicated lines: there is a Salary Description line at end duplicate of compensation; we should keep only one.
We need to preserve all substantive information.
Let's extract content.
Description paragraph: "Martin/Martin, Inc. is looking for a Building Information Modeling (BIM) Designer to join our Structural Engineering Group in our Denver, Colorado office. This position will provide opportunities to work on a variety of structures throughout Front Range of Colorado and nationally in markets such as healthcare, commercial office, sports and entertainment and education. A typical work week can include BIM 3D model development, project setup, drafting of 2D and 3D details, 3D model coordination and site visits working directly with a team of engineers. We operate in a dynamic environment and strive to support a culture that is collaborative, innovative, and creative. We encourage an environment of continuous learning through in-house training and mentoring programs. Additionally, each project presents unique challenges and opportunities to learn and grow as a Designer. The successful candidate will develop expertise in a broad range of BIM skills, demonstrate a willingness to learn, work as part of a team, and produce high-quality designs for our clients."
About Martin/Martin, Inc.: "Martin/Martin, Inc. is a civil, structural, and investigative consulting engineering firm, headquartered in the Denver area, built on experience and industry leadership cultivated since the 1940s. Our engineered solutions are developed through a culture of integrity, service, creativity, and quality for the benefit of our clients and the community. With ten office locations and a staff of 400+, Martin/Martin engineers have project experience in all 50 states and on all seven continents. (Yes, even Antarctica!) View our 2025 Year in Review here."
The Team: "Our structural engineering teams provide custom solutions for new constructions and expansions, with a strong record in notable projects like Coors Field, the Alice L. Walton School of Medicine, and Harborcenter."
We could combine About Martin/Martin and The Team into a single "About the company" section, but we have no heading for that. Could put under About the role? Might be okay to include as separate About the Company
. But instruction didn't forbid. I'd include as About the Company
with two paragraphs.
Responsibilities: list items:
- Develops complex models and drafts complex details
- Models and drafts without explicit redline and sometimes with only verbal direction
- Writes narratives for model and drawing revisions
- Manages production of the contract documents
- Manages downloading/uploading/cloud publishing and maintenance of linked files
- Checks drawings for adherence to department’s modeling/drafting standards
- Communicates with department, company, and client personnel in a professional manner
- Leads or trains lower-level and less experienced staff
- Represents design team at model coordination meetings
Requirements: Required list:
- Advanced knowledge of department’s modeling/drafting software (Revit) and standards
- Advanced knowledge of structural components and systems being designed and how they are constructed
- Advanced knowledge of drawing layout and assembly
- Able to assist project managers in estimating time for budgeting of modeling/drafting tasks
- Demonstrated effective verbal, organizational, and written skills
- Highly proficient in modeling systems and components
- Highly proficient in creating details, plans, drawing sets, and construction packages
- Must be eligible to work for any employer in the United States, without the need for visa sponsorship now or in the future.
- Ability to work in the Denver, Colorado area.
- Relocation reimbursement may be provided, depending on the role and job function.
Desired:
- 2-year Associate’s Degree in a related field
- Develops models from client’s models and is skilled in development of associated drawings
- Addresses coordination issues between disciplines with minimal direction
We could combine required and desired into one list, maybe separate subheadings? But we can just list all items; maybe separate with
indicating required vs desired. But we need to preserve all info. Could do two
- with headings
- for any list of duties/requirements/benefits. It doesn't forbid headings inside. We'll do
Required:
- ... then
- ... but it's a single sentence; could be
. But instruction says use
- for any list of duties/requirements/benefits. This is a list? It's a single item; we could still use
- . Or just
. Safer to use
for prose. Now we need to output HTML fragment only. We'll structure:
About the role
...
About the Company
...
...
(Team)Responsibilities
- ...
Requirements
Required:
- ...
Desired:
- ...
Working Conditions, Skills, and Abilities
- ...
Pay
Base Salary: For individuals hired in Colorado, a reasonable estimate of the current range for this role is $90,000 to $98,000 annually.
Base Salary Review: This role is eligible to participate in Martin/Martin’s annual base salary increase review process.
Annual Bonus: This role is eligible to participate in a discretionary annual bonus program.
Base salary review and increases, in addition to annual bonuses, are dependent on various factors, including a hired individual’s job-level and annual company performance.
Benefits
- ...
Professional Development
Martin/Martin provides ongoing internal continuing education,
- . Or just
- for any list of duties/requirements/benefits. This is a list? It's a single item; we could still use
Desired:
- ...
Working Conditions, Skills, And Abilities: list:
- Move inside or outside the office and on non-ADA accessible construction sites
- Remain stationary for long periods of time
- Repetitive movement on tasks such as using a keyboard or mouse
- Carry, ascend, and descend a ladder
- Identify color
- Read, communicate, and document in English
- Determine and exchange accurate information
- Occasionally move or hold equipment weighing up to 50 pounds
Compensation: includes:
- Base Salary: For individuals hired in Colorado, a reasonable estimate of the current range for this role is $90,000 to $98,000 annually.
- Base Salary Review: This role is eligible to participate in Martin/Martin’s annual base salary increase review process.
- Annual Bonus: This role is eligible to participate in a discretionary annual bonus program.
- Base salary review and increases, in addition to annual bonuses, are dependent on various factors, including a hired individual’s job-level and annual company performance.
Also there is a Salary Description line duplicate: "$90,000 - $98,000 / Year". We'll keep only one.
Perks & Benefits list:
- Medical/Dental/Vision, including plans with 100% (employee-only) coverage
- Minimum 3 weeks Paid Time Off (PTO) and 9-observed company holidays annually
- Hybrid Work Schedule
- Annual Wellness Subsidy
- Sabbatical
- 401(k) Plan Company Match
- Annual Profit Sharing (when appropriate)
- Extensive Employee Events (outings, picnics, golf, and ski days)
- Committee and Community Involvement
Professional Development:
- Martin/Martin provides ongoing internal continuing education, training, and mentorship, reimbursement for PE/SE licenses, and encouraged active participation in professional organizations.
We could format as
- ... but it's a single sentence; could be
Required:
etc. However instruction says use