Jobs · Information Technology · Minnesota

Value Plus Business IT Sr Analyst

SSAB · St Paul, MN · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. We have POSITION PURPOSE (description). Then Essential Functions (list of duties). Then QUALIFICATIONS (competencies, education, etc). Then SUPERVISORY RESPONSIBILITIES (no supervisory responsibilities). Then WORK ENVIRONMENT AND PHYSICAL DEMANDS (physical demands). Then POSITION TYPE/EXPECTED HOURS OF WORK/TRAVEL REQUIREMENTS (full time, exempt, travel 25%, on call). Then OTHER DUTIES (note). Then About Us, About The Team. We need to map to sections: About the role (maybe position purpose). Responsibilities (essential functions). Requirements (maybe qualifications). Qualifications (maybe education/experience). Skills (maybe competencies). Benefits (none given). Pay (none). Schedule (maybe position type/hours/travel). We should only include sections with real content. We have no explicit Benefits or Pay. So omit those. We have schedule info: full time, exempt, travel 25%, on call availability. That's schedule info. So we can include a Schedule section. We have About Us and About The Team maybe could be under About the role? But we have separate About Us and About The Team. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, but we should use those headings when appropriate. Could also add other headings? Probably stick to those. So we can map About Us and About The Team under About the role? Or we could create separate headings but not in list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; not others. So we should only use those headings. So we need to fit content into those categories. Thus: - About the role: position purpose + maybe About Us and About The Team? Could combine. - Responsibilities: essential functions (list). - Requirements: maybe supervisory responsibilities? Not needed. Could be "Requirements" for things like travel, on-call? But schedule covers that. - Qualifications: education, experience, competencies. - Skills: maybe specific skills like Tableau, Power BI, ERP, etc. - Schedule: position type, travel, on call. We must not repeat job title as heading. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none. We need to output only HTML fragment. Let's extract content. Position Purpose paragraph: "The Business IT Senior Analyst serves as the primary liaison between the Value+ business and IT, ensuring that technology solutions support strategic business objectives, operational excellence, and profitable growth. This position combines expertise in manufacturing business processes, ERP systems, digitalization initiatives, data analytics, and project management to identify, implement, and support solutions that improve productivity, customer experience, profitability, and decision-making throughout the Value+ organization. The Business IT Senior Analyst partners with operations, sales, finance, supply chain, and IT teams to drive continuous improvement, optimize business processes, support system enhancements, and lead technology-related projects. The role also serves as a key resource in reporting, business intelligence, software evaluations, and digital transformation initiatives." Essential Functions: It repeats many bullet-like sentences. We need to put them in
  • . There's duplication: "Business Impact" then list, then "Business Process Leadership Systems and Analytics" repeats similar. We need to preserve all substantive information but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must deduplicate, but we should not omit any. However duplication may be considered redundant but still substantive. Safer to keep as is, but we could combine duplicates? Might be considered summarizing away detail if we remove duplicates. Safer to keep each bullet as appears, even if duplicate. Let's list the essential functions as they appear: Under "Business Impact": - Act as the primary IT and business systems liaison for Value+. - Support business growth initiatives through implementation and enhancement of digital solutions, ERP capabilities, reporting tools, and customer-facing technologies. - Identify opportunities to improve profitability, service levels, throughput, and productivity through technology and process improvements. - Evaluate emerging technologies and recommend solutions that support strategic objectives. - Support system integrations across ERP, CRM, production scheduling, nesting, and financial systems. - Develop a deep understanding of SSAB business processes, policies, and operational workflows. - Analyze current-state processes and recommend future-state improvements. - Facilitate requirements gathering sessions with business stakeholders. - Translate business requirements into functional specifications and system requirements. - Ensure alignment between business objectives and technical solutions. - Lead change management activities associated with new systems and process improvements. Then "Systems and Analytics" repeats many of the same lines: "Develop a deep understanding of SSAB business processes, policies, and operational workflows. Analyze current-state processes and recommend future-state improvements. Facilitate requirements gathering sessions with business stakeholders. Translate business requirements into functional specifications and system requirements. Ensure alignment between business objectives and technical solutions. Lead change management activities associated with new systems and process improvements. Act as subject matter expert for assigned business applications and reporting platforms. Support ERP systems, manufacturing execution systems, production planning tools, and related applications. Champion SSAB’s CPMS process for project management and partner with Project Management Team Develop project plans, timelines, budgets, and resource requirements. Coordinate activities among business stakeholders, IT teams, software vendors, and external partners. Manage software selection and implementation projects, including vendor evaluation and system deployment. Monitor project risks, issues, and mitigation plans. Provide regular project status reports to leadership." Then "Problem Solving and Continuous Improvement Leadership & Teamwork" repeats: "Champion SSAB’s CPMS process for project management and partner with Project Management Team Develop project plans, timelines, budgets, and resource requirements. Coordinate activities among business stakeholders, IT teams, software vendors, and external partners. Manage software selection and implementation projects, including vendor evaluation and system deployment. Monitor project risks, issues, and mitigation plans. Provide regular project status reports to leadership Recommend standardized solutions that balance process efficiency and technology capability. Champion continuous improvement initiatives using data and measurable outcomes. Take ownership of issues through resolution, regardless of organizational boundaries. Build strong working relationships across Operations, Sales, Finance, Supply Chain, and IT. Serve as a trusted advisor to business stakeholders. Mentor users and provide guidance on best practices for utilizing business systems. Support organizational change initiatives and digital transformation efforts. Promote a culture of collaboration, accountability, and continuous improvement. Lead cross-functional project teams without direct supervisory authority." Then "Communication": "Communicate complex technical concepts in a business-focused manner. Develop user documentation, process flows, training materials, and operating procedures. Facilitate workshops, project meetings, and stakeholder reviews. Provide regular updates regarding project status, risks, and business impacts" We need to include all these as list items. Qualifications section: It has "QUALIFICATIONS Competencies and Experience Required: Preferred:" then a list of competencies (oral/written communication, PowerPoint, training, weekly status updates, communicate with non-technical, etc). Then "Education Required: Four-year degree from a college or university 7 years’ experience in a Business Analysis or similar role in steel related businesses Expertise in the business processes and e-commerce solutions. Proven track record of developing and implementing business solutions to drive improvement in ROI in the areas of digitalization, ERP, data visualization Excellent communication skills 15 years of work experience MBA Steel plate and cut-to-length experience Tableau, Power BI, and/or Analytics knowledge Manufacturing experience including nesting software ERP solutions experience Software Selection experience" It seems messy. We need to preserve all substantive information. We'll extract each distinct item. Let's parse: - Strong oral, written and interpersonal communication skills. - Able to make formal presentations to internal or external audiences using PowerPoint (or similar tools) - Able to provide initial user training including user documentation and training materials for business functional software - Responsible for providing their manager with weekly status updates as well as escalate issues when necessary - Able to communicate effectively with non-technical staff, members of interdisciplinary teams, outside customers, and vendors on technical and business topics and issues - Possess well defined business and functional specifications by working closely with management and end users - Possess strong applications knowledge - Education Required: Four-year degree from a college or university - 7 years’ experience in a Business Analysis or similar role in steel related businesses - Expertise in the business processes and e-commerce solutions. - Proven track record of developing and implementing business solutions to drive improvement in ROI in the areas of digitalization, ERP, data visualization - Excellent communication skills - 15 years of work experience - MBA - Steel plate and cut-to-length experience - Tableau, Power BI, and/or Analytics knowledge - Manufacturing experience including nesting software - ERP solutions experience - Software Selection experience Also there is "Competencies and Experience Required: Preferred:" maybe indicates preferred but we treat as required. We also have SUPERVISORY RESPONSIBILITIES: "This position has no supervisory responsibilities." That's substantive; we could put under Requirements? But maybe under Qualifications? Could be a separate section but not in allowed headings. Could put under Requirements as a note. WORK ENVIRONMENT AND PHYSICAL DEMANDS: list of physical demands. Could be under Requirements? Or maybe under Qualifications? But we have no specific heading for that. Could put under Requirements as well. POSITION TYPE/EXPECTED HOURS OF WORK/TRAVEL REQUIREMENTS: "Position is full time, exempt Travel 25% of time in the field and other SSAB locations On call availability for IT and Business Process deployments, critical break/fix issues, and month end processing as required". That's schedule. OTHER DUTIES: note about job description not comprehensive. Could be under Responsibilities? Or maybe under About the role? Might be considered boilerplate? It's not EEO but it's a disclaimer. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is a disclaimer about duties may change; could be considered boilerplate but it's substantive? It's a typical disclaimer. Might be considered boilerplate; but it's not explicitly listed. Safer to keep? The instruction says remove boilerplate; this is a typical disclaimer, could be considered boilerplate. I'd remove it. About Us and About The Team: descriptive paragraphs about SSAB. Could be under About the role. Thus final sections:

    About the role

    Position purpose paragraph + About Us + About The Team paragraphs.

    Responsibilities

    • ... list all essential functions items ...

    Requirements

    Supervisory responsibilities: This position has no supervisory responsibilities.

    Work environment and physical demands: list items.

    Qualifications

    • ... list qualifications items ...

    Skills

    • ... list specific skills like Tableau, Power BI, ERP, etc ...

    Schedule

    Position is full time, exempt. Travel 25% of time in the field and other SSAB locations. On call availability for IT and Business Process deployments, critical break/fix issues, and month end processing as required.

    We must not include Benefits or Pay. Now need to ensure we don't include filler like "commensurate with

Similar jobs

IT Sr. Business Analyst

FlatironDragadosBroomfield, CO· 2 wk ago
Information Technology$130k/yrapply on careers-fdcorp.icims.com

Sr IT Business Analyst

CommonSpirit HealthChicago, IL· 3 wk ago
Information Technology$44.18–$65.71/hrapply on commonspirit.careers

Sr IT Business Analyst

Hypertherm AssociatesKent, WA· 1 mo ago
Information Technology$91k–$152k/yrapply on hypertherm.wd503.myworkdayjobs.com