Holistic Optimization of the LinkedIn Newsfeed with Tim Jurka

800 800 This Week in Machine Learning & AI

Today we’re joined by Tim Jurka, Head of Feed AI at LinkedIn.

As you can imagine Feed AI is responsible for curating all the content you see daily on the LinkedIn site. What’s less apparent to those that don’t work on this type of product is the wide variety of opposing factors that need to be considered in organizing the feed. As you’ll learn in our conversation, Tim calls this the holistic optimization of the feed and we discuss some of the interesting technical and business challenges associated with trying to do this. We talk through some of the specific techniques used at LinkedIn like Multi-arm Bandits and Content Embeddings, and also jump into a really interesting discussion about organizing for machine learning at scale.

Thanks to our Sponsor!


I’d like to send a huge thanks to LinkedIn for sponsoring today’s show! LinkedIn Engineering solves complex problems at scale to create economic opportunity for every member of the global workforce. AI and ML are integral aspects of almost every product the company builds for its members and customers. LinkedIn’s highly structured dataset gives their data scientists and researchers the ability to conduct applied research to improve member experiences. To learn more about the work of LinkedIn Engineering, please visit engineering.linkedin.com/blog.

About Tim

Mentioned in the Interview

“More On That Later” by Lee Rosevere licensed under CC By 4.0

3 comments
  • Robb
    REPLY

    Love that LinkedIn is a sponsor! I’ve been super-impressed with the quality and timeliness of the content they put in my LI Feed and it’s cool to hear about the tech underneath.

  • Rosen Dimov
    REPLY

    Awesome! I hope that LinkedIn will keep up sponsoring podcasts of Sam, even if they turn out to be critical about the weaknesses of the AI implementation in LinkedIn! The news feed is just one of the areas that needs significant improvement 🙂

Leave a Reply

Your email address will not be published.