CheckOps home

Leadership

From writing the checks to running the quality organization.

Fourteen years of QA, then engineering management of quality. The themes are the same ones I have taught under: leadership, automation, tools, and talks.

The dates below follow the public timeline onirfanahmadein.com. Titles move from hands-on QA to engineering manager. For the role I hold now, useLinkedIn. I do not keep a second biography here.

Tech leadership

Running a quality organization is an engineering job. The work is hiring, sequencing, and deciding what not to automate yet. At upGrad that meant standing up test engineering, then owning releases, then leading the practice across projects. The team grew from a first tester to groups of twelve and later twenty. The useful measure was not how many tools we bought. It was whether a change could be proved before it met a customer, and whether someone could say no with evidence.

Test automation

Automation is a product. It rots when it is a pile of scripts nobody owns. The through-line in the roles below is to make the check cheap enough to run on every change, and to keep a person in the loop for what the check cannot see. The public description of the QA engineering manager chapter names hands-on work with Cucumber, Selenium, Appium, Gatling, and OWASP ZAP. That is the shape of the practice: behavior, UI, mobile, performance, and a security check in the same pipeline.

Tech tools

The directory exists because teams lose weeks choosing an API client, a device lab, or a test manager. CheckOps is the shelf. Opinion stays on the essay pages, where a tool can be put back in its place. A directory entry is not a sponsorship and not a verdict.

Tech talks

I talk with engineering teams about checking versus testing, about building a quality organization, and about choosing a toolchain without buying a platform you will not run. If you want a session for your team or a meetup, write toirfan@checkops.comwith the audience, the date, and the decision you are trying to make. I would rather prepare for a real room than collect a list of past titles.

Timeline

  1. 2023–

    Senior Engineering Manager, upGrad

    Head of test engineering and cross-team initiatives, focused on test automation, performance testing, and security testing.

  2. 2020–2023

    QA Engineering Manager, upGrad

    Test engineering across projects and cross-team delivery. Led a team of 20+.

  3. 2018–2020

    Release Manager, upGrad

    Owner for releases, testing, and delivery practices across technology teams. Led a team of 12+.

  4. 2016–2018

    Software QA Lead, upGrad

    Joined as the first test engineer, started the test team and the automation, and grew the team to five.

  5. 2015–2016

    Software Quality Engineer, TinyOwl

    Quality ownership for the order-management product line, from test design and execution through automation and support.

  6. 2014–2015

    Senior Software Engineer, Amdocs

    In-house test automation for desktop UI and SQL workflows on CSM/CRM products.

  7. 2012–2014

    Software Engineer, Amdocs

    System testing: scripting and execution of test automation on Amdocs Ensemble.

Hire and advisory

If you are hiring an engineering manager for quality, or you want an advisory conversation about a release process, a flaky suite, or a toolchain, emailirfan@checkops.com. I take a small number of these. Start with the problem: what is shipping, what is breaking, and what you have already tried. A job description pasted in full can wait.