Principal Machine Learning Engineer, Matching and Recommendations
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. So we need to decide which headings to use. The posting has "What You'll Do" which is responsibilities. "About You" includes requirements, qualifications, skills. Could split into Requirements, Qualifications, Skills. But we need to avoid thin sections. Perhaps combine into Requirements and Skills. However we need to preserve all substantive info. Let's extract bullet-like sentences.
Responsibilities (What You'll Do):
- Define and lead the technical strategy for AI and ML systems that power recommendations, ranking, and personalization across Bumble products, delivering measurable improvements in user engagement and safety
- Design, develop, and deploy production-grade models using modern ML frameworks such as PyTorch, ensuring scalability and reliability in high-traffic environments
- Build and deploy production AI Agents using raw and fine-tuned foundational LLMs, along with sub-agents, tools, and MCP integrations
- Architect end-to-end ML pipelines, integrating data processing (e.g. Spark, Airflow) with model training, evaluation, and deployment workflows
- Drive experimentation frameworks, including A/B testing and offline evaluation, to continuously improve model performance and product outcomes
- Partner cross-functionally with Product, Engineering, and Data leadership to translate business challenges into impactful ML solutions, collaborating with purpose and influencing at senior levels
- Mentor and elevate senior individual contributors, fostering a culture of Excellence, Curiosity, and continuous learning across the ML community
- Take ownership of complex, ambiguous problem spaces, seeing initiatives through from insight to impact while adapting approaches with an agile mindset
- Champion responsible AI practices, ensuring fairness, transparency, and user safety are embedded into all machine learning systems
Requirements/Qualifications/Skills (About You):
- Typically requires 10–15 years of experience, though we welcome candidates with alternative backgrounds that demonstrate equivalent skills.
- Deep expertise in machine learning, with hands-on experience building and deploying large-scale systems in production environments
- Strong proficiency in Python and at least one major ML framework (e.g., PyTorch, TensorFlow), with experience in areas such as recommendation systems, ranking models, or NLP
- Expertise in prompting and fine-tuning Large Language Models (LLMs) and building production AI Agents
- Proven experience designing scalable data and ML pipelines using tools such as Spark, Airflow, or similar distributed systems
- Demonstrated ability to operate as a senior individual contributor, influencing technical strategy and decision-making without direct authority
- Experience partnering effectively across functions, collaborating with purpose, and taking ownership of outcomes in complex organizational environments
- A track record of mentoring and uplifting others, role modeling Respect and Excellence while building inclusive, high-performing teams
- Strong AI fluency, with the ability to independently design, evaluate, and optimize ML systems, and guide others in the responsible and effective application of AI
About Us (maybe not needed as a section). Could be omitted.
Pay: Compensation Range: $345K - $410K
No Benefits or Schedule.
Thus we will output sections: About the role (maybe a brief paragraph summarizing role?), Responsibilities (ul), Requirements (ul), Qualifications (ul?), Skills (ul?), Pay (p). But we need to avoid thin sections. Could combine Requirements, Qualifications, Skills into one "Requirements" section with all points. But the instruction says use headings like Requirements, Qualifications, Skills if we have content. We have content for each. Could we split? Might be okay but risk thin. However each heading would have a list of items; that's substantive. So we can include all three.
But we also need an "About the role" section. Could be a short paragraph summarizing the role: "As Principal Machine Learning Engineer, Matching & Recommendations at Bumble, you will define technical strategy for AI/ML systems powering recommendations, ranking, and personalization, remain hands-on, lead through technical influence, etc." That's derived from the intro paragraph before "What You'll Do". Let's capture that: At Bumble, we’re building the Love Company ... As our Principal Machine Learning Engineer, Matching & Recommendations, you’ll help define the technical and ML strategy behind the next generation of Bumble’s recommendation systems. You’ll remain hands-on while tackling complex problems across retrieval, ranking, personalization, experimentation, and two-sided marketplace optimization, partnering across Engineering, Product, Data Science, and Analytics to turn ambiguous member problems into scalable ML solutions. You’ll lead through technical influence, raise the bar for ML engineering across the organization, and help us build systems that optimize not simply for engagement, but for better connections and meaningful member outcomes.
That's good prose for About the role.
Now we need to output HTML fragment only, no /. Use
for each section heading. Use
for prose. Use
- for lists.
We must not include boilerplate like EEO, etc. Already removed.
Let's craft.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Pay
Compensation Range: $345K - $410K
We should not include Benefits or Schedule.
Check that we didn't repeat job title as heading. We didn't.
Check that we didn't include metadata like Job ID. Not present.
Now ensure we preserve all substantive info. Did we miss any? The "About Us" section includes description of Bumble Inc., Bumble Date, BFF, Badoo, Kind Connections, founded 2014, etc. That's substantive but not covered in any heading. Should we include it? The instruction: include a section ONLY when the posting has real, specific content for it. We have content about the company. Could we add an "About the company" section? Not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading. Should we incorporate that info into About the role? Possibly but it's about the company not the role. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should not add other headings. The company description could be considered part of About the role? Might be okay to include a brief sentence in About the role about Bumble's mission. Already we have some mission description. Could incorporate more details: "Bumble Inc. is the parent company of Bumble Date, BFF, and Badoo. The Bumble platform enables people to build healthy and equitable relationships, through Kind Connections. Founded by Whitney Wolfe Herd in 2014, Bumble was one of the first dating apps built with women at the center and connects people across dating (Bumble Date) and friendship (BFF). BFF is a friendship app where people in all stages of life can meet people nearby and create meaningful platonic connections and community based on shared interests. Badoo, which was founded in 2006, is one of the pioneers of web and mobile dating products." That is substantive and could be added to About the role paragraph.
Thus About the role paragraph will include both role description and company overview.
Now ensure we didn't include any boilerplate like "AI Fluency", "Inclusion at Bumble Inc.", etc. Those are boilerplate/EEO etc. Should be removed. The "AI Fluency" section is somewhat like a value statement but could be considered boilerplate? It's about AI importance. Might be considered part of About Us? It's not a standard heading; but it's substantive? It says "AI Fluency AI is important to us...". That's somewhat generic. Might be considered boilerplate. Safer to omit.
Also "Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations." That's generic; we have specific range, so we can omit that sentence.
"Inclusion at Bumble Inc." is EEO boilerplate; omit.
"AI in Bumble Inc. Hiring" etc is boilerplate; omit.
"Fraudulent Candidate Detection" etc is boilerplate; omit.
Thus final HTML includes only the sections we decided.
Now produce HTML.
Make sure to properly escape any special characters? Not needed.
Let's craft the About the role paragraph:
"At Bumble, we’re building the Love Company — a place where healthy, equitable relationships and friendships can start and grow. Machine Learning sits at the heart of that mission, helping us understand what makes a meaningful connection and powering the matching, recommendation, and personalization experiences that bring people together. As our Principal Machine Learning Engineer, Matching & Recommendations, you’ll help define the technical and ML strategy behind the next generation of Bumble’s recommendation systems. You’ll remain hands-on while tackling complex problems across retrieval, ranking, personalization, experimentation, and two-sided marketplace optimization, partnering across Engineering, Product, Data Science, and Analytics to turn ambiguous member problems into scalable ML solutions. You’ll lead through technical influence, raise the bar for ML engineering across the organization, and help us build systems that optimize not simply for engagement, but for better connections and meaningful member outcomes. Bumble Inc. is the parent company of Bumble Date, BFF, and Badoo. The Bumble platform enables people to build healthy and equitable relationships, through Kind Connections. Founded by Whitney Wolfe Herd in 2014, Bumble was one of the first dating apps built with women at the center and connects people across dating (Bumble Date) and friendship (BFF). BFF is a friendship app where people in all stages of life can meet people nearby and create meaningful platonic connections and community based on shared interests. Badoo, which was founded in 2006, is one of the pioneers of web and mobile dating products."
That's a bit long but okay.
Now Responsibilities list items as earlier.
Requirements list: items from About You.
Qualifications list: maybe we can split some items into Qualifications (like education? none). But we have no explicit qualifications besides experience. Could treat Requirements as experience and skills, Qualifications as education? Not present. Might be better to combine Requirements and Qualifications into one? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we don't have specific content for Qualifications, we should not include it. So we should only include sections where we have content. We have content for Requirements (experience, expertise). For Skills we have specific skills (Python, ML frameworks, LLMs, Spark, Air
for prose. Do NOT repeat the job title as a heading. So we need to decide which headings to use. The posting has "What You'll Do" which is responsibilities. "About You" includes requirements, qualifications, skills. Could split into Requirements, Qualifications, Skills. But we need to avoid thin sections. Perhaps combine into Requirements and Skills. However we need to preserve all substantive info. Let's extract bullet-like sentences. Responsibilities (What You'll Do): - Define and lead the technical strategy for AI and ML systems that power recommendations, ranking, and personalization across Bumble products, delivering measurable improvements in user engagement and safety - Design, develop, and deploy production-grade models using modern ML frameworks such as PyTorch, ensuring scalability and reliability in high-traffic environments - Build and deploy production AI Agents using raw and fine-tuned foundational LLMs, along with sub-agents, tools, and MCP integrations - Architect end-to-end ML pipelines, integrating data processing (e.g. Spark, Airflow) with model training, evaluation, and deployment workflows - Drive experimentation frameworks, including A/B testing and offline evaluation, to continuously improve model performance and product outcomes - Partner cross-functionally with Product, Engineering, and Data leadership to translate business challenges into impactful ML solutions, collaborating with purpose and influencing at senior levels - Mentor and elevate senior individual contributors, fostering a culture of Excellence, Curiosity, and continuous learning across the ML community - Take ownership of complex, ambiguous problem spaces, seeing initiatives through from insight to impact while adapting approaches with an agile mindset - Champion responsible AI practices, ensuring fairness, transparency, and user safety are embedded into all machine learning systems Requirements/Qualifications/Skills (About You): - Typically requires 10–15 years of experience, though we welcome candidates with alternative backgrounds that demonstrate equivalent skills. - Deep expertise in machine learning, with hands-on experience building and deploying large-scale systems in production environments - Strong proficiency in Python and at least one major ML framework (e.g., PyTorch, TensorFlow), with experience in areas such as recommendation systems, ranking models, or NLP - Expertise in prompting and fine-tuning Large Language Models (LLMs) and building production AI Agents - Proven experience designing scalable data and ML pipelines using tools such as Spark, Airflow, or similar distributed systems - Demonstrated ability to operate as a senior individual contributor, influencing technical strategy and decision-making without direct authority - Experience partnering effectively across functions, collaborating with purpose, and taking ownership of outcomes in complex organizational environments - A track record of mentoring and uplifting others, role modeling Respect and Excellence while building inclusive, high-performing teams - Strong AI fluency, with the ability to independently design, evaluate, and optimize ML systems, and guide others in the responsible and effective application of AI About Us (maybe not needed as a section). Could be omitted. Pay: Compensation Range: $345K - $410K No Benefits or Schedule. Thus we will output sections: About the role (maybe a brief paragraph summarizing role?), Responsibilities (ul), Requirements (ul), Qualifications (ul?), Skills (ul?), Pay (p). But we need to avoid thin sections. Could combine Requirements, Qualifications, Skills into one "Requirements" section with all points. But the instruction says use headings like Requirements, Qualifications, Skills if we have content. We have content for each. Could we split? Might be okay but risk thin. However each heading would have a list of items; that's substantive. So we can include all three. But we also need an "About the role" section. Could be a short paragraph summarizing the role: "As Principal Machine Learning Engineer, Matching & Recommendations at Bumble, you will define technical strategy for AI/ML systems powering recommendations, ranking, and personalization, remain hands-on, lead through technical influence, etc." That's derived from the intro paragraph before "What You'll Do". Let's capture that: At Bumble, we’re building the Love Company ... As our Principal Machine Learning Engineer, Matching & Recommendations, you’ll help define the technical and ML strategy behind the next generation of Bumble’s recommendation systems. You’ll remain hands-on while tackling complex problems across retrieval, ranking, personalization, experimentation, and two-sided marketplace optimization, partnering across Engineering, Product, Data Science, and Analytics to turn ambiguous member problems into scalable ML solutions. You’ll lead through technical influence, raise the bar for ML engineering across the organization, and help us build systems that optimize not simply for engagement, but for better connections and meaningful member outcomes. That's good prose for About the role. Now we need to output HTML fragment only, no /. Use
for each section heading. Use
for prose. Use
- for lists.
We must not include boilerplate like EEO, etc. Already removed.
Let's craft.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Pay
Compensation Range: $345K - $410K
We should not include Benefits or Schedule. Check that we didn't repeat job title as heading. We didn't. Check that we didn't include metadata like Job ID. Not present. Now ensure we preserve all substantive info. Did we miss any? The "About Us" section includes description of Bumble Inc., Bumble Date, BFF, Badoo, Kind Connections, founded 2014, etc. That's substantive but not covered in any heading. Should we include it? The instruction: include a section ONLY when the posting has real, specific content for it. We have content about the company. Could we add an "About the company" section? Not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading. Should we incorporate that info into About the role? Possibly but it's about the company not the role. However the instruction says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should not add other headings. The company description could be considered part of About the role? Might be okay to include a brief sentence in About the role about Bumble's mission. Already we have some mission description. Could incorporate more details: "Bumble Inc. is the parent company of Bumble Date, BFF, and Badoo. The Bumble platform enables people to build healthy and equitable relationships, through Kind Connections. Founded by Whitney Wolfe Herd in 2014, Bumble was one of the first dating apps built with women at the center and connects people across dating (Bumble Date) and friendship (BFF). BFF is a friendship app where people in all stages of life can meet people nearby and create meaningful platonic connections and community based on shared interests. Badoo, which was founded in 2006, is one of the pioneers of web and mobile dating products." That is substantive and could be added to About the role paragraph. Thus About the role paragraph will include both role description and company overview. Now ensure we didn't include any boilerplate like "AI Fluency", "Inclusion at Bumble Inc.", etc. Those are boilerplate/EEO etc. Should be removed. The "AI Fluency" section is somewhat like a value statement but could be considered boilerplate? It's about AI importance. Might be considered part of About Us? It's not a standard heading; but it's substantive? It says "AI Fluency AI is important to us...". That's somewhat generic. Might be considered boilerplate. Safer to omit. Also "Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations." That's generic; we have specific range, so we can omit that sentence. "Inclusion at Bumble Inc." is EEO boilerplate; omit. "AI in Bumble Inc. Hiring" etc is boilerplate; omit. "Fraudulent Candidate Detection" etc is boilerplate; omit. Thus final HTML includes only the sections we decided. Now produce HTML. Make sure to properly escape any special characters? Not needed. Let's craft the About the role paragraph: "At Bumble, we’re building the Love Company — a place where healthy, equitable relationships and friendships can start and grow. Machine Learning sits at the heart of that mission, helping us understand what makes a meaningful connection and powering the matching, recommendation, and personalization experiences that bring people together. As our Principal Machine Learning Engineer, Matching & Recommendations, you’ll help define the technical and ML strategy behind the next generation of Bumble’s recommendation systems. You’ll remain hands-on while tackling complex problems across retrieval, ranking, personalization, experimentation, and two-sided marketplace optimization, partnering across Engineering, Product, Data Science, and Analytics to turn ambiguous member problems into scalable ML solutions. You’ll lead through technical influence, raise the bar for ML engineering across the organization, and help us build systems that optimize not simply for engagement, but for better connections and meaningful member outcomes. Bumble Inc. is the parent company of Bumble Date, BFF, and Badoo. The Bumble platform enables people to build healthy and equitable relationships, through Kind Connections. Founded by Whitney Wolfe Herd in 2014, Bumble was one of the first dating apps built with women at the center and connects people across dating (Bumble Date) and friendship (BFF). BFF is a friendship app where people in all stages of life can meet people nearby and create meaningful platonic connections and community based on shared interests. Badoo, which was founded in 2006, is one of the pioneers of web and mobile dating products." That's a bit long but okay. Now Responsibilities list items as earlier. Requirements list: items from About You. Qualifications list: maybe we can split some items into Qualifications (like education? none). But we have no explicit qualifications besides experience. Could treat Requirements as experience and skills, Qualifications as education? Not present. Might be better to combine Requirements and Qualifications into one? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we don't have specific content for Qualifications, we should not include it. So we should only include sections where we have content. We have content for Requirements (experience, expertise). For Skills we have specific skills (Python, ML frameworks, LLMs, Spark, Air