Construction Information Specialist (West-Great Plains)
Dodge Construction Network · Las Vegas, NV · 3 wk ago
RemoteRemoteManagementFull-time
We need to output HTML fragment with 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. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Preferred Location" maybe part of location info but not a heading; we can embed in a paragraph. Travel Requirements also can be paragraph. Salary Disclosure: mention compensation includes market competitive salary, comprehensive benefits, variable incentive plans. That's benefits and pay info. We need to decide sections.
We have:
- About the role: description of role responsibilities? Actually the first paragraph describes role: leading acquisition, evaluation, validation of high-value commercial construction project intelligence through strategic engagement... This could be "About the role". We'll put that as prose.
- Responsibilities: list of essential functions (the bullet list). We'll put as
- .
- Requirements: Education, Required Experience, Knowledge & Skills (maybe combine). Could have sections: Requirements (education + required experience). Qualifications maybe preferred experience? But we can combine.
We need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must only include sections with real specific content. Let's see what we have:
- About the role: yes.
- Responsibilities: yes (essential functions list).
- Requirements: we have Education (Bachelor's degree preferred...), Required Experience, Knowledge & Skills (5+ years experience...). That's specific.
- Qualifications: we have Preferred Experience, Knowledge & Skills (familiarity with construction project data...). That's specific.
- Skills: maybe we can extract skills from required and preferred? But we already have skills in those sections. Could create a Skills section summarizing communication, analysis, etc. But we must not invent. We could pull out specific skill statements: "Strong verbal and written communication skills...", "Ability to analyze data...", "Skilled in tailoring value-proposition messaging...", "Ability to demonstrate Dodge tools...", "Proficiency in Microsoft Office...". Those are in Required Experience, Knowledge & Skills. Could move them to Skills section. But we must preserve all info; we can keep them in Requirements or Skills. Better to follow typical structure: Requirements (education + experience), Qualifications (preferred), Skills (specific skill statements). However we must not duplicate content. We can split: Required Experience, Knowledge & Skills includes both experience and skills. To avoid duplication, we could put experience in Requirements, skills in Skills, and preferred experience in Qualifications. Let's parse.
Required Experience, Knowledge & Skills bullet points:
- 5+ years of experience in outreach, research, customer engagement, or data operations roles, with demonstrated ability to independently manage priorities, assess information, and drive outcomes
- 5+ years of experience in the commercial construction industry, with deep knowledge of the construction ecosystem (contractors, owners, architects, subcontractors, project lifecycle, bid and award processes) and the ability to evaluate complex project information within a business context
- Demonstrated ability to analyze data, identify patterns and trends, and proactively diagnose issues and implement solutions
- Ability to analyze territory and source funnel data and conversion rates to evaluate outreach performance and present findings to leadership
- Strong verbal and written communication skills, with the ability to influence stakeholders, communicate complex findings, and adapt engagement strategies based on audience and objectives
- Skilled in tailoring value-proposition messaging by source type and handling objections to data sharing using consultative, value-selling techniques
- Demonstrated ability to independently conduct in-person engagement, including site visits, industry events, and association meetings, to develop high-value sources and gather critical intelligence
- Ability to demonstrate Dodge tools and data capabilities (e.g., Dodge One) to sources, tailoring the walkthrough by stakeholder type (owner, GC, architect) to build trust and encourage ongoing collaboration and data sharing
- Proficiency in Microsoft Office (Outlook, Word, Excel), along with the ability to learn and apply Dodge tools and systems to support data quality and business needs
We can separate: Experience bullets (first two) go to Requirements. Skills bullets (the rest) go to Skills.
Qualifications: Preferred Experience, Knowledge & Skills bullet points:
- Familiarity with construction project data, plan rooms, or bid management platforms, with the ability to interpret and apply information to support data completeness and accuracy
- Familiarity with the assigned territory's active markets, including relationships across major general contractors, architecture firms, owners, and public agencies
- Strong understanding of commercial construction project phases, bid and award processes, and multi-stakeholder project structures, with the ability to translate complex project dynamics into structured, usable data
- Experience working within a performance-driven environment, with accountability for quality and productivity outcomes and the ability to prioritize effectively across competing demands
We'll put those in Qualifications.
Benefits: Salary Disclosure mentions "market competitive salary, comprehensive benefits, and, for applicable roles, uncapped variable incentive plans or an annual discretionary performance bonus." Also maybe other benefits not listed. We have that. So we can create Benefits section with that sentence. Pay section: maybe we can separate salary? But we have no specific salary number. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation includes market competitive salary, comprehensive benefits, variable incentive plans. That's benefits and pay. Could we put both in Benefits? The instruction says include a section ONLY when 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. It does state compensation includes market competitive salary, comprehensive benefits, variable incentive plans. That's specific enough for Benefits and maybe Pay? But we don't have a specific salary figure. The phrase "market competitive salary" is not a specific number but it's still a statement about pay. The instruction says never create Pay section unless posting actually states them. It does state salary component, albeit generic. I'd argue we can include Pay section with that statement. However we also have Benefits section with comprehensive benefits and variable incentive plans. Could combine into Benefits only. But we need to decide.
Schedule: we have full-time position, remote, travel up to 10%. That's schedule info (full-time, remote, travel). So we can create Schedule section with that.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, accommodation, etc. Must remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
Education: Bachelor's degree preferred in Business, Communications, Construction Management, or a related field; OR equivalent professional experience demonstrating advanced proficiency in outreach, data collection, and commercial construction industry knowledge.
Required Experience: 5+ years of experience in outreach, research, customer engagement, or data operations roles, with demonstrated ability to independently manage priorities, assess information, and drive outcomes; 5+ years of experience in the commercial construction industry, with deep knowledge of the construction ecosystem (contractors, owners, architects, subcontractors, project lifecycle, bid and award processes) and the ability to evaluate complex project information within a business context.
Alternatively we could keep as list. But we need to use- for any list of duties/requirements/benefits. For Requirements, we have education and experience; could be list. Let's make a list.
Requirements
- Bachelor's degree preferred in Business, Communications, Construction Management, or a related field; OR equivalent professional experience demonstrating advanced proficiency in outreach, data collection, and commercial construction industry knowledge.
- 5+ years of experience in outreach, research, customer engagement, or data operations roles, with demonstrated ability to independently manage priorities, assess information, and drive outcomes.
- 5+ years of experience in the commercial construction industry, with deep knowledge of the construction ecosystem (contractors, owners, architects, subcontractors, project lifecycle, bid and award processes) and the ability to evaluate complex project information within a business context.
Qualifications
- Familiarity with construction project data, plan rooms, or bid management platforms, with the ability to interpret and apply information to support data completeness and accuracy.
- Familiarity with the assigned territory's active markets, including relationships across major general contractors, architecture firms, owners, and public agencies.
- Strong understanding of commercial construction project phases, bid and award processes, and multi-stakeholder project structures, with the ability to translate complex project dynamics into structured, usable data.
- Experience working within a performance-driven environment, with accountability for quality and productivity outcomes and the ability to prioritize effectively across competing demands.
Skills
- Demonstrated ability to analyze data, identify patterns and trends, and proactively diagnose issues and implement solutions.
- Ability to analyze territory and source funnel data and conversion rates to evaluate outreach performance and present findings to leadership.
- Strong verbal and written communication skills, with the ability to influence stakeholders, communicate complex findings, and adapt engagement strategies based on audience and objectives.
- Skilled in tailoring value‑proposition messaging by source type and handling objections to data sharing using consultative, value‑selling techniques.
- Demonstrated ability to independently conduct in‑person engagement, including site visits, industry events, and association meetings, to develop high‑value sources and gather critical intelligence.
- Ability to demonstrate Dodge tools and data capabilities (e.g., Dodge One) to sources, tailoring the walkthrough by stakeholder type (owner, GC, architect) to build trust and encourage ongoing collaboration and data sharing.
- Proficiency in Microsoft Office (Outlook, Word, Excel), along with the ability to learn and apply Dodge tools and systems to support data quality and business needs.
Benefits
Market‑competitive salary, comprehensive benefits, and for applicable roles uncapped variable incentive plans or an annual discretionary performance bonus.
Pay
Market‑competitive salary (as part of the compensation package).
But we might be duplicating salary info. Better to combine Benefits and Pay? The instruction says prefer a few substantive sections over many thin ones. Having both Benefits and Pay may be thin. However we have specific content for both: benefits (comprehensive benefits, variable incentive plans) and pay (market-competitive salary). Could combine into Benefits section only, mentioning salary as part of compensation. But then we would not have a Pay section, which is okay if we don't have specific pay detail beyond generic statement. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary component, but it's generic. I'd lean to include a Benefits section that mentions salary, comprehensive benefits, variable incentive plans. Then we can omit Pay section. Schedule we have: full-time, remote, travel up to 10%. That's specific enough for Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We must not include Pay. Let's craft Benefits paragraph: "Market‑competitive salary, comprehensive benefits, and for applicable roles uncapped variable incentive plans or an annual discretionary performance bonus." Schedule: "Full‑time, remote home‑