NetSuite Implementation Specialist

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 have Pay: $67–$89/hour, based on experience. So we need a Pay section. Schedule? Not mentioned. Benefits: we have Kelly benefits description; but we need to remove boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Benefits section: The posting includes benefits description from Kelly. It's not boilerplate? It's about benefits. We can include Benefits section with that content, but we need to avoid generic filler like "commensurate with experience". The benefits description is specific: medical, dental, vision, telemedicine, term life, whole life, accident insurance, critical illness, legal plan, short-term disability, retirement savings plan, service bonus and holiday pay plans (earn up to eight paid holidays per benefit year), transit spending account, paid sick leave under applicable state or local plan. That's specific enough. So include Benefits. We also have About The Opportunity and The Role sections. Those could map to About the role (or About The Opportunity) and Responsibilities. The posting includes "About The Opportunity" paragraph, then "The Role" paragraph, then "Key Responsibilities" list. Then "What We're Looking For" (Required Experience) etc. Then "What Success Looks Like", "Ideal Candidate". Then benefits. We need to decide sections: About the role (maybe combine About The Opportunity and The Role). Responsibilities (Key Responsibilities). Requirements/Qualifications/Skills: we have "What We're Looking For" which includes required experience, etc. Could split into Requirements and Skills. But we should prefer few substantive sections over many thin ones. Could combine Requirements and Skills into one section maybe "Requirements". But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have Pay section. Benefits section. About the role section (we have About The Opportunity and The Role). Responsibilities section (Key Responsibilities). Requirements/Qualifications/Skills: we have "What We're Looking For" which includes required experience, etc. Could be Requirements. Could also include Qualifications/Skills but maybe combine. We must not repeat job title as heading. No Job ID. We must output only HTML fragment, no /. Use

for headings,

• for lists,

  for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, except boilerplate etc. We need to include the location: "Contract | 4–5+ Months | Remote | Seeking individuals based in the Eastern Zone". That's metadata; we can fold into a short

  maybe under About the role or at top. Since we cannot have Job ID/requisition numbers as headings, we can put that metadata in a

  . We need to include Pay: $67–$89/hour, based on experience. So Pay section with that. We need to include Benefits: the Kelly benefits description. We'll include that as a

  • list. We need to include About the role: combine About The Opportunity and The Role paragraphs. We need to include Responsibilities: the list under Key Responsibilities. We need to include Requirements/Qualifications/Skills: the "What We're Looking For" paragraph(s) plus maybe "What Success Looks Like" and "Ideal Candidate". Those are also substantive. Could be part of Requirements or separate sections. But we should avoid many thin sections. Perhaps we can have one section "Requirements" that includes all those paragraphs (What We're Looking For, What Success Looks Like, Ideal Candidate). But we need to preserve all detail; we can just put them as

    inside that section. We must not include boilerplate like EEO etc. At the end there is a lot of Kelly EEO etc. We must remove that. Also remove "Click here for more information on benefits and perks..." etc. That's part of benefits but maybe considered boilerplate? It's a link; we can keep but it's not substantive detail? Might be considered navigation. Safer to remove that line. Also remove "Get a complete career fit with Kelly®..." etc. That's marketing boilerplate. Remove. Also remove "About Kelly Work changes everything..." etc. That's boilerplate. Remove. Also remove "Requests for accommodation..." etc. That's legal boilerplate. Remove. Also remove "Kelly participates in E-Verify..." etc. Remove. Also remove "Kelly may use AI-powered tools..." etc. Remove. Thus we keep only the core job description. Now construct HTML. Start with a

    for metadata: "Contract | 4–5+ Months | Remote | Seeking individuals based in the Eastern Zone Pay: $67–$89/hour, based on experience". Actually Pay is separate section; we could still include Pay in metadata but better to have Pay section. So metadata could be just "Contract | 4–5+ Months | Remote | Seeking individuals based in the Eastern Zone". Then Pay section separate. Thus:

    Contract | 4–5+ Months | Remote | Seeking individuals based in the Eastern Zone

    Then

    About the role

    with paragraphs: combine About The Opportunity and The Role. About The Opportunity paragraph: "Seeking a NetSuite Implementation Specialist to support a large multi-entity environment spanning the U.S. and Europe, including the UK and France. The organization currently operates across a number of segmented entities and systems, with different parts of the business following different processes. NetSuite is intended to become the organization's core global financial and transactional platform. Approximately 50% of the implementation work has already been completed, including the overall design and implementation roadmap. We are now looking for a hands-on NetSuite Implementation Specialist to join the team and help drive the project through execution and completion. This is an opportunity for someone who can operate beyond a traditional technical implementation role — someone who understands finance, accounting, financial processes, and complex business requirements, and can translate those requirements directly into NetSuite configuration." The Role paragraph: "The NetSuite Implementation Specialist will work closely with finance and application teams to onboard additional entities into NetSuite and make them fully transactional within the platform. The ideal candidate will be comfortable working independently in a complex environment with multiple entities, systems, integrations, and stakeholders. You will be expected to not only execute the remaining implementation work, but also assess what needs to happen next as the organization transitions into a more sustainable operational model." We can put both as

    inside the section. Then

    Responsibilities

    with
    • list of each responsibility. List items: - Configure and implement multi-entity financials, consolidation, and intercompany workflows - Configure Advanced Inventory, item architecture, costing, and inventory valuation - Configure manufacturing and distribution processes, including: - Bills of Materials (BOMs) - Routings - WIP - MRP - Fulfillment - Build and configure NetSuite workflows, saved searches, roles, permissions, reports, and controls - Map, test, and troubleshoot integrations with systems such as Coupa, MS Dynamics, AS400/Navision, WMS, and other business applications - Support defect resolution, UAT, reconciliation, and cutover activities - Work closely with finance teams to understand accounting requirements, financial models, and business processes - Translate ambiguous business requirements into practical NetSuite solutions - Help bring additional U.S. and European entities into NetSuite - Identify gaps, dependencies, and next steps as the implementation progresses - Provide hands-on configuration and implementation support rather than relying primarily on external consulting resources - Help establish a sustainable model for ongoing NetSuite support and future implementation needs Note: The sublist for manufacturing and distribution processes could be nested
      . We'll keep as
      • with internal
        . Then

        Requirements

        (or maybe Requirements and Skills combined). We'll put all the "What We're Looking For", "What Success Looks Like", "Ideal Candidate" as paragraphs. What We're Looking For paragraph: "Required Experience Significant hands-on experience as a NetSuite Implementation Specialist/ConsultantProven experience delivering complex NetSuite implementationsExperience working with multiple entities, ideally within a large or global organizationExperience supporting international/European entities is highly preferredStrong understanding of financial processes and accounting terminologyAbility to speak comfortably with finance stakeholders and understand:Financial modelsAccounting processesBalance sheetsIntercompany transactionsConsolidationFinancial requirements and controlsStrong hands-on NetSuite configuration experienceExperience with companies that sell, manufacture, distribute, or otherwise manage physical products and inventoryExperience with complex integrations and multiple connected business systemsAbility to work through ambiguity, identify requirements, and determine practical solutionsComfortable operating in an environment where the implementation is already underway and approximately 50% complete" We need to keep the content but it's currently missing spaces. We'll preserve as is but maybe add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces is not changing meaning, just formatting. It's okay. Then What Success Looks Like paragraph: "The primary objective is to complete the NetSuite implementation and bring the remaining entities into the platform so they can become fully transactional as quickly as possible. The successful consultant will also help the organization understand what needs to happen next — both from an implementation perspective and in terms of supporting NetSuite once the current project is complete. This is a hands-on role. We are specifically looking for an experienced individual who can jump into the existing implementation, understand the work that has already been completed, communicate effectively with finance and technical teams, and execute the remaining configuration and implementation work." Then Ideal Candidate paragraph: "The ideal candidate is a seasoned NetSuite implementation professional who has worked in large, complex organizations with multiple entities and physical products. They can sit down with a finance leader, understand the accounting and business process behind the requirement, and then turn that understanding into hands-on NetSuite configuration. Someone who has successfully implemented NetSuite across a complex multi-entity organization — particularly one involving inventory, manufacturing, distribution, and international operations — would be an excellent fit." We could also include the Kelly benefits paragraph but we will put in Benefits section. Now Benefits section:

        Benefits

        with
        • list of benefits. List: - Medical - Dental - Vision - Telemedicine - Term life - Whole life - Accident insurance - Critical illness - Legal plan - Short-term disability - Retirement savings plan - Service bonus and holiday pay plans (earn up to eight paid holidays per benefit year) - Transit spending account - Paid sick leave under the applicable state or local plan We should preserve the description exactly as posted: "Kelly offers eligible employees voluntary benefit plans including medical, dental, vision, telemedicine, term life, whole life, accident insurance, critical illness, a legal plan, and short-term disability. As a Kelly employee, you will have access to a retirement savings plan, service bonus and holiday pay plans (earn up to eight paid holidays per benefit year), and a transit spending account. In addition, employees are entitled to earn paid sick leave under the applicable state or local plan." We could keep as

          or

          . Since it's a list, we can use
          • . We'll break into items. Now Pay section:

            Pay

            with

            $67–$89/hour, based on experience

            We should not include Schedule section because not specified. Now ensure we didn't include any boilerplate. We removed the Kelly marketing and legal bits. Now produce HTML fragment. Let's craft:

            Contract | 4–5+ Months | Remote | Seeking individuals based in the Eastern Zone

            About the role