Lead Infrastructure Engineer

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. The job description includes responsibilities, required qualifications, preferred qualifications, about us, about the team. There's no explicit Pay, Schedule, Benefits details (though about us mentions benefits generically). The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. The posting mentions benefits generically but not specific. It says "We offer a competitive total rewards package... Additional details about total compensation and benefits will be provided during the hiring process." That's vague, not specific benefits. So we should not create Benefits section. Also no Pay or Schedule specifics. So we will have sections: Responsibilities, Requirements (maybe combine Required Qualifications), Preferred Qualifications (maybe as Skills?), About Us, About The Team. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says we can use those headings but only if content exists. We have Responsibilities content. For qualifications we have Required Qualifications, Capabilities, And Skills and Preferred Qualifications, Capabilities, And Skills. Could combine into Requirements and Skills? Probably better to have Requirements (required) and Skills (preferred). Or we could have Qualifications (required) and Skills (preferred). The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine required and preferred into one Requirements section? But they are distinct. Could have Required Qualifications and Preferred Qualifications as separate sections but both are substantive. However headings allowed: Requirements, Qualifications, Skills. We could do: Requirements (required), Skills (preferred). Or Qualifications (required) and Skills (preferred). Let's decide: Use "Requirements" for required qualifications, and "Skills" for preferred qualifications. Also include "About the role"? Not present. Could use "About Us" and "About The Team" but those aren't in the list of allowed headings. The list is examples, not exhaustive? 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 where applicable, but we can also use other headings? Probably we should stick to those. However "About Us" and "About The Team" are not in the list but could be considered as "About the role"? Not exactly. Might be better to omit those sections if they don't match allowed headings? But we need to preserve ALL substantive information; we cannot drop About Us and About Team info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. We could put it under a generic

like "About the company" but not in list. However the instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed, but better to follow the pattern. We'll use headings: Responsibilities, Requirements, Skills, About Us, About Team. All as h3. We need to use

• for any list of duties/requirements/benefits. So responsibilities list: each bullet as
• . Required qualifications list: each bullet as
• . Preferred qualifications list: each as
• . Also maybe "About Us" and "About Team" are prose, use

  . We must not include boilerplate like EEO etc. We removed that. We need to output only HTML fragment. Let's extract responsibilities bullet points: - Provides recommendations and insight on data management, governance procedures, and intricacies applicable to the acquisition, maintenance, validation, and utilization of data. - Works with other team members, including offshore teams, to resolve high-priority issues. - Helps manage GAIA application pools. - Designs and maintains reliable software solutions for monitoring and alerting as needed. - Works with the team on database performance issues, including code and infrastructure issues, sometimes using SQL Sentry. - Monitors and troubleshoots SQL Server Availability Groups, including replication issues, database failovers, and general troubleshooting. - Works with the team on certificate tracking and renewals. - Supports PostgreSQL environments and vector database platforms used for AI/ML retrieval workloads, including embedding storage, indexing, and query performance. - Uses AI tools and agents in day-to-day work to increase productivity, automate routine tasks, and speed up issue diagnosis and resolution. - Partners with offshore and globally distributed teams to ensure consistent coverage, knowledge sharing, and delivery across time zones. - Supports the on-call rotation for the team. - Adds to a team culture of diversity, equity, inclusion, and respect. Required qualifications bullet points: - 7+ years of hands-on experience managing enterprise databases and supporting infrastructure in large-scale, mission-critical environments. - Deep hands-on experience with relational databases, particularly Microsoft SQL Server, plus working experience with PostgreSQL. - Proficiency with Transact-SQL (T-SQL). - Experience designing, deploying, and troubleshooting SQL infrastructure, including Availability Groups (replication and failover). - Working knowledge of vector databases (e.g., pgvector, Pinecone, Milvus, Chroma) and how they support AI/LLM retrieval and search workloads. - Experience with PowerShell scripting and ETL processes. - Experience with database performance troubleshooting and tuning, including tools such as SQL Sentry. - Experience designing and maintaining monitoring and alerting solutions at scale. - Ability to work collaboratively with cross-functional teams, including non-technical business stakeholders and offshore teams. - Experience with internal cloud applications. - Strong communication skills, with the ability to convey complex technical concepts to non-technical audiences. - Experience with version control systems like Git and Bitbucket for data. - A track record of applying AI tools to automate database operations, modernize workflows, and resolve issues more efficiently. - A forward-looking mindset toward AI-driven transformation, with a demonstrated interest in modernizing database automation and tooling using AI capabilities. Preferred qualifications bullet points: - Experience with SQL Server Availability Groups. - Proficiency with PowerShell. - Solid understanding of Transact-SQL. - Experience with internal cloud application infrastructure. - Experience with overall SQL troubleshooting. - Experience working with offshore or globally distributed engineering teams. - Experience with PostgreSQL administration and performance tuning. - Experience with vector database platforms and retrieval-augmented generation (RAG) architectures. - Experience with developing AI agents, Skills, MCPs, and custom targeted agent profiles. - Hands-on experience using AI coding assistants (GitHub Copilot and/or Claude) and applying them to database automation, scripting, and operational tooling. About Us paragraph: "JPMorganChase, one of the oldest financial institutions, offers innovative financial solutions to millions of consumers, small businesses and many of the world's most prominent corporate, institutional and government clients under the J.P. Morgan and Chase brands. Our history spans over 200 years and today we are a leader in investment banking, consumer and small business banking, commercial banking, financial transaction processing and asset management. We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. Additional details about total compensation and benefits will be provided during the hiring process. We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success. We are an equal opportunity employer and place a high value on diversity and inclusion at our company. We do not discriminate on the basis of any protected attribute, including race, religion, color, national origin, gender, sexual orientation, gender identity, gender expression, age, marital or veteran status, pregnancy or disability, or any other basis protected under applicable law. We also make reasonable accommodations for applicants' and employees' religious practices and beliefs, as well as mental health or physical disability needs. Visit our FAQs for more information about requesting an accommodation. JPMorgan Chase & Co. is an Equal Opportunity Employer, including Disability/Veterans" We need to remove EEO/equal-opportunity boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should strip the EEO statements. That includes sentences about equal opportunity employer, non-discrimination, reasonable accommodations, etc. Also the line "Visit our FAQs for more information about requesting an accommodation." and "JPMorgan Chase & Co. is an Equal Opportunity Employer, including Disability/Veterans". So we need to keep the rest: description of firm, history, leadership, total rewards package, benefits list, etc. But we must not create Benefits section unless specific benefits stated. The About Us paragraph includes benefits list: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. That's specific benefits. So we could create a Benefits section with that list. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (list). So we can include Benefits section. However we also have generic statement about total rewards package etc. We could include Benefits section with the list. Also we have mention of base salary etc but not specific numbers, so we should not create Pay section because it's vague. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, they mention base salary determined based on role, experience, skill set and location, commission-based pay etc. That's still vague but it's stating that there is base salary and possible commission. Is that enough to create a Pay section? It says "competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity". That is some detail about pay structure. Might be enough to include a Pay section. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, albeit generically. I'd lean to include a Pay section with that info. But we must avoid filler like "commensurate with experience". This is not filler; it's actual description. So we can include Pay. Schedule: no mention. Thus sections: Responsibilities, Requirements, Skills, Pay, Benefits, About Us, About Team. We need to use

  • for any list of duties/requirements/benefits. For Pay, it's prose not a list, so

    . Benefits list: we can make

    • . About Us and About Team: prose. Now we need to strip duplicated lines. There's no duplication. Now produce HTML. Let's craft:

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Skills

      • ...
      ...

      Pay

      We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions.

      Benefits

      • Comprehensive health care coverage
      • On-site