Technical Support Engineer (Branch Engineer)
GadellNet Consulting Services · Martinsville, IN · 3 wk ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About the Position:" and then" but we have "About the Position:" as a heading. According to rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings for sections present: About the Position (maybe treat as About the role). Responsibilities, Requirements, Qualifications? There's a "Requirements" section. There's also "Desirable Skills" maybe treat as Skills. Benefits present. No Pay or Schedule. Also there is "Values" maybe not a standard heading; we could include as a section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Values section has content; but not in the list of allowed headings? The list is examples, not exclusive. We could include a
.
Now Requirements: list bullet points.
From "Requirements:" section:
- Occasional physical requirement to twist, stretch, and lift over 50 lbs.
- Reliable transportation and valid driver’s license.
- After-Hours work will be required for critical outages, projects, and on-call rotation.
- 2 or more years of experience troubleshooting and working with the following systems
- Desktop systems up to Windows 11
- Server systems up to Server 2022
- Office365 or Online Exchange 2019
- Any brand of Modern (2019) Network equipment
- 2 or more years of experience with network design, maintenance and installation
- Experience troubleshooting Network Cabling
- Mounting Network Hardware into Communication Racks or Mounting Wireless Aps
- Maintaining Network Infrastructure
- Application support
- Microsoft Teams conference Rooms
- Office Suite
- Adobe
- Exceptional interpersonal skills, with a focus on rapport-building, listening and questioning skills
- Strong documentation skills
- Ability to conduct research into a wide range of computing issues is required
- Ability to present ideas in a user-friendly, business-friendly manner
- Working knowledge of a range of diagnostic utilities
- Excellent communication skills, both written and verbal
- Valid Driver’s License (duplicate? Already mentioned reliable transportation and valid driver’s license; we can keep but maybe deduplicate. We'll keep one.)
We need to avoid duplication. We'll combine.
Now Desirable Skills: list bullet points.
- Experience with Server Administration
- Active Directory Management
- GPO maintenance and setup
- In-depth understanding of Zebra printers
- Proficient level of understanding with Powershell/CMD
Now Values: list bullet points? The text: "At GadellNet, we live and celebrate our three core values: Make an Impact 100% Responsibility 0% Excuses Grow or Die". We'll put as list.
Now Benefits: list bullet points.
- Health, vision, and dental insurance.
- Paid time off, including parental leave and volunteer time.
- Flexible work environment.
- Access to mental health services.
- Employee matching donation program.
- 401k and employer matching.
Now also there is "Eligibility to work in the US: GadellNet does not offer work visa sponsorship for this role. All candidates must be legally authorized to work in the United States at the time of application. Employment is contingent on verification of identity and eligibility to work in the United States." This is substantive but maybe not a standard heading; could be under a section like "Eligibility". But not in examples. Could we include as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings for sections present: About the Position (maybe treat as About the role). Responsibilities, Requirements, Qualifications? There's a "Requirements" section. There's also "Desirable Skills" maybe treat as Skills. Benefits present. No Pay or Schedule. Also there is "Values" maybe not a standard heading; we could include as a section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Values section has content; but not in the list of allowed headings? The list is examples, not exclusive. We could include a Values
. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not limited. Safer to include Values as a section.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, scam-warning, application instructions. Also remove duplicated lines.
We need to preserve all substantive information. So we need to capture:
- Intro paragraph about GadellNet: "GadellNet Consulting Services is a rapidly growing IT company based in the Midwest, providing technical solutions to hundreds of businesses across various markets. We are a family-friendly company and an Equal Opportunity Employer committed to building a creative, growth-oriented, and progressive work environment. We believe that diverse perspectives strengthen our team and drive innovation, and we are intentional about creating an environment where all employees feel valued, respected, and empowered to bring their full selves to work. As a Certified B Corporation, we are committed to considering the impact of our decisions on our employees, customers, suppliers, community, and environment. Join us in powering the missions of our team and our clients while making a difference in our communities. We encourage candidates to review our website to learn more about our values and company culture."
But note: The instruction says remove EEO/equal-opportunity boilerplate. The paragraph includes "Equal Opportunity Employer". That's EEO boilerplate; we should remove that line? It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should strip that phrase. However we need to preserve substantive information; the EEO statement is not substantive for the role. So we can remove it. Also "family-friendly company" maybe okay. We'll keep the rest but remove the EEO phrase.
Thus we need to rewrite that paragraph without the EEO phrase. Could keep: "GadellNet Consulting Services is a rapidly growing IT company based in the Midwest, providing technical solutions to hundreds of businesses across various markets. We are a family-friendly company committed to building a creative, growth-oriented, and progressive work environment. We believe that diverse perspectives strengthen our team and drive innovation, and we are intentional about creating an environment where all employees feel valued, respected, and empowered to bring their full selves to work. As a Certified B Corporation, we are committed to considering the impact of our decisions on our employees, customers, suppliers, community, and environment. Join us in powering the missions of our team and our clients while making a difference in our communities. We encourage candidates to review our website to learn more about our values and company culture."
Now "About the Position:" heading -> we will use About the Position
(or About the role). Use About the Position as it's in text.
Then paragraph: "As a Branch Engineer, you will be responsible for all onsite support. Your main objective is to ensure that you are timely in arriving onsite, coordinating with Dispatchers when you will be late to sites, resolving user issues onsite in a timely manner, and escalating issues that you are unable to resolve to remote teams to review. Problem resolution may involve the use of diagnostic and help request tracking tools, as well as require in person, hands on help at the desktop level. As a Branch Engineer, you will be visiting clients onsite as required and will be one of the main points of contact for any IT needs. Additional duties include assisting our project team with network infrastructure rollouts, server migrations, Office 365 deployments, and office moves. All Technical Support Engineers participate in an on-call schedule. Daily time entry and management of your personal ticket queues will be required. This role will be a full-time onsite position for one of our clients located in Martinsville, Indiana."
Now Responsibilities: list bullet points.
We need to extract from "Primary Responsibilities:" list:
- Act as a credible onsite resource for remote teams to resolve issues
- Primary contact for CSE clients that are assigned to you for technical issues
- Repair, Warranty, and deploy workstations for clients
- Diagnosing and resolving network related issues for clients
- Identify and report possible opportunities to account management for hardware and software upgrades or gaps
- Help maintain and write documentation for clients when necessary
- Participate in an On-Call rotation for after hours
- After-Hours responsibilities may include installation, configuration of server room hardware (eg. Switches, Firewalls, UPS devices)
- Troubleshoot and resolve remote tickets when on-site work is not available
We'll put each as
About the Position
(or About the role). Use About the Position as it's in text. Then paragraph: "As a Branch Engineer, you will be responsible for all onsite support. Your main objective is to ensure that you are timely in arriving onsite, coordinating with Dispatchers when you will be late to sites, resolving user issues onsite in a timely manner, and escalating issues that you are unable to resolve to remote teams to review. Problem resolution may involve the use of diagnostic and help request tracking tools, as well as require in person, hands on help at the desktop level. As a Branch Engineer, you will be visiting clients onsite as required and will be one of the main points of contact for any IT needs. Additional duties include assisting our project team with network infrastructure rollouts, server migrations, Office 365 deployments, and office moves. All Technical Support Engineers participate in an on-call schedule. Daily time entry and management of your personal ticket queues will be required. This role will be a full-time onsite position for one of our clients located in Martinsville, Indiana." Now Responsibilities: list bullet points. We need to extract from "Primary Responsibilities:" list: - Act as a credible onsite resource for remote teams to resolve issues - Primary contact for CSE clients that are assigned to you for technical issues - Repair, Warranty, and deploy workstations for clients - Diagnosing and resolving network related issues for clients - Identify and report possible opportunities to account management for hardware and software upgrades or gaps - Help maintain and write documentation for clients when necessary - Participate in an On-Call rotation for after hours - After-Hours responsibilities may include installation, configuration of server room hardware (eg. Switches, Firewalls, UPS devices) - Troubleshoot and resolve remote tickets when on-site work is not available We'll put each asafter Benefits? Probably keep as a paragraph under a heading like "Eligibility". But instruction says only include sections when posting has real specific content; we could add a
Eligibility
. However not in examples but allowed. Safer to include as a paragraph after Benefits without a heading? The instruction: Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those are typical. Might be okay to add Eligibility as a heading. However to be safe, we could incorporate that info into a
after Benefits without a heading. But then we lose a heading; still okay. We also have "If this role sounds like the right fit for you, we’d love to hear from you. Even if you don’t meet every qualification, we encourage you to apply - you might be exactly what we need! #IND". That's application encouragement; we should remove application instructions. So remove that. Now we need to output only HTML fragment. Let's structure:
About the Position
...
Responsibilities
- ... ...
Requirements
-
...
Desirable Skills
-
...
Values
-
...
Benefits
-
...
Eligibility to work in the US: GadellNet does not offer work visa sponsorship for this role. All candidates must be legally authorized to work in the United States at the time of application. Employment is contingent on verification of identity and eligibility to work in the United States.
We need to ensure no duplicate content. Now craft the About the Position paragraph: combine sentences. Let's write: As a Branch Engineer, you will be responsible for all onsite support. Your main objective is to ensure that you are timely in arriving onsite, coordinating with Dispatchers when you will be late to sites, resolving user issues onsite in a timely manner, and escalating issues that you are unable to resolve to remote teams to review. Problem resolution may involve the use of diagnostic and help request tracking tools, as well as require in person, hands‑on help at the desktop level. As a Branch Engineer, you will be visiting clients onsite as required and will be one of the main points of contact for any IT needs. Additional duties include assisting our project team with network infrastructure rollouts, server migrations, Office 365 deployments, and office moves. All Technical Support Engineers participate in an on‑call schedule. Daily time entry and management of your personal ticket queues will be required. This role will be a full‑time onsite position for one of our clients located in Martinsville, Indiana. Now Responsibilities list. Now Requirements list: need to avoid duplicate "Valid Driver’s License". We have "Reliable transportation and valid driver’s license." and later "Valid Driver’s License". We'll keep one. We'll combine: Reliable transportation and valid driver’s license. Now list items: - Occasional physical requirement to twist, stretch, and lift over 50 lbs. - Reliable transportation and valid driver’s license. - After‑hours work will be required for critical outages, projects, and on‑call rotation. - 2 or more years of experience troubleshooting and working with the following systems: - Desktop systems up to Windows 11 - Server systems up to Server 2022 - Office 365 or Online Exchange 2019 - Any brand of Modern (2019) network equipment - 2 or more years of experience with network design, maintenance and installation - Experience troubleshooting network cabling - Mounting network hardware into communication racks or