Lego is hiring a lead engineer to work on their recommendation engine
1–4 of 4 posts
Re: Lego is hiring a lead engineer to work on their recommendation engine
#2LEGO | London (Farringdon) | Hybrid (3 days a week in the office)
* Lead engineer on the personalisation / recommendation engine
* Python, Node JS / TS, Databricks, Aurora RDS, AWS, API Gateway
* Experience required in both data engineering and back-end engineering spaces
* Experience welcome in ML engineering and data science spaces
I've worked on this team for a year or so now and it's fair to say that there's been no shortage of things to work on - you'll be immersed in the challenge of computing and distributing personalised recommendations across the business via operational and analytical workloads.
You will also become a part of a company which adopts a lot of the nice danish working practices (family first).
The office culture is an important aspect of the business so 3 days a week is a needs-must.
If this sounds like your bag - apply :)
Re: Lego is hiring a lead engineer to work on their recommendation engine
#3LEGO | London (Farringdon) | Hybrid (3 days a week in the office) * Lead engineer on the personalisation / recommendation engine * Python, Node JS / TS, Databricks, Aurora RDS, AWS, API Gateway * Experience required in both data engineering and back-end engineering spaces * Experience welcome in ML engineering and data science spaces I've worked on this team for a year or so now and it's fair to say that there's been…
Why go this route, rather than incorporating GenAI provided by OpenAI, Alphabet, Athropic, etc.?
It seems to me that we are at a transition point, similar to the transition of self-hosting to cloud-hosting, where bespoke recommendation systems will no longer be a competitive edge. Or am I betting wrong?
Re: Lego is hiring a lead engineer to work on their recommendation engine
#4LEGO | London (Farringdon) | Hybrid (3 days a week in the office) * Lead engineer on the personalisation / recommendation engine * Python, Node JS / TS, Databricks, Aurora RDS, AWS, API Gateway * Experience required in both data engineering and back-end engineering spaces * Experience welcome in ML engineering and data science spaces I've worked on this team for a year or so now and it's fair to say that there's been…
Why go this route, rather than incorporating GenAI provided by OpenAI, Alphabet, Athropic, etc.? It seems to me that we are at a transition point, similar to the transition of self-hosting to cloud-hosting, where bespoke recommendation systems will no longer be a competitive edge. Or am I betting wrong?
As the position is for a lead engineer, it wouldn't be unusual for applicants to have ideas or a view on more recent developments in this technology area and/or it's application to this particular problem space...that's all I'll say