01011001 01101111 01110101 00100000 01110111 01101001 01101100 01101100 00100000 01101011 01101110 01101111 01110111 00100000 01110011 01101111 01101111 01101110

Achievements as CTO:Improved Communication: Initiated personal meetings with each developer to understand their needs and find effective solutions.Transition to In-House Development Team: Moved from working with contractors to establishing an internal development team, enhancing efficiency and work quality.Hiring and Team Expansion: Recruited more qualified professionals and expanded the development team.Collaboration with CPO to Establish Scrum Methodology: Worked closely with the Chief Product Officer (CPO) to build and implement a robust Scrum methodology, aligning product development with agile practices for enhanced efficiency and team synergy.Microservices Tracing: Implemented microservices tracing, improving architecture, and granting developers more freedom in solution choices.Fostering Trust: Strengthened trust between business units and the development team.Cultivating DevOps Culture: Expanded the team and enhanced IT infrastructure, supporting a DevOps culture.Salary Increase and Leadership Roles: Raised salaries for talented employees and introduced impactful leadership roles.Dismissing Underperforming Staff: Made tough decisions to dismiss underperforming but highly-paid employees to maintain a culture of productivity.Monitoring and Logging System Development: Improved process transparency with the implementation of monitoring and logging systems.Preparing a Successor: Actively preparing your successor for the CTO role to ensure future stability.Enhancing Company Attractiveness: Increased recommendations from current employees by improving the work environment and corporate culture.

1. With the help of Product Owners, I organized two in-house scrum dev teams from scratch. Thanks to the chosen stack (Strapi.js, React.js, ReactNative.js), all devs are interchangeable. Everyone on the team knows what's going on at the front and at the back. Thus, healthy competition appeared in the teams, where everyone can evolve as a full-stack developer and challenge the decisions of colleagues if it seems to them that there is a more beautiful/efficient way to write functions / controllers / components.2. Personal approach to key employees, tete-a-tete meetings, closing of gestalts3. Combined 5 FTE to achieve results faster:FTE:1. senior backend developer (developed 4 in-house projects that have been working steadily for several years and help employees not do manual work)2. TeamLead x2 (Hired employees, conducted technical interviews, received the "best interviewer" award more than 7 times according to candidates, including from strong senior developers with 20 years of experience)3. Techlead (Architecture, stacks, project assistance, experience sharing, implementation of mandatory autotests)4. DevOps (created an almost perfect git-flow with CI / CD, Zero DownTime Deployemnt. Thanks to this, employees can release 10 times a day, without any inconvenience to customers)5. DBA (I accelerated financial analytics by partitioning large tables, analyzing queries and a small number of indexes, migrating data from YandexCloud to our own servers, timely backups, Designing databases and tables)4. The fight against bureaucracy and the mentality of employees who sit in their places for 10 years and they do not need anything:In the very first project, we needed integration with 1C, 1C employees assured us that this was impossible, because the platform was closed. At the moment, 4 projects have already been successfully integrated with 1C 💪

Creation of scrum team, hiring, interviewing developers, code-review, backend development:
 The problem: The company and counterparties, on whose territory we place base stations, interact on paper. Each month, contractors must submit hundreds of thousands of paper documents to HQ about how much electricity the base station consumes and how much the company owes them for rent. The main problem is that it's handmade and people make mistakes. If the counterparty makes a mistake, he needs to fill out the document again and send it to HQ. It happens that people make mistakes several times in a row and can turn off the power for the base station out of anger.The solution: A website where people enter the amount of electricity consumed per month + electricity losses. Based on this inputs, PDF documents are generated and are signed with an EDS on both sidesThe website is synchronized with the document management system. Employees see all new counter readings as a kanban board in which they can reject the readings, approve and move them to the next stage of manager approval. The manager can reject the counter readings or sign the PDF with his EDS and automatically generate a payment that will go to the bank

Input mask:The problem: the document managment system is outdated and has no integrations. the rent department has to fill a lot of inputs to close one deal. Each deal has to be accompanied with photos of different applications. our customers and employees mostly using whatsapp due to huge distance between them - all photos of customers’ applications are stored in phones of our employess. The solution: PWA that acts like a mobile app. in the document managment system was finalized with possibility to generate QR codes for each document. The PWA scans QR code and shows the employee required field where he should place photos of special applications. User can take a photo or chose it via image gallery and the data goes to API with placing images in separate folders. he document managment system listens to the root dir and on new file CRUD operation triggers the handler. In that way employees saved a lot of time and nerve cells because they have to deal with hundreds of applications each day Tech: PWA Vue.js, Express.js

Expense report system:The problem: Expense reporting on business trips was carried out manually. The person had to keep all bills and various documents proving that he was on a business trip. all documents from the regions were sent to the head office of Almaty, and often people lost their documents - for this reason, a package of documents was sent back to the employee so that he could supplement the missing bills and etcSolution: The website that integrated to the document managment system (1c), it:
sends emails and reminders to not forget to take a photo of each document (which are different for different types of business trips)on the UI page the were fields where the employee should take a photo of specific docs (bills, invoices, etc)the admin panel of UI had posibilities to approve or decline single photo or the whole document packif everything is ok, than the system tells to send hardcopy of applictions to the HQelse - the moderator writes comments on each situation Everything syncs with the document managment system

1. RealTime Financial PowerBi Dashboard The problem: each day the analysis of different financial indicators for CTO was done by hands of 3 people (sql reporter, financier x2)everything was done over excell and email. It took them 2-3 hours to match new data to the old one.
My Solution: LTE on BigData DWH that runs special SQL queries each day at 9am, than transformed to Pandas DataFrame and aggregated by particular columns for each record. Than this transformed data was stored in separate Postgresql DB and I’ve build local API to match the data on separate request,Skills: Python, LTE, Node.js Express2. Online Archive of old hardcopy application: 1. The problem: Company had tons of old hardcopy applications over 13 years of company existence that leads to problem where nobody can find special application in a fast time or even couldn’t be found due to loss or due to rule of storing outdated applications: 2. Solution: I’ve build an application that connects to scanner, and each time new document is scanned the image of it is going through the process of OCR with extracting the text in three languages (english, kazakh, russian). Then the full text of the scanned application was stored in Postgres and split to trigrams to for the full-text search or partial text search. 3. Technolgies: Scanner handler (Node.js) , API for application finding (Node.js), matching extracted application title in the document management system (Python, Kafka), Postgresql, OCR (tesseract + python), Docker, Gitlab CI/CD

Helping to reorganize traditional telecommunication business based on big data researches. Creating the architecture and eco-system to work faster with large scale amount of data. Building new services, platforms, API, microservices. Automating boring work to allow coworkers focus only on interesting parts of their work.