About
Curiosity across the stack.
I like engineering problems where a model, a signal, a user, and a production system all have to work together.
Kazakhstan
It started with a keyboard.
As a high-school student, I worked with a team on TBZZ-44, an ergonomic split keyboard built with KiCad and adapted firmware. The project placed in the top 40 among 300 Samsung Solve for Tomorrow Kazakhstan teams.
It taught me that engineering is not a list of technologies. It is deciding what matters, turning an idea into a physical system, and explaining the tradeoffs well enough for other people to understand them.
Michigan State University
Software became a way to build quickly.
I began in computer science, developed production software and retrieval systems, and taught Python as a course assistant. Software gave me the tools to prototype quickly, but I wanted to understand more of the physical and mathematical system beneath it.
Boston University
Electrical engineering connected the layers.
Transferring to BU brought signals, DSP, deep learning, speech recognition, digital hardware, and healthcare into the same frame. Today I am most interested in systems that need both technical performance and earned trust.
Outside the lab
Guitars, music, and custom keyboards.
Speech and signal processing feel natural partly because I care about sound. Away from coursework and code, I play guitar, listen widely, and still enjoy the small mechanical details of custom keyboards.
Compact toolkit
Skills connected to real work.
The detailed evidence lives in research, projects, and experience rather than in an exhaustive inventory.