Picnic master project interview

picnic

  • [Picnic master project interview](#Picnic master project interview)
    • [1. Topics](#1. Topics)
      • [1.1 Systematically identify similar/interchangeable articles](#1.1 Systematically identify similar/interchangeable articles)
      • [1.2 Understanding changing customer behaviour](#1.2 Understanding changing customer behaviour)
    • [2. interview](#2. interview)
    • 等后续

Picnic master project interview

1. Topics

1.1 Systematically identify similar/interchangeable articles

Data integration

Data management for machine learning

Complexity theory

Description

At Picnic, we currently have an assortment of some 8k articles. However, in practice, many play a similar role from the customer's perspective - a customer wants to buy e.g. cola or bananas, but there will be multiple colas or multiple bananas that the vast majority of customers will only buy one variety of. Likewise, if a customer wants to cook a certain meal, say pasta bolognese, there will be many different collections of articles that could represent this; and for the role of 'minced meat', there could be a number of varieties of minced meat in different sizes and of different origin, including vegetarian and vegan options. These are similar concepts, they are a sort of 'product archetype' that play a certain role in a customer's shopping.

However, for different types of product archetypes, and also for different products within certain archetypes, the behaviour might be slightly different. Some articles might be directly interchangeable (e.g. two brands of bananas, or two sizes of exactly the same product), but others not or only in one direction (minced meat vs the vegan option). In some categories, a customer will only buy one product from the archetype in a specific shopping session, while in others (e.g. zoutjes) customers regularly buy multiple. And finally, what should be shown might also depend on the context (where in the app, e.g. in search or in recipe) and on the customer.

This project aims to formalise these inter-product relations. Can we systematically identify these product archetypes? Can we quantify how interchangeable two products are, in different contexts? What different contexts are relevant? And is it generally possible to generate context-specific sets of products by starting from a broad archetype and applying filters or re-ranking, or is this too simplistic?

Work Environment

Picnic Technologies is known for its innovative approach to grocery shopping and delivery. The work environment reflects this innovative and dynamic culture. A lot of creativity, open communication, and a willingness to come up with new ideas!

Expectations

We're aiming for quality thesis work where the intern is able to deepdive into the topic at hand within the context of potentially applying it to Picnic's business on the long term, with guidance from Picnic of course. We require at least 5 months, full-time internships; there's an online code test and two interviews in the process.

1.2 Understanding changing customer behaviour

Modelling complex systems & networks

Data integration

Algorithms and datastructures

Description

Customer preference changes over time. Customers might switch their shopping behaviour for various reasons, e.g.:

-they find a similar but cheaper/better-tasting/preferable alternative

-they start or stop buying certain types of products online (e.g. some customers are wary of fresh products from online)

-their tastes change

-their diet changes

-their family/living situation changes

At Picnic, we have an extensive and very well-maintained Data Warehouse, where relational databases store e.g. personal purchasing behaviour, historical status changes of articles and customer addresses, and so on. There is also considerable data on in-app events that can give insights in how customers are using the app, how they navigate and what actions are performed. Such factual information is quite reliable; other data points such as family size or number of pets are self-reported and require interpretation. Knowledge of SQL is required to unlock this primary source of relevant data; in addition, Python is the language of choice in the Data Science team.

There are a number of interesting research questions in this direction, which can be further refined during the thesis. the A first question is how shopping behaviour changes over time, and if specific stages can be identified during this change in behaviour. This requires systematic detection of patterns in the available historical purchasing data, potentially also including relevant in-app events. Depending on the type of shopping behaviour we are interested in, different kinds of dynamics may occur; i.e., it might be a simple case of transitioning to a different product, but also wider changes in behaviour such as 'ordering more sustainably', 'becoming a more mature customer' (whatever that means exactly is an open question), or 'switching to a vegetarian diet' are of interest.

A similar, but more forward-looking question is whether we can predict behaviour change trajectories for current customers. From the academical point of view, this allows for a validation of the more historically focused analysis in step 1. Likewise, If we can observe customers that are likely to exhibit certain future purchasing behaviour, this can be used to show e.g. more relevant products, choose promotions that might induce them to explore new categories, or proactively reach out to avoid (partial) customer churn. That brings us to a next question: is it possible to nudge customer behaviour via e.g. recommendations or presentation to induce healthier or more sustainable choices? And in what ways can this be achieved, i.e. what are the articles or methods that are best suited to do so? Can different customer groups be identified here that may need to be treated in distinct ways? This is a research question that not only brings recommendation systems directly into play, but is also a next step from the business perspective. Eventually, alignment will be necessary with business-facing and tech teams for implementation of such nudging experiments, but it is certainly possible to validate the research and see if the nudging predictions hold water in real life.

Work Environment

Picnic Technologies is known for its innovative approach to grocery shopping and delivery. The work environment reflects this innovative and dynamic culture. A lot of creativity, open communication, and a willingness to come up with new ideas!

2. interview

  1. selft intro?
    用了个人网站讲解
    提到了腾讯做软件 - 体现自己技术实用的理念
    讲自己knowledge organization课有用
  2. 上过的课?
    讲了研一的服务课等,编程课
  3. 会什么技术?
    先说服务的大理念
    再说python/C#/java
  4. 为什么picnic?
    讲大二对零售感兴趣
    讲公司电车服务,green IT
  5. 为什么这两个项目?
    第一个是知识图谱
    第二个是用户画像,推荐系统
  6. Q&A?
    1. 公司多少人?
      好几百
    2. 在哪?
      overamstel
    3. 什么部门?
      tech - data science
    4. 收几个人?
      1
    5. hybrid?
      2-3 days per week on-site
    6. subsidy?
      800
    7. future career?
      possibile
    8. future interview?
      1. python测试
      2. 技术面
      3. coffee chat

等后续

复制代码
人挺多的估计,等等吧
相关推荐
源代码•宸1 小时前
大厂技术岗面试之谈薪资
经验分享·后端·面试·职场和发展·golang·大厂·职级水平的薪资
马猴烧酒.2 小时前
【面试八股|JVM虚拟机】JVM虚拟机常考面试题详解
jvm·面试·职场和发展
Serene_Dream7 小时前
JVM 并发 GC - 三色标记
jvm·面试
愚者游世9 小时前
Delegating Constructor(委托构造函数)各版本异同
开发语言·c++·程序人生·面试·改行学it
信码由缰10 小时前
Spring Boot 面试问题
spring boot·后端·面试
马猴烧酒.1 天前
【面试八股|Java集合】Java集合常考面试题详解
java·开发语言·python·面试·八股
闻哥1 天前
从测试坏味道到优雅实践:打造高质量单元测试
java·面试·单元测试·log4j·springboot
南风知我意9571 天前
【前端面试5】手写Function原型方法
前端·面试·职场和发展
java1234_小锋1 天前
Java高频面试题:SpringBoot如何自定义Starter?
java·spring boot·面试
努力学算法的蒟蒻1 天前
day77(2.5)——leetcode面试经典150
面试·职场和发展