Interview-Ready Cloud Full-Stack Engineering

[Essential for first interviews — Tier 1] Shape an EF Core read query with projection and an explicit tracking choice while avoiding an N+1 access pattern.

[Essential for first interviews — Tier 1] Use a SQL Server execution plan to justify an index or query rewrite for one portfolio query.

[Essential for first interviews — Tier 1] Configure a deployable Angular client with an environment-aware API base URL and cross-cutting HTTP behavior through an interceptor.

[Essential for first interviews — Tier 2] Strengthen an Angular API model and component with strict TypeScript types instead of unsafe any usage.

[Essential for first interviews — Tier 2] Refactor one Angular feature into current standalone components and lazy-loaded route boundaries.

[Essential for first interviews — Tier 2] Compose an RxJS request flow with cancellation, error handling, and lifecycle-safe subscription management.

[Essential for first interviews — Tier 2] Explain and handle a transaction-isolation or optimistic-concurrency conflict in a portfolio update.

[Essential for first interviews — Tier 1] Explain how images, containers, layers, registries, networks, and volumes support a reproducible delivery workflow.

[Essential for first interviews — Tier 1] Author a multi-stage Dockerfile for the ASP.NET Core 8 API.

[Essential for first interviews — Tier 1] Author a multi-stage Linux Dockerfile that builds and serves the Angular application.

[Essential for first interviews — Tier 1] Compose the Angular, API, and SQL Server containers with persistent database storage.

[Essential for first interviews — Tier 2] Diagnose a container startup, port, DNS, configuration, or persistence failure using inspection and logs.

[Essential for first interviews — Tier 2] Build, tag, and publish versioned API and Angular container images to a registry.

[Essential for first interviews — Tier 3] Automate one critical portfolio journey against the composed local application with Playwright.

[Essential for first interviews — Tier 1] Assign capstone risks to unit, integration, frontend, end-to-end, or smoke tests in a concise test strategy.

[Essential for first interviews — Tier 1] Write xUnit tests for portfolio calculations using parameterized boundary and failure cases.

[Essential for first interviews — Tier 1] Choose appropriately among fakes, stubs, and mocks for time, price, and persistence dependencies.

[Essential for first interviews — Tier 1] Host the API with WebApplicationFactory and verify behavior through its HTTP boundary.

[Essential for first interviews — Tier 1] Build and explain a GitHub Actions workflow that restores, compiles, tests, and publishes the .NET and Angular applications using appropriate triggers, jobs, runners, artifacts, and permissions.

[Essential for first interviews — Tier 2] Use Testcontainers to verify an EF Core repository against an isolated SQL Server instance.

[Essential for first interviews — Tier 2] Test an Angular service or component with an isolated HTTP dependency.

[Essential for first interviews — Tier 2] Translate one GitHub Actions CI stage into Azure Pipelines YAML and compare their triggers, agents, artifacts, environments, secrets, and permissions.

[Essential for first interviews — Tier 1] Prepare a low-cost Azure practice environment with a resource group, least-privilege access, tags, a budget alert, and a teardown plan.

[Essential for first interviews — Tier 1] Draw and explain a basic capstone design covering requirements, request and network flow, components, data, identity, failures, security, and key trade-offs.

[Essential for first interviews — Tier 1] Deploy the API image through Azure Container Registry to Azure Container Apps and verify its health endpoint.

[Essential for first interviews — Tier 1] Connect the deployed API to a low-cost Azure SQL database through a Container Apps secret without placing credentials in source code or images.

[Essential for first interviews — Tier 1] Deploy the Angular image to Azure Container Apps and configure its API base URL, ingress, and explicit API origin allowance.

[Essential for first interviews — Tier 1] Run cloud smoke tests, inspect deployment health and cost, and remove all disposable Azure resources.

[Essential for first interviews — Tier 2] Compare App Service, Container Apps, AKS, and Functions, then justify a practical compute choice for a stated workload.

[Essential for first interviews — Tier 2] Authenticate GitHub Actions to Azure with workload identity federation and deploy a known image version.

[Important] Produce a STRIDE-based threat model for the capstone's assets, actors, trust boundaries, and highest-priority threats.

[Important] Explain OAuth 2.0 authorization code with PKCE and OpenID Connect in the context of an Angular SPA.

[Important] Configure Microsoft Entra application registrations for the Angular client and protected API.

[Important] Configure ASP.NET Core access-token validation and Angular token acquisition.

[Important] Enforce portfolio ownership and privileged operations with policy-based authorization.

[Important] Audit and harden the deployment's CORS allow-list and HTTP security headers for the Angular client.

[Important] Harden ASP.NET Core API endpoints against over-posting and injection using explicit DTO contracts and model validation.

[Important] Write integration tests that distinguish unauthenticated, forbidden, and permitted requests.

[Important] Define service-level indicators and practical objectives for availability, latency, and error rate.

[Important] Instrument the ASP.NET Core API with OpenTelemetry and export telemetry to Azure Monitor Application Insights.

[Important] Add Angular telemetry for page performance, failed requests, and unhandled exceptions.

[Important] Emit structured logs with correlation identifiers while excluding tokens and financial data.

[Important] Build a dashboard and actionable alert for traffic, latency, errors, saturation, and deployment health.

[Important] Diagnose an injected production failure with correlated telemetry and KQL queries.

[Important] Benchmark one API path, optimize the measured bottleneck, and verify the improvement.

[Important] Make an API operation safe for horizontal scaling by removing process-local user state.

[Important] Implement a BackgroundService that creates dependency-injection scopes and stops through cancellation.

[Important] Validate timeout, bounded-retry, and circuit-breaker behavior for the price client during an injected outage.

[Important] Design a queue-backed transaction import with idempotent processing and poison-message handling.

[Important] Design a market-price cache with explicit keys, expiration, invalidation, and stale-data behavior.

[Important] Use a load test and measured query behavior to improve a database access path under increased demand.

[Important] Identify scaling bottlenecks and single points of failure in the deployed capstone architecture.

[Important] Clarify functional requirements, quality attributes, constraints, and assumptions at the start of a design interview.

[Important] Estimate traffic, storage, throughput, and growth using explicit approximations.

[Important] Produce a high-level design covering APIs, identity, data stores, caching, messaging, and observability.

[Important] Select consistency, caching, and asynchronous-processing approaches for a stated business workflow.

[Important] Map a cloud-neutral design to Azure services while explaining cost, complexity, portability, and operational trade-offs.

[Important] Defend a modular-monolith or microservices choice based on domain, team, scale, and delivery constraints.

[Important] Complete a timed architecture scenario and respond systematically to scaling, failure, and security follow-ups.

[Important] Derive time and space complexity for C# code containing loops, recursion, and common collections.

[Important] Solve a lookup or frequency-counting problem with Dictionary or HashSet.

[Important] Solve an array or string problem with a two-pointer or sliding-window invariant.

[Important] Solve a nested-structure problem with an appropriate stack or queue.

[Important] Implement binary search while stating and maintaining its loop invariant.

[Important] Traverse a tree or graph while preventing repeated work and explaining resource usage.

[Important] Solve a timed C# problem while narrating trade-offs, testing edge cases, and analyzing complexity.

[Important] Build a STAR story bank covering ownership, delivery, failure, influence, learning, and measurable impact.

[Important] Explain a consequential technical decision through alternatives, evidence, trade-offs, and outcomes.

[Important] Describe a mentoring example that demonstrates diagnosis, guidance, feedback, and increased capability.

[Important] Structure a conflict example around shared goals, evidence, respectful disagreement, and follow-through.

[Important] Explain how you reduce ambiguity, sequence discovery, communicate risk, and make reversible decisions.

[Important] Lead a simulated production incident while separating mitigation, investigation, stakeholder updates, and retrospective actions.

[Important] Complete a mixed mock interview spanning the capstone, cloud delivery, coding, design, testing, security, and leadership.

[Later deepening] Recreate the capstone's baseline Azure resources in Bicep with parameters, outputs, secure settings, and a change preview.

[Later deepening] Refactor the baseline Bicep into reusable modules with environment-specific parameter files.

[Later deepening] Design private Azure network access with virtual networks, subnets, private endpoints, DNS zones, and controlled egress.

[Later deepening] Explain Kubernetes pods, deployments, services, ingress, configuration, secrets, and probes relative to Container Apps.

[Later deepening] Deploy a small capstone workload to AKS and compare its operational burden with Container Apps.

[Later deepening] Compare at-least-once delivery, deduplication, ordering, outbox, and saga patterns for distributed workflows.

[Later deepening] Define backup, recovery-time, recovery-point, and multi-region failover expectations for a critical service.

[Later deepening] Compare rolling, blue-green, and canary releases alongside their observability and rollback requirements.