Senior Low Latency Java Developer, Equities Connectivity, Vice President

We need to output HTML fragment with sections: About the role? The posting includes description about Citi, Equities Technology, Role Overview, Responsibilities, Recommended Qualifications, Education, Salary range, Benefits, etc. We must not repeat job title as heading. 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. So we need to decide which sections to include. We have content: Role Overview (description). Could map to "About the role". Responsibilities: list. Recommended Qualifications: could be "Requirements" or "Qualifications". Education: maybe part of Qualifications. Salary range: Pay. Benefits: Benefits. Skills: maybe "Skills". Schedule: not given (full time). Could include Schedule if we have info: "Time Type: Full time". That's schedule info. So we can include Schedule section with full time. We must not include placeholder like "commensurate with experience". We have actual salary range and benefits description. We must remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions, etc. Also remove "Job Family Group", "Job Family", "Time Type", "Primary Location", "Primary Location Full Time Salary Range", etc? Actually we need to preserve substantive information: location maybe not required as heading but could be included in a short paragraph? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and maybe job family in a short paragraph under About the role or separate? Probably better to include a short

with location and job family etc. But we must not create headings for those. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

...

Skills

• ...
...

Benefits

• ...
...

Pay

$142,320.00 - $213,480.00 per year

Schedule

Full time

We need to ensure we preserve all substantive information: The role overview description, responsibilities list, qualifications (6-10 years experience, low latency Java, etc), education (Bachelor's degree), skills (maybe list from responsibilities?), benefits (medical, dental & vision coverage; 401(k); life, accident, and disability insurance; wellness programs; paid time off packages). Also mention discretionary and formulaic incentive and retention awards. We need to not invent or summarize away detail. So we must keep the exact details. Let's extract substantive paragraphs. From posting: "Equities Technology Equities Technology at Citi is undertaking a bold, multi‑year transformation to build a best‑in‑class global platform across execution, prime, clearing and cross‑product margining. We are re‑engineering our technology estate to achieve world‑leading performance and resiliency, enabling new capabilities in advanced execution, global market connectivity, and modernized post‑trade, clearing and margin processes. Our ambition is to deliver a seamlessly integrated, highly automated platform that drives outstanding client outcomes and accelerates growth across our global franchise. As part of the team, you’ll collaborate closely with high‑caliber engineers and deeply engaged business and product partners - working together to define and deliver the next generation of Equities technology at Citi." Then "Role Overview Citi's Equities Technology organization is seeking an experienced, hands-on engineer to join the Equities Electronic-Execution (Electronic Trading) technology team. The person in this role will be responsible for the development and operational excellence of Citi's next-generation low-latency connectivity platforms. This encompasses critical components including low-latency Exchange & Client Connectivity, Order Management, Algo access as well as Direct Market Access (DMA). The successful candidate will join a cross-functional team of engineers who partner with product development, quantitative research, technology infrastructure, and production support for the NAM region and beyond. This role requires an engineer who can align closely with the global strategy, drive execution regionally as well as within a global team and platform while helping to inspire a culture of innovation and engineering excellence." That's about the role. Responsibilities list (starting after "Responsibilities:"): each line begins with a verb. List: - Partner with various business and technology stakeholders to ensure appropriate integration of functions to meet goals as well as identify and define necessary system enhancements to deploy new products and process improvements - Resolve variety of high impact problems/projects through in-depth evaluation of complex business processes, system processes, and industry standards - Champion and enforce best practices in software development, including automated testing, quality engineering, and performance optimization. Continuously enhance testing frameworks and development environments to ensure platform reliability at scale. - Develop comprehensive knowledge of how areas of business, such as architecture and infrastructure, integrate to accomplish business goals. Provide in-depth analysis with interpretive thinking to define issues and develop innovative solutions - Help provide mentorship for junior developers within a geographically distributed team of high-performing engineers, fostering a culture of collaboration, accountability, and continuous improvement. - Leverage Citi's suite of AI-powered development tools throughout the Software Development Life Cycle (SDLC) to maximize productivity, code quality, and innovation. - Contribute to the design, creation and maintenance of robust, common solutions for platform monitoring, reconciliation, application recovery, and other essential support functions to guarantee production stability. - Appropriately assess risk when business decisions are made, demonstrating particular consideration for the firm's reputation and safeguarding Citigroup, its clients and assets, by driving compliance with applicable laws, rules and regulations, adhering to Policy, applying sound ethical judgment regarding personal behavior, conduct and business practices, and escalating, managing and reporting control issues with transparency. That's responsibilities. Recommended Qualifications: - 6-10 years of relevant experience in Apps Development in financial technology with experience in low latency development in Java - Experience of low-latency system design, including performance optimization, concurrency, high-throughput architecture, and network protocols. - Experience in managing and implementing successful projects - Ability to adjust priorities quickly as circumstances dictate - Demonstrated leadership and project management skills - Consistently demonstrates clear and concise written and verbal communication Education: - Bachelor’s degree/University degree or equivalent experience Also note: "This job description provides a high-level review of the types of work performed. Other job-related duties may be assigned as required." That's boilerplate maybe can be omitted? It's not a heading but could be considered generic; but it's substantive? It's a disclaimer. Might be considered boilerplate; but it's not cookie/navigation/legal/EEO. It's a generic statement. Might be okay to keep but it's not needed. Probably safe to omit as it's not specific detail. Pay: "Primary Location Full Time Salary Range: $142,320.00 - $213,480.00 In addition to salary, Citi’s offerings may also include, for eligible employees, discretionary and formulaic incentive and retention awards." Benefits: "Citi offers competitive employee benefits, including: medical, dental & vision coverage; 401(k); life, accident, and disability insurance; and wellness programs. Citi also offers paid time off packages, including planned time off (vacation), unplanned time off (sick leave), and paid holidays. For additional information regarding Citi employee benefits, please visit citibenefits.com. Available offerings may vary by jurisdiction, job level, and date of hire." We should keep that. Skills: The posting has "Most Relevant Skills Please see the requirements listed above." and "Other Relevant Skills For complementary skills, please see above and/or contact the recruiter." That's not specific; we could omit Skills section because no specific skills listed besides those in qualifications. But we could still include a Skills section that lists the skills from qualifications? However the instruction: "Prefer a few substantive sections over many thin ones." Might be okay to combine Skills into Qualifications. But we have separate headings allowed: Skills. If we include Skills, we need specific content. We could list skills: Low latency development, Java, performance optimization, concurrency, high-throughput architecture, network protocols, project management, leadership, communication, mentorship, AI-powered tools, etc. But that would be summarizing from qualifications; might be considered inventing? It's derived from qualifications, but still specific. However we risk adding content not explicitly listed as a separate "Skills" section. The posting didn't have a separate skills list; it said "Most Relevant Skills Please see the requirements listed above." So we could treat that as referencing the qualifications; we could omit Skills section entirely to avoid thin section. Schedule: we have "Time Type: Full time". So we can include Schedule section with "Full time". Pay: we have salary range and discretionary awards. Benefits: as above. About the role: combine the introductory paragraphs about Equities Technology and Role Overview. We also might include location and job family as a short paragraph under About the role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph with location and job family etc. Let's include a short

after About the role maybe: "Location: Jersey City, New Jersey, United States. Job Family: Applications Development (Technology)." That's minor metadata. Now produce HTML. We need to ensure we use

for each section heading. Use

• for lists. Use

  for prose. We must not include any markdown fences. Let's craft. Section About the role: combine two paragraphs. Paragraph 1: Equities Technology description. Paragraph 2: Role Overview. Then maybe a short metadata paragraph. Then Responsibilities: list each bullet as

• . Then Requirements: maybe we call it "Requirements" and list the qualifications bullets. Education: could be part of Requirements or separate Qualifications. Since we have both Recommended Qualifications and Education, we could make a "Qualifications" section that includes both experience and education. Or we could have Requirements (experience) and Qualifications (education). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (experience) and Qualifications (education). Let's do that. Thus:

  Requirements

  • 6-10 years of relevant experience in Apps Development in financial technology with experience in low latency development in Java
  • Experience of low-latency system design, including performance optimization, concurrency, high-throughput architecture, and network protocols.
  • Experience in managing and implementing successful projects
  • Ability to adjust priorities quickly as circumstances dictate
  • Demonstrated leadership and project management skills
  • Consistently demonstrates clear and concise written and verbal communication

  Qualifications

  Bachelor’s degree/University degree or equivalent experience

  Alternatively we could combine but fine. Benefits: list each benefit as
• . Pay:

  $142,320.00 - $213,480.00 per year. In addition to salary, Citi’s offerings may also include, for eligible employees, discretionary and formulaic incentive and retention awards.

  Schedule:

  Full time

  We should also include location/job family maybe as a short p after About the role. Let's write. Check for any boilerplate: we