Electronic Security System Designer
DLR Group · Omaha, NE · 3 wk ago
Engineering$80k–$140k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate. We need to parse the posting.
Let's extract content:
Company description: "DLR Group is an integrated design firm with a promise to elevate the human experience through design. This fuels the work we do around the world and inspires our mission to improve the lives of our clients, our communities, and our planet. If this sparks your interest, you’re in the right place." That's about the firm, could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for description of role and maybe company.
Then "Role DLR Group's Telecommunications + Security Design team has an opening for an Electronic Security System Designer. This role could be based in the following cities: AtlantaCharlotteClevelandDallasDenverFort WorthHoustonLos AngelesPhoenixPortlandOmahaOverland ParkWashington, DC". That's location info; maybe we can include in About the role or separate? There's no Schedule or Pay yet.
Then "Position Summary As a Telecommunications Designer at DLR Group you will be responsible for preparing the design of telecommunications Network Cabling Infrastructure from schematic design through construction administration on a wide range of building types. As part of our integrated design team, you will create buildings that elevate the human experience through design. You will be responsible for participating in the design process of technology systems, preparing detailed Telecommunication plans and specifications. We know that our only way to grow is by hiring and keeping the best talent in our industry. If you feel like we are a good fit for you, tell us by applying!" That's more description.
Then "What You Will Do Assist in developing project objectives, goals, and documentation policiesMeet with client’s IT staff to determine project requirements and goalsDevelop telecommunications cabling infrastructure designs from concept through completion of constructionPrepare telecom cabling infrastructure plans and specificationsPrepare detailed telecom systems reports and narrativesCoordinate Telecom design requirements with architecture, structure, mechanical, electrical, and other disciplines". That's responsibilities.
Then "Required Qualifications Registered Communications Distribution Designer (RCDD) certification through BICSIA minimum of 5 years of experience in the Evaluation/Design of Telecommunications Cabling Infrastructure SystemsExperience with Building Construction documentsExperience with BIM (i.e., Autodesk Revit) and AutoCAD workflowProficiency with Microsoft Office (Word, Excel, PowerPoint)Ability to work within an active, multi-disciplined environmentAbility to meet deadlines for multiple projectsAbility to design and detail telecommunications plans and specifications in conjunction with in-house architects, engineers, and specialty design staffAvailability to travel for job meetings, site visits and project interviewsProficiency with a PDF mark-up tool (such as Bluebeam)". That's qualifications.
Then "Preferred Qualifications Experience with a consulting engineering or A/E firm as a telecom cabling infrastructure designerExperience with sustainable building designExperience in facility types that coincide with the firm’s market channels, which include K-12 Education, Higher Education, Healthcare, Justice + Civic, Sports, and WorkplaceA degree from an accredited university in a field(s) relevant to telecommunications design, including electrical engineering, or other related discipline". That's also qualifications/skills.
Then "Our comprehensive Benefits at DLR Group include medical, dental, vision, disability, wellness programs, flex spending, paid holidays, and paid time off. We also offer a 401(k) plan, employee stock ownership, and bonus opportunities." That's benefits.
Then "Compensation considerations are based on location, experience, and skills. The suggested pay range for this position is: Pay Range $80,000 - $140,000 USD". That's pay.
Then later: "DLR Group follows a four-day in-office work model, with employees having the flexibility to work somewhere other than the office on Fridays." That's schedule info.
We need to include sections only if real specific content. So we can have:
- About the role (maybe combine company description and position summary)
- Responsibilities (What You Will Do)
- Qualifications (Required Qualifications + Preferred Qualifications maybe separate? Could combine but better separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples; we can choose which to include. We have qualifications, maybe also skills. We could put Required Qualifications under Qualifications heading, and Preferred Qualifications under Skills? Or we could have Qualifications and Skills separate. The posting includes both required and preferred qualifications; we could treat required as Qualifications, preferred as Skills. Or we could combine both under Qualifications and not have Skills. But we need to follow instruction: prefer a few substantive sections over many thin ones. So maybe we have Qualifications (including both required and preferred) and Skills not needed. But we have Benefits, Pay, Schedule.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We must not include empty sections.
Now format: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate. We need to parse the posting.
Let's extract content:
Company description: "DLR Group is an integrated design firm with a promise to elevate the human experience through design. This fuels the work we do around the world and inspires our mission to improve the lives of our clients, our communities, and our planet. If this sparks your interest, you’re in the right place." That's about the firm, could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for description of role and maybe company.
Then "Role DLR Group's Telecommunications + Security Design team has an opening for an Electronic Security System Designer. This role could be based in the following cities: AtlantaCharlotteClevelandDallasDenverFort WorthHoustonLos AngelesPhoenixPortlandOmahaOverland ParkWashington, DC". That's location info; maybe we can include in About the role or separate? There's no Schedule or Pay yet.
Then "Position Summary As a Telecommunications Designer at DLR Group you will be responsible for preparing the design of telecommunications Network Cabling Infrastructure from schematic design through construction administration on a wide range of building types. As part of our integrated design team, you will create buildings that elevate the human experience through design. You will be responsible for participating in the design process of technology systems, preparing detailed Telecommunication plans and specifications. We know that our only way to grow is by hiring and keeping the best talent in our industry. If you feel like we are a good fit for you, tell us by applying!" That's more description.
Then "What You Will Do Assist in developing project objectives, goals, and documentation policiesMeet with client’s IT staff to determine project requirements and goalsDevelop telecommunications cabling infrastructure designs from concept through completion of constructionPrepare telecom cabling infrastructure plans and specificationsPrepare detailed telecom systems reports and narrativesCoordinate Telecom design requirements with architecture, structure, mechanical, electrical, and other disciplines". That's responsibilities.
Then "Required Qualifications Registered Communications Distribution Designer (RCDD) certification through BICSIA minimum of 5 years of experience in the Evaluation/Design of Telecommunications Cabling Infrastructure SystemsExperience with Building Construction documentsExperience with BIM (i.e., Autodesk Revit) and AutoCAD workflowProficiency with Microsoft Office (Word, Excel, PowerPoint)Ability to work within an active, multi-disciplined environmentAbility to meet deadlines for multiple projectsAbility to design and detail telecommunications plans and specifications in conjunction with in-house architects, engineers, and specialty design staffAvailability to travel for job meetings, site visits and project interviewsProficiency with a PDF mark-up tool (such as Bluebeam)". That's qualifications.
Then "Preferred Qualifications Experience with a consulting engineering or A/E firm as a telecom cabling infrastructure designerExperience with sustainable building designExperience in facility types that coincide with the firm’s market channels, which include K-12 Education, Higher Education, Healthcare, Justice + Civic, Sports, and WorkplaceA degree from an accredited university in a field(s) relevant to telecommunications design, including electrical engineering, or other related discipline". That's also qualifications/skills.
Then "Our comprehensive Benefits at DLR Group include medical, dental, vision, disability, wellness programs, flex spending, paid holidays, and paid time off. We also offer a 401(k) plan, employee stock ownership, and bonus opportunities." That's benefits.
Then "Compensation considerations are based on location, experience, and skills. The suggested pay range for this position is: Pay Range $80,000 - $140,000 USD". That's pay.
Then later: "DLR Group follows a four-day in-office work model, with employees having the flexibility to work somewhere other than the office on Fridays." That's schedule info.
We need to include sections only if real specific content. So we can have:
- About the role (maybe combine company description and position summary)
- Responsibilities (What You Will Do)
- Qualifications (Required Qualifications + Preferred Qualifications maybe separate? Could combine but better separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples; we can choose which to include. We have qualifications, maybe also skills. We could put Required Qualifications under Qualifications heading, and Preferred Qualifications under Skills? Or we could have Qualifications and Skills separate. The posting includes both required and preferred qualifications; we could treat required as Qualifications, preferred as Skills. Or we could combine both under Qualifications and not have Skills. But we need to follow instruction: prefer a few substantive sections over many thin ones. So maybe we have Qualifications (including both required and preferred) and Skills not needed. But we have Benefits, Pay, Schedule.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We must not include empty sections.
Now format: Use for each heading. Then content: use
for prose,
- for any list of duties/requirements/benefits.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details like cities list, etc.
We need to avoid repeating job title as heading; we are not.
We need to drop boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "We are proud to be an Equal Opportunity/Affirmative Action/M/F/Veteran/Disabled employer." That's EEO boilerplate; should remove. Also "DLR Group is an integrated design firm delivering architecture, engineering, interiors, planning, and building optimization for new builds, renovations, and adaptive reuse projects. We are 100% employee-owned: every employee is literally invested in our clients’ success. At the core of our firm are interdisciplinary teams engaged in every step of project lifecycles. Our teams champion true collaboration, open information sharing, shared risk and reward, value-based decision making, and proficient use of technology to deliver exceptional design. We are pursuing the goals of the 2030 Challenge, the ME2040, and the SE2050, and are an initial signatory of the China Accord and the AIA 2030 Commitment. Through our values – commitment, creativity, environmental stewardship, fun, integrity, ownership, sharing, teamwork – we elevate the human experience through design, together." That's more about the firm; could be considered part of About the role? It's substantive but maybe not required? It's about the firm; we could include in About the role. It's not boilerplate; it's descriptive. Keep.
We also need to remove duplicated lines: there may be duplication of "DLR Group is an integrated design firm..." appears twice; we should keep only once? The instruction: remove duplicated lines. So we should keep only one instance.
Let's craft content.
About the role: combine first paragraph about DLR Group promise, plus Position Summary, plus maybe the values paragraph? But we need to avoid too much fluff. Keep substantive: description of firm mission, role summary.
We'll produce:
About the role
DLR Group is an integrated design firm with a promise to elevate the human experience through design. This fuels the work we do around the world and inspires our mission to improve the lives of our clients, our communities, and our planet. As a Telecommunications Designer at DLR Group you will be responsible for preparing the design of telecommunications Network Cabling Infrastructure from schematic design through construction administration on a wide range of building types. As part of our integrated design team, you will create buildings that elevate the human experience through design. You will be responsible for participating in the design process of technology systems, preparing detailed Telecommunication plans and specifications.
Maybe also include location info? Could be part of About the role or separate. The location list is specific; we could add a paragraph: "This role could be based in the following cities: Atlanta, Charlotte, Cleveland, Dallas, Denver, Fort Worth, Houston, Los Angeles, Phoenix, Portland, Omaha, Overland Park, Washington, DC." Use commas. We'll add that. Responsibilities: list from "What You Will Do". We'll make- each duty.
Qualifications: combine required and preferred. Could separate required and preferred as subheadings? But we only have h3 headings; we could have
Qualifications
then maybeRequired:
- ... then
- Assist in developing project objectives, goals, and documentation policies
- Meet with client’s IT staff to determine project requirements and goals
- Develop telecommunications cabling infrastructure designs from concept through completion of construction
- Prepare telecom cabling infrastructure plans and specifications
- Prepare detailed telecom systems reports and narratives
- Coordinate Telecom design requirements with architecture, structure, mechanical, electrical, and other disciplines
- Registered Communications Distribution Designer (RCDD) certification through BICSI
- Minimum of 5 years of experience in the Evaluation/Design of Telecommunications Cabling Infrastructure Systems
- Experience with Building Construction documents
- Experience with BIM (i.e., Autodesk Revit) and AutoCAD workflow
- Proficiency with Microsoft Office (Word, Excel, PowerPoint)
Preferred:
- ... That's okay.
Benefits: list.
Pay: paragraph with pay range.
Schedule: paragraph about four-day in-office model.
We must not include sections with filler like "commensurate with experience". Not present.
Now ensure we don't include any application instructions like "If you feel like we are a good fit for you, tell us by applying!" That's application instruction; should remove. Also "We know that our only way to grow is by hiring and keeping the best talent in our industry." That's maybe okay but it's fluff; but it's not boilerplate; but it's generic. Might be okay to keep? The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The sentence "If you feel like we are a good fit for you, tell us by applying!" is application instruction; remove. Also earlier "If this sparks your interest, you’re in the right place." That's also kind of fluff but not application instruction; maybe keep? It's more marketing. Might be okay.
We also need to remove duplicated lines: The phrase "DLR Group is an integrated design firm..." appears twice; we will keep only once.
Now produce HTML.
Let's draft:
About the role
DLR Group is an integrated design firm with a promise to elevate the human experience through design. This fuels the work we do around the world and inspires our mission to improve the lives of our clients, our communities, and our planet. As a Telecommunications Designer at DLR Group you will be responsible for preparing the design of telecommunications Network Cabling Infrastructure from schematic design through construction administration on a wide range of building types. As part of our integrated design team, you will create buildings that elevate the human experience through design. You will be responsible for participating in the design process of technology systems, preparing detailed Telecommunication plans and specifications. This role could be based in the following cities: Atlanta, Charlotte, Cleveland, Dallas, Denver, Fort Worth, Houston, Los Angeles, Phoenix, Portland, Omaha, Overland Park, Washington, DC.
Responsibilities
Qualifications
Required:
- each duty.
Qualifications: combine required and preferred. Could separate required and preferred as subheadings? But we only have h3 headings; we could have