Nikita Klimov
ABOUT ME:
Quality, to me, is a decision-making discipline. Testing is how we create fast, trustworthy feedback so teams can ship with confidence—and so every user, including people with disabilities, can succeed. I’m a Senior QA/QC leader. My approach blends exploratory testing, observability, and right-sized automation with accessibility baked in from the start.
I’ve helped drive accessibility fixes across web and PDF workflows using NVDA, Colour Contrast Analyzer, and PAC; contributed to open-source (axe-core); and published a book on accessibility in software development. I lead a QA community chapter in Miami, mentor globally via ADPList, judge hackathons, and speak at conferences—including on inclusive testing and pragmatic quality engineering. What keeps me effective is clear risk framing, measurable outcomes, and transparent communication across design, engineering, and stakeholders.
On the AST Board, I want to scale practical, hands-on learning and access to opportunity. My priorities:
• AST Open Test Lab: a free, realistic sandbox (apps/APIs/data) where members practice, teach, and build portfolio artifacts.
• Accessibility & Inclusive Testing Program: micro-courses + clinics that help teams ship WCAG-aligned improvements.
• Mentorship Exchange: structured, time-boxed mentorship with tangible outcomes (artifacts, mock interviews, referrals).
• Test Equity Micro-Grants: small scholarships and connectivity/hardware support for under-represented testers.
I run initiatives with OKRs, public dashboards, and “good-enough-for-now, safe-enough-to-try” decision-making. I enjoy bridging cultures and disciplines to turn stalemates into consent-based decisions—and I won’t stop until learners see real outcomes: jobs, promotions, and accessible products in the world. If that aligns with your vision for AST, I’d be honored to earn your vote.
WHY QUALITY? In 2 paragraphs give us an overview of your philosophy on Quality and how you approach testing in support of achieving quality outcomes… Please provide (non-confidential) real world examples:
Quality is the outcome of informed decisions—not just passing tests. I treat testing as a disciplined way to surface risk, model real user goals (including people with disabilities), and give teams fast, trustworthy feedback to steer. That means context over dogma; whole-team quality over “throw it to QA”; and evidence over opinion. I mix exploratory testing and heuristics with automation where it truly buys us repeatability and signal—instrumented with observability so failures are explainable, not mysterious.
In practice, this looks like: (a) leading integration acceptance testing; and (b) driving accessibility audits for PDFs and web flows using NVDA, Colour Contrast Analyzer, and PAC, then partnering with design/engineering to ship semantic fixes, alt text standards, and form labeling—cutting our accessibility defect backlog and improving CSAT for keyboard and screen-reader users. These were team wins made possible by tight feedback loops and testability built in from the start.
This board role will require 10 - 20 hours per month of often self driven activities and the ideal candidate is someone who is willing to own an initiative and drive it through to completion... Is this something you are willing to commit to, and in your most honest moment, what will keep you motivated when the work gets hard and progress feels slow?
Yes—I can commit 10–20 hours/month and own initiatives end-to-end. I stay motivated by (1) learner outcomes (placements, portfolio artifacts, accessibility fixes shipped), (2) visible cadence (monthly demos, public dashboards), and (3) accountability (a board “buddy,” Kanban, and quarterly OKRs). When progress slows, I scope thinner vertical slices, ship something small, and use that momentum to unlock the next milestone.
What's one thing AST is doing right now that we should stop doing immediately, even if it's popular? And what's one bold experiment we should try, even if it might fail spectacularly?
• Stop (even if popular): Single, one-off webinars with no follow-through. They spike attendance but have shallow learning impact.
• Start (bold experiment): AST Skills Passport—evidence-based micro-credentials earned by completing real scenarios in the Open Test Lab (artifact review + oral defense). It’s harder than quizzes, but it elevates the craft and creates hiring signal employers can trust.
What is your history with AST? Describe why you are interested in serving on the AST Board and what personal / professional strengths make you an ideal board member for the organization?
Follow Up: Are there any particular initiatives or areas you are especially interested in driving / leading?
History & motivation. I’ve followed AST’s work for years and share its context-driven, skills-first ethos. I’ve recommended AST resources to mentees, engaged with the community’s writings, and aligned my local community work with AST’s mission. I’m applying for the Board to help scale that mission globally—especially around accessibility, ethical practice, and practical career ladders for testers outside “traditional” tech hubs.
Strengths I bring.
• Community builder: Chapter lead for a QA community in Miami; frequent mentor (ADPList); conference speaker; hackathon judge.
• Enterprise & delivery: Senior QA/quality leader on high-stakes integrations; comfortable with risk framing, stakeholder communication, and shipping.
• Accessibility & public good: Hands-on with WCAG, PDF/assistive tech testing, and open-source contributions (e.g., axe-core).
• Systems & ops: I run initiatives with OKRs, Kanban, measurable outcomes, and transparent comms.
Initiatives I’d love to drive.
1. AST Accessibility & Inclusive Testing Program (micro-courses + practice labs + community clinics).
2. AST Open Test Lab—a hosted sandbox of realistic, open apps/APIs for practice, teaching, and research.
3. AST Mentorship Exchange—structured, time-boxed mentorship with outcomes (portfolio artifacts, mock interviews).
4. Test Equity Grants—micro-grants and hardware/Internet stipends for under-represented testers.
“As an AST Board member, Nikita Klimov led the creation of the Open Test Lab and the Accessibility & Inclusive Testing Program, helping tens of thousands of testers build real portfolios and ship accessible software worldwide. He expanded AST’s global footprint with scholarships and translation efforts, advanced evidence-based, ethics-forward practice, and made practical, hands-on testing education accessible across borders.”
You're on a board committee with members from Japan, Brazil, Nigeria, Germany, and the US. The group is stuck on a decision because cultural communication styles are clashing and creating misunderstandings. What is your strategy for facilitating breakthrough and building genuine consensus?
Follow-up: Provide an example of how you've successfully worked across significant cultural or professional differences.
Strategy.
1. Reset the ground rules: shared working agreements, plain-language English, and time-zone fairness (rotate meeting times).
2. Clarify decision rights & criteria: who decides (consent-based), by when, using which criteria; record decisions in a public ADR log.
3. Structure the conversation: async pre-reads; “1-2-4-All” to surface ideas; then converge with options, trade-offs, and a consent check (“good enough for now, safe enough to try”).
4. Bridge styles: normalize direct/indirect preferences, invite written input for quieter voices, and use facilitators from different cultures to balance the room.
5. Close the loop: document the call, owners, and review date; verify understanding by restating in writing.
Example. On a multi-region integration (US, India, Eastern Europe) with high payroll risk, we were stuck on release gating. I introduced a short pre-read and a decision template (options, risks, data), ran a time-boxed workshop using “1-2-4-All,” and moved us to a consent decision: ship behind a feature flag with synthetic-data contract tests and observability SLOs; full rollout only after predefined accessibility and error-budget gates. We shipped on time, avoided a production incident, and the template became our standard for future releases.