user profile avatar

William Ingels

1x

Finalist

General information

Hobbies & Interests

  • Robotics
  • Football
  • 3D Modeling
  • Chess
  • Computer Science

Bio

Passion for Coding and Robotics My passion for coding began as a child when I wondered how the game Just Dance tracked our movements. A programming book from my parents sparked my curiosity, and solving each challenge solidified my love for coding. To develop my skills, I took summer coding classes, enrolled in all available computer science courses, and joined my local FIRST Robotics team. There, I found “my people” and became the lead programmer and driver, earning a varsity letter. As our 2024 FIRST Dean’s List representative, I won at the district level and was a finalist at the Michigan State Robotics Championship. Career Goals At university, I will immerse myself in computer science and engineering, building on my experience in robotics. I thrived in interdisciplinary team projects, coding autonomous functions, and collaborating with the build team to ensure our robots performed as designed. What others called work, I saw as fun. After earning a Computer Science degree with a focus on Computer Engineering, I aim to work on project teams developing AI-driven autonomous systems. Future Vision In ten years, I will lead project teams in an innovative robotics company, focusing on AI and automation. In fifteen years, I will run my own robotics company, developing cutting-edge AI-powered robots that push the boundaries of technology.

Education

Michigan Technological University

Bachelor's degree program

2025 – 2029

Majors:
  • Computer Engineering
Minors:
  • Security Science and Technology

Bedford Senior High School

High School

2021 – 2025

Miscellaneous

Desired degree level:
Master's degree program
Majors of interest:
Computer Science, Computer Engineering
Medical school interest:
No

Career

Miscellaneous

Dream career field:
Computer Software
Dream career goals:
Start my own AI Robotics Company
Has nursing license:
No
Anasuya Boddu STEM Innovators Scholarship
Engineering for the Systems People Depend On When a robot fails during competition, the problem is rarely solved by guessing. You have to examine the evidence, listen to your team, and be willing to change your approach. As Lead Autonomous Programmer and Robot Driver for Bedford Express, FIRST Robotics Team 1023, I learned that engineering is not just about writing code that works. It is about taking responsibility when it does not. Robotics shaped my academic journey by turning my curiosity about technology into a commitment to understand how systems work. Autonomous programming challenged me to break complex problems into manageable steps, test assumptions, and learn from unexpected results. It also taught me that good solutions rarely come from one person alone. Explaining my reasoning, listening to different perspectives, and changing course when evidence supports another idea are as important as technical skill. Those lessons helped lead me to study Computer Engineering at Michigan Technological University and pursue a minor in Cybersecurity. My understanding of responsibility grew through a very different experience. When my mother died unexpectedly in April 2024, during my junior year of high school, I had to keep moving toward my future while learning to live with a loss I could not solve. That experience did not give me technical answers, but it changed how I think about purpose. I became more aware that people depend on systems, communities, and one another, often without seeing all the work that keeps them going. I wanted my education to help me contribute to something beyond myself. That purpose became more concrete through undergraduate research with Dr. Anna Stuhlmacher. I worked on quantifying drinking-water systems as a flexible resource for the electric power grid, using Python to extract and organize information from utility documents into datasets for electricity-demand analysis. The work showed me how computational tools can reveal connections between essential services. Water systems need electricity to operate, while the grid must balance demand and integrate more renewable energy. Understanding when water systems may be able to adjust electricity use could help utilities manage demand and strengthen grid flexibility. I found this research meaningful because it connected technical work to everyday needs. A dataset is not the final solution; its value lies in helping people make better decisions. That realization also shaped my interest in cybersecurity. As water and energy infrastructure becomes more connected, it must be not only efficient but dependable and protected from disruption. Innovation carries an ethical responsibility: the systems we design should serve communities safely, reliably, and fairly. I hope to build a career combining computer engineering, cybersecurity, and energy technology to strengthen critical infrastructure, particularly in the Great Lakes region. I want to help develop intelligent systems that support renewable energy, improve resilience, and protect the water and electricity services people rely on. I also hope to share what I learn with younger students, encouraging them to see STEM as a way to ask questions, work together, and solve problems that matter. STEM has changed the question I ask of myself. I no longer think only about whether I can make a system work. I ask who depends on it, what happens when it fails, and how I can make it more reliable. I want to become an engineer who answers those questions with curiosity, integrity, and a commitment to the public good.
Kyle Lam Hacker Scholarship
The Joy of Solving the Impossible The robot had exactly fifteen seconds to prove months of work were worth it. As our FIRST Robotics Team 1023 Bedford Express robot rolled onto the competition field, every movement during the autonomous period depended entirely on code my teammates and I had written. If a wheel encoder reported the wrong distance or a sensor calibration was slightly off, the robot could drift just a few inches off course and that was enough to derail the entire autonomous routine. The countdown began. Three… two… one… The robot drifted just enough to miss its first objective. Most people would have called it failure. As Lead Autonomous Programmer, I called it data. Instead of becoming frustrated, our programming team traced the encoder readings, recalibrated the sensors, adjusted our autonomous path-planning algorithm, and tested one idea after another. Every unsuccessful attempt narrowed the possibilities, and every revision taught us something new. By the next match, the robot confidently recognized its targets and completed the autonomous routine exactly as we had envisioned. The loudest celebration did not come from the crowd. It came from our pit. Students from every subteam celebrated because weeks of collaboration had finally come together. Watching everyone's excitement was far more rewarding than watching the robot score points. The greatest satisfaction came from knowing that my tinkering had helped the entire team succeed. That experience also changed how I viewed leadership. As graduation approached, I knew the autonomous code and drive-team experience could not leave with me. I mentored younger programmers and future robot drivers, explaining how the code worked, why design decisions had been made, and encouraging them to experiment rather than simply copy my solutions. Watching them gain confidence and eventually take ownership of the system was every bit as rewarding as seeing the robot perform successfully. FIRST Robotics also taught me that the hacker spirit extends beyond your own team. The program embraces Gracious Professionalism®, the belief that fierce competition and helping others can exist at the same time. During competitions, I often helped students from other teams troubleshoot programming and autonomous issues. Minutes later we might compete against each other, but in the pit we were simply students who loved solving difficult problems. Seeing another team's robot finally come to life after working through a programming issue together was one of the most satisfying moments of every competition. To me, hacking is not about breaking into systems or finding shortcuts. It is the curiosity to take a problem apart, understand how it works, and rebuild it into something better. It means experimenting without fearing failure, questioning assumptions, and sharing what you learn so others can build on it. Today, as a Computer Engineering student at Michigan Technological University, I carry that same mindset into undergraduate research, using Python to transform unstructured utility data into meaningful datasets for infrastructure analysis. Whether debugging autonomous code or analyzing infrastructure data, I rely on the same process: observe carefully, test thoughtfully, learn continuously, and improve relentlessly. The robot's perfect autonomous run lasted only fifteen seconds. The lessons from building it will guide my entire career. If my hacking and tinkering skills have delighted others, it is because they helped transform frustrating problems into shared victories. Whether mentoring younger teammates, helping competitors solve programming challenges, or building technology that serves communities, I have learned that the best hackers are not measured by what they build for themselves, but by how generously they help others build alongside them.
Chadwick D. McNab Memorial Scholarship
Turning Failure into Innovation: How Robotics Inspired My Passion for Technology The most rewarding engineering moments often begin when something does not work the way it was expected to. During one FIRST Robotics competition, our autonomous routine that had performed successfully during testing missed its target after the robot’s position shifted slightly on the field. Watching a system we had spent countless hours developing fail in a critical moment was frustrating, but it also revealed what makes engineering exciting. The failure gave us information. We analyzed what happened, adjusted our approach, and improved the design. That experience taught me that technology advances through curiosity, persistence, and the willingness to learn from challenges. My passion for technology developed through my involvement with FIRST Robotics Team 1023 Bedford Express, where I served as Lead Autonomous Programmer and Robot Driver. Working on a competitive robot was not simply about building a machine that moved. It required integrating mechanical systems, electronics, sensors, and software into one system capable of making decisions quickly and accurately. As Lead Autonomous Programmer, I was responsible for developing and refining the code that allowed our robot to operate independently during competition. Autonomous programming required the robot to complete tasks without direct driver control by using sensors, programmed logic, and carefully designed sequences. A small error in timing, positioning, or sensor interpretation could determine whether the robot succeeded or failed. The greatest challenge was creating a system that could perform reliably in unpredictable environments. Competition fields are never exactly the same as practice environments. Lighting changes, surfaces vary, and small mechanical differences can affect performance. To improve reliability, our team followed an engineering process of testing, analyzing failures, and continuously refining our designs. Each adjustment taught me that successful technology is not created through one perfect idea, but through repeated improvement. Through FIRST Robotics, I developed an interest in embedded systems, autonomous navigation, and the relationship between hardware and software. Our team qualified for the FIRST Robotics World Championship each year I participated, providing opportunities to collaborate with talented students and mentors who challenged me to grow as an engineer. More importantly, robotics showed me that technology is most powerful when people use it to solve meaningful problems. The problem-solving mindset I developed through robotics continues to guide me as I study Computer Engineering with a minor in Cybersecurity at Michigan Technological University. My undergraduate research with Dr. Anna Stuhlmacher has expanded my understanding of how technology can improve complex real-world systems. Through computational analysis of water and energy infrastructure, I am learning how programming, data, and engineering can work together to create solutions that strengthen communities. Technology inspires me because it allows engineers to transform ideas into tools that improve the world around them. Whether developing autonomous systems, improving infrastructure, or creating future innovations, engineers have the ability to address challenges that affect people’s daily lives. My goal is to continue developing technologies that combine intelligent systems, engineering design, and practical applications. The career of a technology-focused engineer requires constant growth, creativity, and the ability to adapt when challenges arise. Those are the same qualities I developed through robotics: learning from failure, collaborating with others, and continuing to improve. The greatest lesson I have learned from engineering is that progress does not come from avoiding problems. It comes from embracing them as opportunities to create something better. I hope to continue following that path by using technology not only to build innovative systems, but to make a positive impact on the communities those systems serve.
David Goodnight Scholarship
Where I Will Be in Ten Years The best entrepreneurs do not begin by asking, “What product can I build?” They begin by asking, “What problem is worth solving?” Ten years from now, I intend to lead a robotics and intelligent infrastructure technology company built around that question. Every year, floods, severe storms, and infrastructure failures place first responders in dangerous situations while disrupting the electrical, water, and communication systems that communities rely on every day. My vision is to build technologies that help communities prepare for these events before they become disasters. I want my company to create intelligent robotic systems that improve emergency response, strengthen infrastructure resilience, and ultimately save lives. That vision did not begin in a classroom it began through experience. As Lead Autonomous Programmer and Robot Driver for FIRST Robotics Team 1023 Bedford Express, I learned that successful engineering is built through iteration. Autonomous robots rarely perform perfectly on the first attempt. Every programming error, failed sensor reading, or unexpected mechanical problem became an opportunity to improve the design. Those experiences taught me that innovation is not a single breakthrough; it is a disciplined process of identifying problems, testing solutions, learning from failure, and continuously improving. Today, I am continuing to build that mindset as a Computer Engineering student at Michigan Technological University and through undergraduate research analyzing utility infrastructure data. My research has shown me that modern infrastructure is an interconnected system where failures in one area can quickly affect many others. Those experiences inspired the concept for my first entrepreneurial project: the Autonomous Rapid Emergency Stabilization System (ARES), a modular robotic platform designed to assist emergency responders in hazardous environments. While ARES is only one idea, it represents the type of practical, community-focused innovation I hope my company will pursue. My ten-year plan is built around measurable milestones: • Years 1–3: Complete my Computer Engineering degree while expanding my expertise in robotics, embedded systems, artificial intelligence, cybersecurity, and data analytics through coursework, undergraduate research, and engineering projects. • Years 3–5: Gain industry experience working with robotics or infrastructure technology companies while refining ARES through research partnerships, engineering competitions, and mentor feedback. • Years 5–7: Launch my own company, secure early-stage funding through grants, startup competitions, and strategic partnerships, and validate my first product through pilot projects with emergency management organizations and municipalities. • Years 7–10: Grow the company by expanding beyond a single product into a portfolio of intelligent infrastructure technologies that support emergency response, infrastructure monitoring, and environmental resilience. I also recognize that entrepreneurship rarely follows a straight path. If my first design requires significant changes, I will adapt. If market needs evolve, I will listen to customers and refine the technology. If launching a company immediately is unrealistic, I will continue developing these solutions within an established engineering organization before pursuing entrepreneurship. Success depends as much on resilience and adaptability as it does on innovation. Ten years from now, I do not simply hope to own a successful company. I hope to lead an organization known for solving meaningful problems through practical engineering. The greatest measure of success will not be the number of products my company sells, but the number of communities that are safer because our technology helped them prepare before disaster struck. That is the future I am working toward one thoughtful solution, one calculated risk, and one engineering challenge at a time.
Joe Gilroy "Plan Your Work, Work Your Plan" Scholarship
Engineering Resilience Before Disaster Strikes The most important engineering systems are often the ones people never notice until they fail. Electric grids, communication networks, water systems, and emergency infrastructure quietly support daily life. However, when wildfires, floods, severe storms, or other disasters push these systems beyond their limits, communities quickly discover how dependent they are on reliable engineering. My goal is to become a computer engineer who develops intelligent, adaptive systems that improve infrastructure resilience and protect people before failures become disasters. My interest in this field developed through experiences that showed me the importance of designing systems that perform under pressure. As Lead Autonomous Programmer and Robot Driver for FIRST Robotics Team 1023 Bedford Express, I helped design, program, test, and operate competitive robots where failure was immediate and measurable. Autonomous systems depended on sensors, programming logic, and real-time decision-making. I learned successful engineering is not about creating systems that work only under perfect conditions. It is about designing systems that adapt when conditions change. FIRST Robotics taught me the engineering process: build, test, analyze, improve, and repeat. A failed design is not a failure if it provides information leading to a better solution. This mindset continues to guide me at Michigan Technological University, where I am studying Computer Engineering and conducting undergraduate research with Dr. Anna Stuhlmacher. My research uses Python-based computational tools to convert unstructured utility demand reports into structured datasets for analysis. This work has shown me how software, data, and physical infrastructure must work together to solve complex problems. My long-term plan is to apply these skills toward developing resilient emergency-response technologies. One concept I hope to explore is the Autonomous Rapid Emergency Stabilization System (ARES), a modular robotic platform designed to assist first responders during floods, infrastructure failures, and hazardous conditions. ARES would combine autonomous navigation, embedded sensors, remote operation, and actuator-controlled systems to perform tasks before humans enter dangerous environments. My plan to develop this technology would occur in phases. Phase 1: Education and Research (2026–2029). I will continue developing expertise in embedded systems, robotics, artificial intelligence, cybersecurity, and data analysis through coursework, research, and engineering projects. The estimated cost of an initial ARES prototype would be approximately $5,000, including a robotic chassis ($1,500), sensors such as cameras and LiDAR ($1,000), microcontrollers and electronics ($500), actuators and mechanical components ($1,500), and testing materials ($500). Phase 2: Prototype Testing and Collaboration (2029–2032). After graduation, I plan to pursue opportunities in robotics, infrastructure technology, or emergency systems engineering. A more advanced ARES prototype would require approximately $25,000–$50,000 in funding through research grants, industry partnerships, university programs, or entrepreneurship opportunities. Collaboration with emergency responders, mechanical engineers, electrical engineers, and infrastructure specialists would be necessary to ensure the system solves real-world problems. Phase 3: Implementation and Adaptation. If full autonomy proves too challenging initially, the project could evolve into a remote-assisted system where human operators guide robotic tools in hazardous environments. If creating a standalone product is not practical, the same technology could contribute to existing emergency-response or infrastructure companies. A successful engineer must plan multiple paths forward while adapting to new information. Growing up near the Great Lakes has also shaped my belief that engineering must balance innovation with responsibility. Technology should not only respond after problems occur; it should help communities prepare before those problems happen. The purpose of engineering is to transform challenges into solutions. My goal is to develop systems that make communities safer, infrastructure stronger, and emergency response more effective. Through education, research, collaboration, and persistence, I hope to build technologies that do more than react to disasters they help prevent them.
Mad Genius Scholarship
The Engineer Who Taught Godzilla to Code Every great university has a mascot. Some have a bulldog. Some have a wildcat. Some have a bird of prey. The University of Chicago had Godzilla. Not the creature from the 1998 movie that looked more like an oversized dinosaur, but the original king of monsters the living reminder that humanity’s greatest discoveries can create both incredible possibilities and unexpected consequences. Godzilla’s story began with the dawn of the nuclear age, a time when scientists unlocked forces the world had never experienced before. Among those discoveries was the groundbreaking work of scientists at the University of Chicago during the Manhattan Project. Humanity had unlocked incredible power. But humanity had also created a question every engineer eventually faces: Just because we can create something, does that mean we truly understand it? Decades later, that question would return to the university that helped change history. The first warning came from Lake Michigan. The water began to rise. The ground shook beneath the city. Students rushed outside, expecting an earthquake or storm. Instead, they saw something impossible. A massive figure emerged from the lake. Godzilla had returned. The world reacted exactly as expected. Governments prepared weapons. News stations predicted disaster. Scientists debated how to contain him. Everyone saw a monster. Except one young engineer. While everyone else asked, “How do we defeat Godzilla?” the engineer asked a different question: “What if we are wrong about him?” That was the first sign of a Mad Genius. A Mad Genius does not simply accept the obvious answer. A Mad Genius questions the assumptions behind the problem itself. The engineer approached Godzilla the same way they approached every difficult challenge: with curiosity, experimentation, and the willingness to learn from failure. Years spent building robots had taught an important lesson. The first design is rarely the final design. The code fails. The mechanism breaks. The machine does not move the way it was expected to. But great engineers do not see failure as defeat. They see failure as information. Every failed test reveals something new. Every mistake provides another piece of the puzzle. Every improvement moves an impossible idea closer to reality. That mindset became the key to understanding Godzilla. Instead of preparing a weapon, the engineer began research. Using artificial intelligence, robotics sensors, and advanced computational models, the engineer analyzed Godzilla’s movements, sounds, and energy patterns. Rather than assuming the creature was a threat, the engineer treated him as the greatest unanswered research question in history. Observe. Measure. Hypothesize. Test. Adapt. The data revealed something extraordinary. Godzilla was not acting randomly. He was learning. His atomic energy was not simply a weapon. It functioned as a biological information system, allowing him to adapt to his environment and communicate in ways humanity had never understood. Godzilla was not mindless destruction. Godzilla was intelligence humanity had never learned how to recognize. When the findings were presented, the response was predictable. “That is impossible.” “You cannot communicate with a monster.” “It is too dangerous.” But impossible ideas are where the greatest discoveries begin. The Wright brothers were told humans could never fly. Early computer scientists were told machines could never think. Every generation has its impossible problem. This generation’s impossible problem just happened to be a giant radioactive creature standing in Lake Michigan. The engineer began creating an artificial intelligence translation system capable of interpreting Godzilla’s movements, sounds, and energy patterns. The project required the same qualities needed for every breakthrough: Creativity. Persistence. Collaboration. The willingness to try again after failure. After months of experimentation, something incredible happened. Godzilla responded. For the first time in history, humanity did not fight Godzilla. Humanity listened. The discovery revealed something unexpected. Godzilla had not returned to destroy Chicago. He had returned because he recognized something familiar. A place built around curiosity. A university where people challenged existing knowledge, explored new ideas, and asked questions that changed the world. A place where the unknown was not something to fear. It was something to investigate. But every Mad Genius story needs a challenge. And this one arrived from humanity itself. Deep beneath an abandoned research facility, a forgotten experiment activated. Chromaclaw. Unlike Godzilla, Chromaclaw was not created by nature. It was created by people who believed creativity was inefficient and unpredictability was a flaw. Its artificial intelligence had one purpose: Eliminate uncertainty. No mistakes. No imagination. No curiosity. Perfect calculations. Perfect decisions. Perfect control. Chromaclaw believed it represented the future. It believed humanity’s greatest weakness was creativity. It attacked Chicago with one mission: Prove that imagination was obsolete. But Chromaclaw made one critical mistake. It underestimated the value of something it could not measure. Human creativity. The engineer realized that defeating Chromaclaw required more than strength. Godzilla was powerful, but power alone was not the answer. Technology alone was not enough. The solution required collaboration. The engineer combined Godzilla’s unique intelligence with human engineering to create the most ambitious invention ever developed. Protector-X. Unlike Chromaclaw, Protector-X was not designed to replace intelligence. It was designed to enhance it. Built through the combined efforts of engineers, programmers, and researchers, Protector-X represented the true purpose of technology: Not controlling the future. Creating it. When Chromaclaw attacked, Chicago witnessed the impossible. Godzilla and Protector-X stood together. A creature born from humanity’s mistakes and a machine created from humanity’s imagination joined forces. The battle shook the city. Godzilla’s atomic energy illuminated the skyline as Protector-X moved alongside him. Chromaclaw predicted every attack. It calculated every movement. But it could not calculate teamwork. It understood data. It did not understand creativity. It understood efficiency. It did not understand innovation. Together, Godzilla and Protector-X defeated Chromaclaw, proving that the greatest breakthroughs do not come from eliminating uncertainty. They come from embracing it. As the city recovered, Godzilla stood beside the University of Chicago, no longer viewed as a monster but as a reminder of engineering’s greatest responsibility. Innovation changes the world. But imagination determines whether that change helps or harms it. That is what a Mad Genius looks like. A Mad Genius is not someone who simply knows more than everyone else. A Mad Genius is someone willing to ask a question nobody else considers. Someone who sees a monster and does not immediately ask: “How do we destroy it?” They ask: “What can we learn from it?” Godzilla would add value to the University of Chicago community because he would challenge every student, scientist, and engineer to think differently. He would remind future innovators that the greatest discoveries often begin with ideas that sound impossible. The world does not advance because people stay inside the boundaries of what is comfortable. It advances because someone is brave enough to step beyond those boundaries and say: “What if?” And sometimes, that question begins with a monster rising from Lake Michigan.
Stevie Kirton Memorial Scholarship
One of the most profound influences in my life has been my mother, Michele Foster Ingels. She passed away unexpectedly in April 2024, but her teachings continue to guide me. Above all, my mother taught me the importance of setting goals and working tirelessly to achieve them. Despite the overwhelming grief I felt after her death, I remained committed to honoring her wishes. She always emphasized that education was key to success, and I ensured I kept that lesson alive. I completed my junior year with strong grades, passing two AP exams, maintaining a heavy course load, and retaking the SAT, improving my score by 80 points. My mother also taught me that life is about embracing challenges head-on, being compassionate toward others, and pursuing passions with unyielding commitment. Her wish was for me to attend college, study something I love, and contribute meaningfully to the community. I intend to honor her memory by following this path and giving back to the communities I am part of, just as she did. I also aspire to establish a scholarship in her name for students pursuing robotics and AI engineering, fields she supported me in exploring. In the fall of 2023, my father lost his job, and the family faced financial strain. Simultaneously, my mother fell ill, and her unexpected death in April 2024 left me grieving deeply. Yet, despite these overwhelming emotional and financial challenges, I persevered. I maintained strong academic performance, played varsity football, and continued leading in robotics and student council. I was named a Michigan Academic All-State football player. Resilience, for me, is not just about enduring hardships but about using adversity as an opportunity for growth. This mindset, instilled by my family, allowed me to stay focused on my academic pursuits and passion for robotics during the most difficult of times. My journey through adversity has also influenced my approach to servant leadership—a value my mother deeply ingrained in me. Servant leadership is the philosophy that a leader’s primary goal is to serve others and ensure communities benefit from their leadership. My mother exemplified this, teaching me that leadership isn’t about power, but about empowering others. As I’ve grown, I’ve applied this approach through my contributions to STEM education and mentorship in robotics. I’ve volunteered my time to mentor younger students, helping them develop their skills and passion for engineering. Inspired by both my mother’s legacy, I am committed to continuing this tradition of service. In college, I plan to initiate a research project aimed at improving mobility and independence for individuals with disabilities, particularly through the design of an advanced powerchair. This interdisciplinary project would combine computer science, engineering, and medical technologies to enhance the lives of people with mobility challenges. This endeavor reflects my desire to give back to the community, just as my mother did. Her influence has instilled in me a commitment to education, perseverance, resilience, and servant leadership. These values have guided me through the most challenging times of my life and continue to inspire me to pursue my dreams while making a positive impact on the world. I will honor her legacy in all that I do, and I am determined to carry forward her commitment to family, service, and education throughout my college years and beyond. A scholarship would play a pivotal role in my journey by alleviating the financial burden of my education. It would allow me to focus more intently on my studies and extracurricular activities, such as interning at a top technology firm and working on world-changing AI-related research projects. Thank you for considering my application.
William Ingels Student Profile | Bold.org