Principal Database Developer

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. We need to parse the job description. Content: "Job Description Note: Fidelity will not provide immigration sponsorship for this position." That's a note, maybe minor metadata; we can fold into a short

or drop. Not a heading. "The Role" heading: we can treat as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have "The Role" paragraph: description of role. That could go under About the role. Then "The Expertise and Skills You Bring" list: many bullet-like sentences. Could be Requirements or Qualifications or Skills. We need to decide. We have "The Team" paragraph: description of team. "Fidelity’s Onsite Working Model": schedule info? It's about onsite expectations. Could be Schedule. "Certifications Category: Information Technology" maybe minor. Then legal boilerplate: we should remove. We need to preserve all substantive info, not invent. We need to avoid sections with filler like "commensurate with experience". Not present. We need to include sections only if posting has real specific content. Thus we can have:

About the role

... from The Role paragraph.

Responsibilities

maybe we can extract responsibilities from the expertise list: many items like "Own architecture decisions...", "Coordinate with DevOps...", "Build reusable database utility...", "Lead end-to-end database development...", "Ability to lead technical discussion and mentor developers", "Optimized the performance...", "Knows ETL processes...", "Experience working with team in Agile methodology", etc. Those are responsibilities. We could put them in

• .

  Requirements

  maybe the hard requirements: 7+ years hands-on experience as an Oracle PL/SQL developer, Strong RDBMS skills, Strong data analysis, problem-solving, design skills, etc. Could be separate. But we need to avoid duplication. Could combine Requirements and Qualifications? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide what to put where. We have many skill statements: Strong RDBMS skills, Strong data analysis, problem-solving, design skills, Own architecture decisions, Coordinate with DevOps, Build reusable components, Lead end-to-end, Ability to lead technical discussion, Optimize performance, Knows ETL, Experience with Agile, Knowledge of Core Java, Python, scheduling tools (nice to have), Strong experience in database modeling, AWS Cloud experience (plus), Strong data analysis skills, design, coding experience in Financial Industry preferably Capital Markets/Securities Finance, 5+ years working in financial industry (plus), Understand glossaries and terminologies, Ability to work independently and collaborate, Motivated, Good communication skills, Quick learner, adaptable. We could categorize: Requirements: 7+ years experience, Strong RDBMS skills, Strong data analysis/problem-solving/design skills, Ability to work independently and collaborate, Good communication skills, Quick learner, adaptable. Qualifications: maybe certifications? Not much. Skills: list of technical skills: Oracle PL/SQL, SQL, stored procedures, triggers, functions, views, user privileges, object privileges, data modeling, ETL, Agile, Core Java, Python, Control-M, AWS, financial industry knowledge. But we need to avoid filler. We'll include sections with real content. We also have schedule info: Onsite Working Model description. That's schedule. Benefits: none mentioned. Pay: none. So we should not include Benefits or Pay sections. Thus final HTML:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Skills

  ...

  Schedule

  ...

  We need to ensure we don't repeat job title. Not include Job ID. We need to preserve all substantive info: we must not lose any detail from the posting. Let's extract all substantive sentences. From The Role: "The Principal Oracle PL/SQL Developer will work with a team of Software Engineers across the globe to develop high-quality applications servicing the financial trading industry. First and foremost, we look for a proven database developer, with a strong desire to grow their knowledge and capabilities while passionate about the tasks at hand." That's about role. From The Expertise and Skills You Bring (list): - 7+ years of hands-on experience as an Oracle PL/SQL developer. - Strong RDBMS skills – SQL querying, writing stored procedures, triggers, functions, views, user privileges, object privileges, etc. - Strong data analysis, problem-solving, and design skills with a desire to continually learn and grow in a collaborative team environment - Own architecture decisions for database components and ensure alignment with overall application architecture. - Coordinate with DevOps / infrastructure teams for automation, deployment pipelines, and environment readiness. - Build reusable database utility components and frameworks to improve developer productivity and consistency. - Lead end-to-end database development for mission-critical applications - Ability to lead technical discussion and mentor developers - Optimized the performance of stored procedures and database objects through query tuning, indexing strategies, and execution-plan analysis. - Knows ETL processes to load large volumes of data at speed, e.g. SQL Loader, etc. - Experience working with team in Agile methodology - Knowledge of Core Java, Python, and scheduling tools like Control-M is nice to have. - Strong experience in database modeling. - AWS Cloud experience is a plus - Strong data analysis skills, design, and coding experience in Financial Industry preferably in Capital Markets/ Securities Finance. - 5+ years working in financial industry is a plus. - Understand glossaries and terminologies in financial industry - Ability to work independently and collaborate with teams. - Motivated and able to deliver end-to-end solutions. - Good communication skills to both technology folks and business partners. - Quick learner, adaptable, has the right attitude to work across teams to find and deploy solutions. From The Team: "The Senior Oracle PL/SQL Developer will be part of Securities Finance Technology team responsible for management & solution buildout of Stock Borrow Loan, Fully Paid Trading products for Fidelity Capital Markets business unit." Note: The title mismatch (Senior vs Principal) but we keep. From Fidelity’s Onsite Working Model: "Fidelity is transitioning to a full-time onsite working model through a phased rollout across regions and roles. Currently, some roles and locations require 100% onsite presence, while others require less. Onsite expectations are likely to evolve as the rollout continues. This transition does not apply to fully remote roles." That's schedule info. Certifications Category: Information Technology (maybe minor, could be dropped or included as a short p). The instruction: fold minor metadata into a short

  or drop it. So we can include a short p for Certifications Category. Legal boilerplate: remove. Now we need to map to sections. About the role: combine The Role paragraph and maybe The Team paragraph? The Team is about team context; could be part of About the role or separate. But we have no specific "Team" heading. Could include in About the role. Thus About the role: two paragraphs: role description and team description. Responsibilities: items that are action-oriented: Own architecture decisions, Coordinate with DevOps, Build reusable components, Lead end-to-end database development, Ability to lead technical discussion and mentor developers, Optimized performance, Knows ETL processes, Experience working with team in Agile methodology, Ability to work independently and collaborate, Motivated and able to deliver end-to-end solutions, Good communication skills, Quick learner adaptable. But some of those are also skills/qualities. However we need to split. Requirements: maybe the years of experience, strong RDBMS skills, strong data analysis/problem-solving/design skills, 5+ years financial industry (plus), Understand glossaries, etc. But many are plus. Qualifications: maybe certifications category? Not much. Skills: technical skills: Oracle PL/SQL, SQL, stored procedures, triggers, functions, views, user privileges, object privileges, data modeling, ETL, Agile, Core Java, Python, Control-M, AWS, financial industry knowledge. We need to avoid duplication. Let's think: The instruction says prefer a few substantive sections over many thin ones. So maybe we can combine Requirements and Skills into one section? But they ask to use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those that have content. We could have: - About the role - Responsibilities - Requirements (including experience, RDBMS, data analysis, financial industry knowledge, ability to work independently, communication, quick learner) - Skills (technical: Oracle PL/SQL, RDBMS, ETL, Agile, Java, Python, Control-M, AWS, data modeling) - Schedule (onsite model) We could omit Qualifications if no specific certifications. We need to ensure we preserve all substantive info. Let's list each piece and assign. List items: 1. Principal Oracle PL/SQL Developer will work with a team of Software Engineers across the globe to develop high-quality applications servicing the financial trading industry. (role) 2. First and foremost, we look for a proven database developer, with a strong desire to grow their knowledge and capabilities while passionate about the tasks at hand. (role/attitude) 3. 7+ years of hands-on experience as an Oracle PL/SQL developer. (requirement) 4. Strong RDBMS skills – SQL querying, writing stored procedures, triggers, functions, views, user privileges, object privileges, etc. (skill/requirement) 5. Strong data analysis, problem-solving, and design skills with a desire to continually learn and grow in a collaborative team environment. (skill/requirement) 6. Own architecture decisions for database components and ensure alignment with overall application architecture. (responsibility) 7. Coordinate with DevOps / infrastructure teams for automation, deployment pipelines, and environment readiness. (responsibility) 8. Build reusable database utility components and frameworks to improve developer productivity and consistency. (responsibility) 9. Lead end-to-end database development for mission-critical applications. (responsibility) 10. Ability to lead technical discussion and mentor developers. (responsibility/skill) 11. Optimized the performance of stored procedures and database objects through query tuning, indexing strategies, and execution-plan analysis. (responsibility/skill) 12. Knows ETL processes to load large volumes of data at speed, e.g. SQL Loader, etc. (skill) 13. Experience working with team in Agile methodology. (skill/responsibility) 14. Knowledge of Core Java, Python, and scheduling tools like Control-M is nice to have. (skill, nice-to-have) 15. Strong experience in database modeling. (skill) 16. AWS Cloud experience is a plus. (skill, plus) 17. Strong data analysis skills, design, and coding experience in Financial Industry preferably in Capital Markets/ Securities Finance. (skill/requirement) 18. 5+ years working in financial industry is a plus. (requirement/plus) 19. Understand glossaries and terminologies in financial industry. (requirement/skill) 20. Ability to work independently and collaborate with teams. (skill/requirement) 21. Motivated and able to deliver end-to-end solutions. (skill/requirement) 22. Good communication skills to both technology folks and business partners. (skill/requirement) 23. Quick learner, adaptable, has the right attitude to work across teams to find and deploy solutions. (skill/requirement) 24. The Senior Oracle PL/SQL Developer will be part of Securities Finance Technology team responsible for management &