Netsuite Business Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. The posting includes description of role, responsibilities, qualifications, preferred qualifications, etc. No explicit Benefits, Pay, Schedule. So we should not include those sections. We need headings:

for each section. Use

• for lists. Use

  for prose. We need to preserve all substantive info, remove boilerplate (EEO etc). Also remove duplicated lines. We need to include About the role (intro paragraph). Responsibilities (list of duties). Requirements (maybe qualifications). Qualifications (maybe required qualifications). Skills (maybe list of skills). The posting includes "Your qualifications, your influence:" with required qualifications bullet list. Also "Preferred qualifications:" list. Also earlier description of role includes responsibilities. We need to decide sections: About the role (intro paragraph about company and role). Responsibilities (list of duties). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications? Or we could combine required and preferred under Qualifications? But spec says separate sections: Requirements, Qualifications, Skills. We could put required qualifications under Requirements, preferred under Qualifications, and skills under Skills (maybe list of skills like stakeholder management, communication, etc). However the posting includes many skill items within qualifications. We could treat "Skills" as list of skills like stakeholder management, communication, etc. But we need to avoid duplication. Better: About the role: intro paragraph about Sourceability and role. Responsibilities: list of duties from "As the NetSuite Business Analyst, you will..." and "Insight on your impact:" etc. Requirements: required qualifications (Bachelor's degree, 3-5 years experience, etc). Qualifications: preferred qualifications (Experience with NetSuite lot tracking, etc). Skills: maybe list of skills like "Strong working knowledge of finance...", "Proven business analysis skills...", "Advanced proficiency with NetSuite saved searches...", "Testing and release discipline:", "Basic to intermediate SQL...", "Excellent stakeholder management...", "Ability to switch quickly...". However many of those are already in required qualifications. Could split. But we must not invent sections with filler. If we include Skills, we need actual content. The posting does have skill-like statements. So we can include Skills section with those. We must not include Benefits, Pay, Schedule as they are not present. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's extract content. About the role: "Sourceability® is a global digital distributor of electronic components transforming how modern businesses bring products to market. With innovation, quality and logistics as the backbone of the company, Sourceability's cutting-edge products and services expedite the procurement process across a wide range of industries, including communications/cellular, consumer electronics, and auto manufacturing. We are looking for a hands-on Netsuite Business Analyst to become a vital part of our IT team working in a hybrid manner from our Austin, TX office. Join the energy and come be part of the momentum!" That's about the role/company. Responsibilities: list from "As the NetSuite Business Analyst, you will be a key analyst within our Business Technology group and a primary liaison to operations teams across the company, most closely with Finance. You will partner with those teams to understand how they work, translate business problems into clear and buildable requirements, configure and test solutions alongside our developers, and help keep a highly customized ERP coherent as the business scales." Then "Insight on your impact:" bullet-like sentences: "Partner with the business. Work directly with Finance, Operations, and other departments to understand their processes, surface pain points, and shape requirements that reflect how the business actually runs. Translate business needs into specs a developer can build from. Write clear functional requirements, user stories, and acceptance criteria, including data mapping, edge cases, and expected system behavior, so development work can be executed without guesswork. Support the core financial processes. Serve as a functional resource across Order to Cash and Procure to Pay: sales orders, fulfillment, invoicing, cash application, requisitions, purchase orders, receipts, vendor bills, and three-way match, and understand how each step lands in the GL. Configure and maintain NetSuite functionally. Contribute to configuration, roles and permissions, forms, workflows, and application setup within a highly customized environment, in partnership with the wider Business Technology team. Scope and manage the ticket queue. Intake, qualify, and prioritize requests; break work into well-defined tickets; keep stakeholders informed on status, sequencing, and trade-offs. Own testing and release discipline. Write test plans in business terms, run UAT in sandbox, coordinate business sign-off, and provide functional approval before deployment to production. Understand the release cycle and how changes move between environments. Think in terms of downstream impact. Assess how new fields, records, and customizations will affect reporting, integrations, month-end close, and audit, and recommend the simplest solution that meets the business need. Build reporting the business trusts. Create and maintain saved searches, reports, and dashboards; build alert and exception reporting to surface data-quality and procedural setup issues before they become month-end problems. Facilitate process review sessions with Finance and Operations subject matter experts to identify opportunities for streamlining, automation, and continuous improvement. Provide Tier 3 support for enterprise systems, including root-cause analysis, data corrections, and configuration fixes. Maintain functional documentation, process flows, configuration decisions, and specifications, so knowledge does not live in one person's head." We can turn each sentence into

• items. Requirements: required qualifications bullet list: "Bachelor's degree in Information Systems, Accounting, Business Administration, or a related field, or equivalent work experience. 3–5 years of hands-on experience as a functional ERP analyst, business systems analyst, or equivalent, with the majority of that time in NetSuite. Strong working knowledge of finance and accounting fundamentals, the general ledger, subledgers, revenue and expense recognition, and the month-end close, and the ability to hold a credible conversation with Controllers and AP/AR teams. Demonstrated functional depth in Order to Cash and Procure to Pay, including the upstream and downstream dependencies of each. Experience working in a highly customized NetSuite environment: custom records, custom fields, scripted behavior, workflows, and third-party integrations. Proven business analysis skills, requirements gathering, process mapping, gap analysis, user stories, and writing developer-ready specifications with acceptance criteria. Advanced proficiency with NetSuite saved searches (joined records, formula fields, summary and criteria logic) and standard/custom reporting. Testing and release discipline: writing functional test plans, executing UAT in sandbox, documenting results, and formally signing off prior to production deployment. Basic to intermediate SQL or equivalent data query skills for validation, reconciliation, and analysis. Excellent stakeholder management and communication skills, including the ability to question assumptions constructively and explain technical constraints and trade-offs to non-technical audiences. Ability to switch quickly between subject areas to meet the needs of diverse business units." Qualifications: preferred qualifications list: "Experience with NetSuite lot tracking: lot numbered items, inventory detail/lot number records, and lot costing. Conceptual familiarity with SuiteScript and SuiteFlow, enough to discuss options with developers and anticipate the impact of a change. No coding required. Distribution, supply chain, or electronic components industry experience. Exposure to logistics, inventory, and quality processes within an ERP. Experience with reporting and analytics tools beyond native NetSuite (e.g., SuiteAnalytics Workbook, Power BI)." Skills: maybe we could list some of the skill statements that are not already covered? But many are overlapping. Could decide to not include Skills section to avoid duplication. However spec says we can include sections only if posting has real specific content. It does have skill statements, but they are already in Requirements. Could still include Skills as a separate section listing e.g., "Stakeholder management, communication, analytical thinking, problem-solving, etc." But we must not invent or summarize away detail. We could extract explicit skill phrases: "Excellent stakeholder management and communication skills", "Ability to question assumptions constructively", "Explain technical constraints and trade-offs to non-technical audiences", "Ability to switch quickly between subject areas". Those are skills. We could list them. But to avoid duplication, maybe we treat Requirements as required qualifications, Qualifications as preferred qualifications, and Skills as the skill-based items from the required list (like stakeholder management, communication, etc). However that would split the required list. Might be okay. But we must preserve ALL substantive information; we cannot omit any. If we split, we need to ensure all info appears somewhere. Let's allocate: - About the role: intro paragraph. - Responsibilities: list of duties. - Requirements: required qualifications (including education, experience, knowledge, etc). We'll include all required qualifications bullet points. - Qualifications: preferred qualifications bullet points. - Skills: maybe we can list the skill-based items that are not already captured? But they are already in required qualifications. If we include Skills, we would duplicate. Better to omit Skills section to avoid duplication, as the spec says prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Qualifications. That's four sections. That seems sufficient. We must not include Benefits, Pay, Schedule. Now format. Use

  for each section heading. Inside each section, use

  for prose,

  • for lists. For About the role: we have two paragraphs? Could combine into one

    with sentences. For Responsibilities: we have a leading sentence then list. Could put leading sentence in

    then

    • for each bullet. But we must not repeat the job title as heading. That's fine. Now craft HTML. Let's write:

      About the role

      Sourceability® is a global digital distributor of electronic components transforming how modern businesses bring products to market. With innovation, quality and logistics as the backbone of the company, Sourceability's cutting-edge products and services expedite the procurement process across a wide range of industries, including communications/cellular, consumer electronics, and auto manufacturing. We are looking for a hands‑on Netsuite Business Analyst to become a vital part of our IT team working in a hybrid manner from our Austin, TX office. Join the energy and come be part of the momentum!

      Responsibilities

      As the NetSuite Business Analyst, you will be a key analyst within our Business Technology group and a primary liaison to operations teams across the company, most closely with Finance. You will partner with those teams to understand how they work, translate business problems into clear and buildable requirements, configure and test solutions alongside our developers, and help keep a highly customized ERP coherent as the business scales.

      • Partner with the business. Work directly with Finance, Operations, and other departments to understand their processes, surface pain points, and shape requirements that reflect how the business actually runs.
      • Translate business needs into specs a developer can build from.
      • Write clear functional requirements, user stories, and acceptance criteria, including data mapping, edge cases, and expected system behavior, so development work can be executed without guesswork.
      • Support the core financial processes. Serve as a functional resource across Order to Cash and Procure to Pay: sales orders, fulfillment, invoicing, cash application, requisitions, purchase orders, receipts, vendor bills, and three‑way match, and understand how each step lands in the GL.
      • Configure and maintain NetSuite functionally. Contribute to configuration, roles and permissions, forms, workflows, and application setup within a highly customized environment, in partnership with the wider Business Technology team.
      • Scope and manage the ticket queue. Intake, qualify, and prioritize requests; break work into well‑defined tickets; keep stakeholders informed on status, sequencing, and trade‑offs.
      • Own testing and release discipline. Write test plans in business terms, run UAT in sandbox, coordinate business sign‑off, and provide functional approval before deployment to production.
      • Understand the release cycle and how changes move between