Cultural Fit and Working Style Questions

1) No CI/CD or flaky pipeline culture

• How I’d detect: Ask about deployment/testing cadence, review public job descriptions for "manual regression" or lack of CI tools. During interview, ask to see pipeline diagrams or recent build metrics.
• Why it matters: Without CI, automation’s impact is limited; I can’t ship fast or measure test effectiveness.

2) Tests treated as second-class (slow, UI-only suites)

• Detect: Ask about test pyramid, average test run time, and their strategy for API/unit vs end-to-end tests. Look for repos with massive UI test folders.
• Why: Forces slow feedback, high maintenance; my early wins come from building fast, reliable layers.

3) Lack of ownership or unclear QA-engineer split

• Detect: Ask who owns test infrastructure, flaky test triage process, and release sign-off responsibilities.
• Why: Ambiguity blocks impact — I need clear ownership to improve frameworks and reduce tech debt.

4) No metrics or problem-driven quality goals

• Detect: Ask for KPIs (MTTR, flakiness rate, coverage definition). Public blogs/engineering posts often reveal metrics maturity.
• Why: Without metrics, hard to prioritize work or demonstrate ROI for automation.

5) Tech-stack or language mismatch

• Detect: Review tech stack in job posting and repos; ask about languages/frameworks used for tests and infra.
• Why: If I’d need to rewrite core tools or learn unfamiliar stack, my early impact slows.

For each red flag I’d probe with concrete examples, propose immediate small experiments (short CI job, a focused API suite, flaky-test dashboard) to demonstrate value quickly.