Advisor-Operations Research
FedEx Freight · Memphis, TN · 1 mo ago
Information TechnologyFull-time
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 need to parse the posting.
The posting includes:
- Domiciled location: FedEx Freight location in Harrison, AR or Memphis, TN. Required to work at a FedEx Freight Location several times per week.
- Position Overview: description of responsibilities.
- Essential Functions: list of duties.
- Disclaimer: general.
- Qualifications: Master's degree etc.
- Working Conditions: Hours may vary due to operational need.
- Also mention FedEx Freight is an Equal Opportunity Employer etc (EEO boilerplate) - we should remove.
- Also mention ADA assistance etc - remove.
- Also mention compensation disclosure policy - maybe part of boilerplate; but it's about compensation disclosure; not actual pay. Should we include Pay section? The posting does not state actual pay or salary range. So we should NOT include Pay section because no specific pay info. Similarly Benefits: not mentioned. Schedule: only "Hours may vary due to operational need" - that's schedule info but vague. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Hours may vary due to operational need" which is schedule info but vague. Is that considered stating schedule? It's not specific like "full-time", "shift work", etc. It's vague but still mentions hours may vary. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Hours may vary due to operational need" is somewhat vague but it's a statement about schedule. It's not placeholder like "varies"? Actually "varies" is placeholder. The rule says never create Schedule section unless posting actually states them. It does state hours may vary due to operational need. That's a statement, albeit vague. But the rule also says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "Hours may vary due to operational need" includes "may vary". That's similar to "varies". It's arguably filler. Safer to omit Schedule section because it's not specific.
Thus sections we can include:
- About the role (maybe Position Overview). Could be "About the role" heading with paragraph summarizing position overview.
- Responsibilities: essential functions list.
- Requirements: maybe qualifications? Actually Qualifications separate. Could combine Requirements and Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. The posting has "Qualifications" section with degree, experience, etc. Also there may be "Requirements" maybe implied by essential functions? But we can treat "Requirements" as the qualifications? However they'd be duplicate. Better to have "Qualifications" for the degree/experience etc. And "Skills" for technical skills like Tableau, Azure, programming, etc. The posting includes "Advanced knowledge of data visualization tools such as Tableau, PowerBI or Spotfire", "Advanced knowledge of Azure cloud services, developing data solutions and machine learning models on Databricks", "Advanced descriptive, diagnostic, predictive and prescriptive modeling knowledge and skills", "Intermediate programming skills and ability to learn new languages, including but not limited to: JAVA, SQL, SAS", "Intermediate knowledge of relational database systems Oracle, DB2 and Terradata", "Strong computer skills (Excel, Outlook, Word, PowerPoint) with experience using statistical software and reporting interfaces, data mining tools, machine learning techniques and data visualization", "Leadership, analytical, problem solving, time management, organizational and interpersonal skills", "Excellent presentation, verbal and written communication skills". Those could go under Skills.
Thus we can have:
.
Qualifications: list degree/experience etc as . But note that some qualifications also include skills; but we separated skills. However the qualifications list includes also advanced knowledge of data visualization tools etc which we might treat as skills. To avoid duplication, we could keep qualifications as degree/experience only, and skills as the rest. But the instruction says preserve ALL substantive information; we can split but must not lose any. So we need to ensure all items appear either under Qualifications or Skills. Let's decide:
Qualifications:
- Master's Degree in Industrial Engineering, Math/Statistics or related quantitative discipline or Bachelor's Degree (aforementioned disciplines) with 2 years’ experience
- Five (5) years’ experience in engineering, statistics, forecasting, or data analysis
Skills:
- Advanced knowledge of data visualization tools such as Tableau, PowerBI or Spotfire
- Advanced knowledge of Azure cloud services, developing data solutions and machine learning models on Databricks
- Advanced descriptive, diagnostic, predictive and prescriptive modeling knowledge and skills
- Intermediate programming skills and ability to learn new languages, including but not limited to: JAVA, SQL, SAS
- Intermediate knowledge of relational database systems Oracle, DB2 and Terradata
- Strong computer skills (Excel, Outlook, Word, PowerPoint) with experience using statistical software and reporting interfaces, data mining tools, machine learning techniques and data visualization
- Leadership, analytical, problem solving, time management, organizational and interpersonal skills
- Excellent presentation, verbal and written communication skills
That covers all.
Now output HTML fragment.
We must not include or . Just the fragment.
Let's produce:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
The posting includes:
- Domiciled location: FedEx Freight location in Harrison, AR or Memphis, TN. Required to work at a FedEx Freight Location several times per week.
- Position Overview: description of responsibilities.
- Essential Functions: list of duties.
- Disclaimer: general.
- Qualifications: Master's degree etc.
- Working Conditions: Hours may vary due to operational need.
- Also mention FedEx Freight is an Equal Opportunity Employer etc (EEO boilerplate) - we should remove.
- Also mention ADA assistance etc - remove.
- Also mention compensation disclosure policy - maybe part of boilerplate; but it's about compensation disclosure; not actual pay. Should we include Pay section? The posting does not state actual pay or salary range. So we should NOT include Pay section because no specific pay info. Similarly Benefits: not mentioned. Schedule: only "Hours may vary due to operational need" - that's schedule info but vague. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Hours may vary due to operational need" which is schedule info but vague. Is that considered stating schedule? It's not specific like "full-time", "shift work", etc. It's vague but still mentions hours may vary. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Hours may vary due to operational need" is somewhat vague but it's a statement about schedule. It's not placeholder like "varies"? Actually "varies" is placeholder. The rule says never create Schedule section unless posting actually states them. It does state hours may vary due to operational need. That's a statement, albeit vague. But the rule also says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "Hours may vary due to operational need" includes "may vary". That's similar to "varies". It's arguably filler. Safer to omit Schedule section because it's not specific.
Thus sections we can include:
- About the role (maybe Position Overview). Could be "About the role" heading with paragraph summarizing position overview.
- Responsibilities: essential functions list.
- Requirements: maybe qualifications? Actually Qualifications separate. Could combine Requirements and Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. The posting has "Qualifications" section with degree, experience, etc. Also there may be "Requirements" maybe implied by essential functions? But we can treat "Requirements" as the qualifications? However they'd be duplicate. Better to have "Qualifications" for the degree/experience etc. And "Skills" for technical skills like Tableau, Azure, programming, etc. The posting includes "Advanced knowledge of data visualization tools such as Tableau, PowerBI or Spotfire", "Advanced knowledge of Azure cloud services, developing data solutions and machine learning models on Databricks", "Advanced descriptive, diagnostic, predictive and prescriptive modeling knowledge and skills", "Intermediate programming skills and ability to learn new languages, including but not limited to: JAVA, SQL, SAS", "Intermediate knowledge of relational database systems Oracle, DB2 and Terradata", "Strong computer skills (Excel, Outlook, Word, PowerPoint) with experience using statistical software and reporting interfaces, data mining tools, machine learning techniques and data visualization", "Leadership, analytical, problem solving, time management, organizational and interpersonal skills", "Excellent presentation, verbal and written communication skills". Those could go under Skills.
Thus we can have:
About the role
... (position overview paragraph)
Responsibilities
- ... each essential function as list items
Qualifications
- ... Master's degree etc
Skills
- ... list of skills
About the role
This position will be domiciled at a FedEx Freight location in Harrison, AR or Memphis, TN, requiring work at a FedEx Freight location several times per week. Responsible for formulating and applying sophisticated modeling and other advanced analytic methods using a computer to develop and interpret information that assists management with decision making, policy formulation, or other managerial functions; concentrating on collecting, cleansing and analyzing data, developing decision support software and producing actionable information for decision making.
Responsibilities
- Identify business opportunities or expand ideas obtained from management in order to conceptualize and define and model operational problems to assess feasibility and impact
- Identify performance improvement opportunities via data analysis and develop decision support tools to ensure most cost conscience, efficient use of company resources that supports service objectives
- Develop concepts into business plans utilizing appropriate research techniques, methodologies, and experience and present them to senior management with recommendation for implementation
- Lead the evaluation of alternative systems or transportation networks employing financial, computer, geographic or operational models as appropriate
- Develop and implement data collection systems from primary and secondary sources and other strategies that optimize statistical efficiency and data quality
- Identify, analyze, interpret and visualize trends or patterns in complex data sets
- Research cutting edge technologies in support of the “best practices” in any transportation or network related question
- Individually, or as a project lead, design and develop models for testing, validation and evaluation of strategic proposals
- Prepare decision analysis and reports for presentation to senior management
- Utilize multi-media presentations and formal reports for presenting analyses to senior management
- Coordinate personnel involved in project administratively and technically
- Provide technical assistance and