Product Manager · Rambler&Co Search
Rambler Search
Search was already making money for Rambler but was barely being developed. I set up regular product work, built a cross-functional team and took on the results page, monetization and our own search technology.
Constraint
Search made money but was barely being developed, and its team was two developers and a half-time administrator
Key decisions
Set up regular product work: hypotheses, priorities, experiments, quarterly plans and plan-versus-actual reviews against product and revenue metrics.
Outcome
+95% search revenue, year over year
Context
From 2011 Rambler used Yandex search as its base technology. On top of the base web results, Rambler developed its own search product: the results page, advertising, blocks for the group's services and other search scenarios. For specific tasks, such as news search, the team had its own search technology.
When I joined, search was already bringing Rambler significant revenue but was getting almost no product attention.
The constraint
The results page had to do two things at once: help people find the answer and make money. Ads and Rambler&Co service blocks sat on the same page where people were looking for their result, so every change to the results page affected both user behaviour and revenue.
My role
I combined product and project responsibility: I set up work with hypotheses, priorities, experiments and quarterly plans, and owned the search experience and monetization. The team grew from two developers and a half-time administrator into a full cross-functional team: engineering, design, QA, operations and distribution. The team built the ranking, models, infrastructure and interfaces.
Key decisions
Set up regular product work: hypotheses, priorities, experiments, quarterly plans and plan-versus-actual reviews against product and revenue metrics.
Change the results page through experiments. The new SERP first went to 25% of traffic and was compared with the previous version on user behaviour and advertising metrics.
Build Rambler&Co services directly into the results page — Kassa, Championat, Afisha, the TV guide, Organizations — and make these service blocks configurable through an admin tool so routine changes did not need developers.
What changed
I launched the integration with Google as a search provider for foreign traffic and personally led the work with its API. Yandex remained the base search for Russian users.
In 2015 we used a GAN (Generative Adversarial Network) in our work on service blocks: from sets of keywords we generated variants that competed with each other, to choose the blocks' weights and improve the composition of the results page.
In our own news search we shipped a new ranking formula and started using behavioural statistics in ranking.
In 2016 we shipped the new SERP and redesigns of mobile search and Rambler Images, launched the admin tool for service blocks and kept adding new blocks — Championat, the TV guide, Afisha and later Organizations. By the end of the year advertising conversion had grown and the interface followed Rambler's common guidelines.
Historical product artifacts


Result
Rambler Search revenue grew 95% year over year.
In our own news search, the new ranking formula raised the share of queries in which the user found the needed result on the first page from about 40% to 80%. A result counted as needed if the user clicked it and did not return to the results page. 45% of users found the needed result in the first position instead of 13%, and 76% in the top five instead of 33%.
The team's own search technology became the basis for the next stage: local search for Rambler&Co properties.