Skip to content
Prathamesh Kasar
Resume

Open to backend and product engineering roles

Hi, I'm Prathamesh KasarSoftware Engineer, backend and end-to-end product deliveryI take products from a business requirement to production, and own them after they ship.

Backend-focused engineer working in C# / ASP.NET Core and Python. I turn one-line business asks into clear rules, build them with tests, and find the root cause when production breaks.

See my work Get in touchHyderabad, India
Prathamesh Kasar, close-up portrait in a dark blazer
  • C#
  • ASP.NET Core
  • Python
  • FastAPI
  • SQL Server
  • EF Core
  • CQRS / MediatR
  • xUnit
  • Playwright
  • Mutation testing
  • Server-driven UI
  • Claude Code
  • Root-cause analysis

How every change I own moves

  1. 01Requirement

    Start from the business ask, even when it is one line.

  2. 02Spec

    Write down rules, edge cases and acceptance criteria before code.

  3. 03Build

    Implement against the approved design, with tests alongside.

  4. 04Verify

    Prove it works: tests, regression runs, and checking the real data.

  5. 05Release

    Ship with QA and mobile teams briefed on exactly what changed.

  6. 06Own in production

    Watch the logs, triage defects, and fix the root cause.

Proof in numbers

  • 1 yearowning production software at a US ed-tech product company
  • 7 productsworked across: Portal, bbSlate, bbFamily, BBConnect, BBSupport, BBEnroll and shared libraries
  • 1,395 → 1,652automated tests in the module I own
  • 32 / 32API regression cases passed, with no backend defects
  • 9 changesin about 3 weeks, spec-driven, to a VP release deadline

What I bring

Three things to remember me by

  • Ownership

    I own modules end to end: requirement, design, code, tests, release and production.

  • Root cause

    I prove why something broke before I fix it, so the same bug doesn't come back.

  • Business thinking

    I turn vague asks into rules people agree on, and explain technical work in terms of impact.

Featured work

Real problems from production

Case studies from real work, with the confidential parts left out.
All work

  • Production case study

    6 read sitesfixed before release

    The feature that had never worked

    Test weeks were invisible because the module read a column the Portal never writes. I found it before release and fixed detection across 6 read sites.

    • ASP.NET Core 8
    • EF Core
    • SQL Server
    • xUnit

  • Production case study

    10 of 42students processed before the silent stop

    The payment batch that stopped at 10 of 42

    A payment batch job silently stopped after 10 of 42 students. The cause was a blocking call to the payment gateway with no timeout.

    • ASP.NET MVC 5
    • SQL Server

  • Production case study

    2 APIsracing, reproduced on demand

    Proving a race condition with Playwright

    Two APIs, page submit and last-visited page, were racing each other. I proved it with a Playwright concurrency script, then fixed it.

    • ASP.NET Core
    • Playwright
    • SQL Server

How I work

Spec first. Test alongside. Own it in production.

Spec-driven and AI-assisted, with me deciding and verifying.
The full method

  1. 01 · Decide

    Understand the ask and the real data, check the impact, write the spec, get the design approved.

  2. 02 · Build

    Implement against the design, verify it line by line, update the spec, run every test.

  3. 03 · Ship

    Release, then brief QA and mobile on exactly what changed. Then watch it in production.

Now

What I'm working on

  • Owning the backend of the bbSlate In-Person module in production
  • Backend APIs for bbFamily's server-driven UI, in Python and FastAPI
  • Spec-driven, AI-assisted delivery with Claude Code
  • A spec-driven, multi-agent engineering pipeline built on Claude Code

Building something that needs an owner, not just a coder?

I'm open to backend and product engineering roles. The fastest way to reach me is email.

Email meprathameshkasar.work@gmail.comContact form