
Insights from recent episode analysis
Audience Interest
Podcast Focus
Publishing Consistency
Platform Reach
Insights are generated by CastFox AI using publicly available data, episode content, and proprietary models.
Total monthly reach
Estimated from 15 chart positions in 15 markets.
By chart position
- 🇺🇸US · Courses#1215K to 30K
- 🇦🇺AU · Courses#1455K to 30K
- 🇨🇦CA · Courses#1555K to 30K
- 🇯🇵JP · Courses#2330K to 100K
- 🇮🇳IN · Courses#3130K to 100K
- Per-Episode Audience
Est. listeners per new episode within ~30 days
39K to 144K🎙 Daily cadence·26 episodes·Last published 2w ago - Monthly Reach
Unique listeners across all episodes (30 days)
132K to 479K🇯🇵21%🇮🇳21%🇧🇷21%+12 more - Active Followers
Loyal subscribers who consistently listen
53K to 192K
Market Insights
Platform Distribution
Reach across major podcast platforms, updated hourly
Total Followers
—
Total Plays
—
Total Reviews
—
* Data sourced directly from platform APIs and aggregated hourly across all major podcast directories.
On the show
Recent episodes
S1E1 [Preview] - The Job Changed While You Were Sleeping
Jun 6, 2026
Unknown duration
System Design Interview: Payment Settlement Batch Processing
May 17, 2026
Unknown duration
Anatomy of `kubectl apply` - Inside the Kubernetes Control Plane
Apr 24, 2026
Unknown duration
Overview of Mastering REST API Design & Best Practices
Mar 25, 2026
Unknown duration
[DSA] Sliding Window Algorithm
Mar 13, 2026
Unknown duration
Social Links & Contact
Official channels & resources
Official Website
Login
RSS Feed
Login
| Date | Episode | Description | Length | |
|---|---|---|---|---|
| 6/6/26 | ![]() S1E1 [Preview] - The Job Changed While You Were Sleeping | SEASON 1 — "The Shift"Listen to - S1E1 Interview an engineer who transitioned from backend → AI engineer. Their story IS the season premise. | — | |
| 5/17/26 | ![]() System Design Interview: Payment Settlement Batch Processing | Design a batch processing system for end-of-day payment settlement at a payments company that processes 50 million transactions per day. The system must net merchant positions, calculate fees, and initiate fund transfers to merchant bank accounts within a strict bank cutoff window. Walk me through your design, covering reliability, scalability, and how you'd handle failures.Key TakeawaysThe outbox pattern is the canonical solution to the dual-write problem. Know it cold.Partition keys define ordering and parallelism — choose with intention, usually around the natural aggregation boundary (here, merchant ID).Throttling must be distributed when you have multiple workers — Redis-backed buckets or a sidecar.Idempotency is non-negotiable in payments. Design for at-least-once and dedupe.Retries are tiered: in-process for transient, delay-queue for slower-resolving, DLQ for terminal.Backpressure beats dropping — use Kafka lag as your buffer when downstream is slow.Reconciliation closes the loop — you don't know it worked until ground truth confirms.Corrections are new events — never rewrite history in a financial system. | — | |
| 4/24/26 | ![]() Anatomy of `kubectl apply` - Inside the Kubernetes Control Plane | When I run kubectl apply, the request is sent to the Kubernetes API Server, which acts as the entry point to the cluster.The API Server processes the request through several stages:Authentication – validates the client (certificates, tokens, etc.)Authorization – checks permissions using RBACAdmission ControllersMutating (e.g., inject defaults, sidecars)Validating (ensure request is compliant)Once validated, the object is persisted.The API Server stores the Deployment object in etcd, which is the cluster’s consistent key-value store.At this point, the desired state is recorded—but nothing is running yet.The Kubernetes Controller Manager detects the new Deployment via the API Server’s watch mechanism.Deployment Controller creates a ReplicaSetReplicaSet Controller creates the required PodsThis is all driven by control loops comparing:Desired state (in etcd)Current state (actual cluster)The Pods are created without a node assigned.The kube-scheduler:Filters nodes (resource constraints, taints, node selectors)Scores remaining nodes (resource availability, affinity rules)Assigns the best nodeOnce scheduled, the kubelet on the node pulls the image and starts the container."The important thing is Kubernetes is entirely declarative and event-driven.Nothing is executed immediately—instead, components continuously reconcile actual state toward desired state." | — | |
| 3/25/26 | ![]() Overview of Mastering REST API Design & Best Practices | Checkout the deep dive podcast here | — | |
| 3/13/26 | ![]() [DSA] Sliding Window Algorithm | The Sliding Window Algorithm is a powerful technique used to reduce the time complexity of problems involving arrays or strings—specifically those that require finding a sub-segment that meets certain criteria.Instead of using nested loops O(n^2), the sliding window maintains a dynamic range that "slides" across the data, usually bringing the complexity down to O(n).Problem:Find the maximum sum of a contiguous subarray of size `k`.public class SlidingWindow { public static int findMaxSum(int[] arr, int k) { int n = arr.length; if (n < k) return -1; int windowSum = 0; // 1. Compute sum of the first window for (int i = 0; i < k; i++) { windowSum += arr[i]; }int maxSum = windowSum;// 2. Slide the window from index k to n-1 for (int i = k; i < n; i++) { // Add the next element, remove the first element of the previous window windowSum += arr[i] - arr[i - k]; maxSum = Math.max(maxSum, windowSum); } return maxSum; }} | — | |
| 3/13/26 | ![]() [System Design] Database Connection Pooling | Video Summary of our audio podcast of [JAVA] Under the hood: Database Connection Pooling in Spring Boot | — | |
| 3/7/26 | ![]() [System Design] The Rate Limiter Playbook | Video overview of Distributed Rate Limiter | — | |
| 3/7/26 | ![]() [JAVA] Circuit Breaker Interview | Summary video of [JAVA] Circuit Breaker Deep Dive with Resilience4j | — | |
| 3/7/26 | ![]() [DSA] Pattern Recognition | Video Summary of - [DSA] Data Structure and Algorithm (DSA) problem-solving strategies and patterns | — |
Showing 9 of 9
Pitch Fit is a Pro feature
See how bookable this show is for guests, which brands already advertise, the per-episode ad value, and the best-fit guest and sponsor profile. The numbers are blurred on the free plan.
How readily this show books outside guests like you.
How proven this show is for host-read sponsorships.
For Guests
ProFor Advertisers
ProUpgrade to Pro to unlock guest cadence, sponsor categories, fit scores, and per-episode ad value for this show.
Chart Positions
15 placements across 15 markets.
Chart Positions
15 placements across 15 markets.
