Skip to the work

Prateek Mulye · Software engineer

Different systems.
Connected thinking.

11+ years across banking, data platforms and manufacturing. I build reliable software and bring that experience to practical AI applications.

Explore the decisions

Based in Santa Barbara, California. Open to engineering opportunities.

  1. Backend
  2. Full-stack
  3. Applied AI
Work, decisions and evidence

The work, connected

Follow a concern.
Find the evidence.

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.
01Java Kafka Elixir ObanRecover
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é

02PostgreSQL Data 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.
JanOutside scope
FebOutside scope
MarOutside scope
AprOutside scope
MayOutside scope
JunOutside scope
JulOutside scope
AugIn 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.

03AWS DynamoDBChoose
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.

04React TypeScript PythonCarry 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.

01 RetrievePython · LangGraph

Schema-validated routing, parallel retrieval, fallback.

02 DeliverElixir · Phoenix

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.

Inspect the pinned React reducer
Source & attribution

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 evaluations Assay 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 eventsNo events yet.

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.

    Read the full career record

    Personal applications

    AI with a person
    in the loop.

    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.

    Building energy

    Load Review

    A TensorFlow.js regressor must beat the better baseline before flagging.

    All three public-data trials withheld flags. Assumed occupancy; no savings claim.

    Media editing

    Caption Review

    Whisper suggests caption differences. A person listens, edits and exports.

    Speech can be misheard. Synthetic voice checks are not an accuracy benchmark.

    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.

    Travel, photographs and the personal record
    Prateek at the Koko Head summit, with Oahu and the ocean behind him.
    Koko Head, Oahu
    Prateek standing on a sailboat deck with green mountains and blue water behind him.
    On the water
    Prateek in a white cap on rocks beside a pool below a waterfall.
    After the trail

    Start a conversation

    Have a hard problem?
    Let's talk about it.

    prateekmulye@gmail.com

    Let’s talk

    Paste the role. Get a sourced fit brief.

    The router detects what the role asks for. Each requirement is matched to evidence from my record, written in advance and linked to its source. It detects; it never writes claims.

      Or go direct:EmailRésuméLinkedIn

      Submitting sends the role to Cloudflare and, when enabled, Laya on Hugging Face. Contact redaction does not anonymize it. No role is sent when this panel opens.