SOLUTION CONSULTANT
About the role
etc. Use- for any list of duties/requirements/benefits. Use
for prose. We need to decide which sections to include. We have: - About the role: Could be the Job Summary paragraph(s). The posting has "Job Summary As a member of Belden’s Solution Consulting & Services Team, the Solution Consultant (SC) is a critical part of the commercial sales team ..." That's a prose description. So we can put that under About the role. - Responsibilities: There's a big list of responsibilities after "Responsibilities". Many bullet-like sentences separated by periods. We need to turn them into
- . Should we keep each sentence as a list item? Likely yes.
- Requirements: The posting has "Required Skills And Experience". That includes education, years experience, specific skills, certifications. Could be considered Requirements. Could also split into Requirements and Skills? But we have separate headings for Requirements, Qualifications, Skills. We need to decide based on content. Usually "Required Skills And Experience" could be both Requirements and Skills. But we need to avoid thin sections. Perhaps combine into Requirements (or Skills). However we have separate headings; we should only include sections that have real specific content. We could put education/experience under Requirements, and technical skills under Skills. But we need to see if we can split meaningfully.
The "Required Skills And Experience" includes:
- Bachelor's degree in electrical engineering or a related field or 8+ years of related experience.
- 8+ years of consultative, pre-sales experience in enterprise or industrial environments and proven expertise in OT/IT Infrastructure design, implementation
- Experience designing, deploying, commissioning or maintaining Copper or Fiber Networks, support Wireless or Wireless LAN / WAN Networks
- Experience with AIA MasterSpec, CAD, Bluebeam and Estimating Tools preferred
- Demonstrated ability to translate technical solutions into clear, actionable insights to non-technical stakeholders
- Demonstrate solid knowledge and understanding of key technology and market trends, and Competitors’ solutions.
- Strong technical knowledge of network communication systems and related applications
- Demonstrated ability to collaborate with cross-functional teams, including Sales, Marketing, and Product Development.
- Willingness and ability to travel domestically and internationally (50%+ travel frequency).
- RCDD, DCDC, CDCP or other ICT/IT/OT Certifications Preferred
These could be considered Requirements (education, experience) and Skills (technical abilities). We could split: Requirements: education, years experience, travel willingness, certifications. Skills: technical abilities like network design, AIA MasterSpec, translating solutions, knowledge of trends, collaboration, etc.
But we also have a "Qualifications" heading; maybe we could put education/experience there. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have two sections: About the role, Responsibilities, Requirements/Skills combined, Benefits, Pay. But we need to follow headings list: we can include only those that have content. So we could include About the role, Responsibilities, Requirements (combining education/experience), Skills (technical skills), Benefits, Pay. Schedule: not mentioned (no schedule specifics). So omit Schedule.
We also need to include Benefits: The posting mentions benefits near end: "Belden also offers hybrid and remote work practices where feasible and provides employees with benefits that could include health/dental/vision, long term/short term disability, life insurance, HSA/FSA, matching retirement plans, paid vacation, parental leave, employee stock purchase plan, paid leave for volunteer work in your community, training opportunities, professional talent management and succession planning, corporate health well-being initiatives and a work culture which includes commitment to diversity, equity, inclusion and sustainability!" That's a benefits list. So we need Benefits section with
- .
Pay: The posting includes compensation range: "Applicants can expect a base compensation range of $120,000-$160,000, plus benefits and additional incentives based on the level of the role. This is the reasonable estimate that Belden believes it might pay for this job based on applicable circumstances at the time of posting. Belden may ultimately pay more or less than the posted range as permitted by law, and commensurate with the applicant’s experience, qualifications, and geographical location." That's pay info. So we need Pay section with that prose (maybe as
). Should we include the "commensurate with experience" phrase? That's allowed as it's actual content. The instruction says: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That's a bit tricky: they say never emit a heading followed by filler/placeholder text like "commensurate with experience". Does that mean we cannot have a Pay section that only contains that phrase? But we have actual numbers plus that phrase. It's not just filler; we have a range. So it's okay. We need to ensure we don't include boilerplate like EEO, etc. The posting includes "These statements are intended to describe the general nature and level of work involved for this job. It is not an exhaustive list of all responsibilities, duties and skills required of this job." That's somewhat boilerplate but maybe considered generic. Should we remove? It's not EEO but it's a disclaimer. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line could be considered legal boilerplate. Might be safe to remove. Also the final exclamation about "Let's Create Possibilities Together..." is marketing fluff but maybe keep as part of About the role? It's after the Required Skills. It's more like a closing motivational paragraph. Could be considered part of About the role or maybe we could include as a separate section? But we already have About the role; we could append that paragraph there. However the instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep that paragraph somewhere. It's not a list; it's prose. Could be part of About the role (makes sense). Or we could make a separate section like "About Belden" but not in headings list. Better to incorporate into About the role. Now we need to structure HTML. We'll produce:
About the role
... (Job Summary + motivational paragraph)
Responsibilities
- Partner with Sales to drive bookings growth by delivering outcome-based solutions aligned with vertical market strategies.
- Leverage Professional Services, cross practice competencies and SLA offers to enhance customer experience and drive business or financial client outcomes.
- Navigate Customer Challenges and Build Solutions that enable successful customer outcomes
- Define and Develop Infrastructure Requirements, Originate Designs, Build BOM, SLD & Logical Network Hierarchy
- Utilize Standard Tools, i.e. AIA Master Spec Format or similar, to articulate scope, design, installation, and testing requirements for infrastructure supporting DOM Network Designs from Belden
- Lead and manage the development of solutions that utilize a OneBelden approach; Incorporate third party or eco-partner products as required and necessary
- Partner with SCS (Solution Consulting Services) counterparts to translate customer requirements and problem statements into compelling technical solutions with demonstrable financial value impact.
- Collaborate with Customer Innovation Center (CIC) Solution Support team to conduct POCs (Proof of Concepts)
- Provide successful transition from Design Acceptance / POC to Execution Phase with CommOps and PMO Functions
- Support and drive technical sales and solutions for customer applications by providing technical leadership and technical influence
- Maintain competence with ALL Belden products.
- Actively support technology campaigns such as webinars, shows, trade fairs, etc. where SC’s Infrastructure Design Expertise helps accelerate customer acceptance of Belden as a Solution Provider for Network and Data solutions
- Provide technical content to marketing for inclusion in marketing materials, collaterals and solutions guides
- Provide supporting documentation for application notes, “how to” videos, quick start guides or cases studies
- Maintain customer reporting, designs and other artifacts using prescribed tools and systems
- Provide market feedback to product management teams to drive product development
- Translate customer requirements and problem statements into actionable technical solutions with demonstrable financial impact and billable services.
- Represent customers’ voice in Business Unit strategy and new product introduction processes.
Requirements
- Bachelor's degree in electrical engineering or a related field or 8+ years of related experience.
- 8+ years of consultative, pre-sales experience in enterprise or industrial environments and proven expertise in OT/IT Infrastructure design, implementation
- Willingness and ability to travel domestically and internationally (50%+ travel frequency).
- RCDD, DCDC, CDCP or other ICT/IT/OT Certifications Preferred
Skills
- Experience designing, deploying, commissioning or maintaining Copper or Fiber Networks, support Wireless or Wireless LAN / WAN Networks
- Experience with AIA MasterSpec, CAD, Bluebeam and Estimating Tools preferred
- Demonstrated ability to translate technical solutions into clear, actionable insights to non-technical stakeholders
- Demonstrate solid knowledge and understanding of key technology and market trends, and Competitors’ solutions.
- Strong technical knowledge of network communication systems and related applications
- Demonstrated ability to collaborate with cross-functional teams, including Sales, Marketing, and Product Development.
Benefits
- Hybrid and remote work practices where feasible
- Health/dental/vision
- Long term/short term disability
- Life insurance
- HSA/FSA
- Matching retirement plans
- Paid vacation
- Parental leave
- Employee stock purchase plan
- Paid leave for volunteer work in your community
- Training opportunities
- Professional talent management and succession planning
- Corporate health well-being initiatives
- Work culture with commitment to diversity, equity, inclusion and sustainability
Pay
Applicants can expect a base compensation range of $120,000-$160,000, plus benefits and additional incentives based on the level of the role. This is the reasonable estimate that Belden believes it might pay for this job based on applicable circumstances at the time of posting. Belden may ultimately pay more or less than the posted range as permitted by law, and commensurate with the applicant’s experience, qualifications, and geographical location.
We need to ensure we didn't include any boilerplate like "These statements are intended to describe the general nature and level of work involved for this job..." We omitted that. Also omitted the "Let's Create Possibilities Together..." paragraph? We didn't include it explicitly.
- .
Pay: The posting includes compensation range: "Applicants can expect a base compensation range of $120,000-$160,000, plus benefits and additional incentives based on the level of the role. This is the reasonable estimate that Belden believes it might pay for this job based on applicable circumstances at the time of posting. Belden may ultimately pay more or less than the posted range as permitted by law, and commensurate with the applicant’s experience, qualifications, and geographical location." That's pay info. So we need Pay section with that prose (maybe as
- . Should we keep each sentence as a list item? Likely yes.
- Requirements: The posting has "Required Skills And Experience". That includes education, years experience, specific skills, certifications. Could be considered Requirements. Could also split into Requirements and Skills? But we have separate headings for Requirements, Qualifications, Skills. We need to decide based on content. Usually "Required Skills And Experience" could be both Requirements and Skills. But we need to avoid thin sections. Perhaps combine into Requirements (or Skills). However we have separate headings; we should only include sections that have real specific content. We could put education/experience under Requirements, and technical skills under Skills. But we need to see if we can split meaningfully.
The "Required Skills And Experience" includes:
- Bachelor's degree in electrical engineering or a related field or 8+ years of related experience.
- 8+ years of consultative, pre-sales experience in enterprise or industrial environments and proven expertise in OT/IT Infrastructure design, implementation
- Experience designing, deploying, commissioning or maintaining Copper or Fiber Networks, support Wireless or Wireless LAN / WAN Networks
- Experience with AIA MasterSpec, CAD, Bluebeam and Estimating Tools preferred
- Demonstrated ability to translate technical solutions into clear, actionable insights to non-technical stakeholders
- Demonstrate solid knowledge and understanding of key technology and market trends, and Competitors’ solutions.
- Strong technical knowledge of network communication systems and related applications
- Demonstrated ability to collaborate with cross-functional teams, including Sales, Marketing, and Product Development.
- Willingness and ability to travel domestically and internationally (50%+ travel frequency).
- RCDD, DCDC, CDCP or other ICT/IT/OT Certifications Preferred
These could be considered Requirements (education, experience) and Skills (technical abilities). We could split: Requirements: education, years experience, travel willingness, certifications. Skills: technical abilities like network design, AIA MasterSpec, translating solutions, knowledge of trends, collaboration, etc.
But we also have a "Qualifications" heading; maybe we could put education/experience there. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have two sections: About the role, Responsibilities, Requirements/Skills combined, Benefits, Pay. But we need to follow headings list: we can include only those that have content. So we could include About the role, Responsibilities, Requirements (combining education/experience), Skills (technical skills), Benefits, Pay. Schedule: not mentioned (no schedule specifics). So omit Schedule.
We also need to include Benefits: The posting mentions benefits near end: "Belden also offers hybrid and remote work practices where feasible and provides employees with benefits that could include health/dental/vision, long term/short term disability, life insurance, HSA/FSA, matching retirement plans, paid vacation, parental leave, employee stock purchase plan, paid leave for volunteer work in your community, training opportunities, professional talent management and succession planning, corporate health well-being initiatives and a work culture which includes commitment to diversity, equity, inclusion and sustainability!" That's a benefits list. So we need Benefits section with