Export Compliance & Sanctions Analyst

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. Key info: - Job Title: Export Compliance & Sanctions Analyst (already shown, not repeat as heading) - Location: Cupertino, CA, USA, 95014 - Work Model: Hybrid, 3 days onsite per week - Shift: 9 AM - 5 PM - Employment Type: Temporary, Full-Time - Estimated Duration: 13 months - Hourly Rate: Min $46.26, Max $46.26 (same) - Must Have Skills/Attributes: Multitask, Project Management, SAP, Screening Experience - Desired: Export Compliance & Sanctions (3+ yrs); SAP GTS screening system (2+ yrs); Export Administration Regulations and OFAC sanctions regulations (3+ yrs) - Required Minimum Education: Bachelor’s Degree - C2C not available (metadata) - Job Description includes Required Education/Experience: Bachelor's degree in international business, international relations, international trade, law degree or a related degree or equivalent work experience - Required Knowledge & Skills: list bullet points (3+ years export compliance experience, investigating companies, SAP GTS, EAR/OFAC, communication, organization, project management, multitasking, documentation, ability to meet timelines, self-starter, adaptive, Mac/MacOS/iOS proficiency) - Job Responsibilities: list bullet points (perform denied party screenings, assist in export and sanctions compliance review of apps submitted for distribution on the App Store, conduct export compliance due diligence reviews of vendors and suppliers, conduct reviews and investigations to resolve potential matches, conduct investigation of customers, business partners, transactions per SLAs, escalate unusual findings, independent research, accumulating and documenting findings, assist in other tasks) - Benefits: "For information and details on employment benefits offered with this position, please visit here." That's not specific content; it's a placeholder. So we should NOT include Benefits section because no specific benefit details. - Pay: we have hourly rate specific: $46.26 both min and max. That's specific. So we can include Pay section with that info. - Schedule: we have Shift: 9 AM - 5 PM, Work Model: Hybrid 3 days onsite per week. That's schedule info. So we can include Schedule section. - About the role: maybe we can include a brief prose summarizing role? The posting includes job description etc. Could put a short paragraph under About the role summarizing purpose. But we must not invent or summarize away detail; we can use the job description prose? The posting includes "Job Description Required Education/Experience:" etc. That's more like requirements. There's no separate "About the role" paragraph. However we could treat the first paragraph after job title as "About the role": maybe the lines "Job Description Required Education/Experience: Bachelor's degree..." but that's more like qualifications. Better to not create About the role if no specific content. But we could include a short paragraph using the first sentence: "Export Compliance & Sanctions Analyst role involves performing denied party screenings..." but that's from responsibilities. Might be considered summarizing. Safer to only include sections where we have explicit headings in the posting: Responsibilities, Required Knowledge & Skills (maybe Skills), Qualifications (education/experience), Pay, Schedule. Also maybe "Requirements" could combine desired experience etc. But we must not repeat content. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can organize them. Let's extract all substantive info: - Location: Cupertino, CA, USA, 95014 - Work Model: Hybrid, 3 days onsite per week - Shift: 9 AM - 5 PM - Employment Type: Temporary, Full-Time - Estimated Duration: 13 months - Hourly Rate: $46.26 (both min and max) - Must Have Skills/Attributes: Multitask, Project Management, SAP, Screening Experience - Desired Experience: Export Compliance & Sanctions (3+ yrs); SAP GTS screening system (2+ yrs); Export Administration Regulations and OFAC sanctions regulations (3+ yrs) - Required Minimum Education: Bachelor’s Degree - C2C not available (maybe metadata, can drop) - Required Education/Experience: Bachelor's degree in international business, international relations, international trade, law degree or a related degree or equivalent work experience - Required Knowledge & Skills: * 3+ years of export compliance experience is required * Experience with investigating and researching companies and individuals for sanctions and export control risks * Experience using SAP GTS screening system * Experience and working knowledge of the Export Administration Regulations and OFAC sanctions regulations * Excellent oral and written communication skills * Excellent organization, project management, multitasking and documentation skills * Ability to meet aggressive timelines and in a compliance focused environment * Ability to apply sound ethical judgement * Must be a self-starter, adaptive and able to learn new concepts, systems and processes quickly * Mac, MacOS and iOS proficiency - Job Responsibilities: * Perform denied party screenings for various programs within the company * Assist in export and sanctions compliance review of apps submitted for distribution on the App Store * Conduct export compliance due diligence reviews of vendors and suppliers to identify risks to the company * Conduct reviews and investigations to appropriately resolve potential matches generated by the sanctions systems * Conduct investigation of customers, business partners, and transactions in accordance with established policies and procedures and tools per SLAs * Escalate unusual findings that might be related to sanctioned individuals, terrorist financing, law enforcement, or other criminal activities * Conduct independent research utilizing the internet, third party tools, commercial databases, and leverage internal databases to evaluate and disposition sanction system alerts. * Accumulating and documenting relevant findings regarding transactions and screened parties’ facts from investigations so GESC can determine the necessary compliance steps * Assist in other export and sanctions compliance related tasks and projects, as needed - Benefits: only generic pointer, no specifics -> omit. - Pay: $46.26 hourly. - Schedule: Hybrid 3 days onsite per week, Shift 9 AM - 5 PM. We also have "Date Posted: 09/10/2026", "Hiring Organization: Rose International", "Position Number: 507288", "Industry: IT Company". These are metadata; we can fold into a short

  or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short paragraph with that metadata. We must not include boilerplate like EEO, legal, etc. Remove those. Thus final HTML:

  Posted 09/10/2026 by Rose International (Position #507288, IT Industry).

  Then sections: - About the role? Not present; maybe we can skip. - Responsibilities:

  Responsibilities

  ...
  - Requirements: maybe combine Required Knowledge & Skills and Desired Experience? Could have

  Requirements

  with two sublists? But we need to preserve all detail. Could do

  Required Knowledge & Skills

  and

  Desired Experience

  . However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't say we cannot use other headings, but better to stick to those. So we need to map content to those headings. We have: - Responsibilities: yes. - Requirements: could include Required Minimum Education, Required Education/Experience, Desired Experience, Must Have Skills/Attributes? Actually Must Have Skills/Attributes could go under Skills. - Qualifications: could include education and experience. - Skills: could include Must Have Skills/Attributes and Required Knowledge & Skills. - Pay: yes. - Schedule: yes. We need to avoid duplication. Let's decide: -

  Requirements

  : include Required Minimum Education (Bachelor’s Degree), Required Education/Experience (Bachelor's degree in international business... or equivalent work experience), Desired Experience (Export Compliance & Sanctions 3+ yrs; SAP GTS 2+ yrs; EAR/OFAC 3+ yrs). Also maybe Must Have Skills/Attributes? But that is more skills. -

  Skills

  : include Must Have Skills/Attributes (Multitask, Project Management, SAP, Screening Experience) and Required Knowledge & Skills list (the bullet points). Could combine. -

  Responsibilities

  : list responsibilities. -

  Pay

  :

  $46.26 per hour (fixed rate).

  -

  Schedule

  :

  Hybrid work model: 3 days onsite per week; shift 9 AM – 5 PM.

  - Maybe also include a short

  for metadata at top. We must not include Benefits section because no specifics. Check for any other specifics: "Estimated Duration (In months): 13". That's substantive; we could include under maybe a section like "Contract Duration" but not in allowed headings. Could fold into Schedule or a separate paragraph? The instruction says prefer a few substantive sections over many thin ones. We could add duration to Schedule section or a separate

  after metadata. Since Schedule already includes shift and work model, we could add duration there: "Estimated duration: 13 months." That seems okay. Also "Employment Type: Temporary FT/PT: Full-Time". Could include in Schedule or a separate

  . Could add to Schedule: "Temporary full‑time position." Or we could add a separate

  for metadata. We need to preserve ALL substantive information. So we must include duration and employment type somewhere. Let's add a

  after metadata: "Temporary full‑time position, estimated duration 13 months." Now check if any other info: "Work Model Details: 3 days onsite per week" we already have. Now ensure we don't repeat info. Let's craft HTML:

  Posted 09/10/2026 by Rose International (Position #507288, IT Industry).

  Temporary full‑time position, estimated duration 13 months.

  Responsibilities

  • Perform denied party screenings for various programs within the company
  • Assist in export and sanctions compliance review of apps submitted for distribution on the App Store
  • Conduct export compliance due diligence reviews of vendors and suppliers to identify risks to the company
  • Conduct reviews and investigations to appropriately resolve potential matches generated by the sanctions systems
  • Conduct investigation of customers, business partners, and transactions in accordance with established policies and procedures and tools per SLAs
  • Escalate unusual findings that might be related to sanctioned individuals, terrorist financing, law enforcement, or other criminal activities
  • Conduct independent research utilizing the internet, third party tools, commercial databases, and leverage internal databases to evaluate and disposition sanction