Senior Data Developer - Assistant Vice President
or drop it. So we could include a short p with posting close date? Might be considered minor metadata. Could drop. "Automated Processing and AI ..." (boilerplate, remove). "Citi is an equal opportunity employer..." (EEO boilerplate, remove). Thus we need sections: - About the role (intro paragraph) - Responsibilities (list) - Requirements (maybe combine Required Skills And Qualifications) - Qualifications (maybe Qualification / Education) - Skills (maybe Preferred Skills And Qualifications? Or we could treat Required Skills as Requirements, Preferred as Skills. Or we could combine Required and Preferred into Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - About the role: intro paragraph. - Responsibilities: the bullet list under "Key Responsibilities". - Requirements: maybe the "Required Skills And Qualifications" bullet list. - Qualifications: the "Qualification / Education" bullet. - Skills: the "Preferred Skills And Qualifications" bullet list. - Benefits: paragraph about benefits. - Pay: salary range. - Schedule: maybe Time Type: Full time (but schedule maybe not given). Could we include Schedule? Not provided. So we should not create Schedule section if no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated (salary range). Benefits is stated. Schedule? Not given besides "Time Type: Full time". That's maybe schedule? Could be considered schedule (full time). Might be considered schedule content. The instruction: include a section ONLY when the posting has real, specific content for it. "Time Type: Full time" is specific content. So we could include Schedule section with that. But we also have "Primary Location: New York New York United States". That's location, not a heading we have. Could fold into About the role or a short p. Probably we can include location in About the role paragraph or a separate short p. Since we must preserve all substantive info, we should include location somewhere. Could add a short p after About the role: "Location: New York, NY, USA." Or incorporate. We must not repeat job title. No headings for minor metadata. Thus final HTML:
About the role
We are seeking a highly accomplished Java engineer to join our Realtime Risk Data team. This role is at the forefront of architecting, leading, and significantly enhancing our comprehensive real-time risk data acquisition, processing, and distribution framework. You will serve as a technical thought leader, driving the strategic adoption and implementation of cutting-edge streaming technologies such as Apache Kafka for high-throughput data ingestion, Apache Flink for complex event processing and real-time analytics, and Apache Pinot for ultra-low-latency OLAP queries on large datasets. You will also oversee the management of petabyte-scale datasets on S3, enabling efficient querying via Trino. This role demands deep technical expertise, a strategic mindset, and the ability to mentor and guide engineering teams in designing, developing, and optimizing mission-critical, high-performance real-time data solutions that directly impact global financial operations. Location: New York, NY, USA.
Responsibilities
- Architectural Leadership: Serve as the principal architect for scalable, high-performance Java-based real-time data solutions, ensuring robust design for high availability, fault tolerance, and resilience for both real-time and EOD risk processes.
- Strategic Implementation: Drive the strategic implementation and optimization of distributed stream processing frameworks (Apache Kafka, Apache Flink) and real-time data storage technologies (Apache Pinot) for ultra-low-latency analytics and complex event processing.
- Data Pipeline Mastery: Lead the end-to-end design, development, and operation of real-time streaming data pipelines, integrating with large-scale object storage solutions like S3 and analytics engines such as Trino.
- Technical Excellence & Mentorship: Champion continuous improvement in data reliability, efficiency, and scalability. Establish and enforce best practices for code quality, performance optimization, and system resilience through hands-on leadership and thorough peer code reviews. Mentor and technically guide senior and lead developers.
- SDLC Ownership: Drive significant contributions across all phases of the Agile software development lifecycle, from architectural vision and detailed design to implementation, deployment, monitoring, and ongoing support for critical real-time data systems.
- Cross-Functional Collaboration: Collaborate strategically with business analysts, product managers, quality assurance teams, and other engineering leads to ensure the delivery of seamlessly integrated, high-impact technology solutions that align with business objectives and architectural standards.
- Innovation & Research: Stay abreast of industry trends and emerging technologies in real time data processing, distributed systems, and cloud-native architectures, evaluating and proposing their adoption were beneficial.
Requirements
- Senior Data Engineering Expertise: 6+ years of progressive experience in data engineering and software development, with a significant focus on building high-performance, large scale distributed systems.
- Java Mastery: Expert-level command of Java (version 11 or higher) with a deep understanding of concurrent programming, multithreading, advanced OOP concepts, design patterns, and performance tuning.
- Real-time Streaming Core: Proven, hands-on production experience and deep architectural understanding of:
- Apache Kafka or related technologies: For high-throughput, fault-tolerant message queuing and streaming.
- Apache Flink or related technologies: For advanced real-time stream processing, complex event processing (CEP), and stateful computations.
- Apache Pinot or related technologies: For ultra-low-latency OLAP queries on streaming data.
- Distributed Systems Architecture: Strong expertise in designing and implementing highly available, scalable, and resilient distributed systems.
- Data Storage & Querying: Extensive experience with large-scale data storage solutions (e.g., S3, HDFS) and distributed query engines (e.g., Trino/Presto, Spark SQL).
- SQL Proficiency: Advanced SQL knowledge with experience in optimizing complex queries for large datasets.
- Agile Leadership: Demonstrated experience leading technical initiatives and teams within an Agile software development environment.
- Communication & Problem Solving: Exceptional communication, analytical, and problem-solving skills, with the ability to articulate complex technical concepts to diverse audiences and drive consensus on architectural decisions.
Qualifications
- Advanced Degree: Strong academic record, ideally with a Master's in Computer Science, Electrical Engineering, or a related technical/quantitative discipline.
Skills
- Cloud-Native Data Ecosystems: Experience with cloud-native data services on platforms like AWS, Azure, or GCP, particularly related to streaming and real-time analytics.
- Container Orchestration: Hands-on experience with containerization and orchestration technologies such as Kubernetes and OpenShift for deploying and managing real-time data applications.
- API Development: Experience in designing and implementing high-performance RESTful APIs and event-driven microservices architectures.
- Performance Engineering: Deep understanding and experience with performance tuning, profiling, and optimization of real-time streaming applications and data stores.
- Financial Domain Knowledge: Strong understanding of financial derivatives, fixed income products, and risk management concepts from a technical data perspective.
- Technical Leadership & Mentoring: A proven track record of mentoring junior to senior engineers, fostering technical growth, and building high-performing engineering teams.
- Data Governance & Security: Experience with data governance, data quality, and security best practices in real-time data environments.
- Global Team Experience: Experience working effectively within a geographically distributed, global development team.
Benefits
In addition to salary, Citi’s offerings may also include, for eligible employees, discretionary and formulaic incentive and retention awards. 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.
Pay
Primary Location Full Time Salary Range: $121,200.00 - $181,800.00
Schedule
Time Type: Full time
We need to ensure no extra sections like "Job Family Group" etc. We could fold those into About the role or a short p. But we already included location. Could also add job family etc. But not required headings. The instruction: preserve ALL substantive information. So we should include Job Family Group, Job Family, Time Type (already in Schedule), Primary Location (we have location). We could add a short p after About the role: "Job Family Group: Technology; Job Family: Applications Development." But we already have Schedule for Time Type. Could add a p: "Job Family Group: Technology; Job Family: Applications Development." That preserves info. Let's add that p after About the role paragraph. Thus final HTML:About the role
We are seeking a highly accomplished Java engineer to join our Realtime Risk Data team. This role is at the forefront of architecting, leading, and significantly enhancing our comprehensive real-time risk data acquisition, processing, and distribution framework. You will serve as a