search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Pulse


Technology GR8 TECH


GR8 Tech: empowering engineers to take ownership


Responsible for establishing and overseeing this engineering mindset at GR8 Tech - a unit that now generates over half of the company's revenue - is Artur Ashyrov, Chief Technology Officer. Sitting down with G3 Media, Artur sets out how the team is structured in a way that grants teams the autonomy to excel in their specialist niches and the use cases for generative artificial intelligence.


Could you tell us more about GR8 Tech’s engineering division. How big is the team and how is it structured?


At GR8 Tech, our engineering division is quite expansive, with around 400 talented IT specialists. Our team is structured to ensure both autonomy and synchronisation across various functions.


Artur Ashyrov Chief Technology Officer GR8 Tech


Artur Ashyrov is the Chief Technology Officer (CTO) at GR8 Tech, focused on achieving revenue-driven goals and fostering engineers’ growth. Artur helped build a strong engineering unit that now generates over half of GR8 Tech’s revenue.


Artur has been involved in tech platform transformation since 2006, his career journey developing from outsourcing projects to building platforms for booking and CRM systems, media, iGaming, project management tools, and game development industries.


Artur’s main strength lies in disassembling issues in large, inflexible projects and remounting them better to achieve improved results. To do this, he disrupts tech, company culture, and people's mindsets.


Artur is also a visionary behind establishing an engineering mindset in GR8 Tech, promoting knowledge and experience sharing across different technical departments of the company. To drive the growth of the engineering unit, Artur has joined the GR8 Tech Academy, guiding and mentoring the next wave of industry professionals. Over 20 of his trainees have transitioned to join GR8 Tech’s team post-graduation.


P134 WIRE / PULSE / INSIGHT / REPORTS


Teams that focus on platform-wide issues are centralised, which ensures that our core infrastructure remains robust and efficient. We also have dedicated product divisions, such as separate teams for Sportsbook, Casino, CRM, and other key areas. Each business unit operates with its own Head of Engineering, who maintains a functional connection to the management team.


Tis structure grants our teams the autonomy they need to innovate and excel in their specific domains while staying aligned with our overall strategies and policies. It allows us to stay agile and responsive to the unique challenges and opportunities in each area of our business.


How does GR8 Tech foster a conducive environment for engineers that encourages them to do what their best at - solve problems, expand technical knowledge and create new opportunities for the business? And, as senior management, what’s your role in helping to achieve this?


I think engineers, like all people, perform best in a supportive and dynamic environment designed to encourage problem-solving rather than impose rigid constraints. At GR8 Tech, we create such an environment in several ways. First, we focus on growth opportunities, actively seeking out strategic development paths for our employees while considering customer context, industry trends, and emerging technologies.


Tis proactive approach ensures that our engineers are constantly evolving and staying ahead of the curve. We also promote cross- functional projects, allowing our engineers to work on important tasks that develop their skills and significantly impact the business. Tese projects foster collaboration and innovation across different areas of the company, which is incredibly energising and rewarding.


Autonomy and responsibility are, in my opinion, crucial for specialists’ development. Our teams have the freedom to make decisions, which promotes a culture of responsibility and initiative. Tis autonomy empowers our engineers to take ownership of their work and drive results.


As CTO, I try to match my engineers’ growth areas with promising tasks and projects that may help drive their development to the next level. However, I like to focus on creating opportunities first and letting people take the initiative.


As I said, responsibility is key, and owning the initiative in a decision is the foundation of being responsible. Only if no one is eager to take on a task on their own do I start assigning roles—but I'm happy to say that's rarely the case.


To what extent is the technical team integrated with the operational and commercial arms of the company? Do the tech team talk directly to clients or via account managers?


We involve our engineers in client interactions during pre-sales processes. Tis involvement allows them to gain a deeper understanding of customer needs and to offer effective, tailored solutions, asking questions that would never come to the minds of non-tech specialists. Plus, it’s amazing to see how much more impactful engineers’ work can be when they understand the end-user perspective firsthand.


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176