Four areas of work, connected by questions about state, trust and delivery. Choose one to see the decisions behind it.
Related engineering concerns across separate projects and roles. This is not a shared system architecture.
StateScopeDeliveryTrust
01JavaKafkaElixirObanRecover the workflow.What happens after a failure?Dead-letter handling, bounded retries, idempotent replay
Workflow recovery
Give failed work a way back.
Career account · Capital One, via Cognizant · 2018–2021
Java and Kafka
I owned Kafka workflows using Spring Boot and DynamoDB: dead-letter handling, bounded retries with backoff and idempotent replay.
Recovery controls are not a universal exactly-once or zero-data-loss guarantee. The separate OpenResty result of 12K+ transactions per second was measured in test environments.
Career account · HG Insights · 2021–2025
Elixir and Oban Pro
I built an idempotent contract-processing pipeline for 80K+ records, reducing reporting turnaround by 60%. Oban Pro also orchestrated scheduled, on-demand and event-triggered company-spend refresh.
Spend refresh moved from a manual monthly batch to a weekly cadence. My contribution was orchestration; the spend formula was an existing service.
Source: public career account, engineering decisions and résumé in the reviewed public record. Employment outcomes are not independently reproduced here. Read the résumé
02PostgreSQLData platformsNarrow the work.How much data needs to be read?30M+ rows, more than 60% lower dashboard latency
Data & query tradeoffs
Career account · HG Insights · 2021–2025
Read less. Keep the context.
At more than 30M PostgreSQL rows, I used partitioning, composite indexing and read replicas to reduce dashboard latency by more than 60%.
The decision
Make the query's scope explicit.
Partitioning narrows the relevant data; composite indexes support predicates within it. Read replicas separate read traffic from the primary.
Partition
A useful boundary still depends on the query's filter.
Index
Read access comes with write and maintenance costs.
Replica
Read capacity comes with replication lag to consider.
These are general tradeoffs, not a reconstruction of HG Insights' schema or deployment. The reported dashboard result combines the changes; it does not isolate each one's effect.
Synthetic illustrationChoose a query scope.Eight invented monthly partitions. No SQL is executed and no latency is measured.
Jan
Outside scope
Feb
Outside scope
Mar
Outside scope
Apr
Outside scope
May
Outside scope
Jun
Outside scope
Jul
Outside scope
Aug
In scope
1 of 8 illustrative partitions is in scope.
WHERE month = 'Aug'
With JavaScript off, the latest-month illustration remains visible.
The evidence & its limits
30M+ rowsPostgreSQL scale in the career account.
>60% lower latencyDashboard result; not the separate 60% contract-turnaround result.
Authored employment evidence. No production query trace or benchmark is exposed here. Read the public résumé
Read the source account
“He scaled PostgreSQL beyond 30M rows using partitioning, composite indexing and read replicas, reducing dashboard latency by more than 60%.”
Public experience record, HG Insights. The geo-standardization service separately normalized 15M+ US and Canada company records into canonical shapes, with a phased rollout led with stakeholders.
03AWSDynamoDBChoose the boundary.Where does responsibility live?What the record supports, and where it stops
AWS service paths
Start with an evidenced path.
Career account · Capital One, via Cognizant
Spring Boot, Kafka and DynamoDB
The public résumé places DynamoDB alongside the Kafka recovery workflows I owned. AWS is also part of my broader professional tools record.
The published record does not expose the table design, deployment topology or service-by-service AWS ownership. No broader AWS architecture is inferred here.
04ReactTypeScriptPythonCarry trust to the interface.Can the user inspect what happened?A runnable stream reducer demo, in your browser
Full-stack & applied AI
Reviewed source · ChatFormula1 v2
A response is a stream. Make its state legible.
My developing v2 connects a Python/LangGraph retrieval pipeline, an Elixir/Phoenix gateway and a typed React streaming client.
Streaming, conversation persistence and spend accounting.
03 PresentTypeScript · React
A reducer handles duplicate and replayed stream events.
The decision
Keep delivery state separate from answer quality.
The client can avoid repeating token batches and identify a gap. Those controls make transport behavior inspectable; they cannot establish that an answer is correct.
The v2 graph is stateless. Gateway persistence does not mean Redis graph checkpointing. The older v1 demo and developing v2 are separate. Current v2 deployment and live-model quality are unverified.
ChatFormula1 source commit 3574414d2786. The existing portfolio wrapper uses the Apache-2.0 reducer and adds bounded input validation. License
Assay is a separate Python/LangGraph and FastAPI project with an evaluation harness. It originated in SuperDataScience CP044; my contribution is not sole authorship of the upstream project. A harness alone is not a measured quality result. All projects & historical evaluationsAssay source
Runnable local demo · synthetic events
Replay the client behavior.
Uses the original reducer in your browser. No model, API or database request.
Delivery scenario
Ready · 0 events
Choose a fixture, then step through its events.
A late batch can fill the visible text while the gap stays flagged. The real app requests a persisted message; this demo does not make that request.
Open a work area to explore its decisions and evidence.
Career
One career. Several perspectives.
My recent applied AI work builds on a longer software engineering career. Earlier banking and data-platform roles are not years of AI engineering.
2026–present
Agilent Technologies
Senior Software Engineer, Manufacturing. Internal Gemba reporting and action-tracking applications with Power Apps and Power Automate; manufacturing operations, recipe authoring and internal AI enablement.
Broader plant rollout is expressed interest, not a completed deployment. No quantified savings or externally shipped AI product is claimed.
2021–2025
HG Insights
Software Engineer. Data standardization, PostgreSQL performance and Elixir/Oban Pro orchestration.
2018–2021
Capital One, via Cognizant
Software Engineer. Java/Kafka recovery and OpenResty service virtualization.
These separate browser applications pair local model execution with explicit review. Application links are from the public record; availability has not been retested in this offline review.
Banking operations
Payment Exception Desk
Exact constraints first, MiniLM ranking second, a reviewer decides.
No operational matching-accuracy claim. Does not move money or post entries.
Inputs and review decisions stay in browser memory; export before leaving. Caption Review downloads public model files. These are personal applications, separate from employer work.
Beyond work
Mostly, outside.
I hike when I travel, and I will walk a city end to end before I take a car through it.
Languages English, Hindi, Marathi · German A1–A2, learning.
I’m Soren, Prateek’s AI representative. Ask me the questions you’d ask Prateek about his work. I’ll explain what the sources show, share my read, and flag what he’d need to answer himself.
Hiring? Prepare for a conversation
AI voice · ElevenLabs generated it from the introduction above. It plays only when you press the button.
Choose evidence for your next conversation.
How Soren answers & privacy
Soren can research approved public sources and write a conversational interpretation grounded in the material it retrieved. Expand a source to inspect that material. Citations help you check an answer; they do not guarantee its accuracy. If conversational generation is unavailable, Soren identifies the evidence fallback. LinkedIn is a profile link, not a connected private account.
Your question and up to two prior visitor questions (6,000 characters total for those prior questions) and up to four public evidence references go to Cloudflare and, when enabled, Workers AI and optional Groq fallback. Previous answers are not sent as follow-up context. Laya may classify the current question. Providers may retain data under their policies; avoid sensitive information. Email and phone redaction does not anonymize text. Approved GitHub and Hugging Face sources may be read without account credentials. Up to six completed answers, your draft and the bounded follow-up context stay in this tab’s sessionStorage while you browse or reload. No transcript is stored in localStorage or an account. Clear conversation deletes this tab’s saved conversation, draft and follow-up context. Browser session restore may retain tab storage after closing; use Clear to remove it explicitly. If tab storage is unavailable, conversation stays in memory. Local brief selections and the email preview stay in memory only.