Senior ICT / Technology Consultant - Irvine, CA
Tetra Tech · Irvine, CA · 1 mo ago
Information Technology$135k–$165k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "The Opportunity" description, "Position Summary", "Essential Job Functions", "Required Qualifications", "Preferred Qualifications", "Work Environment and Location", "Compensation", "Why Glumac...", "Your Impact", "Life At Glumac...", "About Tetra Tech". We need to use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we should only include sections when posting has real specific content. We need to map content to appropriate headings.
We have:
- About the role: could be the introductory paragraph: "The Opportunity Glumac, a Tetra Tech company, is adding a Senior ICT / Technology Consultant to our team. Are you an experienced and dynamic Technology Project Consultant seeking an opportunity to showcase your expertise in telecommunications design, audiovisual design, and security design? Our team is actively seeking a skilled professional to join our ranks and lead and manage ICT (Information and Communications Technology) projects from concept to completion." That's about the role.
- Responsibilities: "Essential Job Functions" list duties.
- Requirements/Qualifications: "Required Qualifications" and "Preferred Qualifications". Could combine into Qualifications section, maybe separate Required and Preferred? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have a Qualifications heading with subpoints? But we need to use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we should only include sections when posting has real specific content. We need to map content to appropriate headings.
We have:
- About the role: could be the introductory paragraph: "The Opportunity Glumac, a Tetra Tech company, is adding a Senior ICT / Technology Consultant to our team. Are you an experienced and dynamic Technology Project Consultant seeking an opportunity to showcase your expertise in telecommunications design, audiovisual design, and security design? Our team is actively seeking a skilled professional to join our ranks and lead and manage ICT (Information and Communications Technology) projects from concept to completion." That's about the role.
- Responsibilities: "Essential Job Functions" list duties.
- Requirements/Qualifications: "Required Qualifications" and "Preferred Qualifications". Could combine into Qualifications section, maybe separate Required and Preferred? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have a Qualifications heading with subpoints? But we need to use - for any list of duties/requirements/benefits. So we can have a Qualifications section with
for required and preferred? Might be better to have separate sections: Required Qualifications and Preferred Qualifications, but headings must be from list? Not strictly required to use only those exact headings; they gave examples. Likely we can use those headings as appropriate: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications), Skills (maybe technical competency), Benefits (life at Glumac), Pay (compensation), Schedule (work environment location hybrid). We'll include only those with real content.
Let's extract:
About the role: The opening paragraph.
Responsibilities: Essential Job Functions list (bullet points). We'll convert each duty to - .
Requirements: Required Qualifications list (10+ years experience, RCDD, ownership, technical competency, communication skills, work authorization). We'll list.
Qualifications: Preferred Qualifications list (certifications OSP, DCDC, PSP, CTS, PMP, PE, etc). We'll list.
Skills: Could be derived from "Excellent technical competency, communication skills" but that's already in requirements. Maybe we can skip Skills if not distinct. But we could include a Skills heading with bullet list of technical competencies: telecommunications design, audiovisual design, security design, etc. However the posting mentions expertise in those areas. Might be okay to include Skills.
Benefits: Life At Glumac list: Comprehensive and market-competitive benefits, Merit-based financial rewards, Flexibility and company-wide commitment to work/life balance, Collaborative team atmosphere, Learning and development opportunities.
Pay: Compensation Salary Range: $135,000 - $165,000.
Schedule: Work Environment and Location: hybrid, two in-office days per week.
We also have "Why Glumac..." and "Your Impact" and "About Tetra Tech". Those could be considered About the role or maybe separate sections like Company Overview. But we only need to include sections when posting has real specific content. Could include a section "About the Company" but not in 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 suggests those as examples. Safer to stick to those headings. We can incorporate "Why Glumac" and "Your Impact" and "About Tetra Tech" into About the role or maybe a separate "About the Company" but not required. Might be okay to include them under About the role as additional prose.
We must not include boilerplate like EEO, etc. Remove those.
We must not repeat job title as heading. Not include Job ID.
We must output only HTML fragment.
Let's craft:
About the role
The Opportunity Glumac, a Tetra Tech company, is adding a Senior ICT / Technology Consultant to our team. Are you an experienced and dynamic Technology Project Consultant seeking an opportunity to showcase your expertise in telecommunications design, audiovisual design, and security design? Our team is actively seeking a skilled professional to join our ranks and lead and manage ICT (Information and Communications Technology) projects from concept to completion. As a Senior Technology Consultant, your primary focus will be designing, executing, and managing ICT projects, fostering client relationships, mentoring team members, and driving growth and innovation. With a growth mindset and at least 10 years of relevant experience, you will have the opportunity to excel in your career while contributing to our company's success.
Responsibilities
- Responsible for project execution for all aspects of ICT (Information and Communications Technology) projects design.
- Consult with clients on technology systems design for new construction and renovation projects.
- Mentor designers in security, telecommunication, and audiovisual design through presentations and project guidance.
- Prepare Division 27 and Division 28 specifications, construction documentation, and basis of design reports.
- Provide construction administration support including RFI responses and submittal reviews.
- Conduct meticulous QC reviews, uphold rigorous quality assurance standards, and contribute to the improvement of company design standards and documentation.
- Foster a culture of growth and innovation.
Requirements
- 10+ years of relevant experience.
- Registered Communications Distribution Designer (RCDD).
- A strong sense of ownership in projects and standards.
- Excellent technical competency and communication skills.
- Applicants must be currently authorized to work in the United States on a full-time basis; this position is not eligible for current or future employment visa sponsorship.
Qualifications
- Possession of Technology Industry certifications such as OSP, DCDC, PSP, CTS, PMP, PE, or other relevant certifications is highly preferred.
Skills
- Expertise in telecommunications design, audiovisual design, and security design.
- Technical competency in ICT project design and execution.
- Strong communication and client relationship skills.
- Mentoring and leadership abilities.
Benefits
- Comprehensive and market-competitive benefits.
- Merit-based financial rewards.
- Flexibility and company-wide commitment to work/life balance.
- Collaborative team atmosphere that values the contributions of all employees.
- Learning and development opportunities for ongoing professional growth.
Pay
Salary Range: $135,000 - $165,000. The base salary range represents the low and high end of the compensation scale for this role. Actual salaries will be determined based on location, experience, responsibilities, and qualifications.
Schedule
Hybrid work environment with a requirement of two in-office days per week in one of our offices. All candidates must be located in and eligible to work in the U.S.
We should ensure no extra fluff. Also we should not include "Why Glumac..." etc. Could we incorporate that into About the role? Already we have some description; we could add a bit more about company impact but not necessary. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include all substantive info from posting. If we omit "Why Glumac..." and "Your Impact" and "About Tetra Tech", we are losing substantive info. So we need to include that content somewhere. We could add a section "About the Company" but not in the list of headings. However 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 those as examples. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections, but we could also add other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it's a guideline. To be safe, we could fit that content under existing headings like About the role (which already includes some description) or maybe under a heading "About the Company" but that deviates from examples. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should use those exact headings for sections, not others. But we need to preserve all substantive info; we can incorporate the "Why Glumac..." etc into About the role section as prose. That would preserve the info without adding new headings. Let's do that: expand About the role paragraph to include the company description, impact, life at Glumac, Tetra Tech overview. That way we keep all info.
Thus About the role will be a longer paragraph (or multiple paragraphs) covering:
- The opportunity description.
- Position summary.
- Why Glumac, a Tetra Tech company (history, Tetra Tech joining, mission).
- Your Impact.
- Life At Glumac (perks).
- About Tetra Tech (leader in water, environment, sustainable infrastructure, employee count, mission, etc).
We must not invent or summarize away detail; we need to preserve all substantive info. We can copy sentences verbatim.
Let's extract those sections:
"Why Glumac, a Tetra Tech Company
Glumac has been a leader in the sustainable building design industry for over 50 years. In 2017 we joined Tetra Tech, enabling us to combine our expertise with the reach and resources of a prestigious global organization. At Tetra Tech, we are Leading with Science to solve the world’s most complex challenges. Our industry-leading experts in engineering and consulting are committed to driving positive change in communities around the world. For nearly 60 years, we have been at the forefront of innovation and sustainability. Today we stand as a market leader, offering cutting-edge solutions in water, environment, energy, and international development. Our work has improved more than 625 million lives around the world."
"Your Impact
Join Glumac, a Tetra Tech company, to make a real difference. Our work leverages cutting-edge technologies, advanced analytics, and the expertise of world-class scientists and engineers to create meaningful change around the world. Discover your full potential – join us to advance your career while leaving a lasting legacy."
"Life At Glumac, a Tetra Tech Company
The perks of working at Glumac, a Tetra Tech company, include:
- Comprehensive and market-competitive benefits.
- Merit-based financial rewards.
- Flexibility and company-wide commitment to work/life balance.
- Collaborative team atmosphere that values the contributions of all employees.
- Learning and development opportunities for ongoing
- for required and preferred? Might be better to have separate sections: Required Qualifications and Preferred Qualifications, but headings must be from list? Not strictly required to use only those exact headings; they gave examples. Likely we can use those headings as appropriate: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications), Skills (maybe technical competency), Benefits (life at Glumac), Pay (compensation), Schedule (work environment location hybrid). We'll include only those with real content.
Let's extract:
About the role: The opening paragraph.
Responsibilities: Essential Job Functions list (bullet points). We'll convert each duty to
- .
Requirements: Required Qualifications list (10+ years experience, RCDD, ownership, technical competency, communication skills, work authorization). We'll list.
Qualifications: Preferred Qualifications list (certifications OSP, DCDC, PSP, CTS, PMP, PE, etc). We'll list.
Skills: Could be derived from "Excellent technical competency, communication skills" but that's already in requirements. Maybe we can skip Skills if not distinct. But we could include a Skills heading with bullet list of technical competencies: telecommunications design, audiovisual design, security design, etc. However the posting mentions expertise in those areas. Might be okay to include Skills.
Benefits: Life At Glumac list: Comprehensive and market-competitive benefits, Merit-based financial rewards, Flexibility and company-wide commitment to work/life balance, Collaborative team atmosphere, Learning and development opportunities.
Pay: Compensation Salary Range: $135,000 - $165,000.
Schedule: Work Environment and Location: hybrid, two in-office days per week.
We also have "Why Glumac..." and "Your Impact" and "About Tetra Tech". Those could be considered About the role or maybe separate sections like Company Overview. But we only need to include sections when posting has real specific content. Could include a section "About the Company" but not in 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 suggests those as examples. Safer to stick to those headings. We can incorporate "Why Glumac" and "Your Impact" and "About Tetra Tech" into About the role or maybe a separate "About the Company" but not required. Might be okay to include them under About the role as additional prose. We must not include boilerplate like EEO, etc. Remove those. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's craft:
About the role
The Opportunity Glumac, a Tetra Tech company, is adding a Senior ICT / Technology Consultant to our team. Are you an experienced and dynamic Technology Project Consultant seeking an opportunity to showcase your expertise in telecommunications design, audiovisual design, and security design? Our team is actively seeking a skilled professional to join our ranks and lead and manage ICT (Information and Communications Technology) projects from concept to completion. As a Senior Technology Consultant, your primary focus will be designing, executing, and managing ICT projects, fostering client relationships, mentoring team members, and driving growth and innovation. With a growth mindset and at least 10 years of relevant experience, you will have the opportunity to excel in your career while contributing to our company's success.
Responsibilities
- Responsible for project execution for all aspects of ICT (Information and Communications Technology) projects design.
- Consult with clients on technology systems design for new construction and renovation projects.
- Mentor designers in security, telecommunication, and audiovisual design through presentations and project guidance.
- Prepare Division 27 and Division 28 specifications, construction documentation, and basis of design reports.
- Provide construction administration support including RFI responses and submittal reviews.
- Conduct meticulous QC reviews, uphold rigorous quality assurance standards, and contribute to the improvement of company design standards and documentation.
- Foster a culture of growth and innovation.
Requirements
- 10+ years of relevant experience.
- Registered Communications Distribution Designer (RCDD).
- A strong sense of ownership in projects and standards.
- Excellent technical competency and communication skills.
- Applicants must be currently authorized to work in the United States on a full-time basis; this position is not eligible for current or future employment visa sponsorship.
Qualifications
- Possession of Technology Industry certifications such as OSP, DCDC, PSP, CTS, PMP, PE, or other relevant certifications is highly preferred.
Skills
- Expertise in telecommunications design, audiovisual design, and security design.
- Technical competency in ICT project design and execution.
- Strong communication and client relationship skills.
- Mentoring and leadership abilities.
Benefits
- Comprehensive and market-competitive benefits.
- Merit-based financial rewards.
- Flexibility and company-wide commitment to work/life balance.
- Collaborative team atmosphere that values the contributions of all employees.
- Learning and development opportunities for ongoing professional growth.
Pay
Salary Range: $135,000 - $165,000. The base salary range represents the low and high end of the compensation scale for this role. Actual salaries will be determined based on location, experience, responsibilities, and qualifications.
Schedule
Hybrid work environment with a requirement of two in-office days per week in one of our offices. All candidates must be located in and eligible to work in the U.S.
We should ensure no extra fluff. Also we should not include "Why Glumac..." etc. Could we incorporate that into About the role? Already we have some description; we could add a bit more about company impact but not necessary. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include all substantive info from posting. If we omit "Why Glumac..." and "Your Impact" and "About Tetra Tech", we are losing substantive info. So we need to include that content somewhere. We could add a section "About the Company" but not in the list of headings. However the instruction says usefor 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. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections, but we could also add other headings if needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it's a guideline. To be safe, we could fit that content under existing headings like About the role (which already includes some description) or maybe under a heading "About the Company" but that deviates from examples. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should use those exact headings for sections, not others. But we need to preserve all substantive info; we can incorporate the "Why Glumac..." etc into About the role section as prose. That would preserve the info without adding new headings. Let's do that: expand About the role paragraph to include the company description, impact, life at Glumac, Tetra Tech overview. That way we keep all info. Thus About the role will be a longer paragraph (or multiple paragraphs) covering: - The opportunity description. - Position summary. - Why Glumac, a Tetra Tech company (history, Tetra Tech joining, mission). - Your Impact. - Life At Glumac (perks). - About Tetra Tech (leader in water, environment, sustainable infrastructure, employee count, mission, etc). We must not invent or summarize away detail; we need to preserve all substantive info. We can copy sentences verbatim. Let's extract those sections: "Why Glumac, a Tetra Tech Company Glumac has been a leader in the sustainable building design industry for over 50 years. In 2017 we joined Tetra Tech, enabling us to combine our expertise with the reach and resources of a prestigious global organization. At Tetra Tech, we are Leading with Science to solve the world’s most complex challenges. Our industry-leading experts in engineering and consulting are committed to driving positive change in communities around the world. For nearly 60 years, we have been at the forefront of innovation and sustainability. Today we stand as a market leader, offering cutting-edge solutions in water, environment, energy, and international development. Our work has improved more than 625 million lives around the world." "Your Impact Join Glumac, a Tetra Tech company, to make a real difference. Our work leverages cutting-edge technologies, advanced analytics, and the expertise of world-class scientists and engineers to create meaningful change around the world. Discover your full potential – join us to advance your career while leaving a lasting legacy." "Life At Glumac, a Tetra Tech Company The perks of working at Glumac, a Tetra Tech company, include: - Comprehensive and market-competitive benefits. - Merit-based financial rewards. - Flexibility and company-wide commitment to work/life balance. - Collaborative team atmosphere that values the contributions of all employees. - Learning and development opportunities for ongoing