You are viewing content from a past/completed QCon

Presentation: How To: Developers' Community Driven Career Growth

Track: Optimizing You: Human Skills for Individuals

Location: Pacific DEKJ

Duration: 11:50am - 12:40pm

Day of week: Monday

Slides: Download Slides

Level: Intermediate

Persona: Developer

Share this on:

This presentation is now available to view on

Watch video with transcript

What You’ll Learn

  1. Hear about Game of Roles that uses to grow their own developers into senior or leadership positions.
  2. Find out how the framework came about, how they are using it, and the results obtained.
  3. Learn how to apply the framework in an organization.


Forget about classroom trainings - they are boring and can give you knowledge, but not practice nor skills. At there are two developers, who invented the new way of education - online community marathon with heavy focus on self-reflection and practice - which already helped dozens of their colleagues grow and get promoted to Senior developer role. We call it Game of Roles and it already became an internal "franchise" to help people grow in other career roles (e.g. Team Leads).

In this session you will learn about how did we come up with such concept, what does it mean in details. You will learn about the framework behind each training, and, most important, how can you apply same principles at your organization without much effort but with high outcome.


What's your talk about?


The talk is based on my own experience about a new approach of how do we teach people, how do we educate our people. Here at we have a different career process. The typical career pathway for a developer would be to become a senior developer or to become a team leader. And there is a problem for our senior developers for example, because that's a role with clearly defined expectations, what senior developers should be. However, there is not much clarity about how to become a senior developer, what you need to do to become one. There is a description of how the process about promoting somebody to senior happens, with nominations and promotion committees. However, there is no guidance on what exactly do you do to become a senior developer. And that's because the senior role is not only about skills you have or not about knowledge you have. It's more about behavior demonstrated. It's basically about 'Do you care about your products, do you care about other people around you? Do you own systems? Do you teach others?'

A colleague of mine and me had a meeting, just a regular coffee, trying to think about what can we do for this problem. How can we help developers around us grow? Out of nowhere we came up with this concept of an online marathon. We called this Game of Roles and our goal was to create an environment where people could experience the new role, play this role for a while. I mean a senior developer role, and through this experience they can learn more about the role, they can learn more about the behavior, and what's more important they can learn more about themselves, what is their reality, how do they meet the requirements right now, what is missing, what they can do about it.

We created a group of people, we picked up a magic number of 15 people in the group, all of them are developers, and we put them in the online group. We use Facebook at Work. We created the group, you can think about as a normal Facebook group. We put those people there and throughout two weeks we were posting one assignment per day. It were same assignments for everybody, different assignment every day, and then we asked those people to complete those assignments by creating a separate post with their findings, results, outcome.

There were two types of assignments: first was practical, go somewhere, fix a bug, or help implement a feature or something like that. What senior developers usually do, stepping in the other areas of responsibility and fix some issues there or propose the architecture or something like this.

The second type of assignments we had was about self-reflection. The very first question we asked was: read about the expectations of a senior developer role and try to think where do you match, where you do not match and what you can do to actually get there. Having that kind of assessments help people to self-reflect and see what is their reality right now and what they can do about it. So the whole idea was, if we provide this training spread across two weeks we were hoping that we can create the right momentum, we can create a habit of doing unusual things on top of their usual work. It wasn't a classroom, we didn't ask them to come at a certain time in the room. We were posting those assignments online in the morning and then people could work on them at their own pace. That created a habit for people to do things outside of their immediate responsibilities, doing something which senior developers at can do, developing this momentum to make those things happen even after the training ends.


What happened? What did you find out?


We were collecting feedback from our participants. First of all, 80% of people or even more were really positive about going through this training. They were surprised by the fact that they were not only asked to do some practical tasks but also self-reflection. We got a lot of feedback saying: “I didn't expect to self-reflect but I find it really useful”. That was a real match for us. Another piece of feedback was that people understood, got more clarity about the role. One of the quotes was that a person finally understood that the senior role is not about what you do but how you do it. This was a really nice outcome for us.

And the third outcome was a demand we got from people. When we just first planned the training, we aimed at 15 people to start with, we didn't really expect to have more. However, after the announcement we made on our Facebook group, we got almost 80 applications from people to participate in this training. We had to create a waitlist, several rounds of the same training, and in the end, we got a hundred people going through this training. We also applied the same concept to train team leaders as well.


Who are you talking to, software engineers, senior software engineers, about leadership? Who is the main audience?


It could be everyone. Though, I think it will be mostly beneficial for seniors and leads because they have people to grow. At the same time, it can be also beneficial for those who are in the development position and would like to grow because by this they might think that self-reflection is important and that they don’t need to wait for someone to come and help them grow, they can make it themselves.


What are the behaviors that define a senior developer?


For us it is ownership, what we call a role model, what people would like to become. Force multiplication, helping other people grow by mentoring, by coaching, leading by example. Deep knowledge of some area, or broad knowledge of many different areas at The combination of hard skills and soft skills, with soft skills having the major impact.

Speaker: Georgiy Mogelashvili

Lead Developer @bookingcom

In his 10+ years experience, Georgiy had a chance to work for small local companies, country scale enterprises, non-profit organizations and international corporations.

Today Georgiy is working at, world's leading online travel agency. During his 5 years of experience there he changed different teams and roles. Starting as developer in upper funnel, later working as Team Leader in corporate travels segment, he is now working as Lead Developer and looks after tech in the marketing department.

In his spare time, Georgiy likes constructing Lego Technic creations, planespotting in airports around the world, and spending time with his wife and little daughter.

Find Georgiy Mogelashvili at

2020 Tracks

  • The Future of the API: REST, gRPC, GraphQL and More

    Web-based API continue to evolve. The track provides the what, how, and why of future APIs, including GraphQL, Backend for Frontend, gRPC, & ReST

  • Resurgence of Functional Programming

    What was once a paradigm shift in how we thought of programming languages is now main stream in nearly all modern languages. Hear how software shops are infusing concepts like pure functions and immutablity into their architectures and design choices.

  • Social Responsibility: Implications of Building Modern Software

    Software has an ever increasing impact on individuals and society. Understanding these implications helps build software that works for all users

  • Non-Technical Skills for Technical Folks

    To be an effective engineer, requires more than great coding skills. Learn the subtle arts of the tech lead, including empathy, communication, and organization.

  • Clientside: From WASM to Browser Applications

    Dive into some of the technologies that can be leveraged to ultimately deliver a more impactful interaction between the user and client.

  • Languages of Infra

    More than just Infrastructure as a Service, today we have librarys, languages, and platforms that help us define our infra. Languages of Infra explore languages and libraries being used today to build modern cloud native architectures.

  • Mechanical Sympathy: The Software/Hardware Divide

    Understanding the Hardware Makes You a Better Developer

  • Paths to Production: Deployments You've Always Wondered About

    Deployment pipelines allow us to push to production at ever increasing volume. Paths to production looks at how some of software's most well known shops continuous deliver code.

  • Java, The Platform

    Mobile, Micro, Modular: The platform continues to evolve and change. Discover how the platform continues to drive us forward.

  • Security for Engineers

    How to build secure, yet usable, systems from the engineer's perspective.

  • Modern Data Engineering

    The innovations necessary to build towards a fully automated decentralized data warehouse.

  • Machine Learning for the Software Engineer

    AI and machine learning is more approachable than ever. Discover how ML, deep learning, and other modern approaches are being used in practice by Software Engineers.

  • Inclusion & Diversity in Tech

    The road map to a inclusive and diverse tech organization. *Diversity & Inclusion defined as the inclusion of all individuals in an within tech, regardless of gender, religion, ethnicity, race, age, sexual orientation, and physical or mental fitness.

  • Architectures You've Always Wondered About

    How do they do it? In QCon's marquee Architectures track, we learn what it takes to operate at large scale from well-known names in our industry. You will take away hard-earned architectural lessons on scalability, reliability, throughput, and performance.

  • Architecting for Confidence: Building Resilant Systems

    Your system will fail. Build systems with the confidence to know when they do, you won't.

  • Remotely Productive: Remote Teams & Software

    More and more companies are moving to remote work. How do you build, work on, and lead teams remotely?

  • Operating Microservices

    Building and operating distributed systems is hard, and microservices are no different. Learn strategies for not just building a service but operating them at scale.

  • Distributed Systems for Developers

    Computer science in practice. An applied track that fuses together the human side of computer science with the technical choices that are made along the way