Skip to content
View alwayspulkit's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report alwayspulkit

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
alwayspulkit/README.md

Pulkit Chaturvedi — Quality Engineering

Berlin, Germany · LinkedIn · Substack

I build quality platforms and engineer testing cultures — not just test suites.

Currently Quality Chapter Lead and Senior SDET at Delivery Hero, where I work across teams to raise the quality bar at the org level: from test infrastructure and flakiness reduction to defining quality principles that scale beyond any single team.

Previously led QA at NatWest (RBS) as AVP Test Lead, and built testing capability at Barclays and Fiserv across financial services domains.


Projects

Quality Gates CI/CD Reference Implementation

GitHub Repo

A production-grade quality pipeline demonstrating how to enforce quality gates systematically across the development lifecycle. Every gate has a documented threshold and rationale — not cargo cult rules.

What it covers:

  • Gate 1: Static Analysis (Checkstyle + SpotBugs) — fail fast, zero high-severity bugs
  • Gate 2: Unit Tests + Coverage (JaCoCo) — 80% line coverage enforced
  • Gate 3: Integration Tests — full HTTP stack validation with Testcontainers
  • Gate 4: Security Scanning (OWASP Dependency Check) — no critical CVEs
  • Gate 5: Performance Testing (k6) — p95 latency < 500ms, error rate < 1%

Built with Java 17, Spring Boot 3, JUnit 5, and GitHub Actions. The point isn't the tools—it's the thinking: how to make quality checks scale without becoming gatekeeping theater.

Flakey Tests Grouping Dashboard

GitHub Repo

A dashboard for identifying the root causes hiding behind flaky tests. Instead of debugging failures one by one, this tool groups them by common failure patterns and infrastructure issues, so you can fix the system, not the symptom.


What I think about

  • Systemic quality — finding the 20% of root causes behind 80% of test noise
  • Quality as a platform — tooling, dashboards, and standards that multiply team output
  • The IC-to-leader transition — how engineers move from task completion to org impact

Writing


Certifications

ISTQB Advanced Test Manager · Certified Scrum Master · Certified Scrum Product Owner · ISTQB Foundation

Popular repositories Loading

  1. alwayspulkit alwayspulkit Public

    Config files for my GitHub profile.

    1

  2. Quality-Gates-CI-CD Quality-Gates-CI-CD Public

    6 gated quality pipeline

    HTML 1

  3. MacCleanup MacCleanup Public

    Shell

  4. FlakeyTestDashboard FlakeyTestDashboard Public

    HTML

  5. mobile-saas-test-strategy mobile-saas-test-strategy Public

    Production-grade QE strategy for a cross-platform mobile SaaS — React Native, Expo, Supabase, RevenueCat. Anonymized.

    TypeScript