What kind of team would you prefer not to work with?

I prefer not to work with teams that lack psychological safety and operate in a constant firefighting mode, where technical debt is normalized, and effective communication is absent.

Such environments often stem from a lack of psychological safety, where team members fear failure or asking 'dumb' questions, stifling innovation and learning. This frequently leads to a constant firefighting mentality, where teams are reactive to production issues rather than proactively building robust solutions. For a data engineer, this means less time for critical tasks like optimizing Spark jobs (e.g., managing partitions to prevent data skew), implementing robust data quality checks (e.g., dbt tests), or designing resilient data pipelines with proper error handling and observability.

Furthermore, teams that undervalue documentation, thorough testing, or work-life balance inevitably accumulate technical debt. Poor documentation of data models or Kafka topic schemas makes onboarding difficult and debugging complex. A lack of testing leads to silent data quality issues, impacting downstream analytics. Opaque decision-making and politics over merit can also erode trust and motivation, hindering collaborative problem-solving essential for complex data challenges.

For instance, in a team that neglects testing, a critical customer_id column might silently contain nulls or duplicates. While a robust team would implement dbt tests like unique and not_null directly in their model definitions, a struggling team might only discover this issue much later, impacting critical business reports and requiring costly data backfills. This highlights the trade-off between upfront investment in quality and the exponential cost of fixing issues downstream.

# models/marts/core/dim_customers.yml
version: 2
models:
  - name: dim_customers
    columns:
      - name: customer_id
        description: Unique identifier for the customer.
        tests:
          - unique
          - not_null

In the interview, also mention your proactive approach to improving processes from within and how you assess team culture during your own due diligence.