Operations Support Analyst
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Job Summary (maybe About the role). Primary Objectives maybe part of About the role. Duties and Responsibilities (Responsibilities). QUALIFICATIONS (Qualifications). Required Knowledge, Skills and Abilities (Skills). Physical Demands, Work Environment, and Travel (maybe not a standard heading; we could include as part of Requirements? But we only have set headings; we could include a section like "Physical Demands" but not in list; we should only use allowed headings. The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could also use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings only. So we need to map content to those sections. If a section doesn't have specific content, we omit it.
We have:
- About the role: could combine Job Summary and Primary Objectives.
- Responsibilities: Duties and Responsibilities list.
- Requirements: maybe Education and Work Experience? Could be under Qualifications? Actually Qualifications is separate. Requirements could be "Education" and "Work Experience". But we also have Qualifications section for knowledge, skills, abilities. The posting has "QUALIFICATIONS" then subparts: Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. So we could treat Qualifications as the main heading, and maybe Skills as a sub? But they want separate Skills section. Could split: Qualifications for Education and Work Experience; Skills for Required Knowledge, Skills and Abilities and Competencies.
- Benefits: none specific (no benefits mentioned). So omit.
- Pay: they mention salary range: Zone 3: $21 - $23. Also mention starting pay determined by experience etc. So we have pay info. So include Pay section.
- Schedule: none specific. No mention of schedule. So omit.
We also have Physical Demands, Work Environment, Screening Requirements, Background Checks. Those are not in allowed headings; maybe we could put under Requirements? But better to omit if not matching allowed headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they want us to use those headings only. So we should omit Physical Demands etc. However we must preserve ALL substantive information; we cannot drop that info. If we omit a section, we lose that info. But maybe we can incorporate that info into existing sections like Requirements or Qualifications. For example, Physical Demands could go under Requirements (maybe as a subsection). But we are to use - for any list of duties/requirements/benefits, and
for prose. So we could include a
Requirements
and inside include paragraphs about education, work experience, physical demands, work environment, screening requirements. That would preserve info.
Similarly, Benefits: none, so omit.
Schedule: none, omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay.
Check if we have content for each:
- About the role: Job Summary + Primary Objectives.
- Responsibilities: Duties and Responsibilities list (many bullet points).
- Requirements: Education, Work Experience, Physical Demands, Work Environment, Screening Requirements, Background Checks.
- Qualifications: maybe the "QUALIFICATIONS" heading includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. But we already used Education and Work Experience under Requirements. To avoid duplication, we need to decide where each piece goes. The posting has a section labeled "QUALIFICATIONS" with subparts Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. So we could treat that as Qualifications section, and not duplicate Education/Work Experience elsewhere. Then Requirements could be something else? But we don't have a separate "Requirements" section besides that. However the instruction says we can use Requirements heading for any list of requirements. The Qualifications section already contains requirements. So we could map Qualifications to the Qualifications
and include all its subparts. Then we might not need a separate Requirements section. But we still have Physical Demands, Work Environment, Screening Requirements, Background Checks which are not under Qualifications. Those could go under a Requirements
heading (maybe as "Additional Requirements").
Thus we will have:
- About the role (Job Summary + Primary Objectives)
- Responsibilities (Duties and Responsibilities)
- Qualifications (Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies)
- Requirements (Physical Demands, Work Environment, Screening Requirements, Background Checks)
- Pay (salary range)
We must not repeat job title as heading. No Job ID etc.
We must output only HTML fragment.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
Job Summary ... Primary Objectives ...
combine.
We need to preserve all substantive information. Let's extract.
Job Summary: "The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications."
Primary Objectives: list of bullet-like sentences: "Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks. Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements. Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects."
We can combine into a paragraph.
Responsibilities: list of duties (many). We'll put each as - .
Qualifications: includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies.
We need to format as maybe
for each subsection? Could use
with bold? Not required. We'll just put prose.
But we also need to use
- for any list of duties/requirements/benefits. For Qualifications, it's not a list but we can use
for each bullet? The subparts are like "Education High school diploma or equivalent (HSED) requiredAssociate degree or college-level coursework in Computer Science or related field preferred". That's a sentence. We'll put as
.
Similarly Work Experience: "2+ years’ experience in an Application/Helpdesk Support or related position requiredExperience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred". We'll put as
.
Required Knowledge, Skills and Abilities: list of many items separated by periods. Could be turned into
- . But it's a list of knowledge, skills, abilities. We'll treat as list.
Competencies: list of items: "Delivers Results Rigorously drives self and others to achieve high levels of individual and organization performance. Focuses on the Customer & Market Continuously evaluates what is important to the customer/client and develops products or solutions that exceed expectations. Makes Sound Business Decisions Makes timely and well-informed decisions that advance critical priorities, capitalize on new opportunities, and resolve problems. Practices our Values Supports and models The Pasha Way; conduct reflects Excellence, Honesty, Integrity, Innovation and Teamwork." Could be list.
We'll make
- for each.
Requirements section: Physical Demands, Work Environment, Screening Requirements, Background Checks. We'll put each as
maybe with headings? Not needed but we can include as prose.
Pay: include salary range: "Zone 3: $21 - $23". Also note that starting pay determined by experience etc. We'll include that.
Now ensure we don't include boilerplate like "Reasonable accommodations may be made...". That's substantive? It's about accommodations; it's part of Qualifications? It appears under QUALIFICATIONS after Education and Work Experience: "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's substantive; we should keep it. It appears twice (once after Education/Work Experience line, and again under Physical Demands). We'll include where appropriate.
Also "The information included in this description has been designed to indicate the general nature and level of work performed..." that's boilerplate? Might be considered generic; but it's substantive? It's a disclaimer. Might be considered boilerplate; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is a generic disclaimer; maybe consider legal boilerplate; we can drop it. Also "Screening Requirements Background Checks" maybe we keep as part of Requirements.
We need to avoid duplication.
Let's extract sections precisely.
I'll rewrite content.
About the role:
Job Summary: The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications.
Primary Objectives:
- Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks.
- Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements.
- Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects.
We'll combine into with sentences.
Responsibilities (Duties and Responsibilities):
List items:
- Process system updates and changes from service agreements, rate tables, and other customer documents per quality guidelines.
- Review updates, changes, and data for accuracy, duplicate records, and potential issues.
- Prepare and deliver periodic and ad-hoc reports to identify discrepancies, perform audits, and assist with operational and root cause analysis.
- Research, document, and resolve or escalate discrepancies, errors, and system issues using standard operating procedures.
- Monitor, analyze, and escalate issues appropriately.
- Provide training, guidance, and support to internal and external users on assigned applications and integrations.
- Create and manage alerts, reports, and document libraries for assigned applications.
- Perform user account and password maintenance on assigned applications.
- Prepare detailed project plans and ensure timely completion and achievement of project deliverables.
- Prepare, update, and maintain work instructions and job aids for assigned applications.
- Coordinate and assist with corporate helpdesk and IT service requests.
- Assist with customer onboarding and testing of application enhancements, upgrades, and implementations.
- Update schedule, logs, and tasks daily.
- Provide reports as requested.
- Other duties as assigned.
Qualifications:
Education: High school diploma or equivalent (HSED) required; Associate degree or college-level coursework in Computer Science or related field preferred.
Work Experience: 2+ years’ experience in an Application/Helpdesk Support or related position required; Experience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred.
Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Required Knowledge, Skills and Abilities:
- Knowledge of web-based application database and table structures.
- Proficient at navigating computer systems and web-based applications.
- Ability to enter and review data with a high degree of accuracy.
- Ability to communicate clearly with excellent verbal, written, and listening skills.
- Ability to translate technical instructions and jargon into business terms accessible to wide range of skill levels.
- Ability to work as an individual
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings only. So we need to map content to those sections. If a section doesn't have specific content, we omit it.
We have:
- About the role: could combine Job Summary and Primary Objectives.
- Responsibilities: Duties and Responsibilities list.
- Requirements: maybe Education and Work Experience? Could be under Qualifications? Actually Qualifications is separate. Requirements could be "Education" and "Work Experience". But we also have Qualifications section for knowledge, skills, abilities. The posting has "QUALIFICATIONS" then subparts: Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. So we could treat Qualifications as the main heading, and maybe Skills as a sub? But they want separate Skills section. Could split: Qualifications for Education and Work Experience; Skills for Required Knowledge, Skills and Abilities and Competencies.
- Benefits: none specific (no benefits mentioned). So omit.
- Pay: they mention salary range: Zone 3: $21 - $23. Also mention starting pay determined by experience etc. So we have pay info. So include Pay section.
- Schedule: none specific. No mention of schedule. So omit.
We also have Physical Demands, Work Environment, Screening Requirements, Background Checks. Those are not in allowed headings; maybe we could put under Requirements? But better to omit if not matching allowed headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they want us to use those headings only. So we should omit Physical Demands etc. However we must preserve ALL substantive information; we cannot drop that info. If we omit a section, we lose that info. But maybe we can incorporate that info into existing sections like Requirements or Qualifications. For example, Physical Demands could go under Requirements (maybe as a subsection). But we are to use - for any list of duties/requirements/benefits, and
for prose. So we could include a
Requirements
and inside include paragraphs about education, work experience, physical demands, work environment, screening requirements. That would preserve info.
Similarly, Benefits: none, so omit.
Schedule: none, omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay.
Check if we have content for each:
- About the role: Job Summary + Primary Objectives.
- Responsibilities: Duties and Responsibilities list (many bullet points).
- Requirements: Education, Work Experience, Physical Demands, Work Environment, Screening Requirements, Background Checks.
- Qualifications: maybe the "QUALIFICATIONS" heading includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. But we already used Education and Work Experience under Requirements. To avoid duplication, we need to decide where each piece goes. The posting has a section labeled "QUALIFICATIONS" with subparts Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. So we could treat that as Qualifications section, and not duplicate Education/Work Experience elsewhere. Then Requirements could be something else? But we don't have a separate "Requirements" section besides that. However the instruction says we can use Requirements heading for any list of requirements. The Qualifications section already contains requirements. So we could map Qualifications to the Qualifications
and include all its subparts. Then we might not need a separate Requirements section. But we still have Physical Demands, Work Environment, Screening Requirements, Background Checks which are not under Qualifications. Those could go under a Requirements
heading (maybe as "Additional Requirements").
Thus we will have:
- About the role (Job Summary + Primary Objectives)
- Responsibilities (Duties and Responsibilities)
- Qualifications (Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies)
- Requirements (Physical Demands, Work Environment, Screening Requirements, Background Checks)
- Pay (salary range)
We must not repeat job title as heading. No Job ID etc.
We must output only HTML fragment.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
Job Summary ... Primary Objectives ...
combine.
We need to preserve all substantive information. Let's extract.
Job Summary: "The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications."
Primary Objectives: list of bullet-like sentences: "Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks. Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements. Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects."
We can combine into a paragraph.
Responsibilities: list of duties (many). We'll put each as - .
Qualifications: includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies.
We need to format as maybe
for each subsection? Could use
with bold? Not required. We'll just put prose.
But we also need to use
- for any list of duties/requirements/benefits. For Qualifications, it's not a list but we can use
for each bullet? The subparts are like "Education High school diploma or equivalent (HSED) requiredAssociate degree or college-level coursework in Computer Science or related field preferred". That's a sentence. We'll put as
.
Similarly Work Experience: "2+ years’ experience in an Application/Helpdesk Support or related position requiredExperience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred". We'll put as
.
Required Knowledge, Skills and Abilities: list of many items separated by periods. Could be turned into
- . But it's a list of knowledge, skills, abilities. We'll treat as list.
Competencies: list of items: "Delivers Results Rigorously drives self and others to achieve high levels of individual and organization performance. Focuses on the Customer & Market Continuously evaluates what is important to the customer/client and develops products or solutions that exceed expectations. Makes Sound Business Decisions Makes timely and well-informed decisions that advance critical priorities, capitalize on new opportunities, and resolve problems. Practices our Values Supports and models The Pasha Way; conduct reflects Excellence, Honesty, Integrity, Innovation and Teamwork." Could be list.
We'll make
- for each.
Requirements section: Physical Demands, Work Environment, Screening Requirements, Background Checks. We'll put each as
maybe with headings? Not needed but we can include as prose.
Pay: include salary range: "Zone 3: $21 - $23". Also note that starting pay determined by experience etc. We'll include that.
Now ensure we don't include boilerplate like "Reasonable accommodations may be made...". That's substantive? It's about accommodations; it's part of Qualifications? It appears under QUALIFICATIONS after Education and Work Experience: "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's substantive; we should keep it. It appears twice (once after Education/Work Experience line, and again under Physical Demands). We'll include where appropriate.
Also "The information included in this description has been designed to indicate the general nature and level of work performed..." that's boilerplate? Might be considered generic; but it's substantive? It's a disclaimer. Might be considered boilerplate; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is a generic disclaimer; maybe consider legal boilerplate; we can drop it. Also "Screening Requirements Background Checks" maybe we keep as part of Requirements.
We need to avoid duplication.
Let's extract sections precisely.
I'll rewrite content.
About the role:
Job Summary: The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications.
Primary Objectives:
- Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks.
- Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements.
- Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects.
We'll combine into with sentences.
Responsibilities (Duties and Responsibilities):
List items:
- Process system updates and changes from service agreements, rate tables, and other customer documents per quality guidelines.
- Review updates, changes, and data for accuracy, duplicate records, and potential issues.
- Prepare and deliver periodic and ad-hoc reports to identify discrepancies, perform audits, and assist with operational and root cause analysis.
- Research, document, and resolve or escalate discrepancies, errors, and system issues using standard operating procedures.
- Monitor, analyze, and escalate issues appropriately.
- Provide training, guidance, and support to internal and external users on assigned applications and integrations.
- Create and manage alerts, reports, and document libraries for assigned applications.
- Perform user account and password maintenance on assigned applications.
- Prepare detailed project plans and ensure timely completion and achievement of project deliverables.
- Prepare, update, and maintain work instructions and job aids for assigned applications.
- Coordinate and assist with corporate helpdesk and IT service requests.
- Assist with customer onboarding and testing of application enhancements, upgrades, and implementations.
- Update schedule, logs, and tasks daily.
- Provide reports as requested.
- Other duties as assigned.
Qualifications:
Education: High school diploma or equivalent (HSED) required; Associate degree or college-level coursework in Computer Science or related field preferred.
Work Experience: 2+ years’ experience in an Application/Helpdesk Support or related position required; Experience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred.
Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Required Knowledge, Skills and Abilities:
- Knowledge of web-based application database and table structures.
- Proficient at navigating computer systems and web-based applications.
- Ability to enter and review data with a high degree of accuracy.
- Ability to communicate clearly with excellent verbal, written, and listening skills.
- Ability to translate technical instructions and jargon into business terms accessible to wide range of skill levels.
- Ability to work as an individual
for section headings (e.g. those). Likely they want us to use those headings only. So we should omit Physical Demands etc. However we must preserve ALL substantive information; we cannot drop that info. If we omit a section, we lose that info. But maybe we can incorporate that info into existing sections like Requirements or Qualifications. For example, Physical Demands could go under Requirements (maybe as a subsection). But we are to use - for any list of duties/requirements/benefits, and
for prose. So we could include a
Requirements
and inside include paragraphs about education, work experience, physical demands, work environment, screening requirements. That would preserve info.
Similarly, Benefits: none, so omit.
Schedule: none, omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay.
Check if we have content for each:
- About the role: Job Summary + Primary Objectives.
- Responsibilities: Duties and Responsibilities list (many bullet points).
- Requirements: Education, Work Experience, Physical Demands, Work Environment, Screening Requirements, Background Checks.
- Qualifications: maybe the "QUALIFICATIONS" heading includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. But we already used Education and Work Experience under Requirements. To avoid duplication, we need to decide where each piece goes. The posting has a section labeled "QUALIFICATIONS" with subparts Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. So we could treat that as Qualifications section, and not duplicate Education/Work Experience elsewhere. Then Requirements could be something else? But we don't have a separate "Requirements" section besides that. However the instruction says we can use Requirements heading for any list of requirements. The Qualifications section already contains requirements. So we could map Qualifications to the Qualifications
and include all its subparts. Then we might not need a separate Requirements section. But we still have Physical Demands, Work Environment, Screening Requirements, Background Checks which are not under Qualifications. Those could go under a Requirements
heading (maybe as "Additional Requirements").
Thus we will have:
- About the role (Job Summary + Primary Objectives)
- Responsibilities (Duties and Responsibilities)
- Qualifications (Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies)
- Requirements (Physical Demands, Work Environment, Screening Requirements, Background Checks)
- Pay (salary range)
We must not repeat job title as heading. No Job ID etc.
We must output only HTML fragment.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
Job Summary ... Primary Objectives ...
combine.
We need to preserve all substantive information. Let's extract.
Job Summary: "The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications."
Primary Objectives: list of bullet-like sentences: "Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks. Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements. Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects."
We can combine into a paragraph.
Responsibilities: list of duties (many). We'll put each as - .
Qualifications: includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies.
We need to format as maybe
for each subsection? Could use
with bold? Not required. We'll just put prose.
But we also need to use
- for any list of duties/requirements/benefits. For Qualifications, it's not a list but we can use
for each bullet? The subparts are like "Education High school diploma or equivalent (HSED) requiredAssociate degree or college-level coursework in Computer Science or related field preferred". That's a sentence. We'll put as
.
Similarly Work Experience: "2+ years’ experience in an Application/Helpdesk Support or related position requiredExperience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred". We'll put as
.
Required Knowledge, Skills and Abilities: list of many items separated by periods. Could be turned into
- . But it's a list of knowledge, skills, abilities. We'll treat as list.
Competencies: list of items: "Delivers Results Rigorously drives self and others to achieve high levels of individual and organization performance. Focuses on the Customer & Market Continuously evaluates what is important to the customer/client and develops products or solutions that exceed expectations. Makes Sound Business Decisions Makes timely and well-informed decisions that advance critical priorities, capitalize on new opportunities, and resolve problems. Practices our Values Supports and models The Pasha Way; conduct reflects Excellence, Honesty, Integrity, Innovation and Teamwork." Could be list.
We'll make
- for each.
Requirements section: Physical Demands, Work Environment, Screening Requirements, Background Checks. We'll put each as
maybe with headings? Not needed but we can include as prose.
Pay: include salary range: "Zone 3: $21 - $23". Also note that starting pay determined by experience etc. We'll include that.
Now ensure we don't include boilerplate like "Reasonable accommodations may be made...". That's substantive? It's about accommodations; it's part of Qualifications? It appears under QUALIFICATIONS after Education and Work Experience: "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's substantive; we should keep it. It appears twice (once after Education/Work Experience line, and again under Physical Demands). We'll include where appropriate.
Also "The information included in this description has been designed to indicate the general nature and level of work performed..." that's boilerplate? Might be considered generic; but it's substantive? It's a disclaimer. Might be considered boilerplate; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is a generic disclaimer; maybe consider legal boilerplate; we can drop it. Also "Screening Requirements Background Checks" maybe we keep as part of Requirements.
We need to avoid duplication.
Let's extract sections precisely.
I'll rewrite content.
About the role:
Job Summary: The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications.
Primary Objectives:
- Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks.
- Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements.
- Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects.
We'll combine into with sentences.
Responsibilities (Duties and Responsibilities):
List items:
- Process system updates and changes from service agreements, rate tables, and other customer documents per quality guidelines.
- Review updates, changes, and data for accuracy, duplicate records, and potential issues.
- Prepare and deliver periodic and ad-hoc reports to identify discrepancies, perform audits, and assist with operational and root cause analysis.
- Research, document, and resolve or escalate discrepancies, errors, and system issues using standard operating procedures.
- Monitor, analyze, and escalate issues appropriately.
- Provide training, guidance, and support to internal and external users on assigned applications and integrations.
- Create and manage alerts, reports, and document libraries for assigned applications.
- Perform user account and password maintenance on assigned applications.
- Prepare detailed project plans and ensure timely completion and achievement of project deliverables.
- Prepare, update, and maintain work instructions and job aids for assigned applications.
- Coordinate and assist with corporate helpdesk and IT service requests.
- Assist with customer onboarding and testing of application enhancements, upgrades, and implementations.
- Update schedule, logs, and tasks daily.
- Provide reports as requested.
- Other duties as assigned.
Qualifications:
Education: High school diploma or equivalent (HSED) required; Associate degree or college-level coursework in Computer Science or related field preferred.
Work Experience: 2+ years’ experience in an Application/Helpdesk Support or related position required; Experience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred.
Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Required Knowledge, Skills and Abilities:
- Knowledge of web-based application database and table structures.
- Proficient at navigating computer systems and web-based applications.
- Ability to enter and review data with a high degree of accuracy.
- Ability to communicate clearly with excellent verbal, written, and listening skills.
- Ability to translate technical instructions and jargon into business terms accessible to wide range of skill levels.
- Ability to work as an individual
for prose. So we could include a
Requirements
and inside include paragraphs about education, work experience, physical demands, work environment, screening requirements. That would preserve info. Similarly, Benefits: none, so omit. Schedule: none, omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Check if we have content for each: - About the role: Job Summary + Primary Objectives. - Responsibilities: Duties and Responsibilities list (many bullet points). - Requirements: Education, Work Experience, Physical Demands, Work Environment, Screening Requirements, Background Checks. - Qualifications: maybe the "QUALIFICATIONS" heading includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. But we already used Education and Work Experience under Requirements. To avoid duplication, we need to decide where each piece goes. The posting has a section labeled "QUALIFICATIONS" with subparts Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies. So we could treat that as Qualifications section, and not duplicate Education/Work Experience elsewhere. Then Requirements could be something else? But we don't have a separate "Requirements" section besides that. However the instruction says we can use Requirements heading for any list of requirements. The Qualifications section already contains requirements. So we could map Qualifications to theQualifications
and include all its subparts. Then we might not need a separate Requirements section. But we still have Physical Demands, Work Environment, Screening Requirements, Background Checks which are not under Qualifications. Those could go under aRequirements
heading (maybe as "Additional Requirements"). Thus we will have: - About the role (Job Summary + Primary Objectives) - Responsibilities (Duties and Responsibilities) - Qualifications (Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies) - Requirements (Physical Demands, Work Environment, Screening Requirements, Background Checks) - Pay (salary range) We must not repeat job title as heading. No Job ID etc. We must output only HTML fragment. We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
Job Summary ... Primary Objectives ...
combine.
We need to preserve all substantive information. Let's extract.
Job Summary: "The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications."
Primary Objectives: list of bullet-like sentences: "Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks. Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements. Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects."
We can combine into a paragraph.
Responsibilities: list of duties (many). We'll put each as - .
Qualifications: includes Education, Work Experience, Required Knowledge, Skills and Abilities, Competencies.
We need to format as maybe
for each subsection? Could use
with bold? Not required. We'll just put prose.
But we also need to use
- for any list of duties/requirements/benefits. For Qualifications, it's not a list but we can use
for each bullet? The subparts are like "Education High school diploma or equivalent (HSED) requiredAssociate degree or college-level coursework in Computer Science or related field preferred". That's a sentence. We'll put as
.
Similarly Work Experience: "2+ years’ experience in an Application/Helpdesk Support or related position requiredExperience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred". We'll put as
.
Required Knowledge, Skills and Abilities: list of many items separated by periods. Could be turned into
- . But it's a list of knowledge, skills, abilities. We'll treat as list.
Competencies: list of items: "Delivers Results Rigorously drives self and others to achieve high levels of individual and organization performance. Focuses on the Customer & Market Continuously evaluates what is important to the customer/client and develops products or solutions that exceed expectations. Makes Sound Business Decisions Makes timely and well-informed decisions that advance critical priorities, capitalize on new opportunities, and resolve problems. Practices our Values Supports and models The Pasha Way; conduct reflects Excellence, Honesty, Integrity, Innovation and Teamwork." Could be list.
We'll make
- for each.
Requirements section: Physical Demands, Work Environment, Screening Requirements, Background Checks. We'll put each as
maybe with headings? Not needed but we can include as prose.
Pay: include salary range: "Zone 3: $21 - $23". Also note that starting pay determined by experience etc. We'll include that.
Now ensure we don't include boilerplate like "Reasonable accommodations may be made...". That's substantive? It's about accommodations; it's part of Qualifications? It appears under QUALIFICATIONS after Education and Work Experience: "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's substantive; we should keep it. It appears twice (once after Education/Work Experience line, and again under Physical Demands). We'll include where appropriate.
Also "The information included in this description has been designed to indicate the general nature and level of work performed..." that's boilerplate? Might be considered generic; but it's substantive? It's a disclaimer. Might be considered boilerplate; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is a generic disclaimer; maybe consider legal boilerplate; we can drop it. Also "Screening Requirements Background Checks" maybe we keep as part of Requirements.
We need to avoid duplication.
Let's extract sections precisely.
I'll rewrite content.
About the role:
Job Summary: The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications.
Primary Objectives:
- Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks.
- Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements.
- Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects.
We'll combine into with sentences.
Responsibilities (Duties and Responsibilities):
List items:
- Process system updates and changes from service agreements, rate tables, and other customer documents per quality guidelines.
- Review updates, changes, and data for accuracy, duplicate records, and potential issues.
- Prepare and deliver periodic and ad-hoc reports to identify discrepancies, perform audits, and assist with operational and root cause analysis.
- Research, document, and resolve or escalate discrepancies, errors, and system issues using standard operating procedures.
- Monitor, analyze, and escalate issues appropriately.
- Provide training, guidance, and support to internal and external users on assigned applications and integrations.
- Create and manage alerts, reports, and document libraries for assigned applications.
- Perform user account and password maintenance on assigned applications.
- Prepare detailed project plans and ensure timely completion and achievement of project deliverables.
- Prepare, update, and maintain work instructions and job aids for assigned applications.
- Coordinate and assist with corporate helpdesk and IT service requests.
- Assist with customer onboarding and testing of application enhancements, upgrades, and implementations.
- Update schedule, logs, and tasks daily.
- Provide reports as requested.
- Other duties as assigned.
Qualifications:
Education: High school diploma or equivalent (HSED) required; Associate degree or college-level coursework in Computer Science or related field preferred.
Work Experience: 2+ years’ experience in an Application/Helpdesk Support or related position required; Experience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred.
Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Required Knowledge, Skills and Abilities:
- Knowledge of web-based application database and table structures.
- Proficient at navigating computer systems and web-based applications.
- Ability to enter and review data with a high degree of accuracy.
- Ability to communicate clearly with excellent verbal, written, and listening skills.
- Ability to translate technical instructions and jargon into business terms accessible to wide range of skill levels.
- Ability to work as an individual
for prose. Thus:
About the role
Job Summary ... Primary Objectives ...
combine. We need to preserve all substantive information. Let's extract. Job Summary: "The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications." Primary Objectives: list of bullet-like sentences: "Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks. Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements. Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects." We can combine into a paragraph. Responsibilities: list of duties (many). We'll put each asfor each subsection? Could use
with bold? Not required. We'll just put prose. But we also need to use
- for any list of duties/requirements/benefits. For Qualifications, it's not a list but we can use
for each bullet? The subparts are like "Education High school diploma or equivalent (HSED) requiredAssociate degree or college-level coursework in Computer Science or related field preferred". That's a sentence. We'll put as
. Similarly Work Experience: "2+ years’ experience in an Application/Helpdesk Support or related position requiredExperience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred". We'll put as
. Required Knowledge, Skills and Abilities: list of many items separated by periods. Could be turned into
- . But it's a list of knowledge, skills, abilities. We'll treat as list.
Competencies: list of items: "Delivers Results Rigorously drives self and others to achieve high levels of individual and organization performance. Focuses on the Customer & Market Continuously evaluates what is important to the customer/client and develops products or solutions that exceed expectations. Makes Sound Business Decisions Makes timely and well-informed decisions that advance critical priorities, capitalize on new opportunities, and resolve problems. Practices our Values Supports and models The Pasha Way; conduct reflects Excellence, Honesty, Integrity, Innovation and Teamwork." Could be list.
We'll make
- for each.
Requirements section: Physical Demands, Work Environment, Screening Requirements, Background Checks. We'll put each as
maybe with headings? Not needed but we can include as prose. Pay: include salary range: "Zone 3: $21 - $23". Also note that starting pay determined by experience etc. We'll include that. Now ensure we don't include boilerplate like "Reasonable accommodations may be made...". That's substantive? It's about accommodations; it's part of Qualifications? It appears under QUALIFICATIONS after Education and Work Experience: "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's substantive; we should keep it. It appears twice (once after Education/Work Experience line, and again under Physical Demands). We'll include where appropriate. Also "The information included in this description has been designed to indicate the general nature and level of work performed..." that's boilerplate? Might be considered generic; but it's substantive? It's a disclaimer. Might be considered boilerplate; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is a generic disclaimer; maybe consider legal boilerplate; we can drop it. Also "Screening Requirements Background Checks" maybe we keep as part of Requirements. We need to avoid duplication. Let's extract sections precisely. I'll rewrite content. About the role: Job Summary: The Operations Support Analyst is responsible for maintaining, updating, and supporting system tables, user access, and reporting for proprietary and third-party applications. Primary Objectives: - Timely, accurate, and thorough completion of data entry, table maintenance, documentation, user access, and assigned administrative tasks. - Effective communication and collaboration with clients, business units, and internal resources to ensure application data and access is accurate and complies with company standards and service level agreements. - Effective tracking, reporting, and management of application updates, new customer onboarding, system issues, and projects. We'll combine into
with sentences. Responsibilities (Duties and Responsibilities): List items: - Process system updates and changes from service agreements, rate tables, and other customer documents per quality guidelines. - Review updates, changes, and data for accuracy, duplicate records, and potential issues. - Prepare and deliver periodic and ad-hoc reports to identify discrepancies, perform audits, and assist with operational and root cause analysis. - Research, document, and resolve or escalate discrepancies, errors, and system issues using standard operating procedures. - Monitor, analyze, and escalate issues appropriately. - Provide training, guidance, and support to internal and external users on assigned applications and integrations. - Create and manage alerts, reports, and document libraries for assigned applications. - Perform user account and password maintenance on assigned applications. - Prepare detailed project plans and ensure timely completion and achievement of project deliverables. - Prepare, update, and maintain work instructions and job aids for assigned applications. - Coordinate and assist with corporate helpdesk and IT service requests. - Assist with customer onboarding and testing of application enhancements, upgrades, and implementations. - Update schedule, logs, and tasks daily. - Provide reports as requested. - Other duties as assigned. Qualifications: Education: High school diploma or equivalent (HSED) required; Associate degree or college-level coursework in Computer Science or related field preferred. Work Experience: 2+ years’ experience in an Application/Helpdesk Support or related position required; Experience with Supply Chain, Transportation, Logistics, or similar industry enterprise software systems preferred. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Required Knowledge, Skills and Abilities: - Knowledge of web-based application database and table structures. - Proficient at navigating computer systems and web-based applications. - Ability to enter and review data with a high degree of accuracy. - Ability to communicate clearly with excellent verbal, written, and listening skills. - Ability to translate technical instructions and jargon into business terms accessible to wide range of skill levels. - Ability to work as an individual
- for each.
Requirements section: Physical Demands, Work Environment, Screening Requirements, Background Checks. We'll put each as
- . But it's a list of knowledge, skills, abilities. We'll treat as list.
Competencies: list of items: "Delivers Results Rigorously drives self and others to achieve high levels of individual and organization performance. Focuses on the Customer & Market Continuously evaluates what is important to the customer/client and develops products or solutions that exceed expectations. Makes Sound Business Decisions Makes timely and well-informed decisions that advance critical priorities, capitalize on new opportunities, and resolve problems. Practices our Values Supports and models The Pasha Way; conduct reflects Excellence, Honesty, Integrity, Innovation and Teamwork." Could be list.
We'll make