Data Engineer

We need to output HTML fragment with sections: About the role? The posting includes description of company, role description, role objectives, qualifications and skills, hybrid work info. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have company overview maybe "About the role"? Actually "About the role" could be the description of role. Could also have "Responsibilities" from role description bullet points. "Qualifications" and "Skills" maybe combined. There's no explicit Benefits, Pay, Schedule. There's hybrid work info (schedule) maybe schedule? It mentions hybrid work model, but not specific schedule. It says "Hybrid work may not be permitted for certain roles..." Not a specific schedule. Should we include Schedule? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention hybrid work model, but not explicit schedule. Might be considered schedule info? It says "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 schedule info. Could be considered Schedule section. But we need to avoid filler like "not specified". This is specific: hybrid work model. So we can include a Schedule section with that info. Benefits: not mentioned. Pay: not mentioned. So omit those. We need to avoid repeating job title as heading. The job title is Senior Data Engineer. Not to repeat. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's some accommodation info at end: "SMBC provides reasonable accommodations..." That's not boilerplate? It's about accommodations for disability. Might be considered EEO/equal-opportunity boilerplate. Probably should remove. Also the line about accommodations@smbcgroup.com is application instruction? It's about accommodation request. Might be considered boilerplate. Safer to remove. Also remove duplicated lines. Not seeing duplicates. We need to include company overview? Possibly under "About the role" or maybe a separate "About the company"? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company overview under About the role? Or maybe we can have About the role includes role description and company context. We'll put company overview in About the role as prose. Responsibilities: from role description bullet points (the paragraph after "Role Description"). Requirements: maybe from "Role Objectives"? Actually Role Objectives list responsibilities and required skills. Could split: Responsibilities (what you will do) and Requirements (what you need). Qualifications and Skills separate. We have "Qualifications And Skills" section with bullet list. Could split into Qualifications (education, experience) and Skills (technical). But we have allowed headings Qualifications and Skills. So we can put qualifications under Qualifications heading, skills under Skills heading. We need to ensure we don't create sections with filler. We'll include:

  About the role

  company overview + role description summary?

  Responsibilities

  • ... list items from role description

  Requirements

  maybe from Role Objectives? Actually Role Objectives includes both responsibilities and qualifications. But we can treat Role Objectives as responsibilities? Might be better to put Role Objectives under Responsibilities? Hmm. Let's parse the posting: After "Role Description": paragraph: "We are currently seeking a talented and motivated Senior Data Engineer to join our Cloud data solutions team. This role will be responsible for designing, developing & deploying cloud data solutions for risk, regulatory, finance & compliance projects and be at the forefront of on-prem to cloud migration initiative. This role will require indirect leadership and mentorship of junior team members. Work with business teams, product managers, and other stakeholders to understand business requirements, needs, or process gaps that would be addressed via proposed applications. Engage with IT systems architects, database administrators, and cyber security team to meet the back-end functionality demands of the application. Liaise with other technology and development teams as needed to coordinate on the integration of applications with the larger company software ecosystem. Participate in periodic development meetings to align development priorities and objectives, assign tasks, and share experiences and challenges with applications under development." That's responsibilities. Then "Role Objectives:" then a list of bullet-like sentences (not bullet but separated by line breaks). Those are more like required experience/skills: "Delivery Extensive experience on Cloud solutions, specifically in Azure Experience with Azure cloud services, Azure Data Factory, Gen 2, Azure Databases, Functions, Databricks, etc Strong knowledge of Python, Java or similar high-level server-side languages' Advanced working SQL knowledge on relational databases, preferably on MS SQL Server and databases on Azure cloud Experience with the DevOps lifecycle (git, Jenkins, etc.) Experience with Jira/Confluence Experience with REST web services and microservice architecture Databricks Cluster configuration, Unity catalog repository configuration. Build large-scale batch and real-time data pipelines with data processing frameworks in Azure cloud platform. Partner with architects, engineers, information analysts, business, and technology stakeholders for developing and deploying enterprise grade platforms that enable data-driven solutions. Coordinating with platform, APIM, Azure DevOps, and Support. Analyze and design technical solutions on Azure to address business needs. Develop, test, and modify software to improve efficiency of data platforms and applications. Integrating data from a variety of sources, assuring that they adhere to data quality and accessibility standards. Enable streaming data use-cases and standard design patterns in a big data environment. Review and provide feedback on core code changes and support production deployment." That seems like a mix of responsibilities and qualifications. But we can treat as Responsibilities (what you will do) and maybe also as Requirements (what you need). However we already have responsibilities list from earlier paragraph. Could combine. Better: Use Responsibilities for the first paragraph (duties). Use Requirements for the Role Objectives list (experience/knowledge needed). Then Qualifications for education/experience: "Minimum 4 years of software development experience in enterprise applications, preferably in the financial services industry and on data-heavy systems Bachelor’s or master’s degree in computer science or information systems preferred." Skills for technical list: maybe the same as Role Objectives? But we already used Role Objectives for Requirements. Could split: Requirements = minimum years + degree; Skills = technical list. But we have Qualifications heading allowed; we could put degree/experience there. Skills heading for technical list. Let's decide: - About the role: company overview + brief role purpose. - Responsibilities: the paragraph describing duties (designing, developing, deploying, leadership, work with teams, etc.) - Requirements: Minimum 4 years experience, degree preferred. - Skills: the long list of technical expertise (Azure, Python/Java, SQL, DevOps, Jira/Confluence, REST, microservices, Databricks, etc.) - Schedule: hybrid work model description. We must not repeat job title. We must not include boilerplate like accommodation request. We must not include duplicated lines. Now craft HTML. We need to ensure we use

  for each section heading. Inside sections, use

  for prose,

  • for lists. For About the role: we can have a

    containing company overview and maybe role purpose. Company overview: "SMBC Group is a top-tier global financial group. Headquartered in Tokyo and with a 400-year history, SMBC Group offers a diverse range of financial services, including banking, leasing, securities, credit cards, and consumer finance. The Group has more than 130 offices and 80,000 employees worldwide in nearly 40 countries. Sumitomo Mitsui Financial Group, Inc. (SMFG) is the holding company of SMBC Group, which is one of the three largest banking groups in Japan. SMFG’s shares trade on the Tokyo, Nagoya, and New York (NYSE: SMFG) stock exchanges. In the Americas, SMBC Group has a presence in the US, Canada, Mexico, Brazil, Chile, Colombia, and Peru. Backed by the capital strength of SMBC Group and the value of its relationships in Asia, the Group offers a range of commercial and investment banking services to its corporate, institutional, and municipal clients. It connects a diverse client base to local markets and the organization’s extensive global network. The Group’s operating companies in the Americas include Sumitomo Mitsui Banking Corp. (SMBC), SMBC Nikko Securities America, Inc., SMBC Capital Markets, Inc., SMBC MANUBANK, JRI America, Inc., SMBC Leasing and Finance, Inc., Banco Sumitomo Mitsui Brasileiro S.A., and Sumitomo Mitsui Finance and Leasing Co., Ltd." Then role purpose maybe: "We are currently seeking a talented and motivated Senior Data Engineer to join our Cloud data solutions team." Could be included. We'll combine. Responsibilities list: we need to break into bullet items. The paragraph has multiple sentences; we can turn each sentence into

  • . Let's extract: - designing, developing & deploying cloud data solutions for risk, regulatory, finance & compliance projects and be at the forefront of on-prem to cloud migration initiative. - indirect leadership and mentorship of junior team members. - Work with business teams, product managers, and other stakeholders to understand business requirements, needs, or process gaps that would be addressed via proposed applications. - Engage with IT systems administrators, database administrators, and cyber security team to meet the back-end functionality demands of the application. - Liaise with other technology and development teams as needed to coordinate on the integration of applications with the larger company software ecosystem. - Participate in periodic development meetings to align development priorities and objectives, assign tasks, and share experiences and challenges with applications under development. We'll make each a
  • . Requirements: Minimum 4 years of software development experience in enterprise applications, preferably in the financial services industry and on data-heavy systems. Bachelor’s or master’s degree in computer science or information systems preferred. We can put as
    • ...
    • ...
    . Skills: list of technical expertise. We need to break into items. The long list includes many items separated by commas and periods. We'll split logically: - Extensive experience on Cloud solutions, specifically in Azure - Experience with Azure cloud services, Azure Data Factory, Gen 2, Azure Databases, Functions, Databricks, etc. - Strong knowledge of Python, Java or similar high-level server-side languages - Advanced working SQL knowledge on relational databases, preferably on MS SQL Server and databases on Azure cloud - Experience with the DevOps lifecycle (git, Jenkins, etc.) - Experience with Jira/Confluence - Experience with REST web services and microservice architecture - Databricks Cluster configuration, Unity catalog repository configuration. - Build large-scale batch and real-time data pipelines with data processing frameworks in Azure cloud platform. - Partner with architects, engineers, information analysts, business, and technology stakeholders for developing and deploying enterprise grade platforms that enable data-driven solutions. - Coordinating with platform, APIM, Azure DevOps, and Support. - Analyze and design technical solutions on Azure to address business needs. - Develop, test, and modify software to improve efficiency of data platforms and applications. - Integrating data from a variety of sources, assuring that they adhere to data quality and accessibility standards. - Enable streaming data use-cases and standard design patterns in a big data environment. - Review and provide feedback on core code changes and support production deployment. We'll put each as
  • . Schedule: hybrid work model description. We'll put as

    . Now ensure we don't include any boilerplate like accommodation request. Remove that paragraph. Now produce HTML fragment. Check for any repeated content: we