A career in technology offers endless opportunities and encourages personal growth for those willing to pursue it.
Chadwick D. McNab embodied this ideal throughout his career as an elite software developer. He inspired countless others to reach their full potential as engineers and members of their community, always championing growth and progress. The Chadwick D. McNab Scholarship seeks to honor his life by supporting undergraduate students looking to achieve these same goals in their technological career.
Undergraduate students are eligible to apply if they are majoring in or planning to major in computer science and related technology fields. To apply, write about a project you worked on that you were passionate about, and share how working in technology inspires you.
Selection Criteria:
Ambition, Need, Boldest Bold.org Profile
Essay Topic Requirements
Tell us about a project you worked on that you were passionate about and how working in technology inspires you.
400–600 words
$2,000
2 winners, $1,000 each
Awarded
Application Deadline
Oct 12, 2026
Winners Announced
Nov 13, 2026
Education Level
Undergraduate
Share
Explore All Kinds of Scholarships for All Kinds of Students
The project I am most proud of is a touch-based study tool I built and presented as honors research this past semester. It runs on a Raspberry Pi 5. It reads touch input directly from the Linux kernel and writes pixels directly to the framebuffer. There is no operating system desktop, no window manager, no browser, nothing between the user's finger and the screen except my code.
I built it because I wanted to understand what was actually happening underneath the abstractions I had been using for two years. Most of what I had written before that project sat on top of stacks I had not built and could not see into. I wanted to know what the layers were. I wanted to know what the operating system did when I clicked something, what the display did when I drew something, what was happening in the bytes underneath the rectangle I had been told was a button.
The project taught me how to read from /dev/input and write to /dev/fb0. It taught me how touch events are timestamped and queued in the kernel. It taught me how a frame buffer is laid out in memory and how to map color values onto specific pixel addresses. None of that was in any class I had taken. I learned it by reading kernel documentation, by writing small programs that failed, by debugging through serial output when the display had not yet started rendering, by sitting with code for hours and slowly putting together a picture of what the machine was doing.
I presented the project at my college's academic showcase. The version on display held hand-drawn study cards for organic chemistry and tracked which questions a user got right and which they got wrong. Students could study without a phone or laptop in front of them, which several visitors told me they had been looking for. Underneath that simple interface was code that talked to the hardware in a language most students never need to learn.
That experience is why I want to keep working in technology. The thing that inspires me about software engineering is that the abstractions go down forever, and the engineers who can move between them are the ones who get to build systems that work in places other systems do not. Every screen anyone has ever touched is the top of a tower of code, some of which was written sixty years ago and is still running underneath. The engineers I admire are the ones who treat that tower as one continuous thing rather than as a set of locked floors.
I want to design surgical robotics, specifically orthopedic systems that operate in real time during procedures. That work requires the same kind of layered understanding. The control loop has to read sensor input at the kernel level. The visual processing has to render at the framebuffer level. The decision logic has to live somewhere between the two, fast enough to keep up with a surgeon's hands. There is no version of building those systems that does not start with someone, somewhere, willing to learn what /dev/input does and why it matters.
The honors project was the first time I built something where I knew what every line was talking to. I want the rest of my career to feel like that. I want to keep going down the stack, all the way to the metal, and then build the kind of machines that change what is medically possible because someone finally bothered to understand how the layers fit together.
A hush falls over the crowd as the video plays, the only sound the flipping of pages and the faint scribble of pen on paper. You can almost feel the gears turning in everyone’s mind as we try to comprehend the task that is being presented to us. The beginning of January marks the kickoff to the First Robotics Competition for the year. I joined the robotics team in my eleventh grade year and trying to figure out what game we’re playing is one of the most exciting topics to talk about. It is different each year and I know it will be a challenge to design and code the scouting system for the game in the upcoming months, but it is fun to discuss the theme, debate what the teasers might allude to, and joke about whether it will be a water game finally. I am drawn to the unpredictability of the event and the challenge it will ultimately present as I get to work with a close team to figure it out. There will be frustration, laughter, and games, but I crave the underlying excitement of it all.
Working on the scouting system for my robotics team was months of hard work. 7 days, 30 hours per week. It nearly qualified as a full time job. But it was my passion. What we made was innovative and new. Instead of following a traditional route of paper scouting, we designed and created our own software that allowed us to program Xbox controllers to record actions of robots on the playing field which would then be transferred through SQL server to an Excel spreadsheet that generated statistics and predictions about our competition as well as our allies. This data could be used by our drive team to come up with a strategy for each of our matches. Often at competition we would have other teams approach us to ask about our unique system, and asking us for help improving their own.
While our system was very beneficial to our team, it was also a lot of fun to work on. We had a small group, 3 of us students as well as two mentors, who would work on it together each night. We’d have brainstorm sessions on the whiteboards, play games as a mental break, host mini presentations and design reviews, and help each other out. I became the captain for our small group and was in charge of bringing the project to the rest of our robotics team, lead presentations to elementary school kids, and teach people from across the world at competition how our system worked. It is what got me into computer science as a career and it something that I am still very proud of to this day.
Imagine missing your bus four times in one week, forgetting to pull the stop request line, and ending up in a random town when you are just trying to get home. That was me during the first week of my internship in downtown Pittsburgh. But later that summer, I found that I would use that experience to create something to help people with this exact problem.
Two summers ago, I worked as a project assistant for Simcoach Games, a company focused on creating both entertaining and educational games. The project I contributed to was called Next Stop, designed to teach people, especially those with learning differences, how to confidently navigate public transportation.
My rocky start with public transit made me realize how hard it can be for young people with learning challenges. How do they manage commuting without any guidance?
Needless to say, I was pleasantly surprised when I learned that our project for the summer would teach just that. Next Stop would guide players on how to get where they need to go without all the chaos I’d experienced firsthand.
Over six weeks, our team of two artists, two programmers, and one level designer built a prototype of a 3D bus simulator using Unreal Engine. We used agile scrum development to make sure everyone stayed on track and contributed their best work. We also learned how to more comfortably use GitHub to collaborate and make changes to our project as needed
I served as one of the programmers, and I was responsible for developing mechanics that made the experience feel real. One of my tasks was to create an in-game public transportation app similar to Transit or Google Maps. Players could pull up their virtual phone, complete with GPS, a clock, and specific instructions for pickup and drop-off. I also programmed various player interactions, such as pulling the stop request wire, flagging down the bus, and sitting down in the bus without flying off as soon as it moved. To add more realism, I created NPCs who moved around the city, walking only on sidewalks or crosswalks, and slowing down the bus when necessary.
The coolest part of this project? It was later used in a study conducted by the University of Pittsburgh. The study focused on which medium was most effective in teaching individuals with learning differences how to navigate public transportation. Knowing that our work might contribute to helping millions of people get to where they need to go without feeling lost or intimidated was incredibly rewarding.
I took my struggles with public transportation and, with my technical and teamwork skills, turned them into something that could help others avoid the same headaches I went through. That’s a pretty great feeling.
To answer how working in technology inspires me, I think back to the end of that summer, when a researcher said to our team, “Thank you. We hope this game helps a lot of people.” It’s Moments like these, and the fulfillment of creating something meaningful, that inspire me to want to continue using technology for positive change through games and interactive experiences.
In eighth grade, I decided to join the high school robotics team as a useful introduction to programming and engineering design, as well as a fun experience to meet new people. What I discovered was that much of the organization was student-led, and the adult mentors were very hands-off. I found out during my first year that we were short on experience in several crucial areas of the team. Because of this, we struggled to perform together as a group. The following year, I stepped up and decided to bring things together.
One of the first things I did was take charge of the financial aspects of the team and create a fundraising committee to raise money for parts, tools, and other resources. Even though this was something new to me, I taught myself how to apply for grants and reach out for sponsorships and donations. Using my writing and organization skills, I was able to coordinate a spreadsheet with a master list of all possible grants and sponsors to contact regarding potential funding and support. I conducted regular meetings with a fundraising committee to check that our team was putting in sufficient effort toward fundraising and sponsorship outreach. These skills have been passed down over my four years of high school and remain with the team now that I have graduated.
Another area of improvement was in our team's ability to communicate common engineering technology concepts in electronics, programming, and product design. Having a very limited array of engineering and technology classes to gain knowledge and experience from, I sought out YouTube tutorials and online courses to help me be better equipped to take the initiative in our robotics projects. With an already small attendance roster for our team that first year, I took it upon myself to supervise the construction of our electronics board and main robot structure and transfer information between teams, which included the programming team that utilized Java and provided API libraries to code the robot's movement and task performance objectives. I was able to learn on the job and communicate the instructions to those with less experience for a team effort.
In just two years, we raised over $21,000 in grants and expanded our team from ten to thirty members actively helping make our team the best it could be. I was able to gain confidence in an area that had originally been completely foreign to me, and I am inspired to lead others in having an enriching experience learning about STEM and the world of robotics. Working in engineering and technology constantly inspires me to push myself out of my comfort zone and work to create things from ideas in my head. Through working with robotics, I have gained both soft and technical skills that allow me to take initiative and produce applications and projects in my college career. I am excited to learn more that will help me improve and level up my creations and make a lasting impact on important issues in my community.
Bold.org is Built to Make Scholarships Feel Possible
Step 01
Start with your story
Bold.org helps students show donors who they are beyond a transcript.
Step 02
Where scholarships are awarded
Every scholarship is funded by donors and managed directly on Bold.org.
Step 03
Fund your future
Scholarship dollars are disbursed through Bold.org to help students pay for school.
FAQ
When is the scholarship application deadline?
The application deadline is Oct 12, 2026. Winners will be announced on Nov 13, 2026.
How will scholarship application information be used?
Your privacy is a top priority on the Bold.org platform, and you can find our privacy policy in full here. You may opt out of communications from Bold.org at any time, and unless we’ve first notified you and gotten your consent, you’ll never receive communication from any third parties related to personal information you give us.
What is the scholarship award?
Award amounts per winner are designated by the donor. Check the award amount for a detailed breakdown.
When will the scholarship winner be chosen? How will they be notified?
The winner will be publicly announced on Nov 13, 2026. Prior to the announcement date, we may contact finalists with additional questions about their application. We will work with donors to review all applications according to the scholarship criteria. Winners will be chosen based on the merit of their application.
How will the scholarship award be paid?
Award checks will be sent to the financial aid office of the winner's academic institution in their name to be applied to their tuition, and in the name of their institution (depending on the school's requirements). If the award is for a qualified educational non-tuition expense, we will work with the winner directly to distribute the award and make sure it goes towards qualified expenses.
How will my scholarship application be verified?
Before we award the scholarship, the winner will be required to confirm their academic enrollment status. Depending on the circumstances, verification of Student ID and/or their most recent transcript will be required.
How should I get in touch with questions?
If you have any questions about this scholarship or the Bold.org platform, just email contact@bold.org and we’ll get back to you as quickly as we can.
Does the scholarship have terms and conditions?
Yes. The terms and conditions for this scholarship can be found here.
97% of students don't win scholarships. We’re here to change that.