JRIA Business Planning

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - Intro about SMBC Group: description. That could be "About the role"? Actually "About the role" is a section heading for description of role? Usually "About the role" includes overview. The posting includes "Role Description" paragraph. So we can put that under

About the role

with paragraphs. - Responsibilities: list under Key Responsibilities with bullet points. - Requirements: maybe "Required Qualifications". That's qualifications. Could be under

Requirements

or

Qualifications

. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications separate. We need to decide what goes where. Usually Requirements = required qualifications, Qualifications = preferred qualifications. Skills maybe separate? Could combine. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we need to see if we have content for each. We have: - Required Qualifications (list). That's specific content. Could go under

Requirements

. - Preferred Qualifications (list). Could go under

Qualifications

. - Skills: maybe we can extract skills from required qualifications: strong ability to gather..., strong analytical..., ability to work independently... Could be placed under

Skills

. But we might also include them under Requirements. However we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required Qualifications and Skills into one section? But they ask to use headings for those specific names if we include them. We could include Requirements (covers required qualifications) and Qualifications (covers preferred). Skills maybe not needed separately if we incorporate into Requirements. But we need to decide. We also have Benefits: mention of Hybrid workforce model, reasonable accommodations, etc. That's benefits. So we can include

Benefits

with paragraphs about hybrid work, reasonable accommodations. Pay: not mentioned. So we should NOT include Pay section. Schedule: mention of hybrid work schedule, but not specific schedule. The posting says "Prospective candidates will learn more about their specific hybrid work schedule during their interview process." That's not specific schedule; it's vague. According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits we have actual statements (Hybrid workforce model, reasonable accommodations). So Benefits is okay. For Schedule, we have only vague statement about learning more during interview; that's not specific schedule. So we should NOT include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills? Might combine Skills into Requirements or Qualifications. But we have separate headings for Skills; we could include Skills if we have specific skill content. We have "Strong ability to gather, assess, consolidate, and structure information from a wide range of stakeholders for management purposes. Strong analytical, numerical, and logical thinking skills. Ability to work independently in ambiguous situations and drive outcomes through collaboration and influence." Those are skills. Could be placed under Skills. However we also have Required Qualifications includes language proficiency, years experience, etc. So we could separate: Requirements = language proficiency, experience years; Qualifications = preferred qualifications; Skills = abilities. That would be three sections. That seems okay as each has specific content. But we need to avoid too many thin sections. However each has substantive content. Let's see: - About the role: paragraph(s) from Role Description. - Responsibilities: bullet list from Key Responsibilities (multiple bullet points). Good. - Requirements: Required Qualifications bullet list (language proficiency, 3 years experience in planning/business management/governance within IT org of Japan-headquartered financial institution or comparable regulated industry; 5 years hands-on experience in system development/management; ability to gather..., analytical..., etc? Actually those ability items are under Required Qualifications as well? Let's re-read Required Qualifications section: "Required Qualifications Business-level proficiency in both Japanese and English. Both languages are required. Minimum three years of experience in a planning, business management, or governance function within the IT organization of a Japan-headquartered financial institution or a comparable regulated industry. Minimum five years of hands-on experience in any type of system development and/or management of system development projects, with sufficient understanding to interpret system project status, project issues, and incident-related information. Strong ability to gather, assess, consolidate, and structure information from a wide range of stakeholders for management purposes. Strong analytical, numerical, and logical thinking skills. Ability to work independently in ambiguous situations and drive outcomes through collaboration and influence." So all those are required qualifications. So we could put all under Requirements. Then Preferred Qualifications separate. Skills maybe not needed separately because they are part of Required Qualifications. But we could still have Skills section if we want to highlight abilities. However that would duplicate content. Better to not duplicate. So we can have Requirements (includes language, experience, abilities). Qualifications (preferred). Benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Check if we have any content for Skills separate: not needed. Now we need to format. - About the role: include the paragraph(s) from Role Description: "The Director of Business Planning supports JRI America's corporate planning, management reporting, corporate governance, and Japan - Americas coordination activities. Reporting to the Business Planning Lead, this role serves as a senior leader within the Business Planning function and supports the coordination, review, and enhancement of planning, reporting, governance, and business management activities across the team. The position is expected to provide leadership, oversight, prioritization, and quality control across team's activities, while supporting effective communication and collaboration between Japan and the Americas. The role also consolidates and organizes information related to business operations, technology initiatives, project activities, and organizational matters to support management visibility and regional alignment." Make sure to keep as prose

. - Responsibilities: list items under Key Responsibilities. There are four bullet groups each with a heading (Management Reporting, Corporate Planning & Budget Management; Corporate Governance & Business Administration Oversight; Japan - Americas Coordination & Information Integration; Team Leadership & Continuous Improvement). Each has sub-bullets. We need to output

• for any list of duties/requirements/benefits. Should we preserve the subheadings inside li? Probably we can include them as part of li text. Eg:
• Management Reporting, Corporate Planning & Budget Management: Oversee the preparation ...
. But we cannot add unless it's in original? The instruction didn't forbid adding markup for emphasis, but we should preserve content. Could just include the heading as plain text within li. We'll keep as: "Management Reporting, Corporate Planning & Budget Management: Oversee the preparation and quality review of management reports, business plans, budget plans, and related materials used by management and Japan-based stakeholders. Coordinate information related to business operations, financial performance, technology initiatives, project portfolios, and organizational activities to ensure reporting is accurate, consistent, and appropriately supported." Similarly for others. - Requirements: list Required Qualifications items. Each as
• . - Qualifications: list Preferred Qualifications items. - Benefits: include hybrid work model statement and reasonable accommodations. Also maybe mention that employees live within reasonable commuting distance. That's also a condition but could be considered benefit? It's a requirement? It's a condition: "SMBC requires that employees live within a reasonable commuting distance of their office location." That's not a benefit but a requirement. However we already have Requirements section; we could add that as a requirement? But it's not a qualification; it's a location requirement. Could be placed under Requirements as well. But we already have Requirements filled. Might add another bullet under Requirements: "Employees must live within a reasonable commuting distance of the office location." However the instruction says preserve ALL substantive information. So we need to include that somewhere. Could be under Requirements as a bullet. Or we could create a separate section like "Work Arrangement" but not in allowed headings. Better to add to Requirements. Also mention: "SMBC’s employees participate in a Hybrid workforce model that provides employees with an opportunity to work from home, as well as, from an SMBC office." That's a benefit. Also: "SMBC requires that employees live within a reasonable commuting distance of their office location." That's a requirement. Also: "Prospective candidates will learn more about their specific hybrid work schedule during their interview process." That's vague; we might not include as it's not specific. Also: "Hybrid work may not be permitted for certain roles, including, for example, certain FINRA-registered roles for which in-office attendance for the entire workweek is required." That's a note but not specific to this role? It's a general statement; we could include but it's not specific to this role; still substantive. Could be under Benefits as a note. Also: "SMBC provides reasonable accommodations during candidacy for applicants with disabilities consistent with applicable federal, state, and local law. If you need a reasonable accommodation during the application process, please let us know at accommodations@smbcgroup.com." That's also a benefit/note. We'll include Benefits section with hybrid work model and reasonable accommodations. Now we need to ensure we don't include boilerplate like EEO etc. Already removed. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  • Management Reporting, Corporate Planning & Budget Management: Oversee the preparation and quality review of management reports, business plans, budget plans, and related materials used by management and Japan-based stakeholders. Coordinate information related to business operations, financial performance, technology initiatives, project portfolios, and organizational activities to ensure reporting is accurate, consistent, and appropriately supported.
  • Corporate Governance & Business Administration Oversight: Oversee corporate governance and business administration activities, including Board support, policy and procedural compliance reviews, expatriate administration support, contract management support, audit support, and internal and external reporting requirements. While day-to-day execution may be performed by subject matter experts or supporting corporate functions, this role ensures that required activities are appropriately coordinated, reviewed, and completed in accordance with company and group requirements.
  • Japan - Americas Coordination & Information Integration: Serve as a key interface between Japan and the Americas for business, technology, and management-related matters. Coordinate communications, reporting, and planning activities across stakeholders, and consolidate information from multiple functions and organizations to support effective decision-making, collaboration, and organizational alignment.
  • Team Leadership & Continuous Improvement: Provide leadership, oversight, prioritization, coaching, and quality control across Business Planning team activities. Promote continuous improvement of management reporting, planning processes, governance activities, and Japan - Americas collaboration, with a focus on quality, consistency, transparency, and operational effectiveness.

  Requirements

  • Business-level proficiency in both Japanese and English (both languages required).
  • Minimum three years of experience in a planning, business management, or governance function within the IT organization of a Japan-headquartered financial institution or a comparable regulated industry.
  • Minimum five years of hands-on experience in any type of system development and/or management of system development projects, with sufficient understanding to interpret system project status, project issues, and incident-related information.
  • Strong ability to gather, assess, consolidate, and structure information from a wide range of stakeholders for management purposes.
  • Strong analytical,