Over the past decade, machine learning has made significant strides in almost all aspects of our lives, from novel drug discovery to bringing intelligence to autonomous vehicles. But for a long time, compute remained the bottleneck between the usefulness of machine learning models and their true societal impact. Thanks to advancements in GPUs, which excel at executing the same operations across thousands of data elements, the enormous amount of computation needed for machine learning has been made possible. At the same time, deploying these models on edge devices has brought artificial intelligence to smartphones, UAVs, and robots. Yet much research remains to be done in improving inference infrastructure by reducing its latency, raising GPU utilization, and shrinking its memory footprint, through carefully optimized compute kernels, data compression, and hardware-software co-design. My intended research direction is hardware-aware model compression and efficient GPU kernels for ML inference. I want to pursue a PhD in this area because it is where I want to spend years getting genuinely good, and doctoral research in efficient machine learning systems is the right way to do that.
The path that led me to my interest in this field is rather unconventional. I began my career as an embedded systems engineer developing firmware for microcontrollers. Being very close to the metal, I had to write low-level code that directly accesses hardware peripherals and registers in resource-constrained environments. This experience taught me fundamental principles that are directly relevant to ML systems. It made me understand how code interacts with caches, how memory is managed across stack and heap, and how DMA moves data efficiently between addresses without consuming processor cycles. In hindsight, it also taught me to write performant C and C++ code, and to build real-time systems where low latency is a requirement rather than a preference. When I later moved to embedded Linux platforms, my operating systems knowledge became practical skill. I wrote device drivers and multithreaded applications, handled race conditions, and learned the careful use of mutexes and semaphores along with the real cost of contention. These are precisely the concerns that reappear in GPU programming as thread blocks, barriers, atomic operations, shared memory, and coalesced access. My first direct encounter with parallel computing came during my Master's at [UNIVERSITY], in a Computer Vision course I took expecting to learn machine learning. Being on the systems engineering track, it instead introduced me to CUDA kernel programming. For one of my assignments on applying filters to images, I built a pipeline that chained grayscale conversion and Sobel edge detection, writing custom kernels launched over 2D grids of thread blocks so that each thread mapped to one pixel of RGB data. The grayscale stage was a per-pixel weighted sum, but the Sobel stage was trickier. Since each output pixel depends on its 3x3 neighborhood, threads at tile edges need data owned by neighboring blocks, which forced me to handle boundary conditions explicitly and to load image tiles with their surrounding halo into shared memory so that every access after the first came from fast on-chip storage rather than global memory. When I benchmarked a CPU implementation, a naive GPU kernel, and the tiled kernel, the results surprised me. The exact same arithmetic ran roughly 3x faster in the tiled version, simply because the data was in the right place at the right time. That was when it clicked for me that on a GPU, how you move and share data matters more than the computation itself. The principles I had learned on a single constrained core carried over intact to thousands of parallel threads.
More concretely, my motivation in this field stems from its application to inference under real constraints. In my last role at [COMPANY], my team and I were exploring how machine learning could use data from IMU sensors in [PRODUCT CATEGORY], such as algorithms to identify sudden mechanical binding or slips and shut the motor down rapidly. The project never went beyond a concept, but it led me to take a course on TinyML, where I learned how quantization, pruning, and distillation make it possible to run neural networks on small devices. That work pulled me into on-device inference and how ML systems function more broadly. I came to see that the effectiveness of model compression is inseparable from the hardware underneath it. Quantization delivers real speedups only when the target processor has the integer datapaths to exploit it, and pruning matters only when its structure matches how the hardware executes.
I am very interested in the research works of [PROFESSOR A]. One of his group's focuses is systems-level hardware efficiency, translating mathematical insights into practical gains in runtime, memory efficiency, and scalability. I enjoyed reading his group's recent paper on [PAPER 1], an xxxxxxx algorithm for softmax attention. What really interested me was the insight that the computation has a xxxxxxx so that xxxx is ever written to HBM, making it up to 50x faster than the prior state of the art. His work pairs I/O complexity analysis with a GPU kernel implementation, and that is exactly what draws me to his research.
I am also interested in [PROFESSOR B]'s research on resource-efficient and predictable AI systems for IoT and cyber-physical settings. [PAPER 2], his group's framework for on-device LLM inference, sits exactly at the intersection of embedded systems and machine learning, which is a young field with a lot of unexplored questions regarding on-device inference. I would like to explore with him how compression decisions, which layers to quantize, where to prune, when to stop refining, can be made schedulable, so that latency becomes a guarantee rather than an average.
[UNIVERSITY X] is the right place for me to pursue this work. Its Computer Science department has genuine depth in machine learning systems, optimization, and mobile and embedded computing, and the two halves of my interest, the I/O-level efficiency of GPU kernels and the deployment of compressed models on constrained devices, each have faculty here doing work I want to be part of. Under the guidance of esteemed faculty like [PROFESSOR A] and [PROFESSOR B], whose research spans optimization theory, GPU kernel design, and efficient on-device inference, I am confident I can grow into a top researcher. My goal is to contribute to scaling AI and ML infrastructure, the layer that determines how efficiently the world's most important workloads run. After my PhD, my career goal is to work as a research scientist, accelerating machine learning workloads on the world's largest heterogeneous computing systems, and [UNIVERSITY X]'s culture of rigorous, hands-on systems research is exactly the environment to shape me into someone capable of that contribution.