Kutsan Aleksandr
Senior QA Engineer - PSBank
Moscow, Russia

Senior QA Engineer

PSBank



Native City: Voronezh, RU

Current City: Moscow


Education: Higher, Technical. Military Space Academy by the name of A. Mozhaisky (2011), St. Petersburg

Specialization: Operations modeling and research in technical organizational systems

Career:
  • QA and Developer, ADM-Telecom, Voronezh, RU
  • Junior QA, Reksoft, Voronezh, RU
  • QA, Reksoft, Voronezh, RU
  • Senior QA, Reksoft, Voronezh, RU
  • Project Manager (QA Team), Reksoft, Voronezh, RU
  • Head of Business Development Department (QA and Testing), Reksoft, Saint-Petersburg, RU
  • Associate Manager (QA Architect), Accenture, Moscow, RU
  • Senior QA Engineer, PSBank, Moscow, RU

Key achievements:
  • ISTQB Certified Professional Tester
  • HP ALM Certified Professional
  • Member of the Russian College of Software Testing Experts (RSTQB) 
  • Accredited ISTQB examiner in Russia
  • Member of the largest professional IT conferences CEE SECR, SQA Days, Agile Days

Starting career in 2012 as a Junior QA engineer. During time, was rising up to QA Team Lead, Crisis Project Manager (QA Team) and Head of Business Development Department (QA and Testing) in Reksoft.

Over the years, had been engaged in analytic-, testing-, team- and project management activities at various projects for the Russian public sector, E-commerce, Retail domain, Banks and Financial domain and envolved in QA research and testing systems, based on image and speech realtime analysis.

Since 2020, working in PSBank, Moscow as Senior QA Engineer


Talks (2)
  • 24.02.2019
    Economics of software testing, v.2.0

    The continuation of Alexander Alexandrov's talk "Economics of software testing, v.2.0" where we will extend the field for discussions and discuss the issues of the economics of testing with the audience.


    The main points of the talk: 

    • Exhaustive testing is not possible. 
    • Testing is as well an economic activity. 
    • Version 1.0, or What need to do. We work within a plan and evaluation, when a lack of resources, we ask to add them (extensive approach).
    • Version 2.0, or How need to do. We work within a plan and assessment as efficiently as possible (intensive approach).

    The round table will be devoted to the discussion on how to proceed to version 2.0, analysing the following tasks and using reasonable labour costs efficiently, analysing: 

    • What the test cases we need (do we really need them?). 
    • What the test data we need.
    • What testers we need - a few strong ones (but expensive) or many of weak (but inexpensive). 
    • What kind of automation we need (do we need it at all), what tools, coverage.

    • Hard
    • SQA Days / 25
  • 13.09.2016
    How not to crash and burn on Scrum’s fast track of advantages: Scrum team testing organization and optimization when working with public sector customers

    Amongst IT companies and project teams, in today’s world of software development, preference is being given ever more often to Agile methodologies of achieving visibility and transparency in software development and testing processes, improving their efficiency, and reducing project risks, which, as a result, yield a positive effect on the quality of the product. When applying Agile methodologies while working on projects, particularly for public sector customers, one must be prepared for unexpected challenges in forming the interaction of development and testing teams within the bounds of a project. In my report, listeners will get to find out how the paths for the solution of this specific problem, as well as others, were found in practice and how, considering all of the particularities in working with the public sector, to properly organize and stamp out a huge product’s the development and testing process.

    • Average
    • 20 min
    • SQA Days / 20
Chat with us, we are online!