Field Support Administrator-Phoenix, AZ and Las Vegas, NV
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.
We need to decide which sections to include based on content.
We have:
- About Forged Fiber (company description) - could be "About the role"? Actually "About the role" is a heading they suggest. But we have "The Role" description. Could map to "About the role". We'll include that.
- Work Location Hybrid - Phoenix, AZ or Las Vegas, NV (maybe location info). Could be part of "About the role" or separate? Not a required heading; we can embed in paragraph.
- The Main Responsibilities: list of duties.
- What We Look For In a Candidate: includes culture description and then "Main Requirements". Could be "Requirements" or "Qualifications". We'll have a Requirements section.
- Compensation: includes salary range and benefits description. So we can have Pay section (salary range) and Benefits section (benefits). Also schedule? Not given.
- What To Expect Next: background screening etc. That's application instructions? Might be considered boilerplate? It's about process; maybe we keep as part of "About the role"? But instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What To Expect Next" includes background screening etc. That's application instructions; we should remove.
- Equal Employment Opportunities: boilerplate, remove.
- Copyright line: remove.
Thus we keep: About the role (company description + role description), Responsibilities, Requirements (including education, experience, skills), Pay (salary range), Benefits (benefits description). Possibly also Work Location as part of About the role.
We must not repeat job title as heading. So we won't put "Field Support Administrator". We'll just have headings.
We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must preserve all substantive information; do not invent or summarize away detail.
We need to ensure we don't create sections with filler text.
Let's extract content.
Company description (About Forged Fiber):
"At Forged Fiber, our mission is bold but simple: deliver fast, reliable, future-proof connectivity that builds the foundation for everything online. As we execute, we believe the right way to do something is the only way. This foundation guides how the company builds, operates, and maintains a state-of-the-art open-access fiber network platform that empowers millions. Forged Fiber is about more than building a network. It is about people. Every role matters. Every contribution counts. Together, employees create impact through teamwork, trust, and a shared commitment to excellence."
We can put that in a
under About the role heading.
Then "The Role" description:
"The Field Support Administrator (FSA) is responsible for planning, coordinating, and supporting construction projects related to the restoration, maintenance, and deployment of Outside Plant (OSP) fiber infrastructure, including FTTx, GPON, and related network systems. This role manages projects from initiation through completion, ensuring quality, compliance, and timely delivery. The FSA works cross-functionally with Field Operations, Engineering, contractors, and project management teams to ensure accurate execution and reporting of all project activities."
We can include that as part of About the role or separate? Since we have About the role heading, we can combine both company description and role description under that heading.
Then Work Location: "Hybrid - Phoenix, AZ or Las Vegas, NV". Could be a short paragraph.
Then Responsibilities: list bullet points.
Let's list responsibilities from "The Main Responsibilities" section:
- Coordinate with Field Operations and contractors to support project planning, execution, and restoration efforts.
- Manage multiple concurrent projects from initiation through invoicing/completion.
- Ensure project activities align with timelines, scope, and company standards.
- Conduct site visits to monitor construction progress and verify quality of work performed by internal teams and contractors.
- Ensure compliance with engineering designs, specifications, and safety standards.
- Inspect OSP work prints and construction activities for accuracy and adherence to standards.
- Partner with Engineering to ensure designs are accurately implemented in the field.
- Review engineering work prints, standards documentation, and installation procedures.
- Provide field feedback to improve design effectiveness and constructability.
- Review and approve contractor invoices for accuracy and completeness.
- Support contract compliance and vendor performance oversight.
- Assist with tracking project costs and identifying discrepancies.
- Maintain accurate project records and documentation in applicable systems
- Provide timely and accurate updates on project status, risks, and issues.
- Document and report on deficiencies, quality issues, and corrective actions.
- Act as a liaison between Engineering, Operations, contractors, and project managers.
- Proactively identify and resolve project issues and escalations.
- Provide regular feedback to internal teams and external partners.
- Ensure all work complies with USDA RUS standards, regional construction practices, and ForgedFiber37 requirements.
- Maintain working knowledge of engineering standards, safety regulations, and construction procedures.
- Monitor site housekeeping and overall project compliance.
We need to put each as
- inside a
.
Then Requirements: from "What We Look For In a Candidate" includes culture description (maybe not needed as requirement) and then "Main Requirements". We'll extract the requirements list:
- Bachelor’s degree in a related field (Construction Management, Engineering, or Telecommunications) preferred OR equivalent work experience
- 4+ years of experience in OSP/ISP construction, engineering support, or project coordination
- Experience with fiber network deployments (FTTx, GPON) preferred
- Proven experience supporting or managing construction projects
- Strong knowledge of: Underground, buried, and aerial fiber construction, OSP and ISP infrastructure, Engineering prints, schematics, and specifications
- Familiarity with central office configurations, switching, and routing (preferred)
- Working knowledge of construction codes, regulations, and compliance standards
- Strong organizational and multitasking abilities
- Excellent communication and stakeholder coordination skills
- Attention to detail and problem-solving capability
- Ability to work independently and in fast-paced environments
- Ability to travel 30–40%
- Valid driver’s license with satisfactory driving record
We can put these as - .
We might also include the culture description as prose under Requirements? But it's not a requirement; it's about culture. Could be omitted or placed under About the role? The instruction: Prefer a few substantive sections over many thin ones. We could include a short paragraph about culture under About the role or maybe under Requirements as "What we look for". But we already have Requirements section for the main requirements. The culture description could be considered part of "What we look for" but not a requirement; we could keep as prose under Requirements heading? Might be okay. However, we must not create filler. The culture description is substantive: "Forged Fiber’s culture is built on honesty, respect, trust, transparency, and a growth mindset. We strive to treat people as they want to be treated, and to operate with consistency, integrity, customer obsession, and courage. We’re looking for top tier talent to join Forged Fiber that can help us bring this mindset to our everyday work and deliver meaningful results." That's substantive; we could include as a
under Requirements or maybe under About the role. Since we already have About the role with company description and role description, we could add culture there. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put culture under About the role as part of prose.
Thus About the role heading will contain: company description, role description, work location, culture description.
Now Pay: we have compensation details: "Compensation This information reflects the anticipated base salary range for this position based on current national data. Minimums and maximums may vary based on location. Individual pay is based on skills, experience and other relevant factors. Location Based Pay Ranges: $80,000-$120,000". That's substantive; we need a Pay section with that info as
. Also note they mention benefits after that: "Forged Fiber offers a comprehensive package featuring a broad range of Health, Life, Voluntary Lifestyle benefits and other perks that enhance your physical, mental, emotional and financial wellbeing." That's benefits; we can have Benefits section with that as
.
We should not include schedule (not given). So we omit Schedule.
We must not include any boilerplate like EEO, background screening, etc.
Now we need to output HTML fragment only.
Structure:
About the role
... company description ...
... role description ...
Work Location: Hybrid - Phoenix, AZ or Las Vegas, NV
... culture description ...
Responsibilities
- ...
...
Requirements
Forged Fiber’s culture is built on honesty, respect, trust, transparency, and a growth mindset. We strive to treat people as they want to be treated, and to operate with consistency, integrity, customer obsession, and courage. We’re looking for top tier talent to join Forged Fiber that can help us bring this mindset to our everyday work and deliver meaningful results.
- Bachelor’s degree in a related field (Construction Management, Engineering, or Telecommunications) preferred OR equivalent work experience
- 4+ years of experience in OSP/ISP construction, engineering support, or project coordination
- Experience with fiber network deployments (FTTx, GPON) preferred
- Proven experience supporting or managing construction projects
- Strong knowledge of: Underground, buried, and aerial fiber construction, OSP and ISP infrastructure, Engineering prints, schematics, and specifications
- Familiarity with central office configurations, switching, and routing (preferred)
- Working knowledge of construction codes, regulations, and compliance standards
- Strong organizational and multitasking abilities
- Excellent communication and stakeholder coordination skills
- Attention to detail and problem-solving capability
- Ability to work independently and in fast-paced environments
- Ability to travel 30–40%
- Valid driver’s license with satisfactory driving record
Pay
This information reflects the anticipated base salary range for this position based on current national data. Minimums and maximums may vary based on location. Individual pay is based on skills, experience and other relevant factors. Location Based Pay Ranges: $80,000-$120,000
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. We need to decide which sections to include based on content. We have: - About Forged Fiber (company description) - could be "About the role"? Actually "About the role" is a heading they suggest. But we have "The Role" description. Could map to "About the role". We'll include that. - Work Location Hybrid - Phoenix, AZ or Las Vegas, NV (maybe location info). Could be part of "About the role" or separate? Not a required heading; we can embed in paragraph. - The Main Responsibilities: list of duties. - What We Look For In a Candidate: includes culture description and then "Main Requirements". Could be "Requirements" or "Qualifications". We'll have a Requirements section. - Compensation: includes salary range and benefits description. So we can have Pay section (salary range) and Benefits section (benefits). Also schedule? Not given. - What To Expect Next: background screening etc. That's application instructions? Might be considered boilerplate? It's about process; maybe we keep as part of "About the role"? But instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What To Expect Next" includes background screening etc. That's application instructions; we should remove. - Equal Employment Opportunities: boilerplate, remove. - Copyright line: remove. Thus we keep: About the role (company description + role description), Responsibilities, Requirements (including education, experience, skills), Pay (salary range), Benefits (benefits description). Possibly also Work Location as part of About the role. We must not repeat job title as heading. So we won't put "Field Support Administrator". We'll just have headings. We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must preserve all substantive information; do not invent or summarize away detail.
We need to ensure we don't create sections with filler text.
Let's extract content.
Company description (About Forged Fiber):
"At Forged Fiber, our mission is bold but simple: deliver fast, reliable, future-proof connectivity that builds the foundation for everything online. As we execute, we believe the right way to do something is the only way. This foundation guides how the company builds, operates, and maintains a state-of-the-art open-access fiber network platform that empowers millions. Forged Fiber is about more than building a network. It is about people. Every role matters. Every contribution counts. Together, employees create impact through teamwork, trust, and a shared commitment to excellence."
We can put that in a
under About the role heading.
Then "The Role" description:
"The Field Support Administrator (FSA) is responsible for planning, coordinating, and supporting construction projects related to the restoration, maintenance, and deployment of Outside Plant (OSP) fiber infrastructure, including FTTx, GPON, and related network systems. This role manages projects from initiation through completion, ensuring quality, compliance, and timely delivery. The FSA works cross-functionally with Field Operations, Engineering, contractors, and project management teams to ensure accurate execution and reporting of all project activities."
We can include that as part of About the role or separate? Since we have About the role heading, we can combine both company description and role description under that heading.
Then Work Location: "Hybrid - Phoenix, AZ or Las Vegas, NV". Could be a short paragraph.
Then Responsibilities: list bullet points.
Let's list responsibilities from "The Main Responsibilities" section:
- Coordinate with Field Operations and contractors to support project planning, execution, and restoration efforts.
- Manage multiple concurrent projects from initiation through invoicing/completion.
- Ensure project activities align with timelines, scope, and company standards.
- Conduct site visits to monitor construction progress and verify quality of work performed by internal teams and contractors.
- Ensure compliance with engineering designs, specifications, and safety standards.
- Inspect OSP work prints and construction activities for accuracy and adherence to standards.
- Partner with Engineering to ensure designs are accurately implemented in the field.
- Review engineering work prints, standards documentation, and installation procedures.
- Provide field feedback to improve design effectiveness and constructability.
- Review and approve contractor invoices for accuracy and completeness.
- Support contract compliance and vendor performance oversight.
- Assist with tracking project costs and identifying discrepancies.
- Maintain accurate project records and documentation in applicable systems
- Provide timely and accurate updates on project status, risks, and issues.
- Document and report on deficiencies, quality issues, and corrective actions.
- Act as a liaison between Engineering, Operations, contractors, and project managers.
- Proactively identify and resolve project issues and escalations.
- Provide regular feedback to internal teams and external partners.
- Ensure all work complies with USDA RUS standards, regional construction practices, and ForgedFiber37 requirements.
- Maintain working knowledge of engineering standards, safety regulations, and construction procedures.
- Monitor site housekeeping and overall project compliance.
We need to put each as
- inside a
.
Then Requirements: from "What We Look For In a Candidate" includes culture description (maybe not needed as requirement) and then "Main Requirements". We'll extract the requirements list:
- Bachelor’s degree in a related field (Construction Management, Engineering, or Telecommunications) preferred OR equivalent work experience
- 4+ years of experience in OSP/ISP construction, engineering support, or project coordination
- Experience with fiber network deployments (FTTx, GPON) preferred
- Proven experience supporting or managing construction projects
- Strong knowledge of: Underground, buried, and aerial fiber construction, OSP and ISP infrastructure, Engineering prints, schematics, and specifications
- Familiarity with central office configurations, switching, and routing (preferred)
- Working knowledge of construction codes, regulations, and compliance standards
- Strong organizational and multitasking abilities
- Excellent communication and stakeholder coordination skills
- Attention to detail and problem-solving capability
- Ability to work independently and in fast-paced environments
- Ability to travel 30–40%
- Valid driver’s license with satisfactory driving record
We can put these as - .
We might also include the culture description as prose under Requirements? But it's not a requirement; it's about culture. Could be omitted or placed under About the role? The instruction: Prefer a few substantive sections over many thin ones. We could include a short paragraph about culture under About the role or maybe under Requirements as "What we look for". But we already have Requirements section for the main requirements. The culture description could be considered part of "What we look for" but not a requirement; we could keep as prose under Requirements heading? Might be okay. However, we must not create filler. The culture description is substantive: "Forged Fiber’s culture is built on honesty, respect, trust, transparency, and a growth mindset. We strive to treat people as they want to be treated, and to operate with consistency, integrity, customer obsession, and courage. We’re looking for top tier talent to join Forged Fiber that can help us bring this mindset to our everyday work and deliver meaningful results." That's substantive; we could include as a
under Requirements or maybe under About the role. Since we already have About the role with company description and role description, we could add culture there. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put culture under About the role as part of prose.
Thus About the role heading will contain: company description, role description, work location, culture description.
Now Pay: we have compensation details: "Compensation This information reflects the anticipated base salary range for this position based on current national data. Minimums and maximums may vary based on location. Individual pay is based on skills, experience and other relevant factors. Location Based Pay Ranges: $80,000-$120,000". That's substantive; we need a Pay section with that info as
. Also note they mention benefits after that: "Forged Fiber offers a comprehensive package featuring a broad range of Health, Life, Voluntary Lifestyle benefits and other perks that enhance your physical, mental, emotional and financial wellbeing." That's benefits; we can have Benefits section with that as
.
We should not include schedule (not given). So we omit Schedule.
We must not include any boilerplate like EEO, background screening, etc.
Now we need to output HTML fragment only.
Structure:
About the role
... company description ...
... role description ...
Work Location: Hybrid - Phoenix, AZ or Las Vegas, NV
... culture description ...
Responsibilities
- ...
...
Requirements
Forged Fiber’s culture is built on honesty, respect, trust, transparency, and a growth mindset. We strive to treat people as they want to be treated, and to operate with consistency, integrity, customer obsession, and courage. We’re looking for top tier talent to join Forged Fiber that can help us bring this mindset to our everyday work and deliver meaningful results.
- Bachelor’s degree in a related field (Construction Management, Engineering, or Telecommunications) preferred OR equivalent work experience
- 4+ years of experience in OSP/ISP construction, engineering support, or project coordination
- Experience with fiber network deployments (FTTx, GPON) preferred
- Proven experience supporting or managing construction projects
- Strong knowledge of: Underground, buried, and aerial fiber construction, OSP and ISP infrastructure, Engineering prints, schematics, and specifications
- Familiarity with central office configurations, switching, and routing (preferred)
- Working knowledge of construction codes, regulations, and compliance standards
- Strong organizational and multitasking abilities
- Excellent communication and stakeholder coordination skills
- Attention to detail and problem-solving capability
- Ability to work independently and in fast-paced environments
- Ability to travel 30–40%
- Valid driver’s license with satisfactory driving record
Pay
This information reflects the anticipated base salary range for this position based on current national data. Minimums and maximums may vary based on location. Individual pay is based on skills, experience and other relevant factors. Location Based Pay Ranges: $80,000-$120,000
for prose. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we don't create sections with filler text. Let's extract content. Company description (About Forged Fiber): "At Forged Fiber, our mission is bold but simple: deliver fast, reliable, future-proof connectivity that builds the foundation for everything online. As we execute, we believe the right way to do something is the only way. This foundation guides how the company builds, operates, and maintains a state-of-the-art open-access fiber network platform that empowers millions. Forged Fiber is about more than building a network. It is about people. Every role matters. Every contribution counts. Together, employees create impact through teamwork, trust, and a shared commitment to excellence." We can put that in a
under About the role heading. Then "The Role" description: "The Field Support Administrator (FSA) is responsible for planning, coordinating, and supporting construction projects related to the restoration, maintenance, and deployment of Outside Plant (OSP) fiber infrastructure, including FTTx, GPON, and related network systems. This role manages projects from initiation through completion, ensuring quality, compliance, and timely delivery. The FSA works cross-functionally with Field Operations, Engineering, contractors, and project management teams to ensure accurate execution and reporting of all project activities." We can include that as part of About the role or separate? Since we have About the role heading, we can combine both company description and role description under that heading. Then Work Location: "Hybrid - Phoenix, AZ or Las Vegas, NV". Could be a short paragraph. Then Responsibilities: list bullet points. Let's list responsibilities from "The Main Responsibilities" section: - Coordinate with Field Operations and contractors to support project planning, execution, and restoration efforts. - Manage multiple concurrent projects from initiation through invoicing/completion. - Ensure project activities align with timelines, scope, and company standards. - Conduct site visits to monitor construction progress and verify quality of work performed by internal teams and contractors. - Ensure compliance with engineering designs, specifications, and safety standards. - Inspect OSP work prints and construction activities for accuracy and adherence to standards. - Partner with Engineering to ensure designs are accurately implemented in the field. - Review engineering work prints, standards documentation, and installation procedures. - Provide field feedback to improve design effectiveness and constructability. - Review and approve contractor invoices for accuracy and completeness. - Support contract compliance and vendor performance oversight. - Assist with tracking project costs and identifying discrepancies. - Maintain accurate project records and documentation in applicable systems - Provide timely and accurate updates on project status, risks, and issues. - Document and report on deficiencies, quality issues, and corrective actions. - Act as a liaison between Engineering, Operations, contractors, and project managers. - Proactively identify and resolve project issues and escalations. - Provide regular feedback to internal teams and external partners. - Ensure all work complies with USDA RUS standards, regional construction practices, and ForgedFiber37 requirements. - Maintain working knowledge of engineering standards, safety regulations, and construction procedures. - Monitor site housekeeping and overall project compliance. We need to put each as
- .
Then Requirements: from "What We Look For In a Candidate" includes culture description (maybe not needed as requirement) and then "Main Requirements". We'll extract the requirements list:
- Bachelor’s degree in a related field (Construction Management, Engineering, or Telecommunications) preferred OR equivalent work experience
- 4+ years of experience in OSP/ISP construction, engineering support, or project coordination
- Experience with fiber network deployments (FTTx, GPON) preferred
- Proven experience supporting or managing construction projects
- Strong knowledge of: Underground, buried, and aerial fiber construction, OSP and ISP infrastructure, Engineering prints, schematics, and specifications
- Familiarity with central office configurations, switching, and routing (preferred)
- Working knowledge of construction codes, regulations, and compliance standards
- Strong organizational and multitasking abilities
- Excellent communication and stakeholder coordination skills
- Attention to detail and problem-solving capability
- Ability to work independently and in fast-paced environments
- Ability to travel 30–40%
- Valid driver’s license with satisfactory driving record
We can put these as
- .
We might also include the culture description as prose under Requirements? But it's not a requirement; it's about culture. Could be omitted or placed under About the role? The instruction: Prefer a few substantive sections over many thin ones. We could include a short paragraph about culture under About the role or maybe under Requirements as "What we look for". But we already have Requirements section for the main requirements. The culture description could be considered part of "What we look for" but not a requirement; we could keep as prose under Requirements heading? Might be okay. However, we must not create filler. The culture description is substantive: "Forged Fiber’s culture is built on honesty, respect, trust, transparency, and a growth mindset. We strive to treat people as they want to be treated, and to operate with consistency, integrity, customer obsession, and courage. We’re looking for top tier talent to join Forged Fiber that can help us bring this mindset to our everyday work and deliver meaningful results." That's substantive; we could include as a
under Requirements or maybe under About the role. Since we already have About the role with company description and role description, we could add culture there. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put culture under About the role as part of prose. Thus About the role heading will contain: company description, role description, work location, culture description. Now Pay: we have compensation details: "Compensation This information reflects the anticipated base salary range for this position based on current national data. Minimums and maximums may vary based on location. Individual pay is based on skills, experience and other relevant factors. Location Based Pay Ranges: $80,000-$120,000". That's substantive; we need a Pay section with that info as
. Also note they mention benefits after that: "Forged Fiber offers a comprehensive package featuring a broad range of Health, Life, Voluntary Lifestyle benefits and other perks that enhance your physical, mental, emotional and financial wellbeing." That's benefits; we can have Benefits section with that as
. We should not include schedule (not given). So we omit Schedule. We must not include any boilerplate like EEO, background screening, etc. Now we need to output HTML fragment only. Structure:
About the role
... company description ...
... role description ...
Work Location: Hybrid - Phoenix, AZ or Las Vegas, NV
... culture description ...
Responsibilities
- ... ...
Requirements
Forged Fiber’s culture is built on honesty, respect, trust, transparency, and a growth mindset. We strive to treat people as they want to be treated, and to operate with consistency, integrity, customer obsession, and courage. We’re looking for top tier talent to join Forged Fiber that can help us bring this mindset to our everyday work and deliver meaningful results.
- Bachelor’s degree in a related field (Construction Management, Engineering, or Telecommunications) preferred OR equivalent work experience
- 4+ years of experience in OSP/ISP construction, engineering support, or project coordination
- Experience with fiber network deployments (FTTx, GPON) preferred
- Proven experience supporting or managing construction projects
- Strong knowledge of: Underground, buried, and aerial fiber construction, OSP and ISP infrastructure, Engineering prints, schematics, and specifications
- Familiarity with central office configurations, switching, and routing (preferred)
- Working knowledge of construction codes, regulations, and compliance standards
- Strong organizational and multitasking abilities
- Excellent communication and stakeholder coordination skills
- Attention to detail and problem-solving capability
- Ability to work independently and in fast-paced environments
- Ability to travel 30–40%
- Valid driver’s license with satisfactory driving record
Pay
This information reflects the anticipated base salary range for this position based on current national data. Minimums and maximums may vary based on location. Individual pay is based on skills, experience and other relevant factors. Location Based Pay Ranges: $80,000-$120,000