Data Analyst
for headings: 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.
Content:
- Intro about Ole Miss: maybe "About the role"? Actually "About the role" could be a summary of the position. The posting includes "Job Summary". That could be "About the role". We'll put that as About the role
with
containing the job summary text. - Responsibilities: The "Job Description" bullet list of duties. We'll put
Responsibilities
with- each duty. - Requirements: Might be education and experience. The posting includes "Education Qualifications: Bachelor's (Required)" and "Experience Relevant experience | 3 Years | Required". Also "Substitution Statement". So we can put Requirements section with education and experience. - Qualifications: Could be similar to Requirements; but we might combine. However we need separate sections only if content. Could put Qualifications for skills like SAS, SPSS, R, SQL, Excel, Tableau, etc. Those are in Job Description as tools used. Could be Skills section. - Benefits: Not mentioned. No benefits specifics. So omit Benefits. - Pay: Compensation range given: "$62,441.60 - $93,641.60". So include Pay section. - Schedule: Not mentioned (work arrangement says not eligible for remote work, but not schedule). No schedule details. So omit Schedule. - Also maybe "Work Arrangement" could be considered Schedule? But it's about remote work eligibility. Not schedule like full-time/part-time. Not given. So omit. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all duties listed. Let's extract duties from Job Description (the paragraph after "Job Description"). It's a long sentence with many items separated by periods. We'll split into list items. List: - Prepares and submits accurate and timely institutional reports to the Mississippi Board of Trustees of Institutions of Higher Learning, the federal government, university administration, and other external agencies. - Coordinates data collection across campus partners to complete external data requests, reports, and questionnaires. - Conducts statistical analyses using SAS, SPSS, R, or other analytical tools to analyze a wide variety of data. - Uses SQL, Excel, and Tableau extensively to perform data transformations and other complex operations. - Maintains datasets and reporting structures used for institutional reporting. - Serves as a point of contact for internal and external data requests. - Completes questionnaires from outside agencies on behalf of the university. - Provides historical research information for statistical studies and ad hoc requests. - Responds to time-critical ad-hoc requests - Facilitates the submission and analysis of national surveys on behalf of the university. - Coordinates and participates in assigned special and recurring projects to include planning, development, implementation, and evaluation. - Responds to requests for data from multiple constituents and may act as a liaison to academic and non-academic departments. - Collects, analyzes, and manages data from enterprise systems to support reporting, compliance, and operational decision-making. - Prepares, interprets, and communicates complex statistical information in writing, verbally and graphically for diverse audiences. - Supports data governance initiatives by documenting reporting definitions, identifying data-quality concerns, and working with data owners and subject-matter experts to validate institutional data and promote consistent reporting practices. - Handles institutional data in accordance with FERPA and other applicable university policies and regulations. - Documents the data definitions, sources, methodologies, validation procedures, and reporting processes used in assigned reports, dashboards, surveys, and data requests. - Uses SQL to query, join, transform, and validate data in a relational database environment, preferably PostgreSQL. - Combines and validates data from Ellucian Insights/Reporting and Analytics and other institutional data sources to support reporting and analysis. We need to ensure we didn't miss any. Now Responsibilities section will contain these as
- .
Now About the role: Use Job Summary paragraph: "The University of Mississippi seeks a Data Analyst I/II who will collect, retrieve, transform, analyze, validate, and report data required for institutional research, effectiveness, decision-making, and reporting processes of the institution. The incumbent completes voluntary and compulsory surveys, including college directories and publications; responds to stakeholder data requests; identifies data visualization needs; and completes questionnaires received by the University. The Data Analyst I/II should demonstrate a strong attention to detail; the ability to complete work with a high degree of accuracy; the ability to examine data critically; and contribute to the improvement of data sources, data visualizations, and use of data by stakeholders."
We'll put that as
. Now Requirements: Education and Experience. Education: Bachelor's (Required) Experience: Relevant experience | 3 Years | Required Also substitution statement: "An equivalent combination of related experience and education may be considered for this role. Substitutions of the required experience or education will be assessed on a 1:1 substitution basis." We can include that in Requirements as well. Now Qualifications: maybe we can list specific technical qualifications: SAS, SPSS, R, SQL, Excel, Tableau, PostgreSQL, Ellucian Insights/Reporting and Analytics, data governance, FERPA, etc. But those are already in responsibilities. However we could still have a Qualifications section for "Knowledge, Skills, and Abilities". But we need to avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we put them in Qualifications, we still need to keep them somewhere; we could keep them in Responsibilities (as they are duties) and also maybe in Skills section. But we should not duplicate content? It didn't forbid duplication, but better to avoid redundancy. However we need to include sections only when posting has real specific content for it. The posting does mention specific tools and skills in the Job Description; we could treat those as Skills section. But then we would be moving content from Responsibilities to Skills, potentially losing some duty description. Better to keep duties in Responsibilities and have Skills section list the tools/technologies required. However the posting does not explicitly list a separate "Skills" section; it's embedded in duties. But we can still extract them as skills. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Responsibilities or Qualifications. Since we already have Responsibilities with detailed duties, we could add a Qualifications section for education and experience, and maybe a Skills section for technical skills. But we need to avoid thin sections. Let's see: we have About the role, Responsibilities, Requirements (education/experience), Pay. That's four sections. Could add Skills as fifth if we have substantive content. The posting does mention specific tools: SAS, SPSS, R, SQL, Excel, Tableau, PostgreSQL, Ellucian Insights/Reporting and Analytics. That's substantive. So we can add Skills section. But we must ensure we don't lose any info: we already have those tools mentioned in Responsibilities duties; if we also list them in Skills, we are duplicating but not losing info. The instruction says preserve ALL substantive information; duplication is okay as long as we don't lose info. However they might prefer not to duplicate but it's not prohibited. I'd rather not duplicate to keep concise. But we can still include Skills section summarizing the tools, while keeping duties unchanged. That would be extra info but not losing any. It's okay. Alternatively we could incorporate skills into Responsibilities by keeping the duties as is (they already mention tools). Then we don't need a separate Skills section. That would be fewer sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to avoid extra thin sections. So we will not add Skills section unless we have content not already covered. Since the tools are already in duties, we can skip Skills. Thus sections: About the role, Responsibilities, Requirements (education/experience), Pay. Check if any other section like Benefits: none. Schedule: none. Now we need to format. We must not include /. Just fragment. We'll output:
About the role
...
Responsibilities
- ... ...
Requirements
Education: Bachelor's (Required)
Experience: 3 years of relevant experience (Required)
Substitution statement: An equivalent combination of related experience and education may be considered for this role. Substitutions of the required experience or education will be assessed on a 1:1 substitution basis.
Pay
$62,441.60 - $93,641.60
Make sure to preserve all details exactly as in posting. Check the job summary text: It includes semicolons. We'll copy exactly. Now responsibilities list: need to ensure each duty ends with a period as in original. We'll copy exactly. Let's copy each duty precisely: 1. Prepares and submits accurate and timely institutional reports to the Mississippi Board of Trustees of Institutions of Higher Learning, the federal government, university administration, and other external agencies. 2. Coordinates data collection across campus partners to complete external data requests, reports, and questionnaires. 3. Conducts statistical analyses using SAS, SPSS, R, or other analytical tools to analyze a wide variety of data. 4. Uses SQL, Excel, and Tableau extensively to perform data transformations and other complex operations. 5. Maintains datasets and reporting structures used for institutional reporting. 6. Serves as a point of contact for internal and external data requests. 7. Completes questionnaires from outside agencies on behalf of the university. 8. Provides historical research information for statistical studies and ad hoc requests. 9. Responds to time-critical ad-hoc requests 10. Facilitates the submission and analysis of national surveys on behalf of the university. 11. Coordinates and participates in assigned special and recurring projects to include planning, development, implementation, and evaluation. 12. Responds to requests for data from multiple constituents and may act as a liaison to academic and non-academic departments. 13. Collects, analyzes, and manages data from enterprise systems to support reporting, compliance, and operational decision-making. 14. Prepares, interprets, and communicates complex statistical information in writing, verbally and graphically for diverse audiences. 15. Supports data governance initiatives by documenting reporting definitions, identifying data-quality concerns, and working with data owners and subject-matter experts to validate institutional data and promote consistent reporting practices. 16. Handles institutional data in accordance with FERPA and other applicable university policies and regulations. 17. Documents the data definitions, sources, methodologies, validation procedures, and reporting processes used in assigned reports, dashboards, surveys, and data requests. 18. Uses SQL to query, join, transform, and validate data in a relational database environment, preferably PostgreSQL. 19. Combines and validates data from Ellucian Insights/Reporting and Analytics and other institutional data sources to support reporting and analysis. Check duty 9: "Responds to time-critical ad-hoc requests" (no period at end? In original there is a period after? Actually original: "Responds to time-critical ad-hoc requests" then a space then "Facilitates...". It ends with a period? The text: "Responds to time-critical ad-hoc requestsFacilitates..." Actually there is no space? Let's look: In the posting: "Responds to time-critical ad-hoc requestsFacilitates the submission and analysis of national surveys on behalf of the university." There's missing space and period. It seems a typo. We should preserve as is? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep exactly as given, including missing space and period? The original: "Responds to time-critical ad-hoc requestsFacilitates the submission and