Apple

I started out at Apple as the sole developer on my application, an internal-facing automation API that previously had been worked on by a wide range of contributors and become important enough to require a dedicated lead. Over the summer and fall I developed my understanding about the AirPlay space and the wide world of Apple engineering and began to make huge strides with the app. I brought it to enter the customer build (a mark of intense pride at Apple), scaled up our user base, took on development work for features in their earliest stages of conception, and more.

Sticking to my job’s intended responsibilities has never been my strong suit, though. 8 months into my time at Apple, I picked up two new responsibilities in the course of a week: developing the knowledge base and automation of our lab spaces, and co-leading the effort to improve AI use practices in internal development. The former was instructive in how relevant physical systems can be to their digital counterparts, and taught me how deep the depths of precision can go.

Working on AI at Apple is a joy. I spend time documenting and presenting about it, sure, but mostly I just build. I’m always finding more ways to automate and interact with systems I’d previously thought untouchable, and building a very strong knowledge base in working with agentic flows. They say teaching is the best way to learn, and that’s proven true here - my understanding of AI in my work has grown exponentially in the last few months.

Apple is a unique company and keeps a wonderfully high bar for who it brings into the circle. My coworkers have taught me a ton, and I’m so honored to be able to have learned with them this early in my career.