Senior Data Center Technician (On-site)
Trace3 · Henderson, NV · 4 wk ago
On-siteInformation Technology$35/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate (EEO, etc). Must preserve all substantive info.
We need to parse the posting.
First part: "Who is Trace3?" description about company. That's not part of role specifics; but maybe we can include as "About the company"? Not required sections list includes About the role only. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. The posting includes "About the Role:" heading with description. So we will have About the role section.
Responsibilities: The "What You’ll Do:" section includes bullet points with percentages. Those are responsibilities. So we need a Responsibilities section with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. The posting includes "About the Role:" heading with description. So we will have About the role section.
Responsibilities: The "What You’ll Do:" section includes bullet points with percentages. Those are responsibilities. So we need a Responsibilities section with - items.
Requirements: There's a "Qualifications and Interests" section listing qualifications. Also "EDUCATION/CERTIFICATION:" part. Those are requirements. So we can have Requirements section.
Qualifications: Might be overlapping with Requirements. The instruction says we can have both Requirements and Qualifications sections if there is distinct content. But we might combine? The posting has "Qualifications and Interests" and then "EDUCATION/CERTIFICATION:" which are qualifications. There's also maybe "Skills" implied? Not explicit. Could create Skills section from list of skills like networking hardware, protocols, troubleshooting tools, etc. But we need to see if there is specific content for Skills. The qualifications list includes many skill-like items. Could treat them as Skills. However we must not create thin sections. Better to have Requirements (including experience, education) and Skills (technical skills). Let's see.
The posting includes: "At least six years’ experience in a technical or data center support role." etc. That's experience requirement. Then "Experience working with various networking hardware such as multiplexers, routers, and switches." etc. Those are skills. Then "Proficient knowledge of common network protocols such as TCP/IP." etc. Those are skills. Then "Familiarity with configuring networking and security equipment." etc. Then "Familiarity with configuring Microsoft Windows and various versions of Linux." etc. Then "Experience with data communication issues." Then "Proficiency in Network troubleshooting tools (ping, traceroute, SNMP)." etc. Then "Ability to work independently and manage multiple priorities and interruptions." etc. Then "Good understanding of Internet technologies (firewall/router/switch/VPN/DNS/Proxy)." etc. Then "Driven to independently research solutions when provided the desired result." etc. Then "Ability to travel to support our Professional Services requirements." Then education/certification.
Thus we can split: Requirements: experience, education/certification, ability to travel. Skills: technical skills list.
Benefits: The posting includes "The Perks" bullet list: Comprehensive medical, dental and vision plans..., 401(k) Retirement Plan..., Competitive Compensation, Training and development programs, Major offices stocked with snacks and beverages, Collaborative and cool culture, Work-life balance and generous paid time off. That's benefits.
Pay: The posting includes "Estimated Pay Range: $35 USD - $40 USD". That's pay.
Schedule: Not mentioned besides "100% Onsite requirement and will require some travel". That's schedule/location. Could be considered Schedule? The instruction says include Schedule section only if posting actually states them. It mentions onsite requirement and travel. That's schedule/location. We could include Schedule section with that info. However they said "Prefer a few substantive sections over many thin ones." Might combine schedule into About the role? But we have separate sections. The schedule info is specific: "*** This is a position with a 100% Onsite requirement and will require some travel***". That's schedule/location. We'll include Schedule section.
We must not include boilerplate like EEO, equal opportunity, scam warning, etc. Also remove duplicated lines, navigation, cookie, legal. Also remove "Our Commitment" etc (EEO). Also remove "Who is Trace3?" maybe not needed as it's company overview but could be considered About the company not required. The instruction says we should not repeat job title as heading, but we can include other content. However they said "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the company description? It's substantive but not part of role sections. Where to put it? Could be placed before sections as a
maybe. The instruction says output ONLY the HTML fragment, no /. We can include a
describing Trace3 at top. That's fine.
We must not include "About the Role:" heading as we will use
About the role
and then the prose under it. The original "About the Role:" includes a sentence: "Under the general direction of the Lead, Data Center Operations, the Senior Data Center Technician will provide hands-on support and remote hand services for customers, train and mentor lower-level resources, complete standard reports, and support cross-functional teams in fulfilling service requests. *** This is a position with a 100% Onsite requirement and will require some travel***". We'll need to keep that prose. The schedule info we might move to Schedule section, but we could keep it in About the role? Better to follow instruction: include Schedule section only if posting has real specific content for it. It does. So we should extract schedule info into its own section. However the About the role section should still contain the rest of the description (the duties under general direction). We'll keep that.
Now responsibilities: The "What You’ll Do:" includes bullet points with percentages. We'll turn each bullet into - . Should we keep the percentages? Yes preserve. We'll keep them as part of the li text.
We need to avoid duplication: The responsibilities list includes many items; we will keep them all.
Now Requirements section: We'll include the experience requirement sentences, maybe combine into a
. Also include education/certification.
We need to decide what goes into Requirements vs Skills. Let's define:
Requirements: Minimum experience, education/certification, ability to travel (maybe schedule). But we already have schedule separate. So Requirements: "At least six years’ experience in a technical or data center support role." plus "Experience working with various networking hardware such as multiplexers, routers, and switches."? Actually that's skill. Hmm.
Better: Requirements: experience, education/certification, ability to travel (maybe). Skills: technical skills list (networking hardware, protocols, OS, troubleshooting tools, internet technologies, etc.) plus soft skills like ability to work independently, manage priorities, research solutions.
But the instruction says we can have both Requirements and Qualifications sections. However they gave example list includes Qualifications as a section. So we could have Requirements (experience, education) and Qualifications (skills). But they also have Skills as separate. Might be overlapping.
Given the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect possibly all these sections. We need to include a section only when posting has real specific content for it. So we need to decide what content maps to each.
Let's map:
- About the role: description of role (general direction).
- Responsibilities: What You’ll Do (the bullet list).
- Requirements: maybe the "At least six years’ experience..." and "EDUCATION/CERTIFICATION:" (high school diploma/GED required, certifications preferred). Also ability to travel? Might be schedule.
- Qualifications: maybe the list of "Experience working with various networking hardware...", "Experience creating SOP’s...", "Manage solutions to objectives and metrics.", "Proficient knowledge of common network protocols...", "Proven experience with fault isolation...", "Familiarity with configuring networking and security equipment.", "Familiarity with configuring Microsoft Windows and various versions of Linux.", "Experience with data communication issues.", "Proficiency in Network troubleshooting tools...", "Ability to work independently and manage multiple priorities and interruptions.", "Good understanding of Internet technologies...", "Driven to independently research solutions...", "Ability to travel to support our Professional Services requirements." That's a lot; could be qualifications.
- Skills: maybe not needed if we used Qualifications. But we could still have Skills for technical skills like networking hardware, protocols, OS, troubleshooting tools, internet technologies. However that would split the qualifications list thinly. Better to have Qualifications cover all those, and maybe omit Skills.
But the instruction says we can have both Requirements and Qualifications sections if there is real specific content. The posting has both "Qualifications and Interests" heading and then "EDUCATION/CERTIFICATION:" which is more like qualifications. So we can treat "Qualifications and Interests" as Qualifications section, and EDUCATION/CERTIFICATION as part of Requirements (or also Qualifications). However we need to avoid duplication.
Let's decide:
- Requirements: Minimum experience (six years), education (HS diploma/GED), certifications (preferred). Also maybe ability to travel? But we have schedule.
- Qualifications: The list of specific technical and soft skills under "Qualifications and Interests". That seems appropriate.
- Skills: Could be omitted because we used Qualifications. But we could still have Skills for maybe the technical skills like networking hardware, protocols, OS, troubleshooting tools, internet technologies. However that would be thin.
Given the instruction to prefer few substantive sections over many thin ones, we might combine Qualifications and Skills into one Qualifications section. But they gave both as possible headings; we can choose to omit Skills if content not distinct enough. The posting does not have a separate "Skills" heading; it's all under Qualifications and Interests. So we can omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Now we need to strip boilerplate: Remove "Who is Trace3?"? That's company overview; maybe we keep as introductory paragraph before sections. It's substantive about the company. Not boilerplate. We'll keep it as a
at top.
Remove "Street-Smart - Thriving in Dynamic Times", "Juice - The “Stuff” it takes to be a Needle Mover", "Teamwork - Humble, Hungry and Smart". Those are cultural values; maybe they are substantive but not part of role. Could be considered company culture; we could keep as a
maybe under About the company? But they are not required sections. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep them somewhere. Could be placed in a
after the company overview. However they are not part of role; but we can include them as a general description. It's okay.
But we must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "Our Commitment" section is EEO boilerplate; we must remove that. Also the lines about accommodation, recruitment agencies, etc. Must remove.
Thus we keep:
- Opening paragraph: "Who is Trace3? Trace3 is a leading Transformative IT Authority, providing unique technology solutions and consulting services to our clients. Equipped with elite engineering and dynamic innovation, we empower IT executives and their organizations to achieve competitive advantage through a process of Integrate, Automate, Innovate. Our culture at Trace3 embodies the spirit of a startup with the advantage of a scalable business. Employees can grow their career and have fun while doing it! Trace3 is headquartered in Irvine, California. We employ more than 1,200 people all over the United States. Our major field office locations include Denver, Indianapolis, Grand Rapids, Lexington, Los Angeles, Louisville, Texas, San Francisco. Ready to discover the possibilities that live in technology? Come Join Us!"
- Then the cultural values
maybe. The instruction says output ONLY the HTML fragment, no /. We can include a
describing Trace3 at top. That's fine. We must not include "About the Role:" heading as we will use
About the role
and then the prose under it. The original "About the Role:" includes a sentence: "Under the general direction of the Lead, Data Center Operations, the Senior Data Center Technician will provide hands-on support and remote hand services for customers, train and mentor lower-level resources, complete standard reports, and support cross-functional teams in fulfilling service requests. *** This is a position with a 100% Onsite requirement and will require some travel***". We'll need to keep that prose. The schedule info we might move to Schedule section, but we could keep it in About the role? Better to follow instruction: include Schedule section only if posting has real specific content for it. It does. So we should extract schedule info into its own section. However the About the role section should still contain the rest of the description (the duties under general direction). We'll keep that. Now responsibilities: The "What You’ll Do:" includes bullet points with percentages. We'll turn each bullet into- . Also include education/certification.
We need to decide what goes into Requirements vs Skills. Let's define:
Requirements: Minimum experience, education/certification, ability to travel (maybe schedule). But we already have schedule separate. So Requirements: "At least six years’ experience in a technical or data center support role." plus "Experience working with various networking hardware such as multiplexers, routers, and switches."? Actually that's skill. Hmm.
Better: Requirements: experience, education/certification, ability to travel (maybe). Skills: technical skills list (networking hardware, protocols, OS, troubleshooting tools, internet technologies, etc.) plus soft skills like ability to work independently, manage priorities, research solutions.
But the instruction says we can have both Requirements and Qualifications sections. However they gave example list includes Qualifications as a section. So we could have Requirements (experience, education) and Qualifications (skills). But they also have Skills as separate. Might be overlapping.
Given the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect possibly all these sections. We need to include a section only when posting has real specific content for it. So we need to decide what content maps to each. Let's map: - About the role: description of role (general direction). - Responsibilities: What You’ll Do (the bullet list). - Requirements: maybe the "At least six years’ experience..." and "EDUCATION/CERTIFICATION:" (high school diploma/GED required, certifications preferred). Also ability to travel? Might be schedule. - Qualifications: maybe the list of "Experience working with various networking hardware...", "Experience creating SOP’s...", "Manage solutions to objectives and metrics.", "Proficient knowledge of common network protocols...", "Proven experience with fault isolation...", "Familiarity with configuring networking and security equipment.", "Familiarity with configuring Microsoft Windows and various versions of Linux.", "Experience with data communication issues.", "Proficiency in Network troubleshooting tools...", "Ability to work independently and manage multiple priorities and interruptions.", "Good understanding of Internet technologies...", "Driven to independently research solutions...", "Ability to travel to support our Professional Services requirements." That's a lot; could be qualifications. - Skills: maybe not needed if we used Qualifications. But we could still have Skills for technical skills like networking hardware, protocols, OS, troubleshooting tools, internet technologies. However that would split the qualifications list thinly. Better to have Qualifications cover all those, and maybe omit Skills. But the instruction says we can have both Requirements and Qualifications sections if there is real specific content. The posting has both "Qualifications and Interests" heading and then "EDUCATION/CERTIFICATION:" which is more like qualifications. So we can treat "Qualifications and Interests" as Qualifications section, and EDUCATION/CERTIFICATION as part of Requirements (or also Qualifications). However we need to avoid duplication. Let's decide: - Requirements: Minimum experience (six years), education (HS diploma/GED), certifications (preferred). Also maybe ability to travel? But we have schedule. - Qualifications: The list of specific technical and soft skills under "Qualifications and Interests". That seems appropriate. - Skills: Could be omitted because we used Qualifications. But we could still have Skills for maybe the technical skills like networking hardware, protocols, OS, troubleshooting tools, internet technologies. However that would be thin. Given the instruction to prefer few substantive sections over many thin ones, we might combine Qualifications and Skills into one Qualifications section. But they gave both as possible headings; we can choose to omit Skills if content not distinct enough. The posting does not have a separate "Skills" heading; it's all under Qualifications and Interests. So we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to strip boilerplate: Remove "Who is Trace3?"? That's company overview; maybe we keep as introductory paragraph before sections. It's substantive about the company. Not boilerplate. We'll keep it as a
at top. Remove "Street-Smart - Thriving in Dynamic Times", "Juice - The “Stuff” it takes to be a Needle Mover", "Teamwork - Humble, Hungry and Smart". Those are cultural values; maybe they are substantive but not part of role. Could be considered company culture; we could keep as a
maybe under About the company? But they are not required sections. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep them somewhere. Could be placed in a
after the company overview. However they are not part of role; but we can include them as a general description. It's okay. But we must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "Our Commitment" section is EEO boilerplate; we must remove that. Also the lines about accommodation, recruitment agencies, etc. Must remove. Thus we keep: - Opening paragraph: "Who is Trace3? Trace3 is a leading Transformative IT Authority, providing unique technology solutions and consulting services to our clients. Equipped with elite engineering and dynamic innovation, we empower IT executives and their organizations to achieve competitive advantage through a process of Integrate, Automate, Innovate. Our culture at Trace3 embodies the spirit of a startup with the advantage of a scalable business. Employees can grow their career and have fun while doing it! Trace3 is headquartered in Irvine, California. We employ more than 1,200 people all over the United States. Our major field office locations include Denver, Indianapolis, Grand Rapids, Lexington, Los Angeles, Louisville, Texas, San Francisco. Ready to discover the possibilities that live in technology? Come Join Us!" - Then the cultural values