Staff Machine Learning Engineer, Financial Products
Adyen · San Francisco, CA · 1 mo ago
Engineering$297k–$401k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: there is a paragraph after "Financial Products About The Role". Actually the text: "Financial Products About The Role The Financial Products org at Adyen is at the forefront of our evolution, building the foundational infrastructure that enables our customers to manage their finances, issue cards, and access credits and financing globally. Adyen is building a Machine Learning Engineering team in San Francisco focused on Credit Risk Modeling for Underwriting within Financial Products. This team will develop the models, scorecards, and production systems that enable Adyen to scale its credit products 100x. As a Staff Machine Learning Engineer you will design, productionize, and operate machine learning models and rule-based decision systems that power credit products. You will work across the full model lifecycle, from research and data analysis to training, deployment, monitoring, and continuous improvement. This role is ideal for an engineer who combines strong machine learning and production engineering experience with sound judgment in high-integrity financial systems. You will help build continuous data flywheels that improve underwriting decisions while balancing rapid product innovation with robustness, explainability, and global scale. We are looking for engineers with a customer-problem-first mindset and experience building reliable ML systems in production. You will work closely with product, engineering, risk, and data teams to deliver underwriting capabilities for some of the world’s leading businesses."
That's about the role.
- In This Role, You Will: bullet list of responsibilities. So we can create a Responsibilities section with
- . List items: - Develop and maintain scalable production ML pipelines for feature engineering, model training, validation, and deployment. - Examples ML domains are- supervised and semi-supervised learning methods for inference on credit risk patterns; - Identify and fix performance bottlenecks in ML training and inference (memory consumption, online latency, training time etc.); - Collaborate with software engineers to integrate ML solutions into products and services; - Collaborate with CreditOps and data teams to integrate effectively with current tools, and shape priority for future tools; - Support and encourage good engineering practices on product ML teams; We need to preserve content exactly; maybe keep punctuation. - Who You Are: list of requirements/qualifications. Could be split into Requirements and Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide based on content. The "Who You Are" bullet list includes experience, skills, knowledge. Could treat as Requirements (mandatory) and maybe Skills separate? But we can combine into Requirements or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one section "Requirements" (or "Qualifications") containing all bullet points. But we also have "Nice To Have" separate list. We could have: - Requirements (mandatory): list of mandatory items from Who You Are. - Nice To Have: could be a subsection under Requirements? Or separate "Preferred Qualifications". Since we have a section Qualifications maybe we can put mandatory there and Nice To Have as separate? But we need to avoid many thin sections. Could have "Requirements" containing both mandatory and nice-to-have? But better to separate: Requirements (mandatory) and Preferred Qualifications (nice to have). That's two sections. Skills: maybe we can extract specific technical skills: Python, Java, Spark, Trino SQL, Tensorflow, PyTorch, XGBoost/LightGBM, Pandas, MLFlow, Airflow, k8s, docker, argo-workflows, prometheus, grafana. Could be a Skills section. But we already have those in Who You Are bullet list. Could put them under Skills. We need to avoid duplication. Let's think: The posting includes: Who You Are bullet list (mandatory): - 8+ years experience as an engineer working in the machine learning domain; - Strong Python programmer and experience in Java; - Experience with the full machine learning model lifecycle in production flows; - Experience leveraging big data to create the pipelines needed to feed the models with appropriate data; - Strong understanding of good software engineering practices as well as data engineering and MLOps principles; - Knowledge of data science, statistics and machine learning techniques; - Strong familiarity with the standard data science toolkit in python, such as (py)spark, (Trino) SQL, Tensorflow, PyTorch, XGBoost/LightGBM, Pandas, MLFlow or similar MLOps frameworks, and Airflow; - Knowledge/experience of working with ML infrastructure components with tools such as k8s, docker, airflow, argo-workflows, prometheus, grafana - Experimental mindset with a launch fast and iterate mentality; - Proactively take the lead in projects, from ideation to deployment; - Experience working with a wide range of stakeholders and can clearly communicate complex outcomes over a wide range of audiences. Nice To Have: - Experience on underwriting models or systems - Experience working with a Machine Learning ‘Feature Store’ Benefits: The posting includes "Why Adyen?" section with many bullet points about environment, datasets, ownership, speed, etc. Also mentions compensation: "The annual base salary range for this role is $297,000 - $401,000, plus RSUs". Also mentions location: San Francisco office, office-first, no remote-only. Also mentions global mobility, relocation conversations to Amsterdam or Madrid. Also mentions "We offer an environment of ownership and speed, where a focused research team can make a significant difference." etc. Also mentions "We are looking for individuals who are eager to stay connected to the edge of ML innovation while ensuring we deliver practical value to our global platform." Also mentions "Our aim is to build a lasting foundation for you at Adyen—starting in San Francisco, but with the flexibility to adapt as life evolves." Also mentions "Our Diversity, Equity and Inclusion commitments" but that's boilerplate EEO; we should remove. Also mentions "What’s next?" about timeline; that's application instructions; we should remove. Also mentions "Don’t be afraid to let us know if you need more flexibility." That's also maybe part of process; could be considered boilerplate; but it's about flexibility; maybe keep? It's part of "What’s next?" which is application instructions; we should remove. Also mentions "Adyen is an equal opportunity employer..." remove. Also mentions "San Francisco Pursuant to the San Francisco Fair Chance Ordinance..." remove. Also mentions "We are an office-first company and value in-person collaboration; we do not offer remote-only roles." That's a substantive detail about work arrangement; could be included under Schedule? Actually schedule refers to work schedule (remote, hybrid, office). This is about office-first, no remote-only. Could be placed under Schedule or maybe under Benefits? The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. The posting states location and work arrangement (office-first, no remote-only). That's about schedule/location. Could be placed under Schedule. Pay: we have salary range and RSUs. Benefits: we have many bullet points under "Why Adyen?" about environment, datasets, ownership, speed, impact, global datasets, etc. Also mention "We offer an environment of ownership and speed, where a focused research team can make a significant difference." Also "You will be at the forefront of bridging ML and fintech, shaping how these two critical areas intersect." Also "We are looking for individuals who are eager to stay connected to the edge of ML innovation while ensuring we deliver practical value to our global platform." Also "Our aim is to build a lasting foundation for you at Adyen—starting in San Francisco, but with the flexibility to adapt as life evolves." Also mention global mobility, relocation conversations to Amsterdam or Madrid. Also mention "We have deep roots in Europe and a strong global presence". Also mention "We offer an environment of ownership and speed". Also mention "You’ll have direct access to massive global datasets (e.g., payments, identity data) and the ability to see your team's work have an immediate impact at scale." Also mention "We are looking for individuals who are eager to stay connected to the edge of ML innovation while ensuring we deliver practical value to our global platform." Also mention "While this is a San Francisco-based role, we recognize that global mobility matters—especially for candidates navigating complex situations. Adyen has deep roots in Europe and a strong global presence, and we’re open to future relocation conversations to our offices in Amsterdam or Madrid if that better supports your personal or professional goals in the future." Also mention "Our aim is to build a lasting foundation for you at Adyen—starting in San Francisco, but with the flexibility to adapt as life evolves." Also mention "We offer an environment of ownership and speed, where a focused research team can make a significant difference." Also mention "You will be at the forefront of bridging ML and fintech, shaping how these two critical areas intersect." Also mention "We are looking for individuals who are eager to stay connected to the edge of ML innovation while ensuring we deliver practical value to our global platform." Also mention "Our aim is to build a lasting foundation for you at Adyen—starting in San Francisco, but with the flexibility to adapt as life evolves." Also mention "Our Diversity, Equity and Inclusion commitments" (remove). Also mention "Studies show that women and members of underrepresented communities apply for jobs only if they meet 100% of the qualifications. Does this sound like you? If so, Adyen encourages you to reconsider and apply." That's encouraging but maybe considered EEO? It's about encouraging underrepresented groups; could be considered part of DEI but maybe still boilerplate? It's not exactly EEO legal; it's a call to action. Might be considered part of the posting but could be considered fluff. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly legal EEO but it's about encouraging underrepresented groups; could be considered part of DEI statement. Might be considered boilerplate; safer to remove. Also "What’s next? Ensuring a smooth and enjoyable candidate experience is critical for us. We aim to get back to you regarding your application within 5 business days. Our interview process tends to take about 4 weeks to complete, but may fluctuate depending on the role. Learn more about our hiring process here. Don’t be afraid to let us know if you need more flexibility." That's application instructions; remove. Also "Adyen is an equal opportunity employer..." remove. Also "San Francisco Pursuant to the San Francisco Fair Chance Ordinance..." remove. Also "We are an office-first company and value in-person collaboration; we do not offer remote-only roles." Keep as schedule. Now we need to decide sections. Potential sections: - About the role (already have) - Responsibilities (list) - Requirements (mandatory qualifications) - Preferred Qualifications (nice to have) - Skills (technical skills list) - Benefits (why Adyen) - Pay (salary range + RSUs) - Schedule (location, office-first, no remote-only, global mobility, relocation) We must not create sections with filler like "commensurate with experience". We have real content. Check if any duplication: Skills list overlaps with Requirements; but we can keep Skills separate as a concise list of tools/languages. Requirements includes experience, knowledge, etc. That's okay. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from Who You Are (mandatory) and Nice To Have, all responsibilities, all About the role paragraph, all Why Adyen bullet points, salary, location details. We must not lose any detail. Let's extract all substantive content precisely. First, About the role paragraph: we need to copy it exactly as in the posting (maybe minor punctuation). Let's copy: "Financial Products About The Role The Financial Products org at Adyen is at the forefront of