Network Operations Center (NOC) Technician (3rd Shift)
Limitless Mobile · Harrisburg, PA · 1 mo ago
Information TechnologyInternship
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- Role description: "The NOC Technician works as part of the Network Operations Center (NOC) team, consisting of NOC Engineers and NOC Technicians, with responsibility for monitoring and management of Limitless Mobile’s network and service delivery as well as managing the identification, analysis and resolution of service impacting issues. This is an ideal role for a recent graduate or some with a couple of years of experience at a wireless carrier and desire to build a career in telecommunications."
That's about the role.
- Tasks/Responsibilities: many bullet-like sentences. We need to put them in
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- Role description: "The NOC Technician works as part of the Network Operations Center (NOC) team, consisting of NOC Engineers and NOC Technicians, with responsibility for monitoring and management of Limitless Mobile’s network and service delivery as well as managing the identification, analysis and resolution of service impacting issues. This is an ideal role for a recent graduate or some with a couple of years of experience at a wireless carrier and desire to build a career in telecommunications."
That's about the role.
- Tasks/Responsibilities: many bullet-like sentences. We need to put them in - . Should we separate into sections? The instruction: Use
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.
Thus we can have:
About the role
...
Responsibilities
- ...
...
Then maybe Requirements: includes education, experience, knowledge etc. Could be split into Requirements and Qualifications? The posting includes "Desired Expertise & Experience" and "Desired Personality". Also "Working Conditions". Also "Physical Requirements". Also "Measurement Salary development based on a structured set of certification and length-of-service milestones." That's about salary development but not explicit salary figure. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting mentions "Salary development based on a structured set of certification and length-of-service milestones." That's about salary development but not a specific pay range. It's still about salary. It says "Measurement Salary development based on a structured set of certification and length-of-service milestones." That's a statement about salary development. It's not a specific number but it's still about salary. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about salary development, so we could include Pay section with that content. However they also say "Prefer a few substantive sections over many thin ones." Might combine Pay into Requirements? But they want sections for Pay if present. I'd include a Pay section with that sentence.
Schedule: posting says "Work week 40 hours + as needed. Requires working in shifts including nights, weekends, and holidays. Participation in NOC on-call rotation." That's schedule info. So we can include Schedule section.
Benefits: none mentioned. So omit Benefits.
Qualifications: Could be separate from Requirements? The posting includes "Desired Expertise & Experience" (education, experience, knowledge) and "Desired Personality". Also "Working Conditions" and "Physical Requirements". Could treat "Desired Expertise & Experience" as Requirements/Qualifications. "Desired Personality" as Skills? Or maybe Skills section for technical skills. Let's map:
- About the role: role description.
- Responsibilities: list of tasks.
- Requirements: education, experience, knowledge (wireless concepts, transmission, Cisco etc.)
- Qualifications: maybe certifications (CompTIA Linux+, CCNA) and career path? But could be part of Requirements. However we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But they ask to use headings for those categories if content exists. We could have both Requirements and Qualifications if we have distinct content.
Let's extract:
Desired Expertise & Experience:
- Associate’s, bachelor’s or master’s degree in computer science or engineering or Telecommunications.
- Ideally two years working in the telecommunications industry including ideally min two years of experience with a wireless carrier.
- Understanding of wireless networking concepts, including GSM, WCDMA, HSPA, LTE, VoLTE, VoWiFi as well as SS7 and Diameter signalling seen as advantageous.
- Understanding of both T-carrier (copper) and Optical carrier (SONET) transmission technologies seen as advantageous.
- Basic knowledge of Cisco, Juniper and Extreme Networks IP routing and switching.
- Candidates who can demonstrate proficiency in Cisco technologies through a current CCNA certification preferred.
- Knowledge of SNMP -based Network Management System (NMS) configuration and administration seen as advantageous.
- Familiarity with industry standard troubleshooting tools such as Wireshark and CACTI seen as advantageous.
- Comprehensive computer skills, including familiarity with industry standard software and Operating Systems (OS) such as Red Hat, Ubuntu, CentOS Linux, Windows Server, and MS Office 365.
Desired Personality:
- Entrepreneurial and proactive self-starter with ambition to make a difference as well as strong performance and results orientation.
- Ability to thrive in a fast-paced start-up environment, managing multiple projects and deadlines in parallel with ability to recognise and adjust priorities as required.
- Meticulous, methodical, and well organised yet able to demonstrate a high degree of flexibility and adaptability.
- Ability to work effectively both independently as well as in a team.
- Confident, self-motivated, self-directed, and energetic personality.
- Strong analytical and problem-solving skills.
- Excellent skills in building and managing relationships as well as influencing.
- Excellent communications and presentation skills.
- Positive and constructive personality, including willingness to go beyond the call-of-duty to ensure successful and on-time delivery of the projects as well as ambition for continuous self-development.
Working Conditions:
- Work week 40 hours + as needed.
- Requires working in shifts including nights, weekends, and holidays.
- Participation in NOC on-call rotation.
Physical Requirements:
- Lifting and/or ability to lift 20 lbs.
- Sitting for extended periods of time.
Measurement Salary development based on a structured set of certification and length-of-service milestones.
Thus we could have sections:
- About the role (role description)
- Responsibilities (list of tasks)
- Requirements (education, experience, knowledge)
- Skills (personality traits? maybe "Skills" includes both technical and soft skills)
- Qualifications (certifications and career development)
- Schedule (work week, shifts, on-call)
- Pay (salary development)
- Physical Requirements maybe could be part of Requirements or separate? But we have no heading for Physical Requirements in the list; we could fold into Requirements or maybe into a separate section not listed but we should only use those headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use others? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should not create other headings like Physical Requirements. We should fold that content into an appropriate existing section, maybe Requirements or Qualifications.
Thus we need to map all content into those sections.
Let's decide:
About the role: role description paragraph.
Responsibilities: list of tasks from Tasks/Responsibilities.
Requirements: education, experience, knowledge (wireless concepts, transmission, Cisco etc.) plus maybe computer skills.
Skills: desired personality traits (soft skills) plus maybe technical skills like troubleshooting tools? But we already put technical skills in Requirements. Could separate: Requirements = education/experience; Skills = technical and soft skills. But we have both technical and soft. Let's think.
Qualifications: certifications (CompTIA Linux+, CCNA) and career development path (NOC Engineer roles). Also maybe measurement salary development? Actually salary development is Pay.
Schedule: work week, shifts, on-call.
Pay: salary development based on certification and length-of-service milestones.
Benefits: none -> omit.
Thus we need to ensure we don't create thin sections. Each should have substantive content.
Let's extract content for each.
About the role: The NOC Technician works as part of the Network Operations Center (NOC) team, consisting of NOC Engineers and NOC Technicians, with responsibility for monitoring and management of Limitless Mobile’s network and service delivery as well as managing the identification, analysis and resolution of service impacting issues. This is an ideal role for a recent graduate or some with a couple of years of experience at a wireless carrier and desire to build a career in telecommunications.
Responsibilities: list items:
- Monitoring and management of Limitless Mobile’s wireless network and service delivery, including Limitless Mobile’s own Ericsson based Radio Access Network (RAN) and mobile core network, customer owned Nokia based Radio Access Network as well as external service providers, including e.g., backhaul, IPX and roaming partners.
- Monitoring network and service Key Performance Indicators (KPIs) with a goal to proactively identifying issues before these begin to degrade Quality of Service (QoS) towards retail and/or wholesale customers.
- Providing regular reporting on network and service KPIs to internal (e.g., Core Network Engineering, Roaming & Wholesale, Management, etc.) as well as external (e.g., customers vendors / partners) stakeholders.
- Assist NOC Engineers and Core Network Engineering team on network dimensioning and management of critical infrastructure utilization.
- Participating in the projects to deploy new wholesale customers and/or network component with responsibility to ensure sufficient monitoring is configured to enable NOC to manage Limitless Mobile network and service delivery at a high standard as well as ensuring that support processes are defined and documented with the customer.
- All NOC team members are expected to be able to participate in on-call rotation as well as work in shifts including evenings, nights, weekends, and holidays.
- Supporting the NOC Manager in identification, evaluation, and analysis of procedure, process, and tool enhancements to constantly seek to improve the sophistication of monitoring and proactive identification of issues.
- Driving incident management through a structured and efficient approach to analysis and troubleshooting / issue identification, including escalation / coordination of support from NOC Engineers, Core Network Engineering, Partners, and Management as required.
- Managing communications with internal and external stakeholders (e.g., customers) during the issue analysis and resolution process.
- Preparing Root Cause Analysis (RCA) for issues and distributing this as part of the internal / external communications to close out incidents and identify lessons learned.
- Supporting the NOC Manager in identification and analysis of procedure, process, and tool improvements to constantly seek improvements in incident response and solution times.
- Supporting relevant management identified company initiatives, which currently include supporting Roaming & Wholesale team with IREG testing of new roaming and wholesale wireless carrier partners.
Note: Some items about on-call rotation and shifts also appear in Schedule; we might avoid duplication. But we can keep them in Responsibilities as part of duties, but also Schedule section will have schedule specifics. It's okay to have some overlap? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all info. Duplication is okay if it's in original? The original mentions on-call rotation and shifts in Responsibilities and also in Working Conditions. We'll keep both.
Requirements: education, experience, knowledge.
- Associate’s, bachelor’s or master’s degree in computer science or engineering or Telecommunications.
- Ideally two years working in the telecommunications industry including ideally min two years of experience with a wireless carrier.
- Understanding of wireless networking concepts, including GSM, WCDMA, HSPA, LTE, VoLTE, VoWiFi as well as SS7 and Diameter signalling seen as advantageous.
- Understanding of both T-carrier (copper) and Optical carrier (SONET) transmission technologies seen as advantageous.
- Basic knowledge of Cisco, Juniper and Extreme Networks IP routing and switching.
- Knowledge of SNMP -based Network Management System (NMS) configuration and administration seen as advantageous.
- Familiarity with industry standard troubleshooting
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.
Thus we can have:
About the role
...
Responsibilities
- ...
...
Then maybe Requirements: includes education, experience, knowledge etc. Could be split into Requirements and Qualifications? The posting includes "Desired Expertise & Experience" and "Desired Personality". Also "Working Conditions". Also "Physical Requirements". Also "Measurement Salary development based on a structured set of certification and length-of-service milestones." That's about salary development but not explicit salary figure. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting mentions "Salary development based on a structured set of certification and length-of-service milestones." That's about salary development but not a specific pay range. It's still about salary. It says "Measurement Salary development based on a structured set of certification and length-of-service milestones." That's a statement about salary development. It's not a specific number but it's still about salary. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about salary development, so we could include Pay section with that content. However they also say "Prefer a few substantive sections over many thin ones." Might combine Pay into Requirements? But they want sections for Pay if present. I'd include a Pay section with that sentence.
Schedule: posting says "Work week 40 hours + as needed. Requires working in shifts including nights, weekends, and holidays. Participation in NOC on-call rotation." That's schedule info. So we can include Schedule section.
Benefits: none mentioned. So omit Benefits.
Qualifications: Could be separate from Requirements? The posting includes "Desired Expertise & Experience" (education, experience, knowledge) and "Desired Personality". Also "Working Conditions" and "Physical Requirements". Could treat "Desired Expertise & Experience" as Requirements/Qualifications. "Desired Personality" as Skills? Or maybe Skills section for technical skills. Let's map:
- About the role: role description.
- Responsibilities: list of tasks.
- Requirements: education, experience, knowledge (wireless concepts, transmission, Cisco etc.)
- Qualifications: maybe certifications (CompTIA Linux+, CCNA) and career path? But could be part of Requirements. However we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But they ask to use headings for those categories if content exists. We could have both Requirements and Qualifications if we have distinct content.
Let's extract:
Desired Expertise & Experience:
- Associate’s, bachelor’s or master’s degree in computer science or engineering or Telecommunications.
- Ideally two years working in the telecommunications industry including ideally min two years of experience with a wireless carrier.
- Understanding of wireless networking concepts, including GSM, WCDMA, HSPA, LTE, VoLTE, VoWiFi as well as SS7 and Diameter signalling seen as advantageous.
- Understanding of both T-carrier (copper) and Optical carrier (SONET) transmission technologies seen as advantageous.
- Basic knowledge of Cisco, Juniper and Extreme Networks IP routing and switching.
- Candidates who can demonstrate proficiency in Cisco technologies through a current CCNA certification preferred.
- Knowledge of SNMP -based Network Management System (NMS) configuration and administration seen as advantageous.
- Familiarity with industry standard troubleshooting tools such as Wireshark and CACTI seen as advantageous.
- Comprehensive computer skills, including familiarity with industry standard software and Operating Systems (OS) such as Red Hat, Ubuntu, CentOS Linux, Windows Server, and MS Office 365.
Desired Personality:
- Entrepreneurial and proactive self-starter with ambition to make a difference as well as strong performance and results orientation.
- Ability to thrive in a fast-paced start-up environment, managing multiple projects and deadlines in parallel with ability to recognise and adjust priorities as required.
- Meticulous, methodical, and well organised yet able to demonstrate a high degree of flexibility and adaptability.
- Ability to work effectively both independently as well as in a team.
- Confident, self-motivated, self-directed, and energetic personality.
- Strong analytical and problem-solving skills.
- Excellent skills in building and managing relationships as well as influencing.
- Excellent communications and presentation skills.
- Positive and constructive personality, including willingness to go beyond the call-of-duty to ensure successful and on-time delivery of the projects as well as ambition for continuous self-development.
Working Conditions:
- Work week 40 hours + as needed.
- Requires working in shifts including nights, weekends, and holidays.
- Participation in NOC on-call rotation.
Physical Requirements:
- Lifting and/or ability to lift 20 lbs.
- Sitting for extended periods of time.
Measurement Salary development based on a structured set of certification and length-of-service milestones.
Thus we could have sections:
- About the role (role description)
- Responsibilities (list of tasks)
- Requirements (education, experience, knowledge)
- Skills (personality traits? maybe "Skills" includes both technical and soft skills)
- Qualifications (certifications and career development)
- Schedule (work week, shifts, on-call)
- Pay (salary development)
- Physical Requirements maybe could be part of Requirements or separate? But we have no heading for Physical Requirements in the list; we could fold into Requirements or maybe into a separate section not listed but we should only use those headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use others? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should not create other headings like Physical Requirements. We should fold that content into an appropriate existing section, maybe Requirements or Qualifications.
Thus we need to map all content into those sections.
Let's decide:
About the role: role description paragraph.
Responsibilities: list of tasks from Tasks/Responsibilities.
Requirements: education, experience, knowledge (wireless concepts, transmission, Cisco etc.) plus maybe computer skills.
Skills: desired personality traits (soft skills) plus maybe technical skills like troubleshooting tools? But we already put technical skills in Requirements. Could separate: Requirements = education/experience; Skills = technical and soft skills. But we have both technical and soft. Let's think.
Qualifications: certifications (CompTIA Linux+, CCNA) and career development path (NOC Engineer roles). Also maybe measurement salary development? Actually salary development is Pay.
Schedule: work week, shifts, on-call.
Pay: salary development based on certification and length-of-service milestones.
Benefits: none -> omit.
Thus we need to ensure we don't create thin sections. Each should have substantive content.
Let's extract content for each.
About the role: The NOC Technician works as part of the Network Operations Center (NOC) team, consisting of NOC Engineers and NOC Technicians, with responsibility for monitoring and management of Limitless Mobile’s network and service delivery as well as managing the identification, analysis and resolution of service impacting issues. This is an ideal role for a recent graduate or some with a couple of years of experience at a wireless carrier and desire to build a career in telecommunications.
Responsibilities: list items:
- Monitoring and management of Limitless Mobile’s wireless network and service delivery, including Limitless Mobile’s own Ericsson based Radio Access Network (RAN) and mobile core network, customer owned Nokia based Radio Access Network as well as external service providers, including e.g., backhaul, IPX and roaming partners.
- Monitoring network and service Key Performance Indicators (KPIs) with a goal to proactively identifying issues before these begin to degrade Quality of Service (QoS) towards retail and/or wholesale customers.
- Providing regular reporting on network and service KPIs to internal (e.g., Core Network Engineering, Roaming & Wholesale, Management, etc.) as well as external (e.g., customers vendors / partners) stakeholders.
- Assist NOC Engineers and Core Network Engineering team on network dimensioning and management of critical infrastructure utilization.
- Participating in the projects to deploy new wholesale customers and/or network component with responsibility to ensure sufficient monitoring is configured to enable NOC to manage Limitless Mobile network and service delivery at a high standard as well as ensuring that support processes are defined and documented with the customer.
- All NOC team members are expected to be able to participate in on-call rotation as well as work in shifts including evenings, nights, weekends, and holidays.
- Supporting the NOC Manager in identification, evaluation, and analysis of procedure, process, and tool enhancements to constantly seek to improve the sophistication of monitoring and proactive identification of issues.
- Driving incident management through a structured and efficient approach to analysis and troubleshooting / issue identification, including escalation / coordination of support from NOC Engineers, Core Network Engineering, Partners, and Management as required.
- Managing communications with internal and external stakeholders (e.g., customers) during the issue analysis and resolution process.
- Preparing Root Cause Analysis (RCA) for issues and distributing this as part of the internal / external communications to close out incidents and identify lessons learned.
- Supporting the NOC Manager in identification and analysis of procedure, process, and tool improvements to constantly seek improvements in incident response and solution times.
- Supporting relevant management identified company initiatives, which currently include supporting Roaming & Wholesale team with IREG testing of new roaming and wholesale wireless carrier partners.
Note: Some items about on-call rotation and shifts also appear in Schedule; we might avoid duplication. But we can keep them in Responsibilities as part of duties, but also Schedule section will have schedule specifics. It's okay to have some overlap? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all info. Duplication is okay if it's in original? The original mentions on-call rotation and shifts in Responsibilities and also in Working Conditions. We'll keep both.
Requirements: education, experience, knowledge.
- Associate’s, bachelor’s or master’s degree in computer science or engineering or Telecommunications.
- Ideally two years working in the telecommunications industry including ideally min two years of experience with a wireless carrier.
- Understanding of wireless networking concepts, including GSM, WCDMA, HSPA, LTE, VoLTE, VoWiFi as well as SS7 and Diameter signalling seen as advantageous.
- Understanding of both T-carrier (copper) and Optical carrier (SONET) transmission technologies seen as advantageous.
- Basic knowledge of Cisco, Juniper and Extreme Networks IP routing and switching.
- Knowledge of SNMP -based Network Management System (NMS) configuration and administration seen as advantageous.
- Familiarity with industry standard troubleshooting
for prose. Thus we can have:
About the role
...
Responsibilities
- ... ...