IT - Software Intelligence Specialist
Hyundai Motor Group Metaplant America (HMGMA) · Illinois, United States · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. No placeholder like "commensurate with experience". We must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also we must not repeat job title as heading. No Job ID/requisition numbers as headings.
We need to parse the job description.
Job title: [Biz Admin] (IT) Software Intelligence (but we ignore as heading). The description includes:
WHAT YOU WILL DO (list of duties)
HOW WILL YOU MAKE AN IMPACT (some description about HMGMA)
WHAT YOU WILL BRING TO THE ROLE (qualifications/requirements)
Competency Based: (list of competencies)
Travel Requirement
Working Hours (Shift) Requirement
WHAT HYUNDAI CAN OFFER YOU (benefits)
OTHER DETAILS (FLSA Classification, Language Proficiency, Physical Demands, etc.)
HMGMA is an equal opportunity employer (EEO boilerplate) -> remove.
We need to decide sections: About the role? Could be the "HOW WILL YOU MAKE AN IMPACT" describing company. Could be "About the role" maybe combine WHAT YOU WILL DO and HOW YOU WILL MAKE AN IMPACT? But we need headings only when there is real specific content. We can have sections: Responsibilities (from WHAT YOU WILL DO), Requirements (maybe combine WHAT YOU WILL BRING TO THE ROLE and Competency Based?), Skills (maybe list specific technical skills), Benefits (WHAT HYUNDAI CAN OFFER YOU), Schedule (Working Hours (Shift) Requirement), Travel (Travel Requirement) maybe could be part of Schedule? But we have a Schedule heading only if posting actually states schedule info. It does: "Working Hours (Shift) Requirement". So we can have Schedule section.
Pay: Not mentioned specifically (just "competitive pay" but no numbers). The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "competitive pay" but no specific numbers; is that considered stating? It says "competitive pay" but not a number or range. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive pay" is vague but maybe considered placeholder? It's not a specific number. Safer to omit Pay section.
Benefits: we have specific benefits listed: competitive Medical / Vision / Dental insurance, paid holidays, paid time off, competitive 401k plan. So we can have Benefits section.
Schedule: we have shift assignment may change, etc. That's specific enough.
Travel: we have Domestic / International travel required. Could be its own section or part of Schedule? There's no Travel heading in the list of allowed headings; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Travel is not in allowed headings. So we must fold travel info into another section, maybe Responsibilities or Requirements? Probably under Requirements (as a requirement). Or we could put under "About the role"? Better to put under Requirements as a requirement.
Qualifications vs Requirements vs Skills: The allowed headings include Requirements, Qualifications, Skills. We need to decide which to use. We have qualifications: Bachelor’s degree or higher (Master’s preferred) in computer science, IT, or equivalent experience. Experience in Manufacturing (EV Manufacturing highly preferred). Programming experience with Python, Java, ETL, ELK stack and/or k8s. Experience with ELK stack highly preferred. Experience with writing SQL-based applications such as MySQL, Maria DB or Oracle DB. Experience creating data products and dashboards in Grafana or Prometheus. Excellent communication skills, both verbal and written. Ability to work independently on multiple projects with complex requirements. Competency Based: list of competencies (Working With a Team, Planning and Organizing, Problem Solving, Communication, Strategic thinking and mindset, Willingness for transformational changes, Flexibility). Travel Requirement. Working Hours (Shift) Requirement.
We could have a Requirements section for the degree, experience, programming, etc. Skills section for technical skills like SQL/Python, etc. Qualifications maybe for degree? But we have overlapping.
Better to have: Requirements (education, experience, travel, shift), Skills (technical skills: Python, Java, ETL, ELK, k8s, SQL, MySQL/MariaDB/Oracle, Grafana/Prometheus, RPA, Airflow, SQL/Python code, etc.), Qualifications maybe not needed if we cover in Requirements. But we need to avoid thin sections. Perhaps combine education and experience into Requirements, and technical skills into Skills, and competencies into Requirements or a separate section? There's no "Competencies" heading allowed. Could fold into Requirements or Skills. Probably include under Requirements as "Core competencies".
Let's plan sections:
- Responsibilities (
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. No placeholder like "commensurate with experience". We must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also we must not repeat job title as heading. No Job ID/requisition numbers as headings.
We need to parse the job description.
Job title: [Biz Admin] (IT) Software Intelligence (but we ignore as heading). The description includes:
WHAT YOU WILL DO (list of duties)
HOW WILL YOU MAKE AN IMPACT (some description about HMGMA)
WHAT YOU WILL BRING TO THE ROLE (qualifications/requirements)
Competency Based: (list of competencies)
Travel Requirement
Working Hours (Shift) Requirement
WHAT HYUNDAI CAN OFFER YOU (benefits)
OTHER DETAILS (FLSA Classification, Language Proficiency, Physical Demands, etc.)
HMGMA is an equal opportunity employer (EEO boilerplate) -> remove.
We need to decide sections: About the role? Could be the "HOW WILL YOU MAKE AN IMPACT" describing company. Could be "About the role" maybe combine WHAT YOU WILL DO and HOW YOU WILL MAKE AN IMPACT? But we need headings only when there is real specific content. We can have sections: Responsibilities (from WHAT YOU WILL DO), Requirements (maybe combine WHAT YOU WILL BRING TO THE ROLE and Competency Based?), Skills (maybe list specific technical skills), Benefits (WHAT HYUNDAI CAN OFFER YOU), Schedule (Working Hours (Shift) Requirement), Travel (Travel Requirement) maybe could be part of Schedule? But we have a Schedule heading only if posting actually states schedule info. It does: "Working Hours (Shift) Requirement". So we can have Schedule section.
Pay: Not mentioned specifically (just "competitive pay" but no numbers). The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "competitive pay" but no specific numbers; is that considered stating? It says "competitive pay" but not a number or range. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive pay" is vague but maybe considered placeholder? It's not a specific number. Safer to omit Pay section.
Benefits: we have specific benefits listed: competitive Medical / Vision / Dental insurance, paid holidays, paid time off, competitive 401k plan. So we can have Benefits section.
Schedule: we have shift assignment may change, etc. That's specific enough.
Travel: we have Domestic / International travel required. Could be its own section or part of Schedule? There's no Travel heading in the list of allowed headings; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Travel is not in allowed headings. So we must fold travel info into another section, maybe Responsibilities or Requirements? Probably under Requirements (as a requirement). Or we could put under "About the role"? Better to put under Requirements as a requirement.
Qualifications vs Requirements vs Skills: The allowed headings include Requirements, Qualifications, Skills. We need to decide which to use. We have qualifications: Bachelor’s degree or higher (Master’s preferred) in computer science, IT, or equivalent experience. Experience in Manufacturing (EV Manufacturing highly preferred). Programming experience with Python, Java, ETL, ELK stack and/or k8s. Experience with ELK stack highly preferred. Experience with writing SQL-based applications such as MySQL, Maria DB or Oracle DB. Experience creating data products and dashboards in Grafana or Prometheus. Excellent communication skills, both verbal and written. Ability to work independently on multiple projects with complex requirements. Competency Based: list of competencies (Working With a Team, Planning and Organizing, Problem Solving, Communication, Strategic thinking and mindset, Willingness for transformational changes, Flexibility). Travel Requirement. Working Hours (Shift) Requirement.
We could have a Requirements section for the degree, experience, programming, etc. Skills section for technical skills like SQL/Python, etc. Qualifications maybe for degree? But we have overlapping.
Better to have: Requirements (education, experience, travel, shift), Skills (technical skills: Python, Java, ETL, ELK, k8s, SQL, MySQL/MariaDB/Oracle, Grafana/Prometheus, RPA, Airflow, SQL/Python code, etc.), Qualifications maybe not needed if we cover in Requirements. But we need to avoid thin sections. Perhaps combine education and experience into Requirements, and technical skills into Skills, and competencies into Requirements or a separate section? There's no "Competencies" heading allowed. Could fold into Requirements or Skills. Probably include under Requirements as "Core competencies".
Let's plan sections:
- Responsibilities (Responsibilities
) with - items from WHAT YOU WILL DO.
- About the role (
About the role
) with paragraph from HOW WILL YOU MAKE AN IMPACT (description of HMGMA). Could also include other descriptive paragraphs like "WHAT YOU WILL MAKE AN IMPACT". That's about company.
- Requirements (Requirements
) with education, experience (manufacturing, EV preferred), ability to work independently, communication, travel requirement, shift requirement, core competencies (list). Could also include language proficiency? That's in OTHER DETAILS: Language Proficiency: Strong command of English. Could be part of Requirements.
- Skills (Skills
) with technical skills: Python, Java, ETL, ELK stack, k8s, SQL (MySQL, MariaDB, Oracle), Grafana/Prometheus, RPA, Airflow, SQL/Python code, data pipelines, etc.
- Benefits (Benefits
) with list: competitive Medical/Vision/Dental insurance, paid holidays, paid time off, competitive 401k plan.
- Schedule (Schedule
) with paragraph about shift assignment may change, etc.
We must not include Pay.
We must remove boilerplate: EEO statement, FLSA Classification? That's in OTHER DETAILS: FLSA Classification: Exempt/Salary. That's not boilerplate? It's metadata but maybe minor; we could fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So FLSA Classification is minor metadata; we can include in a short p maybe under Requirements or OTHER DETAILS? But we already have sections; we could add a short p after sections? Better to drop it as minor metadata. Similarly Language Proficiency could be part of Requirements. Physical Demands could be part of Requirements? It's not minor but could be included under Requirements as a bullet? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep Physical Demands info. Where to put? Could be under Requirements as a bullet list. Or we could create a separate section? Not allowed headings besides those. So we must fold into existing sections. Probably under Requirements as "Physical demands". Or we could add a
after sections for minor metadata? The instruction says fold minor metadata into a short
or drop it. Physical Demands is not minor; it's substantive. So we need to include it somewhere.
We could add a section "Requirements" that includes education, experience, travel, shift, language proficiency, physical demands, competencies.
We need to ensure we don't create headings with filler text. All headings we propose have substantive content.
Now produce HTML fragment.
Structure:
Responsibilities
- ...
About the role
...
Requirements
- ...
maybe also include paragraphs for paragraphs like language proficiency, physical demands.
But we can also use for prose and
- for lists.
We need to preserve all substantive information: let's extract each piece.
Responsibilities (WHAT YOU WILL DO):
- Identify, analyze, and interpret manufacturing data with patterns in complex data sets and provide KPI via dashboards and reports.
- Provide and integrated crucial connections between IT and OT systems, enabling analysis of interrelations and providing a dashboard that showcases selected KPIs to production team and users.
- Develop Robotic Process Automation (RPA) to rapidly configure and update production needs.
- Designing tests and analyzing manufacturing data to improve manufacturing productivity and quality.
- Write efficient SQL/Python code and complex queries across extensive data sets.
- Work effectively with engineers and conduct end-to-end analysis, from data requirement gathering, to data processing and modeling.
- Automate analysis processes and construct pipelines using SQL, Python, and Airflow.
Note: some grammar issues but we keep as is.
About the role (HOW WILL YOU MAKE AN IMPACT):
- HMGMA is the abbreviation of Hyundai Motor Group Metaplant America. It is Hyundai Motor Group's first dedicated EV mass-production plant and is an innovative plant with cutting-edge production technology applied.
We could make a paragraph.
Requirements:
- Bachelor’s degree or higher (Master’s degree preferred) in computer science, IT, or equivalent experience.
- Experience in Manufacturing (EV Manufacturing highly preferred)
- Programming experience with Python, Java, ETL, ELK stack and/or k8s
- Experience with ELK stack highly preferred.
- Experience with writing SQL-based applications such as MySQL, Maria DB or Oracle DB
- Experience creating data products and dashboards in Grafana or Prometheus
- Excellent communication skills, both verbal and written
- Ability to work independently on multiple projects with complex requirements.
- Competency Based: Working With a Team, Planning and Organizing, Problem Solving, Communication, Strategic thinking and mindset, Willingness for transformational changes, Flexibility
- Travel Requirement: Domestic / International travel required.
- Working Hours (Shift) Requirement: Employment opportunities at HMGMA will be completed in multiple phases. Shift assignment for this position may change to meet the business needs. Any changes will be communicated to employees and according to accommodation; will be considered.
- Language Proficiency: Strong command of the English language (written and spoken) is essential for safety, communication, documentation, and collaboration across the organization.
- Physical Demands While in Office: This position is primarily sedentary and requires working at a desk and computer for extended periods. Responsibilities may include: • Occasional lifting of office supplies (up to 15 pounds) • Frequent use of hands and fingers for typing and handling documents • Ability to sit, stand, and walk within the office environment as needed
When in Production Area (if applicable): • Standing, walking, bending, and reaching for extended durations • Repeated lifting, carrying, pushing, or pulling of materials and products (up to 25–30 pounds) • Manual dexterity for handling power tools, machinery, or production equipment • Working in environments that may be noisy, hot, or require the use of personal protective equipment (PPE) • Ability to climb ladders or stairs and operate equipment safely and effectively • Capability to learn and work on multiple production processes, as required • Adequate visual and auditory abilities to identify safety hazards and communicate clearly • Consistent and punctual attendance • Ability to collaborate and perform effectively in a team-oriented environment
We need to preserve bullet points exactly? We can convert to
- .
Skills:
From responsibilities and requirements we have technical skills: SQL/Python code, RPA, Airflow, Python, Java, ETL, ELK stack, k8s, MySQL/MariaDB/Oracle
About the role
) with paragraph from HOW WILL YOU MAKE AN IMPACT (description of HMGMA). Could also include other descriptive paragraphs like "WHAT YOU WILL MAKE AN IMPACT". That's about company. - Requirements (Requirements
) with education, experience (manufacturing, EV preferred), ability to work independently, communication, travel requirement, shift requirement, core competencies (list). Could also include language proficiency? That's in OTHER DETAILS: Language Proficiency: Strong command of English. Could be part of Requirements. - Skills (Skills
) with technical skills: Python, Java, ETL, ELK stack, k8s, SQL (MySQL, MariaDB, Oracle), Grafana/Prometheus, RPA, Airflow, SQL/Python code, data pipelines, etc. - Benefits (Benefits
) with list: competitive Medical/Vision/Dental insurance, paid holidays, paid time off, competitive 401k plan. - Schedule (Schedule
) with paragraph about shift assignment may change, etc. We must not include Pay. We must remove boilerplate: EEO statement, FLSA Classification? That's in OTHER DETAILS: FLSA Classification: Exempt/Salary. That's not boilerplate? It's metadata but maybe minor; we could fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So FLSA Classification is minor metadata; we can include in a short p maybe under Requirements or OTHER DETAILS? But we already have sections; we could add a short p after sections? Better to drop it as minor metadata. Similarly Language Proficiency could be part of Requirements. Physical Demands could be part of Requirements? It's not minor but could be included under Requirements as a bullet? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep Physical Demands info. Where to put? Could be under Requirements as a bullet list. Or we could create a separate section? Not allowed headings besides those. So we must fold into existing sections. Probably under Requirements as "Physical demands". Or we could add a
after sections for minor metadata? The instruction says fold minor metadata into a short
or drop it. Physical Demands is not minor; it's substantive. So we need to include it somewhere. We could add a section "Requirements" that includes education, experience, travel, shift, language proficiency, physical demands, competencies. We need to ensure we don't create headings with filler text. All headings we propose have substantive content. Now produce HTML fragment. Structure:
Responsibilities
- ...
About the role
...
Requirements
- ...
for prose and
- for lists.
We need to preserve all substantive information: let's extract each piece.
Responsibilities (WHAT YOU WILL DO):
- Identify, analyze, and interpret manufacturing data with patterns in complex data sets and provide KPI via dashboards and reports.
- Provide and integrated crucial connections between IT and OT systems, enabling analysis of interrelations and providing a dashboard that showcases selected KPIs to production team and users.
- Develop Robotic Process Automation (RPA) to rapidly configure and update production needs.
- Designing tests and analyzing manufacturing data to improve manufacturing productivity and quality.
- Write efficient SQL/Python code and complex queries across extensive data sets.
- Work effectively with engineers and conduct end-to-end analysis, from data requirement gathering, to data processing and modeling.
- Automate analysis processes and construct pipelines using SQL, Python, and Airflow.
Note: some grammar issues but we keep as is.
About the role (HOW WILL YOU MAKE AN IMPACT):
- HMGMA is the abbreviation of Hyundai Motor Group Metaplant America. It is Hyundai Motor Group's first dedicated EV mass-production plant and is an innovative plant with cutting-edge production technology applied.
We could make a paragraph.
Requirements:
- Bachelor’s degree or higher (Master’s degree preferred) in computer science, IT, or equivalent experience.
- Experience in Manufacturing (EV Manufacturing highly preferred)
- Programming experience with Python, Java, ETL, ELK stack and/or k8s
- Experience with ELK stack highly preferred.
- Experience with writing SQL-based applications such as MySQL, Maria DB or Oracle DB
- Experience creating data products and dashboards in Grafana or Prometheus
- Excellent communication skills, both verbal and written
- Ability to work independently on multiple projects with complex requirements.
- Competency Based: Working With a Team, Planning and Organizing, Problem Solving, Communication, Strategic thinking and mindset, Willingness for transformational changes, Flexibility
- Travel Requirement: Domestic / International travel required.
- Working Hours (Shift) Requirement: Employment opportunities at HMGMA will be completed in multiple phases. Shift assignment for this position may change to meet the business needs. Any changes will be communicated to employees and according to accommodation; will be considered.
- Language Proficiency: Strong command of the English language (written and spoken) is essential for safety, communication, documentation, and collaboration across the organization.
- Physical Demands While in Office: This position is primarily sedentary and requires working at a desk and computer for extended periods. Responsibilities may include: • Occasional lifting of office supplies (up to 15 pounds) • Frequent use of hands and fingers for typing and handling documents • Ability to sit, stand, and walk within the office environment as needed
When in Production Area (if applicable): • Standing, walking, bending, and reaching for extended durations • Repeated lifting, carrying, pushing, or pulling of materials and products (up to 25–30 pounds) • Manual dexterity for handling power tools, machinery, or production equipment • Working in environments that may be noisy, hot, or require the use of personal protective equipment (PPE) • Ability to climb ladders or stairs and operate equipment safely and effectively • Capability to learn and work on multiple production processes, as required • Adequate visual and auditory abilities to identify safety hazards and communicate clearly • Consistent and punctual attendance • Ability to collaborate and perform effectively in a team-oriented environment
We need to preserve bullet points exactly? We can convert to
- . Skills: From responsibilities and requirements we have technical skills: SQL/Python code, RPA, Airflow, Python, Java, ETL, ELK stack, k8s, MySQL/MariaDB/Oracle