AceStack AI Open interactive practice

Public task directory

Technical interview practice tasks

Every entry below is a crawlable link to a unique public task page. This directory complements the interactive filters and keeps the complete catalog connected through standard pagination.

Page 187 of 386 · 18,491 tasks

Project Deep Dive · Hard · 40 min

Use one real project related to software supply-chain hardening. The target problem was: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and auditable exceptions without blocking delivery. Lead with scope,

Use one real project related to software supply-chain hardening. The target problem was: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and auditable.

Project Deep Dive · Hard · 40 min

Use one real project related to software supply-chain hardening. The target problem was: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and auditable exceptions without blocking delivery. Lead with scope,

Use one real project related to software supply-chain hardening. The target problem was: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and auditable.

Project Deep Dive · Hard · 40 min

Use one real project related to capacity and cost strategy. The target problem was: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful degradation, and investment triggers. Lead with

Use one real project related to capacity and cost strategy. The target problem was: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful.

Project Deep Dive · Hard · 40 min

Use one real project related to capacity and cost strategy. The target problem was: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful degradation, and investment triggers. Lead with

Use one real project related to capacity and cost strategy. The target problem was: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful.

Project Deep Dive · Hard · 40 min

Use one real project related to capacity and cost strategy. The target problem was: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful degradation, and investment triggers. Lead with

Use one real project related to capacity and cost strategy. The target problem was: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful.

Project Deep Dive · Hard · 40 min

Use one real project related to backup and recovery modernization. The target problem was: Replace assumed recoverability with tiered objectives, immutable backups, restore automation, data-integrity checks, and exercised ownership. Lead

Use one real project related to backup and recovery modernization. The target problem was: Replace assumed recoverability with tiered objectives, immutable backups, restore automation.

Project Deep Dive · Hard · 40 min

Use one real project related to backup and recovery modernization. The target problem was: Replace assumed recoverability with tiered objectives, immutable backups, restore automation, data-integrity checks, and exercised ownership. Lead

Use one real project related to backup and recovery modernization. The target problem was: Replace assumed recoverability with tiered objectives, immutable backups, restore automation.

Project Deep Dive · Hard · 40 min

Use one real project related to backup and recovery modernization. The target problem was: Replace assumed recoverability with tiered objectives, immutable backups, restore automation, data-integrity checks, and exercised ownership. Lead

Use one real project related to backup and recovery modernization. The target problem was: Replace assumed recoverability with tiered objectives, immutable backups, restore automation.

Project Deep Dive · Hard · 40 min

Use one real project related to identity and secret boundary redesign. The target problem was: Reduce credential blast radius through workload identity, least privilege, rotation, migration controls, and observable policy enforcement. Lead

Use one real project related to identity and secret boundary redesign. The target problem was: Reduce credential blast radius through workload identity, least privilege, rotation, migration.

Project Deep Dive · Hard · 40 min

Use one real project related to identity and secret boundary redesign. The target problem was: Reduce credential blast radius through workload identity, least privilege, rotation, migration controls, and observable policy enforcement. Lead

Use one real project related to identity and secret boundary redesign. The target problem was: Reduce credential blast radius through workload identity, least privilege, rotation, migration.

Project Deep Dive · Hard · 40 min

Use one real project related to identity and secret boundary redesign. The target problem was: Reduce credential blast radius through workload identity, least privilege, rotation, migration controls, and observable policy enforcement. Lead

Use one real project related to identity and secret boundary redesign. The target problem was: Reduce credential blast radius through workload identity, least privilege, rotation, migration.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for regional resilience migration. Current conditions: Move a revenue-critical service from single-region recovery to tested regional failover without violating data-integrity or availability

You own a twelve-month technical strategy for regional resilience migration. Current conditions: Move a revenue-critical service from single-region recovery to tested regional failover.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for regional resilience migration. Current conditions: Move a revenue-critical service from single-region recovery to tested regional failover without violating data-integrity or availability

You own a twelve-month technical strategy for regional resilience migration. Current conditions: Move a revenue-critical service from single-region recovery to tested regional failover.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for regional resilience migration. Current conditions: Move a revenue-critical service from single-region recovery to tested regional failover without violating data-integrity or availability

You own a twelve-month technical strategy for regional resilience migration. Current conditions: Move a revenue-critical service from single-region recovery to tested regional failover.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for deployment safety transformation. Current conditions: Replace fragile manual releases with progressive delivery, provenance controls, measurable rollback gates, and clear service ownership.

You own a twelve-month technical strategy for deployment safety transformation. Current conditions: Replace fragile manual releases with progressive delivery, provenance controls, measurable.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for deployment safety transformation. Current conditions: Replace fragile manual releases with progressive delivery, provenance controls, measurable rollback gates, and clear service ownership.

You own a twelve-month technical strategy for deployment safety transformation. Current conditions: Replace fragile manual releases with progressive delivery, provenance controls, measurable.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for deployment safety transformation. Current conditions: Replace fragile manual releases with progressive delivery, provenance controls, measurable rollback gates, and clear service ownership.

You own a twelve-month technical strategy for deployment safety transformation. Current conditions: Replace fragile manual releases with progressive delivery, provenance controls, measurable.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for Kubernetes multi-tenancy. Current conditions: Introduce safe cluster tenancy boundaries while preserving developer velocity, cost visibility, workload isolation, and incident diagnosability.

You own a twelve-month technical strategy for Kubernetes multi-tenancy. Current conditions: Introduce safe cluster tenancy boundaries while preserving developer velocity, cost visibility.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for Kubernetes multi-tenancy. Current conditions: Introduce safe cluster tenancy boundaries while preserving developer velocity, cost visibility, workload isolation, and incident diagnosability.

You own a twelve-month technical strategy for Kubernetes multi-tenancy. Current conditions: Introduce safe cluster tenancy boundaries while preserving developer velocity, cost visibility.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for Kubernetes multi-tenancy. Current conditions: Introduce safe cluster tenancy boundaries while preserving developer velocity, cost visibility, workload isolation, and incident diagnosability.

You own a twelve-month technical strategy for Kubernetes multi-tenancy. Current conditions: Introduce safe cluster tenancy boundaries while preserving developer velocity, cost visibility.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for infrastructure governance. Current conditions: Scale infrastructure-as-code ownership across teams while controlling drift, privilege, destructive changes, policy exceptions, and recovery

You own a twelve-month technical strategy for infrastructure governance. Current conditions: Scale infrastructure-as-code ownership across teams while controlling drift, privilege.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for infrastructure governance. Current conditions: Scale infrastructure-as-code ownership across teams while controlling drift, privilege, destructive changes, policy exceptions, and recovery

You own a twelve-month technical strategy for infrastructure governance. Current conditions: Scale infrastructure-as-code ownership across teams while controlling drift, privilege.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for infrastructure governance. Current conditions: Scale infrastructure-as-code ownership across teams while controlling drift, privilege, destructive changes, policy exceptions, and recovery

You own a twelve-month technical strategy for infrastructure governance. Current conditions: Scale infrastructure-as-code ownership across teams while controlling drift, privilege.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for SLO operating model. Current conditions: Shift teams from host-level alert volume to user-centered SLOs, error-budget decisions, actionable paging, and explicit reliability investment. Define

You own a twelve-month technical strategy for SLO operating model. Current conditions: Shift teams from host-level alert volume to user-centered SLOs, error-budget decisions, actionable.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for SLO operating model. Current conditions: Shift teams from host-level alert volume to user-centered SLOs, error-budget decisions, actionable paging, and explicit reliability investment. Define

You own a twelve-month technical strategy for SLO operating model. Current conditions: Shift teams from host-level alert volume to user-centered SLOs, error-budget decisions, actionable.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for SLO operating model. Current conditions: Shift teams from host-level alert volume to user-centered SLOs, error-budget decisions, actionable paging, and explicit reliability investment. Define

You own a twelve-month technical strategy for SLO operating model. Current conditions: Shift teams from host-level alert volume to user-centered SLOs, error-budget decisions, actionable.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for observability platform adoption. Current conditions: Standardize traces, metrics, logs, ownership metadata, and telemetry quality without creating uncontrolled cardinality or migration risk.

You own a twelve-month technical strategy for observability platform adoption. Current conditions: Standardize traces, metrics, logs, ownership metadata, and telemetry quality without.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for observability platform adoption. Current conditions: Standardize traces, metrics, logs, ownership metadata, and telemetry quality without creating uncontrolled cardinality or migration risk.

You own a twelve-month technical strategy for observability platform adoption. Current conditions: Standardize traces, metrics, logs, ownership metadata, and telemetry quality without.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for observability platform adoption. Current conditions: Standardize traces, metrics, logs, ownership metadata, and telemetry quality without creating uncontrolled cardinality or migration risk.

You own a twelve-month technical strategy for observability platform adoption. Current conditions: Standardize traces, metrics, logs, ownership metadata, and telemetry quality without.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for incident reduction program. Current conditions: Turn recurring high-severity incidents into a cross-team prevention program with ranked causes, funded controls, and measurable risk reduction.

You own a twelve-month technical strategy for incident reduction program. Current conditions: Turn recurring high-severity incidents into a cross-team prevention program with ranked causes.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for incident reduction program. Current conditions: Turn recurring high-severity incidents into a cross-team prevention program with ranked causes, funded controls, and measurable risk reduction.

You own a twelve-month technical strategy for incident reduction program. Current conditions: Turn recurring high-severity incidents into a cross-team prevention program with ranked causes.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for incident reduction program. Current conditions: Turn recurring high-severity incidents into a cross-team prevention program with ranked causes, funded controls, and measurable risk reduction.

You own a twelve-month technical strategy for incident reduction program. Current conditions: Turn recurring high-severity incidents into a cross-team prevention program with ranked causes.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for developer platform strategy. Current conditions: Build a paved road that improves lead time and reliability while preserving escape hatches, platform product discovery, and adoption measurement.

You own a twelve-month technical strategy for developer platform strategy. Current conditions: Build a paved road that improves lead time and reliability while preserving escape hatches.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for developer platform strategy. Current conditions: Build a paved road that improves lead time and reliability while preserving escape hatches, platform product discovery, and adoption measurement.

You own a twelve-month technical strategy for developer platform strategy. Current conditions: Build a paved road that improves lead time and reliability while preserving escape hatches.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for developer platform strategy. Current conditions: Build a paved road that improves lead time and reliability while preserving escape hatches, platform product discovery, and adoption measurement.

You own a twelve-month technical strategy for developer platform strategy. Current conditions: Build a paved road that improves lead time and reliability while preserving escape hatches.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for software supply-chain hardening. Current conditions: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and auditable exceptions without blocking delivery. Define

You own a twelve-month technical strategy for software supply-chain hardening. Current conditions: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for software supply-chain hardening. Current conditions: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and auditable exceptions without blocking delivery. Define

You own a twelve-month technical strategy for software supply-chain hardening. Current conditions: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for software supply-chain hardening. Current conditions: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and auditable exceptions without blocking delivery. Define

You own a twelve-month technical strategy for software supply-chain hardening. Current conditions: Add artifact provenance, dependency integrity, secret isolation, promotion policy, and.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for capacity and cost strategy. Current conditions: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful degradation, and investment triggers.

You own a twelve-month technical strategy for capacity and cost strategy. Current conditions: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for capacity and cost strategy. Current conditions: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful degradation, and investment triggers.

You own a twelve-month technical strategy for capacity and cost strategy. Current conditions: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for capacity and cost strategy. Current conditions: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance limits, graceful degradation, and investment triggers.

You own a twelve-month technical strategy for capacity and cost strategy. Current conditions: Resolve a capacity constraint by connecting demand forecasts, unit economics, performance.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for backup and recovery modernization. Current conditions: Replace assumed recoverability with tiered objectives, immutable backups, restore automation, data-integrity checks, and exercised

You own a twelve-month technical strategy for backup and recovery modernization. Current conditions: Replace assumed recoverability with tiered objectives, immutable backups, restore.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for backup and recovery modernization. Current conditions: Replace assumed recoverability with tiered objectives, immutable backups, restore automation, data-integrity checks, and exercised

You own a twelve-month technical strategy for backup and recovery modernization. Current conditions: Replace assumed recoverability with tiered objectives, immutable backups, restore.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for backup and recovery modernization. Current conditions: Replace assumed recoverability with tiered objectives, immutable backups, restore automation, data-integrity checks, and exercised

You own a twelve-month technical strategy for backup and recovery modernization. Current conditions: Replace assumed recoverability with tiered objectives, immutable backups, restore.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for identity and secret boundary redesign. Current conditions: Reduce credential blast radius through workload identity, least privilege, rotation, migration controls, and observable policy

You own a twelve-month technical strategy for identity and secret boundary redesign. Current conditions: Reduce credential blast radius through workload identity, least privilege, rotation.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for identity and secret boundary redesign. Current conditions: Reduce credential blast radius through workload identity, least privilege, rotation, migration controls, and observable policy

You own a twelve-month technical strategy for identity and secret boundary redesign. Current conditions: Reduce credential blast radius through workload identity, least privilege, rotation.

Technical Strategy · Hard · 40 min

You own a twelve-month technical strategy for identity and secret boundary redesign. Current conditions: Reduce credential blast radius through workload identity, least privilege, rotation, migration controls, and observable policy

You own a twelve-month technical strategy for identity and secret boundary redesign. Current conditions: Reduce credential blast radius through workload identity, least privilege, rotation.

Coding (Platform) · Easy · 35 min

Appointment Audit Directory

Workspace: Angular Difficulty: Easy Time: 35 minutes Context A candidate uses the Appointments screen to reproduce the final state from observable evidence. The supplied Angular project.