Trading Analytics Developer, Quantitative Trading

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Benefits section with details: Competitive salary, Attractive annual leave entitlement including: birthday, work anniversary, 401(k) plan with employer match, Eligible for company-sponsored group health, dental, vision, and life/disability insurance, Work Flexibility Adoption. Flexi-work hour and hybrid set-up, Aspire career alternatives through us - our internal mobility program offers employees a new scope. Also repeated lines. So Benefits section exists. Pay: Not explicitly stated; only "Competitive salary" is mentioned under Benefits. That is a pay detail but not a specific number. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary" which is a pay statement. However they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive salary" could be considered vague but it's still a statement about pay. Might be acceptable? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Competitive salary, which is a statement about pay. So we could include a Pay section with that line. However they also said "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they have separate headings list. We could include Benefits section that includes compensation details. But they said to include a section ONLY when the posting has real, specific content for it. The posting does have content about benefits, including competitive salary, leave, 401k, insurance, flexibility, internal mobility. So Benefits section is appropriate. Pay section maybe redundant if we already have salary in Benefits. But they said to not create Pay unless posting actually states them. It does state competitive salary, but that's also in Benefits. Might still be okay to have Pay section with that line. However to avoid thin sections, maybe we omit Pay and include salary detail within Benefits. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Pay and include salary in Benefits. Schedule: The posting mentions "Work Flexibility Adoption. Flexi-work hour and hybrid set-up". That's schedule info. Could be included in Benefits or a Schedule section. Since schedule info is present, we could create a Schedule section. But again we want few sections. Could combine schedule into Benefits as well. However they gave separate headings list; we can choose to include Schedule if we have content. The posting does mention flexible work hours and hybrid set-up. That's schedule. So we could include a Schedule section with that content. But then Benefits would still have other benefits. That seems reasonable: Benefits (salary, leave, 401k, insurance, internal mobility) and Schedule (flexi-work hour, hybrid). However the posting repeats "Work Flexibility Adoption. Flexi-work hour and hybrid set-up Aspire career alternatives through us - our internal mobility program offers employees a new scope." That appears twice. We'll deduplicate. Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (first paragraph). Responsibilities (list). Requirements (list). Qualifications (Preferred Qualifications). Skills? The posting includes skill sets within Requirements; but we could separate Skills section if there is explicit skills list. There's no separate "Skills" heading; but we could extract skills like Python, Java, Kafka, Flink, Spark, SQL, etc. However the instruction: "Prefer a few substantive sections over many thin ones." Might combine Skills into Requirements or Qualifications. Since there is no explicit Skills section, we might omit Skills heading. Similarly Qualifications: we have Preferred Qualifications; we could treat that as Qualifications section. Requirements: Mandatory Foundations. So we have Requirements and Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Possibly also include "Skills" if we want to separate but not needed. We must not repeat job title. Use

for section headings. Use

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

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from Responsibilities, Requirements, Preferred Qualifications, Benefits, etc. Must not drop any detail. Must not add extra. We need to be careful to not include boilerplate like EEO, legal, etc. Also remove duplicated lines. Let's extract content. Original posting: "We are seeking an experienced Trading Analytics Developer to join our Quant Trading team and play a pivotal role in advancing our data and AI infrastructure. This role combines traditional quantitative development with cutting-edge AI platform engineering, focusing on building robust, scalable systems that serve both data analytics and artificial intelligence workloads. The ideal candidate will bridge the gap between high-performance trading systems and modern AI capabilities, ensuring reliability, performance, and actionable insights across both domains." That's About the role. Job Responsibilities: - Data Platform & Analytics - Design, build, and operate high throughput batch and streaming data pipelines using Kafka, Flink, and ETL technologies - Design and build unified analytics engine designed for processing large-scale data using Apache Spark and related tools - Develop and optimize analytical data models for time-series, financial metrics, and trading activity - Implement and manage analytical databases (ClickHouse, MongoDB, BigQuery, Snowflake, or similar) with cost-aware architecture - Build idempotent data pipelines with robust backfill and reconciliation capabilities - Create comprehensive monitoring for data quality, freshness, and pipeline reliability - AI Platform Development - Design, build, and operate internal AI platforms serving multiple trading teams - Build reusable AI tooling including standardized RAG pipelines, prompt management, and self-service workflows - Create and maintain agent systems using modern frameworks (LangGraph, A2A, MCP) with focus on controllability and auditability Job Requirements Mandatory Foundations: - 5+ years production experience with both Python and Java in high-performance environments - Strong software engineering fundamentals: system design, data structures, algorithms, data integrity, accuracy and performance optimization - Expertise in Linux, Github, and modern CI/CD practices - Proven experience with AWS cloud services and Kubernetes orchestration - Comfort working with large-scale, complex datasets in financial/trading contexts - Data Platform Expertise - Advanced SQL with window functions and query optimization, realtime data synchronization together with database design and infrastructure support - Experience with data workflow and messaging orchestration (Airflow, Jenkins, AMPS etc.) - Metric design and implementation for trading analytics (PnL, risk, balance and trade reconciliation, backfill and performance tuning) - Time-series data visualization with Grafana, TradingView, web-based interactive dashboards and BI tools etc - Kafka, Flink, and event processing in production environments - AI Platform Capabilities - Retrieval system evaluation methodologies and quality frameworks - RAG pipeline architecture and optimization techniques - LLMOps practices including model lifecycle and prompt management - Experience with AI agent frameworks in production settings like A2A and MCP Preferred Qualifications: - Financial/Trading Domain Experience in trading systems, quantitative finance, or financial technology - Understanding of market data, data subscription using Rest API / Web Socket - Knowledge of cryptocurrency markets, defi and related technologies - Professional Attributes - Excellent problem-solving skills with ability to perform under pressure - Strong communication skills for cross-team collaboration - Proactive approach to system reliability and performance optimization - Continuous learning mindset in rapidly evolving AI/ML landscape - Balance of practical engineering rigor with innovative solution development Life @ Crypto.com (some fluff) but we need to extract Benefits section later. Benefits: - Competitive salary - Attractive annual leave entitlement including: birthday, work anniversary - 401(k) plan with employer match - Eligible for company-sponsored group health, dental, vision, and life/disability insurance - Work Flexibility Adoption. Flexi-work hour and hybrid set-up - Aspire career alternatives through us - our internal mobility program offers employees a new scope. - Our Crypto.com benefits packages vary depending on region requirements, you can learn more from our talent acquisition team. (This is maybe boilerplate but still substantive? It's a note about variation; we could keep it but it's somewhat generic. Might be considered boilerplate? It's about benefits varying by region; could keep but it's not specific. Might be okay to keep as it's part of benefits description. However we should avoid filler like "varies". The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "Our Crypto.com benefits packages vary depending on region requirements" includes "vary". That's a placeholder-ish. Might be considered filler. Safer to omit that line. Also there is repeated "Work Flexibility Adoption. Flexi-work hour and hybrid set-up Aspire career alternatives through us. Our internal mobility program can offer employees a diverse scope." We'll deduplicate. Now About Crypto.com description: that's boilerplate about company; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Crypto.com" paragraph is likely boilerplate but could be considered substantive? It's describing the company; not directly about the role. The instruction says remove boilerplate; likely we should remove that. Also the EEO statement etc. Remove. Thus final HTML will have sections:

  About the role

  We are seeking an experienced Trading Analytics Developer to join our Quant Trading team and play a pivotal role in advancing our data and AI infrastructure. This role combines traditional quantitative development with cutting-edge AI platform engineering, focusing on building robust, scalable systems that serve both data analytics and artificial intelligence workloads. The ideal candidate will bridge the gap between high-performance trading systems and modern AI capabilities, ensuring reliability, performance, and actionable insights across both domains.

  Responsibilities

  • Design, build, and operate high throughput batch and streaming data pipelines using Kafka, Flink, and ETL technologies
  • Design and build unified analytics engine designed for processing large-scale data using Apache Spark and related tools
  • Develop and optimize analytical data models for time-series, financial metrics, and trading activity
  • Implement and manage analytical databases (ClickHouse, MongoDB, BigQuery, Snowflake, or similar) with cost-aware architecture
  • Build idempotent data pipelines with robust backfill and reconciliation capabilities
  • Create comprehensive monitoring for data quality, freshness, and pipeline reliability
  • Design, build, and operate internal AI platforms serving multiple trading teams
  • Build reusable AI tooling including standardized RAG pipelines, prompt management, and self-service workflows
  • Create and maintain agent systems using modern frameworks (LangGraph, A2A, MCP) with focus on controllability and auditability

  Requirements

  • 5+ years production experience with both Python and Java in high-performance environments
  • Strong software engineering fundamentals: system design, data structures, algorithms, data integrity, accuracy and performance optimization
  • Expertise in Linux, Github,