Tildei Innovation & Technology Culture

What’s your rule for fast, safe releases — and what KPI proves it works?

My rule is small, frequent releases with concentrated, well-tested changes, going through a multi-environment deployment pipeline to ensure quality and compatibility. Releases must satisfy comprehensive test suites focused on mission-critical features and code paths. The KPI that provides it is the ratio of successful deployments compared to those that experience deployment issues, create degraded service or require rollback proves this works.

What standard or metric defines “quality” in your stack?

Checks and tests at every stage of the software development lifecycle. This includes: type checking; test coverage (unit, integration and end-to-end); durable execution (Temporal) history testing; code reviews from Claude and Microsoft Copilot, allowing engineers to focus their reviews on higher-level topics; and multiple human reviews and approvals for release promotion, all of which must be completed/passed, with no exceptions.

Name one AI/automation that shipped recently and its impact on your team and/or the business.

Recently, we shipped a built-in framework for rapidly defining custom tools for agents to securely engage with external integrations. This has enabled us to quickly integrate with many third-party services to provide value to any customer or prospect, regardless of their existing stack.