Shriji Barot

Shriji Barot

R&D engineering leader — test, validation, and instrumentation for advanced energy systems

I spent nine years running R&D programs on plasma, electrolytic, and calorimetric reactor platforms across six laboratory sites. I designed the experiments, built much of the instrumentation they ran on, led the team, and reported results directly to the CEO and board. Experience gained from working at Industrial Heat LLC.

Most of that work came down to one question: is this effect real, or is it the measurement? Answering it well meant building better instruments, running honest controls, and being willing to find the flaw in your own result.

Experience

Where I've worked

R&D Lead Engineer / Technical Program Manager

Aug 2019 – Nov 2025 · Raleigh, NC

Industrial Heat LLC

  • Senior engineering and program lead across all technical work, reporting directly to the CEO and board.
  • Led an 8–10 person team of engineers, technicians, interns, and contractors across six laboratory sites.
  • Ran weekly engineering syncs, monthly executive reviews, and milestone reviews; maintained integrated schedules, dependency maps, and technical risk registers.
  • Managed a $1M+ annual program budget and coordinated outside partners, vendors, and contractors.
  • Built distributed DAQ and control systems across all six sites, including custom instrumentation that replaced expensive commercial hardware.
  • Established GitHub CI/CD for version control of software and hardware schematic releases.
  • Directed experimental design, system validation, safety procedures, and failure mode analysis for novel, safety-critical programs.

R&D Engineering Project Manager

May 2016 – Aug 2019 · Champaign, IL

Industrial Heat LLC

  • Led experimental design, thermal modeling, and instrumentation for metal hydride energy storage systems, including custom calorimetry hardware and gas handling.
  • Built automated DAQ and control systems in Python, MySQL, and LabVIEW, including electronics and solenoid valve control integration.
  • Designed experimental apparatus in SolidWorks and managed fabrication through to working hardware.
  • Onboarded and mentored new engineering hires; supervised interns and reviewed experimental plans and documentation.

Founder & Principal

2025 – present · Raleigh, NC

Ad Astra Research LLC / Ad Astra DAQ LLC

  • The umbrella I take freelance work under: independent technical validation and feasibility assessment for investors evaluating advanced energy and deep tech companies. A one-person practice rather than a firm.
  • Ad Astra DAQ holds DAQ hardware and software developed over a decade of field use, licensed out in an equity-only spinout arrangement.

Founder & Lead Developer

2025 – present · Remote

LootScout

  • Built and shipped a React Native / TypeScript mobile app for collectibles price intelligence, solo and full-stack.
  • Supabase/PostgreSQL backend with multiple pricing API integrations, EAS build and deployment, and n8n automation workflows on a self-hosted VPS.

Selected work

Things I built and how I verified them

Confidentiality limits what I can show from this work, so these describe the problem, the approach, and how the result was checked rather than specific outcomes. Happy to go deeper in conversation where appropriate.

Third-party technology evaluation: an emissions reduction claim

Problem
An outside inventor submitted a retrofit device for small internal combustion engines, claiming it largely eliminated carbon emissions while multiplying fuel efficiency, alongside several exotic physical claims about what was happening inside it. I ran the evaluation program and owned the determination.
Designed and ran
A matched control-versus-retrofit campaign across multiple engine sizes and load levels, using identical fuel volumes, two independent exhaust gas analyzers from different manufacturers, and component-by-component disconnection to isolate what each part of the device actually contributed. I also tested a post-removal state — device stripped off, engine otherwise unchanged — to confirm the baseline returned.
What the data showed
The retrofitted configuration produced exactly what the claim predicted: dramatically lower carbon species and much higher oxygen in the exhaust, consistently, across every load and both engines. The fuel efficiency claim did not hold at any load.
Where it broke
The analyzers measured concentration, not mass flow. The device introduced a large volume of additional air into the exhaust path, and the apparent emissions improvement scaled with how much air it pulled. Without intake and exhaust flow measurement there was no way to convert concentration into total emitted mass — which is the quantity the claim was actually about. A device that dilutes its own exhaust looks identical, on a concentration-only instrument, to one that eliminates emissions.
Also documented
A leak in the device that could recirculate exhaust back to the intake, inconsistent probe placement between runs, and heat damage to one analyzer's probe partway through the campaign. Each was written into the report as a stated limitation on the data rather than smoothed over, because a reader needs to know which conclusions the apparatus could actually support.
Outcome
The determination was that the claim was not demonstrated, together with a specification of exactly what would demonstrate it: intake and exhaust flow measurement, fuel consumed by mass rather than volume, in-situ mass spectrometry to detect alternative carbon products, before-and-after mass measurement of the device to test for deposition, and calibrated power measurement at the load. I designed that follow-on protocol. The point was never to dismiss the technology — it was to make the next round capable of producing an answer either way.

* Details of the technology, the parties involved, and the measured values are confidential and have been generalized here. What is described is the validation approach and the reasoning behind the determination.

Flow calorimetry resolving ±0.05°C

Problem
Measuring small thermal power changes on experimental energy systems in electrically and thermally noisy lab conditions, where the effect under investigation was close to the noise floor.
Built
A water flow calorimeter resolving ±0.05°C differential temperature — roughly ±1.5 W on a 100 W system — with full error analysis, baseline drift correction, and uncertainty quantification built into the measurement rather than estimated afterward.
Verified
Calibration runs against known resistive input power across the operating range, with mass flow cross-checked gravimetrically against the flow meter's own reading.

Charged particle detection below 100 keV

Problem
Distinguishing genuine charged particle events below 100 keV from electrical noise and detector artifacts, where a false positive would have been indistinguishable from a real result.
Built
A solid-state detector chain with RF amplification, using pulse-shape discrimination and shielding geometry to separate signal from background below 100 keV, paired with custom Python peak discrimination software. Also worked with nuclear track detectors, diamond detectors, and gamma spectroscopy across the same programs.
Verified
Shielding geometry validated against modeled attenuation; extended background characterization runs analyzed with identical discrimination logic to establish the false positive rate.

Distributed DAQ across six laboratory sites

Problem
Synchronized, trustworthy data from many concurrent experiments across six sites, at a hardware cost the program could actually carry. The deeper problem was fragmentation: instruments accumulated over years, each with its own vendor software, file format, and clock, reconciled by hand in spreadsheets afterward — which is exactly where errors enter and stay invisible.
Built
Distributed data acquisition and control in Python, SQL, and LabVIEW, with custom multi-channel isolated instrumentation replacing commercial equipment that would have consumed a large fraction of the budget.
Centralized control
The part that mattered most was one piece of software that talked to every instrument on the bench regardless of vendor or protocol, streamed everything into a single timebase, and let an operator configure and run an experiment without touching six different applications. Parallel experiments ran under independent control, with structured session and channel schemas and a browser-based interface for remote monitoring. Simple enough to use correctly under pressure, structured enough that a dataset from eighteen months earlier could still be traced to the configuration that produced it.
Verified
Per-channel calibration frameworks, with configuration control and version-managed releases through GitHub CI/CD so any recorded dataset could be traced to the exact software and hardware revision behind it.

A recorded walkthrough of a centralized DAQ web interface built along these lines:

Watch the interface walkthrough

* This video is an example of what centralized DAQ streaming and control software can look like, based on a system I have worked on in the past. It is shown to illustrate the approach rather than as a product — I can build a comparable system from scratch for a given instrument set.

Gas dosing and pressure regulation for under $300

Problem
Precise gas dosing and pressure control for electrolytic and metal hydride platforms, without commercial controllers priced well beyond what the experiment could justify.
Built
A dosing and regulation system using orifice gaskets, low-cost solenoid valve actuators, and a custom Python control layer — specified against what the experiment actually needed to resolve rather than against a catalog.
Verified
Dosing and pressure accuracy characterized directly on the platforms it served, under operating conditions.

Calibrated four-wire PT1000 probes for under $20 each

Problem
Programs needing dozens of accurate temperature probes, where catalog prices made adequate sensor coverage unaffordable and teams were tempted to under-instrument.
Built
Custom four-wire PT1000 RTD probes using top-tier sensing elements, assembled and calibrated in-house for under twenty dollars each, with shielded cabling designed for the electrical environment they operated in.
Verified
Calibrated against a reference standard before deployment, with periodic recalibration built into the lab's operating procedure.

High-voltage plasma experiments on UHV platforms

Problem
Running novel plasma experiments safely and repeatably on systems with genuine hazard potential and no established operating procedure.
Built and ran
High-voltage plasma experiments including AC plasma and pulsed capacitor-bank discharges, on ultra-high-vacuum and gas handling platforms. I owned the experimental design, the safety procedures, and the failure mode analysis.
Verified
Full system validation before each campaign, with interlocks and procedure review as a precondition for operation.
Note
Specifics on voltages, energies, and pressures are covered by confidentiality.

Materials characterization supporting experiment interpretation

Problem
Understanding what physically changed in a sample after a run, to distinguish genuine material effects from contamination, handling damage, or surface artifacts.
Worked with
SEM/EDS, TOF-SIMS, XRD, Raman spectroscopy, and surface profilometry, alongside sample preparation including plating, annealing, etching, and rolling.
Verified
Pre- and post-run characterization on matched samples, with control specimens processed identically but not exposed to the experimental condition.

Instrumentation & tools

What I work with

DAQ & automation

  • Python, LabVIEW, SQL / MySQL, C, Arduino
  • Distributed multi-site acquisition
  • Instrument control and calibration frameworks
  • GitHub CI/CD and configuration control

Sensors & detectors

  • Solid-state charged particle detection below 100 keV
  • Pulse-shape discrimination with RF amplification
  • Nuclear track detectors, diamond detectors
  • Gamma spectroscopy
  • PT1000 RTDs, thermocouples, flow calorimetry

Experimental systems

  • Ultra-high vacuum and gas handling
  • AC plasma and pulsed capacitor-bank discharge
  • Electrolytic and metal hydride platforms
  • RF systems and interference characterization

Design & analysis

  • SolidWorks, Autodesk, MATLAB
  • Thermal modeling and heat transfer analysis
  • Error propagation and uncertainty budgets
  • Linux, signal processing tooling

Materials analysis

  • SEM/EDS, TOF-SIMS
  • XRD, Raman spectroscopy
  • Surface profilometry
  • Plating, annealing, etching, rolling

Software

  • React Native, TypeScript, Supabase / PostgreSQL
  • Docker, n8n workflow automation
  • Retrieval and language-model tooling for private document sets
  • AI-assisted development workflows

Leadership

How I run a program

The technical work only matters if the program around it holds together. Most of what I learned about that came from doing it without a template.

01

Team and structure

Led an 8–10 person team of engineers, technicians, interns, and contractors distributed across six laboratory sites, with clear ownership defined per workstream rather than per person.

02

Program rhythm

Weekly engineering syncs, monthly executive reviews, and milestone-gated technical reviews. Integrated schedules, dependency maps, and technical risk registers maintained continuously rather than assembled for meetings.

03

Budget and investment

Managed a $1M+ annual program budget, including ROI and feasibility assessment on technology investments and coordination of outside partners, vendors, and contractors.

04

Executive interface

Reported directly to the CEO and board — translating technical status, design trade-offs, and program risk into decisions leadership could actually act on, including recommendations to stop work that was not going to pay off.

05

Developing engineers

Mentored engineers and technicians and built onboarding for new hires, deliberately structured to push early-career people across disciplines rather than into narrow specializations. Deep hands-on lab capability is getting rarer, and it does not develop on its own.

This is the part of the work I most want to keep doing. Passing on accumulated skill and judgment to newcomers — so they can operate confidently in hands-on technical environments rather than only around them — is worth as much over time as anything I build myself.

Education

Background

M.S. Aerospace Engineering

2018

University of Illinois at Urbana-Champaign

Thesis: D₂ and H₂ interactions with chemically reactive metal hydrides — hydrogen storage, reaction kinetics, and thermal systems. The work fed more or less directly into what I spent the following decade doing.

B.S. Aerospace Engineering

2016

University of Illinois at Urbana-Champaign

Ad Astra Research

Ad Astra Research is the name I take freelance work under when it comes up — independent technical validation and due diligence for investors and deep tech teams. It's a one-person practice, not a firm. I've written up the methodology separately: a staged validation protocol, a catalog of the measurement failure modes I check for, and worked examples of how I'd approach a given claim.

Read the validation methodology

Contact

Get in touch

I'm open to senior R&D engineering, technical program management, and validation roles — remote, hybrid, or onsite with travel. I'm based in Raleigh, North Carolina, and I'm a US citizen.

Industrial Heat LLC maintains a limited public presence as a private research organization. References, including direct contact with the CEO, are available on request to verify the scope and nature of this experience.