Sashikanta Sahoo
Healthcare products where every speedup is measured and every data path is designed for audit. The current build is agentic AI that can sit inside regulated systems.
Latency budget
What production actually moved.
Load time, deploy time, and API time. Each one was measured on a healthcare system that stayed up.
Practice
Platform first, model second.
The surface is React and Next.js. Under it, Node and AWS carry the API, and JWT with RBAC keeps each tenant on its own trial data. When a model is allowed in, retrieval, citation, and the audit log are part of the design, not a later patch. The products are eCOA, prior authorization, and the clinical document path around them.
Case file
Systems with a before and after.
Public retrieval builds sit beside production eCOA and prior authorization. Open a card for the architecture.
Scroll sideways · click for details
Clinical tenure
From the UI to the tenant boundary.
eCOA and GenAI at IQVIA, prior authorization at CitiusTech, a CGM glucose graph at L&T, then the first enterprise front end.
IQVIA R&D Solutions
SDE-4 · Senior Full Stack Engineer. Clinical technology, full-stack architecture, and GenAI enablement for pharmaceutical R&D.
Platform
- Lead the clinical data platform on React and Next.js, with Node.js and TypeScript services on AWS.
- Own eCOA delivery for ePRO, ClinRO, ObsRO, and PerfO: protocol-driven forms, offline capture, and cloud sync for sponsor and CRO monitoring.
- Cut load time about 30% by batching chatty APIs, caching hot reads in Redis, and rewriting the slow query plans.
- Standardised JWT and RBAC so each tenant only reaches its own trial data, with HIPAA audit logs on access.
- Rebuilt the Jenkins and AWS pipeline from 35–40 minutes to under 25, with no outage on the cutover.
- Mentor three engineers through architecture reviews before a clinical change is allowed to ship.
- Keep tenant isolation on the query path itself, so a missing filter cannot leak another sponsor's trial data.
GenAI
- Prototype RAG for clinical PDFs: ingestion, chunking, embeddings, and semantic retrieval so answers stay tied to the source passage.
- Build citation-backed Q&A over trial documentation, with the retrieved chunk shown beside the model answer.
- Run structured extraction with prompting plus schema validation, and block records that fail the schema before they enter downstream systems.
- Scope every model call with RBAC, sanitize prompts and outputs, redact PII, and write an audit log for the request.
- Work with compliance and clinical stakeholders on those guardrails before an AI feature is allowed into production.
CitiusTech
Senior Software Engineer → Tech Lead. Healthcare prior-authorization platform, above 10k requests a day.
Delivery
- Owned the prior-authorization engine end to end: React screens, Node.js APIs, MongoDB and PostgreSQL records, above 10k requests a day.
- Ran a full performance audit, rebuilt the heavy screens, and added lazy loading. Page load dropped about 25%.
- Raised API speed about 20% with Redis on the hot reads, MongoDB compound indexes, and removal of N+1 query loops.
- Put SonarQube gates on CI and cleared 40+ code smells in two sprints so quality stopped being a late review.
- Shipped a React and TypeScript component library in Storybook, aligned to WCAG 2.1, and adopted by three product teams.
- Moved from senior engineer to tech lead in 2022: design reviews, shared UI contracts, and stakeholder tradeoffs on the insurance workflow.
- Treated the component library as the contract between teams, so prior-auth screens stopped drifting in spacing, focus order, and error states.
L&T Technology Services
Software Engineer. CGM and glucose monitoring. The graph is the day's sensor curve, and the CGM data also supplies the daily insulin details.
Monitoring
- Built the glucose monitoring graph from CGM readings so a day of sensor data reads as one curve.
- Used that CGM data to show daily insulin details, instead of leaving insulin off the graph.
- Aligned glucose and insulin on the same day timeline, so a rise or drop in glucose can be read next to the insulin for that day.
- Kept the day as the unit of review: one graph, the sensor curve, and the insulin that CGM data recorded for it.
Huawei Technologies
Associate Software Engineer. First role after graduation, inside a large enterprise JavaScript front end.
Foundation
- Fixed UI defects and shipped small features inside a large shared JavaScript front end, without breaking neighboring modules.
- Learned the delivery path that the later roles assumed: Git history, code review comments, and Agile sprint commitments on a shared front end.
- Shipped fixes in small slices so a change in one screen did not regress the rest of the enterprise UI.
Workbench
The runtime I trust.
Typed UI, tenant-aware APIs, vector retrieval, and the pipeline that ships them. One layer at a time.
Next.js
Select a branch to explore its connected skills.
Review bar
Rules that survive a merge.
Performance, HIPAA, shared UI, and a number you can point at. That is the bar before a clinical change ships.
A clinical screen is a latency budget. No change merges without a before and after on load time or the API.
HIPAA is the data flow: JWT, RBAC, tenant filters, PII redaction, and an audit log written on the request.
A Storybook library is a UI contract. Spacing, focus order, and error states stay stable when the next team adopts it.
A review that teaches beats a review that only patches. Pull the engineer up with the code.
If the improvement cannot be measured, it has not been proven.
Ship, measure, tighten the query or the pipeline, then repeat until the architecture itself is the bottleneck.
In flight
What the next quarter is for.
Agent graphs, retrieval quality, and the platform around them. This is the work beside delivery, not a second résumé.
Record
The file a recruiter keeps.
Education, the direct line, and the PDF. Same tenure as the timeline: Huawei, L&T, CitiusTech, IQVIA.
B.E. Computer Science from Govt. College of Engineering, Kalahandi · BPUT. 8.5+ years from Huawei to SDE-4 at IQVIA R&D Solutions.
Open channel
Name the conversation.
Open to Senior, Lead, and Principal roles. Bengaluru · Remote · Hybrid. Pick a case. The note opens in your mail app with that subject already set.