Jeevan Jyoti SrivastavaEngineering leadership · Backend & AI
Menu
← Back to the deskJeevan’s field notes / Selected work
Selected workNo. 01

Engineering in practice

Systems work.
Decisions included.

Technical challenges across products and teams: the architecture I worked on, the trade-offs I weighed, and how I resolved the problems.

Browse more projects

02 / From the workbench

Good questions.
Working answers.

Some things I’ve built, untangled and learned from. Open a case study for the decisions behind the work.

01 / Voice AI · Stateful orchestration

A voice tutor with an explicit learning journey.

Connecting real-time speech with curriculum flow, ordered playback and recoverable learner state.

Open field note
My responsibility
Designed the voice pipeline and the boundaries between teaching, assessment and conversation.
The key decision
Keep lesson progression in explicit learner state, with bounded agents for each learning activity.
What changed
Streaming speech, learning agents and recovery coordinated within one learning flow.
Architecture & hands-on engineeringInside the architecture

02 / Backend reliability · AWS

Finding the bottleneck before adding servers.

Tracing peak-hour failures through Redis lookups, request-path I/O and misleading capacity signals.

Open field note
My responsibility
Led the investigation from production request behavior to infrastructure signals.
The key decision
Replace repeated cache scans and move expensive processing into background workers.
What changed
Cheaper request lookups, separated heavy processing and a repeatable capacity investigation process.
Platform architecture & performance leadRead the case study

03 / Data access · Asynchronous workloads

Keeping expensive work out of the request path.

Reducing unnecessary data work and separating background jobs from latency-sensitive APIs.

Open field note
My responsibility
Reviewed data access and execution patterns across platform workflows.
The key decision
Use lighter reads and bounded concurrency; make background processing an explicit boundary.
What changed
Reusable practices for data reads, asynchronous jobs and evidence-based cache sizing.
Platform architecture leadRead the case study

04 / Media infrastructure · Content delivery

Adaptive video for inconsistent connections.

Designing the path from source video to adaptive playback across bandwidth and device constraints.

Open field note
My responsibility
Designed the media publishing and delivery architecture for a learning platform.
The key decision
Separate encoding from durable storage and deliver adaptive HLS renditions through a CDN.
What changed
An automated publishing path with multiple renditions, independent of application request capacity.
Platform & media delivery architectureRead the case study

Further reading

More from the workbench.

Subscriptions · Product infrastructure

Keeping access in step with a subscription.

Coordinating payment events, plan changes and usage limits so product access follows a clear set of rules.

Speech assessment

Turning a spoken attempt into useful feedback.

Connecting audio preparation, transcription and word alignment so reading feedback stays attached to the learner’s attempt.

Media assets · Upload & delivery

An upload is only the start of a media workflow.

Connecting large-file uploads with media records, topic metadata, sharing and downstream learning experiences.

Curriculum · Content operations

From a content draft to the right classroom.

Structuring curriculum content, scheduling publication and tracking file handoffs across the content-production workflow.

Investment infrastructure

Keeping an investment journey connected across services.

Connecting investor accounts, bank verification, purchase orders, mandates and reports through a shared backend.

Classroom authoring & export

Taking an interactive classroom beyond the browser.

Adapting classroom authoring and video-export workflows so scenes, narration and assets can become a rendered lesson.

Jeevan Jyoti SrivastavaThink → build → understand