Jobs · Information Technology · Michigan

Systems Administrator

Continental · Sterling Heights, MI · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role? The description includes "A Taste of Who We Are", "Our Mission", "Our Core Values", "The Experience You’ll Create". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings where appropriate. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). There's no explicit boilerplate besides maybe "Savor The Benefits". We'll include Benefits section. We need sections only when posting has real specific content. So we can have: - About the role (maybe combine "A Taste of Who We Are", "Our Mission", "Our Core Values", "The Experience You’ll Create") - Responsibilities (Key Responsibilities, Essential Duties by Focus Area) - Requirements (maybe "Ingredients For Thriving Required Qualifications:" and "Preferred Qualifications") - Skills (maybe "Core Competencies") - Benefits (Savor The Benefits) - Working Conditions maybe not a standard heading; but we could include under About the role or separate? The instruction list includes only those headings; we should not create extra headings like Working Conditions unless content matches one of those. Could embed Working Conditions in About the role or Responsibilities? Probably better to include as a paragraph under About the role or maybe under Responsibilities? But we should not invent headings. So we can include Working Conditions as a

inside About the role or maybe under Responsibilities? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to those, but we should prefer those. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add a section for Working Conditions if we want, but it's not in the list; but we could still use

for Working Conditions if we think it's appropriate. However they gave examples; not strict. Safer to stick to given headings. Thus we can put Working Conditions content under About the role or Responsibilities as a paragraph. We need to preserve all substantive info. Let's extract. About the role: "A Taste of Who We Are: Backed by a tireless commitment to high quality, innovative culinary offerings and unparalleled client and guest services, Continental consistently ranks among the top contract dining and refreshment providers in the nation according to Food Management Magazine, the industry’s source for food service news and trends. Our Mission Delight our guest. Every meal. Every day. Our Core Values Exceptional – We recruit and retain phenomenal people who consistently go the extra mile to deliver results that lead the industry. Hospitality – We are tirelessly committed to providing the highest quality food, beverages, and service by anticipating our guests' needs so they can count on memorable experiences every time. Collaboration – We prioritize working together with a shared vision and effective & transparent communication, we unite as one team to achieve remarkable experiences. Responsibility – we hold ourselves accountable to be there for our team and clients, to deliver what we say we will, when we say we will and check in on progress along the way. Innovation – We are forward-thinkers always looking for new processes, technologies, and techniques to increase efficiencies and scalability to improve our services. The Experience You’ll Create The Systems Administrator supports the reliable, accurate, and efficient operation of Refreshment Services Group business systems. This role maintains customer, location, asset, route, item, and reference data; completes system configuration and administrative activities; supports operational changes; and helps resolve user and data issues. The position works closely with Operations, Merchandising, Finance, Accounting, IT, and systems leadership to ensure business changes are reflected accurately and consistently across supported platforms." We can combine into a few paragraphs. Responsibilities: list of Key Responsibilities bullet points and Essential Duties by Focus Area (which is more detailed). We'll combine into a
  • list. Requirements: Required Qualifications and Preferred Qualifications. Skills: Core Competencies. Benefits: list from "Savor The Benefits". We must not include Pay or Schedule as they are not present. We must not include duplicated lines. Let's craft HTML. We'll start with

    About the role

    then paragraphs. Then

    Responsibilities

    then
      with items. Then

      Requirements

      then maybe split into Required and Preferred? Could keep as paragraphs. Then

      Skills

      then
        for Core Competencies. Then

        Benefits

        then
          . Make sure to preserve all details. Let's extract bullet points. Key Responsibilities (as listed): - Maintain customer and delivery location records, including new setups, changes, and ongoing data quality review. - Create and maintain assets, machines, markets, routes, schedules, and related system mappings. - Enter and maintain planograms, store configurations, custom fields, attributes, and controlled reference data. - Process vending and market installations, removals, transfers, and other operational changes in supported systems. - Complete approved route, schedule, and service changes and validate that downstream records remain aligned. - Support item and product maintenance, imports, and data cleanup activities in coordination with the appropriate business owners. - Produce or support operational system outputs, including pre-pick information, reports, and administrative files, as assigned - Investigate system, data, and workflow issues; document findings; resolve routine issues; and escalate complex problem. - Perform quality checks to identify incomplete, duplicate, inconsistent, or inaccurate master data. - Participate in acquisition onboarding, system integrations, process standardization, and special projects as needed. - Maintain clear procedures, trackers, and documentation for recurring system administration processes. Essential Duties by Focus Area (maybe redundant but we can include as separate bullet points? It repeats similar content but more grouped. To avoid duplication, we could merge but instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we merge we might lose some nuance. However the Essential Duties by Focus Area repeats many of the same points but grouped. Could we keep both sections? That would duplicate content. The instruction says remove duplicated lines. So we should deduplicate. The Essential Duties by Focus Area includes: Master Data Administration - Customer and location creation and maintenance - Asset, machine, market, and route record maintenance - Item, product, hierarchy, attribute, and reference-data support - Routine data validation, correction, and cleanup Operational Systems Support - Install, removal, route, schedule, and configuration updates - Planogram and store configuration administration - Operational imports, reports, and assigned administrative processing - Cross-functional issue triage and user support - Support testing, system upgrades, integrations, and acquisition activities These are largely covered in Key Responsibilities but some phrasing differs. To preserve all substantive info, we could keep both but ensure not exact duplicate lines. However many are similar but not identical. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines means exact duplicates? Likely they mean if same sentence appears twice, remove one. The Essential Duties by Focus Area is not exact duplicate but similar. Might be considered duplicated content? Safer to keep both but maybe combine into a single list that captures all unique points. Let's try to combine unique points: From Key Responsibilities we have: 1. Maintain customer and delivery location records, including new setups, changes, and ongoing data quality review. 2. Create and maintain assets, machines, markets, routes, schedules, and related system mappings. 3. Enter and maintain planograms, store configurations, custom fields, attributes, and controlled reference data. 4. Process vending and market installations, removals, transfers, and other operational changes in supported systems. 5. Complete approved route, schedule, and service changes and validate that downstream records remain aligned. 6. Support item and product maintenance, imports, and data cleanup activities in coordination with the appropriate business owners. 7. Produce or support operational system outputs, including pre-pick information, reports, and administrative files, as assigned. 8. Investigate system, data, and workflow issues; document findings; resolve routine issues; and escalate complex problem. 9. Perform quality checks to identify incomplete, duplicate, inconsistent, or inaccurate master data. 10. Participate in acquisition onboarding, system integrations, process standardization, and special projects as needed. 11. Maintain clear procedures, trackers, and documentation for recurring system administration processes. From Essential Duties by Focus Area we have additional nuance: - Master Data Administration: Customer and location creation and maintenance (same as #1) - Asset, machine, market, and route record maintenance (same as #2) - Item, product, hierarchy, attribute, and reference-data support (similar to #3 and #6) - Routine data validation, correction, and cleanup (similar to #9) - Operational Systems Support: Install, removal, route, schedule, and configuration updates (similar to #2, #4, #5) - Planogram and store configuration administration (similar to #3) - Operational imports, reports, and assigned administrative processing (similar to #6, #7) - Cross-functional issue triage and user support (similar to #8) - Support testing, system upgrades, integrations, and acquisition activities (similar to #10) Thus the Essential Duties doesn't add new substantive info beyond what's already covered. So we can omit to avoid duplication. Good. Now Requirements: Required Qualifications: - High school diploma or equivalent required; associate or bachelor’s degree in business, information systems, operations, or a related field preferred. - Two or more years of experience in system administration, master data, business applications, operations support, data entry, or a related function preferred. - Experience maintaining detailed records in an ERP, point-of-sale, field-service, routing, CRM, or similar business system. - Intermediate Microsoft Excel skills, including filtering, lookups, sorting, validation, and reconciliation of data. - Ability to manage recurring work and project-based assignments while meeting deadlines and maintaining accuracy. - Strong written communication, documentation, organization, and problem-solving skills. Preferred Qualifications: - Experience supporting vending, micro-market, office coffee, distribution, warehouse, route, or field-service operations. - Experience with Seed or comparable vending and route-management platforms. - Experience working across Operations, Merchandising, Finance, Accounting, and IT teams. Skills (Core Competencies): - Accuracy and Data Integrity: Completes detailed work consistently and validates changes before closing requests. - Customer Service: Responds professionally, communicates status clearly, and helps users reach practical resolutions. - Ownership: Takes responsibility for assigned processes, follows through, and escalates risks promptly. - Problem Solving: Investigates root causes, distinguishes data issues from system issues, and documents findings. - Process Discipline: Follows standards, approvals, and controls while looking for opportunities to simplify work. - Collaboration: Works effectively across regions and functions with competing priorities. Benefits: - Health Coverage – Medical, Dental and Vision - Voluntary Life/AD&D, Short-Term and Long-Term Disability, Critical Illness, Parental Leave - 401(k) with company match - Paid Time Off - Paid Parental Leave - Wellness Programs - Referral bonus - Additional Perks (link to benefits page) We should include the link as maybe a inside the Benefits list? The instruction: preserve ALL substantive information; we can include the link as part of the Benefits section. Could be a
        • with a link. Working Conditions: "This position performs computer-based work for extended periods and may occasionally support time-sensitive operational changes outside standard business hours. Limited travel between company locations may be required based on business needs. Reasonable accommod

Similar jobs

Systems Administrator

Zachary Piper SolutionsRome, NY· 3 mo ago
Information Technology$70k–$85k/yrapply on careers.zacharypiper.com

Systems Administrator

Yampa Valley Electric AssociationSteamboat Springs, CO· 2 mo ago
Information Technology$120k/yrapply on yvea.applicantpro.com

Systems Administrator

Digital Monitoring ProductsSpringfield, MO· 4 mo ago
Information Technologyapply on secure6.saashr.com

Systems Administrator

SIMCO, LLCCarlsbad, NM· 4 mo ago
Information Technology$75k–$131k/yrapply on career-hcm03.ns2cloud.com

Systems Administrator

Aquila TechnologyLexington, MA· 3 mo ago
Information Technologyapply on aquila.technology

Systems Administrator

AVAnnapolis Junction, MD· 2 mo ago
Information Technology$150k–$175k/yrapply on avav.wd1.myworkdayjobs.com