Vice President, Senior Engineer

We need to output HTML fragment with sections: About the role? The posting includes "About This Role" then details. We need headings for sections present: About the role (maybe "About the role" heading), Responsibilities (Job Duties), Qualifications, Benefits, Pay, Schedule (if present). Also maybe "Skills"? Not needed. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: navigation, legal, EEO, etc. Must preserve substantive info. We need to include sections only when posting has real specific content. Let's extract: - About the role: The first paragraph after "About This Role Company: BlackRock Financial Management, Inc. Job Title: Vice President, Senior Engineer Location: 400 Howard St San Francisco, CA 94105". That's meta." The "About This Role" likely includes description: "Engineer core services for the next generation Aladdin Container Platform to host cloud native applications at scale. Manage edge routing, load balancing, security, and web asset caching services for our internal and internet-facing applications. Support all phases of the software development lifecycle, including requirements gathering, design, system development, testing, implementation and production support for services and applications to scale system operations. Design and develop core distributed systems and cloud computing infrastructure, including Sybase, MSSQL, Docker, and Kubernetes. Create development environment for developers and build technology to scale system operations. Develop and support tools, frameworks, languages, and core libraries. Build different components of the distributed compute engine that retrieves, transforms, loads, and distributes complex, unstructured and structured reference data into Aladdin, while architecting a scalable, fault- tolerant, and highly available system. Contribute to the open API platform to enable clients to integrate Aladdin into their enterprise." That's essentially the duties. So we could treat that as "Responsibilities". The "Job Duties" heading is present in the posting: "Job Duties:" then list. So we can have a Responsibilities section with that content. Qualifications: The qualifications paragraph with bullet-like list of required experience. Benefits: There's a paragraph: "Additionally, employees are eligible for an annual discretionary bonus, and benefits including healthcare, leave benefits, and retirement benefits." Then later: "Our Benefits To help you stay energized, engaged and inspired, we offer a wide range of benefits including a strong retirement plan, tuition reimbursement, comprehensive healthcare, support for working parents and Flexible Time Off (FTO) so you can relax, recharge and be there for the people you care about." Pay: There's salary range: "For San Francisco, CA Only the salary range for this position is USD$213,512.00 - USD$215,000.00." Also mention discretionary bonus. Schedule: There's hybrid work model description: "Employees are currently required to work at least 4 days in the office per week, with the flexibility to work from home 1 day a week." That's schedule info. We should not include boilerplate like EEO, legal, etc. We need to use

for section headings. Use

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

  for prose. We need to decide what to list as lists. For responsibilities, we could list each duty as

• . For qualifications, list each requirement as
• . For benefits, list each benefit as
• . For pay, maybe just a

  . For schedule, maybe a

  . We must preserve all substantive info; do not invent or summarize away detail. So we need to include all specifics: mention technologies, years of experience, etc. Let's extract responsibilities bullet points from the paragraph: It's a long sentence; we could break into logical items: - Engineer core services for the next generation Aladdin Container Platform to host cloud native applications at scale. - Manage edge routing, load balancing, security, and web asset caching services for internal and internet-facing applications. - Support all phases of the software development lifecycle, including requirements gathering, design, system development, testing, implementation and production support for services and applications to scale system operations. - Design and develop core distributed systems and cloud computing infrastructure, including Sybase, MSSQL, Docker, and Kubernetes. - Create development environment for developers and build technology to scale system operations. - Develop and support tools, frameworks, languages, and core libraries. - Build different components of the distributed compute engine that retrieves, transforms, loads, and distributes complex, unstructured and structured reference data into Aladdin, while architecting a scalable, fault‑tolerant, and highly available system. - Contribute to the open API platform to enable clients to integrate Aladdin into their enterprise. That seems to capture all. Qualifications: Must have Bachelor’s degree in Computer Science, Engineering or related field and five (5) years of experience in the job offered or as an Associate, Analyst or a related role. Must have five (5) years of experience with: - Software development using Go, Java and Python; - Kubernetes and Docker for Containerization; - Software development principles and best practices, including object oriented programming, clean and modular code design, code reviews, testing strategies, version control, and long term maintainability; - Agile software development methodologies; - CI/CD using Azure DevOps and Amazon AWS; - Linux environments and shell scripting; - GitOps workflows including ArgoCD and Flux, and source control management; - Cloud Native concepts and best practices, including containerization, microservices, declarative infrastructure, scalability, resilience, and automation; - Sybase and MSSQL Database Experience. Must have four (4) years of experience with: - Networking and containerization fundamentals, including edge routing, DNS, ingress and network security; - Secrets management, PKI, and certificate lifecycle automation including Vault, cert-manager and cert-based auth, and k8s secrets; - Helm, Kustomize, and manifest management including templating, overlays, and chart design; - Monitoring, alerting, and SLOs including Prometheus, Grafana, dashboards, and alert tuning. We should keep these as list items. Benefits: There's mention of annual discretionary bonus, healthcare, leave benefits, retirement benefits, strong retirement plan, tuition reimbursement, comprehensive healthcare, support for working parents, Flexible Time Off (FTO). Also maybe "benefits including healthcare, leave benefits, and retirement benefits" appears twice. We'll combine unique items. List: - Annual discretionary bonus - Healthcare - Leave benefits - Retirement benefits / strong retirement plan - Tuition reimbursement - Support for working parents - Flexible Time Off (FTO) We could combine retirement benefits and strong retirement plan as one item: "Retirement benefits (including a strong retirement plan)". But we need to preserve detail; we can list both but might duplicate. Safer to list each distinct benefit mentioned: "annual discretionary bonus", "healthcare", "leave benefits", "retirement benefits", "strong retirement plan", "tuition reimbursement", "support for working parents", "Flexible Time Off (FTO)". However "retirement benefits" and "strong retirement plan" are similar; but we can keep both as they appear. Pay: Salary range USD$213,512.00 - USD$215,000.00, plus annual discretionary bonus (already in benefits). Also mention BlackRock operates a pay-for-performance compensation philosophy and total compensation may vary based on role, location, firm, department and individual performance. We'll include that in a

  . Schedule: Hybrid work model: Employees required to work at least 4 days in the office per week, with flexibility to work from home 1 day a week. Some business groups may require more time in the office due to their roles and responsibilities. Also mention hybrid work model designed to enable culture of collaboration and apprenticeship, etc. We'll include that. We must not include boilerplate like "Guidance on AI use for candidates", "About BlackRock", etc. Those are not required sections; we should omit them. We also need to include a short

  for metadata like location? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include location in a short

  maybe before sections. But we already have location in the responsibilities? Actually location is separate: "Location: 400 Howard St San Francisco, CA 94105". We could include that as a

  at top. But we must not repeat job title as heading. So we can start with a

  containing location and maybe company? The company is BlackRock Financial Management, Inc. Could include that as well. We need to output only HTML fragment, no /, no markdown fences. Thus final HTML:

  Location: 400 Howard St, San Francisco, CA 94105

  About the role

  Engineer core services for the next generation Aladdin Container Platform to host cloud native applications at scale. Manage edge routing, load balancing, security, and web asset caching services for our internal and internet-facing applications. Support all phases of the software development lifecycle, including requirements gathering, design, system development, testing, implementation and production support for services and applications to scale system operations. Design and develop core distributed systems and cloud computing infrastructure, including Sybase, MSSQL, Docker, and Kubernetes. Create development environment for developers and build technology to scale system operations. Develop and support tools, frameworks, languages, and core libraries. Build different components of the distributed compute engine that retrieves, transforms, loads, and distributes complex, unstructured and structured reference data into Aladdin, while architecting a scalable, fault‑tolerant, and highly available system. Contribute to the open API platform to enable clients to integrate Aladdin into their enterprise.

  But we could also treat that as Responsibilities. However the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have either About the role or Responsibilities. Since we have both a generic description and a Job Duties list, we could combine them under Responsibilities. But we need to avoid duplication. The "About This Role" paragraph is essentially the duties. The "Job Duties:" heading then repeats similar content. To avoid duplication, we could just have a Responsibilities section with the list items (the bullet list). That would capture all duties. The "About This Role" paragraph may be considered filler? But it's substantive. However we can incorporate its content into the list items; we already captured duties from that paragraph. So we can skip a separate About the role section. Thus we will have sections: Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to use

  for each. Responsibilities:

  • ... each duty

  Qualifications: We'll have maybe a

  for the degree and 5 years experience, then two

  for 5 years and 4 years experience. Benefits:
  • ... each benefit
  Pay:

  Salary range: USD$213,512.00 - USD$215,000.00. Employees are eligible for an annual discretionary bonus. BlackRock operates a pay-for-performance compensation philosophy; total compensation may vary based on role, location, firm, department and individual performance.

  Schedule:

  Hybrid work model: Employees are required to work at least 4 days in the office per week, with the flexibility to work from home 1 day a week. Some business groups may require more time in the office due to their roles and responsibilities.

  We should also include location maybe as a

  before sections. Check for any boilerplate: We omitted EEO, legal, AI guidance, About BlackRock, etc. Now ensure we didn't miss any substantive info: The responsibilities list we created includes