
Please be patient while this website is being built. It has been a few years since I have worked with raw HTML rather than jekyll or react-UI and I am trying to re-learn what is important in accessibility practices. In addition, I'm still figuring out exactly what it is that I want to say about my past experience that explains why you should bring me on to your team.
I’m a full-stack software engineer with a background in systems development at Northrop Grumman, where I contributed to applications in defense and aerospace. Working in this environment taught me how to build reliable, scalable software under strict requirements and collaborate within multidisciplinary teams where precision and clarity are essential. I had the great pleasure to act as a team leader in our transition to modern version control systems in git and it's integration to our transition to agile development.
Alongside my engineering work, I’ve spent over a decade as a post-secondary educator, teaching courses such as Introduction to Programming, Data Structures, Theory of Computation, and Principles of Programming Languages. My background as an educator has honed my skills in breaking down complex technical concepts to communicating them clearly to a range of audiences, whether that’s teammates, customers, or end users. In teaching large, diverse classrooms, I’ve learned how to quickly assess different levels of understanding and adapt explanations in real time. Those same skills transfer directly to software development where shared understanding is critical to project success on cross-functional teams. I have regularly applied these skills when documenting code, reviewing pull requests, mentoring junior developers, or translating technical trade-offs for product managers and non-technical stakeholders.
Most of my professional background is in developing data storage and access systems for computer-to-computer interactions. In my graduate studies I grew my skills in user centered design and object oriented design to bring a more rounded approach to my software development in future employment.
A11y is a "numeronym" for "accessibility" used commonly by the technical community that works with accessible technologies (AT) and and standards. In my personal life, I use a screen reader for most of my readings. While I am capable of sighted reading, I often find it fatiguing and prefer to access information through audio formats. I use the text-to-speech feature on Mac wich requires highlighting information. Sometimes it actually keeps highlight tracking for me so that I can follow along with sight, but it's quite inconsistent. I'd like to explore these quirks futher in my research someday.
A special thank you to the mentors that helped me get my start in teaching CSCI 3155 Principles of Programming Langauges at the University of Colorado Boulder, Bor-Yuh Evan Chang and Sriram Sankaranarayanan
