I work on a pair of apps for a strategically-important partner. One in Swift, one in Objective-C. I have taken the lead on a number of features by doing the needful to turn incomplete specs into finished features. I get and receive code reviews and have helped part of the team learn to do git better.

As an iOS developer I primarily write code for a brand-new SDK. We're in a tight loop with a high-profile client and we're building features out to support their initial product demo. The core of the SDK is written in C++. I don't maintain that but it's been fun to learn about how to bridge languages and managing memory with that. I get to work with AVFoundation quite a bit, which is super cool. I am responsible for new features, documentation, automation of SDK packaging, and some git-fu that this team was needing.

As an iOS Support Engineer my primary job was to quickly gain a deep understanding of a never-before-public SDK. I have suggested many improvements that have made integration by external developers easier. I worked to continuously improve all documentation. I initiated a project to automate SDK packaging and led another developer to successfully complete the effort. I provided technical integration support directly to external developers.

I led our front-end team. We were responsible for our public and internal dashboards. We worked with a variety of front-end stacks, often preferring (for better or worse) homegrown. I contributed a lot of code as an individual but ultimately felt more successful when I could get away with doing code reviews for a really busy team -- things just hummed. I had great relationships with other team leads and that more than anything was what let me be successful. Lots of git just weaving together releases, Jenkins plus WebDriver/Selenium and some other tools to automate browser-based UI testing, and some back-end Python thrown in now and then. This was a great job.