Systems Engineer

Hitesh Pranav

Building across software×hardware×AI.

I study ECE, but apparently decided one field wasn't enough.

ECE @ PES UniversityBengaluru2027
GitHubLinkedIn
Currently

Building software and intelligent systems. Exploring systems engineering, AI/ML, and hardware-software integration.

Institution
PES University
Program
B.Tech, ECE
Graduating
2027
Based in
Bengaluru, India
01About

Ground up, then across.

I started in electronics because I wanted to understand technology from the ground up — not just use it, but know what's happening underneath.

That led me toward the software and systems built on top of hardware. Since then I've worked across full-stack development, embedded systems, machine learning, and cybersecurity — not by accident, but because I keep finding the interesting problems at the boundary between disciplines.

I like understanding how a system works underneath the abstraction, then actually building it. A CAN bus intrusion detector isn't just a classifier — it's sensors, a protocol, an attack model, and a response system that has to work in real time. That's the kind of problem I go looking for.

I'm now looking for engineering roles where I can keep working on systems like that, and grow into an engineer who can take a problem from architecture through implementation — not just one layer of it.

Background

Electronics & Communication Engineering

PES University, Bengaluru — Class of 2027

Where it shows up

SoftwareEmbedded SystemsMachine LearningHardware

How I Think

I like the whole system.

Most problems don't live inside one discipline. A product might start at a sensor, move through firmware, get processed by a backend, pass through a model, and end up as something a person actually interacts with.

Understanding one of those pieces is useful. Understanding how they hold together — where the constraints of one layer show up as bugs two layers away — is the part I actually enjoy.

01
Sensor
02
Firmware
03
Backend
04
Model
05
Interface
02Selected Work

Systems worth explaining.

Each one is a case study, not a portfolio card — the problem, the approach, and what made it worth building.

01

PESU ResearchMatch

Hybrid retrieval system that matches students to research faculty by meaning, not just keywords.

PythonFlaskReactBGE-LargeBM25Qwen-2.5-0.5BSemantic Search
GitHub2026

Problem

Finding the right research advisor means reading through dozens of faculty pages. A plain keyword search misses faculty who describe their work in different words, and a black-box LLM answer can't be checked against the underlying data.

Approach

A hybrid retrieval pipeline combining BGE-Large dense embeddings (1024-dimensional) with BM25 sparse keyword matching, so results capture semantic meaning and exact term matches together. A local Qwen-2.5-0.5B model generates a short explanation for each match. Flask backend, React frontend, with client-side PDF parsing so a resume can be matched directly.

Engineering detail

Embeddings, retrieval and explanation generation all run locally instead of calling an external LLM API per query — the system stays self-contained with no per-query dependency on a hosted model.

Outcome

A working search system across faculty on PES University's RR and EC campuses that returns ranked, explained matches instead of a flat keyword list.

02

Automotive ML IDS

Machine-learning intrusion detection and real-time firewall for automotive CAN networks.

Pythonpython-canRandom ForestAnomaly DetectionCAN BusAutomotive Security
GitHub2025

Problem

CAN bus, the protocol most vehicle components use to talk to each other, has no built-in authentication — any device on the bus can inject messages, which makes it a real attack surface for connected vehicles.

Approach

An intrusion detection pipeline built around a Random Forest classifier trained to flag anomalous CAN traffic, paired with a real-time Python firewall that can act on detections as they happen. python-can simulates bus traffic and attack scenarios for testing without physical hardware.

Engineering detail

The interesting part isn't the classifier — it's closing the loop: detection feeds directly into a firewall that intervenes on live traffic, rather than just flagging anomalies after the fact.

Outcome

A working detection-and-response pipeline, later extended during a research internship at C-ISFCR into a fuller cybersecurity framework for automotive networks.

03

Motorsport Telemetry Dashboard

Real-time motorsport telemetry — IMU, GPS and live video, built in 18 hours.

IMUGPSSensor FusionEmbedded SystemsJavaScriptChart.jsLeaflet

Problem

A race team needs to see what's happening to the vehicle as it happens — acceleration, position, speed — not reconstruct it afterward from logs.

Approach

Built during Ignition 1.0, an 18-hour hackathon run by Team Vegavath PESU and sponsored by Ather Energy. The dashboard streamed live IMU acceleration data (Ax, Ay, Az), GPS-based position tracking and a 720p MJPEG video feed, with speed estimated by fusing IMU and GPS instead of trusting either sensor alone. Driving behavior was inferred from acceleration-variance analysis. Frontend built with Chart.js and Leaflet.

Engineering detail

The hardware had to stay light enough not to affect the vehicle it was measuring — it ended up the second-lightest system at the event while still handling live sensor fusion and video.

Outcome

5th place overall among competing teams, and a working answer to a real constraint: instrumentation that measures a vehicle without meaningfully changing its weight.

04

Joy of Engineering Lab — Website

The official website for a student engineering lab, running in production.

Next.jsTypeScriptTailwind CSSVercel
Live2025

Problem

JoEL needed a real digital presence for its flagship events and student projects, not a placeholder page.

Approach

Built with Next.js, TypeScript and Tailwind CSS, structured around the lab's actual events — HackeZee and Roadshow — and its student project showcase. Deployed on Vercel with maintainability treated as a first-class requirement, since a different set of students maintains it after handoff.

Engineering detail

It isn't a personal or academic project — it's production software a club runs, edited by people who didn't build it.

Outcome

Live and in active use as JoEL's official site.

03Experience

Leadership and research.

Aug 2024 — Present

Student Head

Joy of Engineering Lab (JoEL), PES University

Engineering leadership for a student lab that runs a flagship hardware hackathon and mentors project teams through a full build cycle.

  • Led backend planning and logistics for HackeZee 2025 and Roadshow 2026.
  • Coordinated volunteers, mentors, vendors, and technical teams for engineering events.
  • Mentored multiple student teams on IoT and embedded systems projects.
  • Developed and maintained the official JoEL website using Next.js and TypeScript.

Jun 2025 — Jul 2025

Research Intern

Center for Information Security, Forensics and Cyber Resilience (C-ISFCR)

Automotive cybersecurity research — building and evaluating a machine-learning intrusion detection system for CAN networks.

  • Developed an ML-based Intrusion Detection System for automotive CAN bus networks
  • Built a Python firewall for real-time anomaly detection and traffic filtering.
  • Trained ensemble machine learning models using Scikit-learn.
  • Developed a Tkinter GUI for CAN message injection, testing, and analytics.
04Engineering Stack

Organized by what it does, not what it looks like.

Software

  • Python
  • C / C++
  • TypeScript
  • JavaScript
  • React
  • Next.js
  • Node.js
  • Flask

AI / ML

  • PyTorch
  • Scikit-learn
  • NLP
  • Semantic Search
  • Embeddings
  • RAG / Hybrid Retrieval

Systems

  • Linux
  • Git
  • SystemC
  • APIs
  • PostgreSQL
  • Supabase

Hardware

  • Arduino
  • Raspberry Pi
  • FPGA
  • Verilog / VHDL
  • Embedded Systems
  • Sensors / IMU / GPS

Security

  • CAN Bus Security
  • Intrusion Detection
  • Anomaly Detection
  • Automotive Security
Contact

I'm looking for the next system worth building.

Open to software, systems, embedded, and AI/ML engineering roles — anywhere software, hardware, and machine learning intersect.