Senior Software Engineer, Quant - hybrid in Chicago, IL, Overland Park, KS or NYC
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits only if posting actually states them.
We have content: Job Description includes intro paragraphs about Cboe, role overview, responsibilities list, ideal candidate list (skills, experience, education), Benefits And Perks list, More About Cboe (maybe not needed?), Equal Employment Opportunity (boilerplate remove), visa sponsorship note (maybe keep? It's legal but maybe considered boilerplate? It's about eligibility; could be considered relevant but maybe it's boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The visa sponsorship note is legal; likely remove. Salary Ranges section is pay info, we should include Pay section. Schedule: they mention "this role follows a four day in office work model." That's schedule info, so include Schedule section.
We need to decide sections: About the role (role overview), Responsibilities, Requirements (maybe combine ideal candidate?), Qualifications (education), Skills (maybe technical skills), Benefits, Pay, Schedule.
We must not create sections with filler. Ensure each section has substantive content.
Let's extract:
About the role: The role overview paragraph: "Cboe Data Vantage is looking for an experienced software engineer who is excited about combining strong engineering skills with financial quantitative analysis. The role focuses on modeling a diverse set of financial instruments and includes portfolio analysis. You will work within a team of seasoned developers, technologists, and quants all with deep experience in financial markets and financial modeling. Data Vantage’s clients are among the largest and most prestigious financial institutions and rely on our expertise in this space."
That's substantive.
Responsibilities: bullet list after "Your responsibilities will be:" includes many items.
Ideal candidate: list of qualifications: 3+ years in Java or C#, 1+ year in C++ preferred, background in financial markets, derivatives pricing, risk analysis, equity derivatives experience a plus, ability to explain complex system, ability to work as self-starter, education: minimum bachelor's in STEM, master's preferred.
We could split into Requirements (experience), Qualifications (education), Skills (technical). But we can also combine. However instruction: prefer few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Requirements (covers experience, skills, education), Benefits, Pay, Schedule.
But we also have Benefits list.
Pay: Salary ranges.
Schedule: four day in-office work model.
We need to avoid duplication. Also remove duplicated lines: there may be duplicate sentences? Not seeing.
We must not include boilerplate like "Equal Employment Opportunity", "More About Cboe Global Markets", "Learn more about life at Cboe on our website and LinkedIn." Those are maybe not boilerplate but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "More About Cboe Global Markets" is not exactly those but could be considered fluff; but it's substantive about company culture. Might keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that unless it's considered boilerplate. It's not EEO, not legal, not scam-warning. It's about company culture. Could keep as part of About the role? But we already have About the role section; we could incorporate that into About the role or maybe a separate section "About Cboe". However we have no heading for About Cboe in the list; we could add a section heading "About Cboe" but not in the prescribed list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those headings. The "More About Cboe Global Markets" could go under About the role or maybe we can omit as it's not strictly required? But it's substantive about company culture; maybe we can incorporate into About the role.
We'll create sections:
About the role
... (combining role overview and maybe more about Cboe)
Responsibilities
- ... each responsibility
Requirements
- ... experience requirements (Java/C#, C++, financial markets, ability to explain, self-starter, etc.)
Qualifications
Education: Minimum of a bachelor’s degree in a STEM field, but a master’s degree preferred.
Alternatively combine education into Requirements. But we have separate Qualifications heading allowed.
We could also have Skills heading for technical skills (Java/C#, C++, CUDA, parallel/multithreaded). But we already have experience.
Given we want few sections, maybe we combine Requirements and Qualifications into one Requirements section. But we have both headings allowed; we can use both if substantive.
Let's decide: Use About the role, Responsibilities, Requirements (experience & skills), Qualifications (education), Benefits, Pay, Schedule.
Now extract content:
About the role: combine role overview paragraph and maybe the intro about Cboe? The intro: "Building trusted markets — powered by our people At Cboe Global Markets, we inspire our people to solve complex challenges together because what we do matters. We provide the financial infrastructure that powers the global economy. As a leading provider of market infrastructure and tradable products, Cboe delivers cutting-edge trading, clearing and investment solutions to market participants around the world. We’re building meaningful ways to support professional and personal development while strengthening the trust we’ve earned as a global market leader. Our teams are empowered to share ideas, actively pursue them and bring on a challenge. As champions of internal mobility and access to opportunity, we encourage our people to “go for it” and equip our managers with the training to coach their teams to the next level. We strive to provide employees a safe space to network, share ideas and create opportunities. To support strong partnership and team connection, this role follows a four day in office work model."
That's a lot of fluff but it's about company culture and work model. The schedule info is separate; we could keep some of that in About the role but schedule will be separate. The work model mention could be moved to Schedule section. So we can keep About the role as the role overview paragraph only (the paragraph after Role Overview). That seems sufficient.
Responsibilities list:
- Develop, optimize, and debug real-time financial analytics software
- Evaluate, tune, and improve model performance, stability, and accuracy
- Analyze market data, derived market data, and reference data
- Collaborate closely with our reference data, real-time data, and historical data teams
- Provide 2nd level support for production applications developed by the team.
- Respond to customer questions regarding our analytics and models
- Write technical specifications, project plans, and documentation
- Regular communication with senior managers and technical colleagues
- Work with sales team to support presales engagements
Requirements (experience & skills):
- 3+ years in Java or C# (or equivalent), including understanding of parallel and multithreaded design patterns.
- 1+ year in C++ preferred — our system is primarily Java, but performance-critical calculations run in C/C++ and CUDA
- Background in financial markets, derivatives pricing, and/or risk analysis.
- Equity derivatives experience is a plus.
- Ability to explain a complex software system end-to-end, from inputs to output, including its design rationale and business value
- Ability to work as a self-starter; take ownership of projects from start to finish; develop requirements and specifications; QA testing, documentation and production release
Qualifications (education):
- Minimum of a bachelor’s degree in a STEM field, but a master’s degree preferred.
Benefits list:
- Medical Coverage
- Prescription Drug Coverage
- Additional Medical Benefit
- Dental Coverage
- Vision Coverage
- 401K or Pension Company Match
- Spending Accounts
- Life and AD&D Insurance
- Retirement Savings Plan
- Employee Stock Purchase Plan (ESPP)
- Voluntary & Additional Benefits
- Paid Time Off
Pay:
- Anticipated base salary range: $119,000-$154,000 in Kansas, $130,900-$169,400 in Chicago, and $148,750-$192,500 in New York, with actual compensation determined by job‑related factors such as skills, relevant experience, education, internal alignment, and location. This role may also be eligible for annual incentive compensation and, where applicable, participation in Cboe's long-term equity programs.
Schedule:
- This role follows a four day in office work model.
We must not include filler like "commensurate with experience". Not present.
Now produce HTML fragment. Use for each section heading. Use - for lists. Use
for prose.
We need to ensure we don't include any markdown fences. Just raw HTML.
Let's craft:
About the role
Cboe Data Vantage is looking for an experienced software engineer who is excited about combining strong engineering skills with financial quantitative analysis. The role focuses on modeling a diverse set of financial instruments and includes portfolio analysis. You will work within a team of seasoned developers, technologists, and quants all with deep experience in financial markets and financial modeling. Data Vantage’s clients are among the largest and most prestigious financial institutions and rely on our expertise in this space.
Responsibilities
- Develop, optimize, and debug real-time financial analytics software
- Evaluate, tune, and improve model performance, stability, and accuracy
- Analyze market data, derived market data, and reference data
- Collaborate closely with our reference data, real-time data, and historical data teams
- Provide 2nd level support for production applications developed by the team.
- Respond to customer questions regarding our analytics and models
- Write technical specifications, project plans, and documentation
- Regular communication with senior managers and technical colleagues
- Work with sales team to support presales engagements
Requirements
- 3+ years in Java or C# (or equivalent), including understanding of parallel and multithreaded design patterns.
- 1+ year in C++ preferred — our system is primarily Java, but performance-critical calculations run in C/C++ and CUDA
- Background in financial markets, derivatives pricing, and/or risk analysis.
- Equity derivatives experience is a plus.
- Ability to explain a complex software system end-to-end, from inputs to output, including its design rationale and business value
- Ability to work as a self-starter; take ownership of projects from start to finish; develop requirements and specifications; QA testing, documentation and production release
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits only if posting actually states them. We have content: Job Description includes intro paragraphs about Cboe, role overview, responsibilities list, ideal candidate list (skills, experience, education), Benefits And Perks list, More About Cboe (maybe not needed?), Equal Employment Opportunity (boilerplate remove), visa sponsorship note (maybe keep? It's legal but maybe considered boilerplate? It's about eligibility; could be considered relevant but maybe it's boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The visa sponsorship note is legal; likely remove. Salary Ranges section is pay info, we should include Pay section. Schedule: they mention "this role follows a four day in office work model." That's schedule info, so include Schedule section. We need to decide sections: About the role (role overview), Responsibilities, Requirements (maybe combine ideal candidate?), Qualifications (education), Skills (maybe technical skills), Benefits, Pay, Schedule. We must not create sections with filler. Ensure each section has substantive content. Let's extract: About the role: The role overview paragraph: "Cboe Data Vantage is looking for an experienced software engineer who is excited about combining strong engineering skills with financial quantitative analysis. The role focuses on modeling a diverse set of financial instruments and includes portfolio analysis. You will work within a team of seasoned developers, technologists, and quants all with deep experience in financial markets and financial modeling. Data Vantage’s clients are among the largest and most prestigious financial institutions and rely on our expertise in this space." That's substantive. Responsibilities: bullet list after "Your responsibilities will be:" includes many items. Ideal candidate: list of qualifications: 3+ years in Java or C#, 1+ year in C++ preferred, background in financial markets, derivatives pricing, risk analysis, equity derivatives experience a plus, ability to explain complex system, ability to work as self-starter, education: minimum bachelor's in STEM, master's preferred. We could split into Requirements (experience), Qualifications (education), Skills (technical). But we can also combine. However instruction: prefer few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Requirements (covers experience, skills, education), Benefits, Pay, Schedule. But we also have Benefits list. Pay: Salary ranges. Schedule: four day in-office work model. We need to avoid duplication. Also remove duplicated lines: there may be duplicate sentences? Not seeing. We must not include boilerplate like "Equal Employment Opportunity", "More About Cboe Global Markets", "Learn more about life at Cboe on our website and LinkedIn." Those are maybe not boilerplate but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "More About Cboe Global Markets" is not exactly those but could be considered fluff; but it's substantive about company culture. Might keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that unless it's considered boilerplate. It's not EEO, not legal, not scam-warning. It's about company culture. Could keep as part of About the role? But we already have About the role section; we could incorporate that into About the role or maybe a separate section "About Cboe". However we have no heading for About Cboe in the list; we could add a section heading "About Cboe" but not in the prescribed list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those headings. The "More About Cboe Global Markets" could go under About the role or maybe we can omit as it's not strictly required? But it's substantive about company culture; maybe we can incorporate into About the role.
We'll create sections:
About the role
About the role
... (combining role overview and maybe more about Cboe)
Responsibilities
- ... each responsibility
Requirements
- ... experience requirements (Java/C#, C++, financial markets, ability to explain, self-starter, etc.)
Qualifications
Education: Minimum of a bachelor’s degree in a STEM field, but a master’s degree preferred.
Alternatively combine education into Requirements. But we have separate Qualifications heading allowed. We could also have Skills heading for technical skills (Java/C#, C++, CUDA, parallel/multithreaded). But we already have experience. Given we want few sections, maybe we combine Requirements and Qualifications into one Requirements section. But we have both headings allowed; we can use both if substantive. Let's decide: Use About the role, Responsibilities, Requirements (experience & skills), Qualifications (education), Benefits, Pay, Schedule. Now extract content: About the role: combine role overview paragraph and maybe the intro about Cboe? The intro: "Building trusted markets — powered by our people At Cboe Global Markets, we inspire our people to solve complex challenges together because what we do matters. We provide the financial infrastructure that powers the global economy. As a leading provider of market infrastructure and tradable products, Cboe delivers cutting-edge trading, clearing and investment solutions to market participants around the world. We’re building meaningful ways to support professional and personal development while strengthening the trust we’ve earned as a global market leader. Our teams are empowered to share ideas, actively pursue them and bring on a challenge. As champions of internal mobility and access to opportunity, we encourage our people to “go for it” and equip our managers with the training to coach their teams to the next level. We strive to provide employees a safe space to network, share ideas and create opportunities. To support strong partnership and team connection, this role follows a four day in office work model." That's a lot of fluff but it's about company culture and work model. The schedule info is separate; we could keep some of that in About the role but schedule will be separate. The work model mention could be moved to Schedule section. So we can keep About the role as the role overview paragraph only (the paragraph after Role Overview). That seems sufficient. Responsibilities list: - Develop, optimize, and debug real-time financial analytics software - Evaluate, tune, and improve model performance, stability, and accuracy - Analyze market data, derived market data, and reference data - Collaborate closely with our reference data, real-time data, and historical data teams - Provide 2nd level support for production applications developed by the team. - Respond to customer questions regarding our analytics and models - Write technical specifications, project plans, and documentation - Regular communication with senior managers and technical colleagues - Work with sales team to support presales engagements Requirements (experience & skills): - 3+ years in Java or C# (or equivalent), including understanding of parallel and multithreaded design patterns. - 1+ year in C++ preferred — our system is primarily Java, but performance-critical calculations run in C/C++ and CUDA - Background in financial markets, derivatives pricing, and/or risk analysis. - Equity derivatives experience is a plus. - Ability to explain a complex software system end-to-end, from inputs to output, including its design rationale and business value - Ability to work as a self-starter; take ownership of projects from start to finish; develop requirements and specifications; QA testing, documentation and production release Qualifications (education): - Minimum of a bachelor’s degree in a STEM field, but a master’s degree preferred. Benefits list: - Medical Coverage - Prescription Drug Coverage - Additional Medical Benefit - Dental Coverage - Vision Coverage - 401K or Pension Company Match - Spending Accounts - Life and AD&D Insurance - Retirement Savings Plan - Employee Stock Purchase Plan (ESPP) - Voluntary & Additional Benefits - Paid Time Off Pay: - Anticipated base salary range: $119,000-$154,000 in Kansas, $130,900-$169,400 in Chicago, and $148,750-$192,500 in New York, with actual compensation determined by job‑related factors such as skills, relevant experience, education, internal alignment, and location. This role may also be eligible for annual incentive compensation and, where applicable, participation in Cboe's long-term equity programs. Schedule: - This role follows a four day in office work model. We must not include filler like "commensurate with experience". Not present. Now produce HTML fragment. Use for each section heading. Use - for lists. Use
for prose.
We need to ensure we don't include any markdown fences. Just raw HTML.
Let's craft:
About the role
Cboe Data Vantage is looking for an experienced software engineer who is excited about combining strong engineering skills with financial quantitative analysis. The role focuses on modeling a diverse set of financial instruments and includes portfolio analysis. You will work within a team of seasoned developers, technologists, and quants all with deep experience in financial markets and financial modeling. Data Vantage’s clients are among the largest and most prestigious financial institutions and rely on our expertise in this space.
Responsibilities
- Develop, optimize, and debug real-time financial analytics software
- Evaluate, tune, and improve model performance, stability, and accuracy
- Analyze market data, derived market data, and reference data
- Collaborate closely with our reference data, real-time data, and historical data teams
- Provide 2nd level support for production applications developed by the team.
- Respond to customer questions regarding our analytics and models
- Write technical specifications, project plans, and documentation
- Regular communication with senior managers and technical colleagues
- Work with sales team to support presales engagements
Requirements
- 3+ years in Java or C# (or equivalent), including understanding of parallel and multithreaded design patterns.
- 1+ year in C++ preferred — our system is primarily Java, but performance-critical calculations run in C/C++ and CUDA
- Background in financial markets, derivatives pricing, and/or risk analysis.
- Equity derivatives experience is a plus.
- Ability to explain a complex software system end-to-end, from inputs to output, including its design rationale and business value
- Ability to work as a self-starter; take ownership of projects from start to finish; develop requirements and specifications; QA testing, documentation and production release
for prose. We need to ensure we don't include any markdown fences. Just raw HTML. Let's craft:
About the role
Cboe Data Vantage is looking for an experienced software engineer who is excited about combining strong engineering skills with financial quantitative analysis. The role focuses on modeling a diverse set of financial instruments and includes portfolio analysis. You will work within a team of seasoned developers, technologists, and quants all with deep experience in financial markets and financial modeling. Data Vantage’s clients are among the largest and most prestigious financial institutions and rely on our expertise in this space.
Responsibilities
- Develop, optimize, and debug real-time financial analytics software
- Evaluate, tune, and improve model performance, stability, and accuracy
- Analyze market data, derived market data, and reference data
- Collaborate closely with our reference data, real-time data, and historical data teams
- Provide 2nd level support for production applications developed by the team.
- Respond to customer questions regarding our analytics and models
- Write technical specifications, project plans, and documentation
- Regular communication with senior managers and technical colleagues
- Work with sales team to support presales engagements
Requirements
- 3+ years in Java or C# (or equivalent), including understanding of parallel and multithreaded design patterns.
- 1+ year in C++ preferred — our system is primarily Java, but performance-critical calculations run in C/C++ and CUDA
- Background in financial markets, derivatives pricing, and/or risk analysis.
- Equity derivatives experience is a plus.
- Ability to explain a complex software system end-to-end, from inputs to output, including its design rationale and business value
- Ability to work as a self-starter; take ownership of projects from start to finish; develop requirements and specifications; QA testing, documentation and production release