Working in the new subjects area to bring Music education to the masses.

Building a reusable, production ready platform to launch social products in a matter of days. Breaking apart the homogeny of modern social media, by enabling novel and interesting experiences using a portable social network, design system, and common infrastructure.

To learn more, find us on the App Store:

Throwback by Loop - a weekly nostalgia app, breathing new life into your camera roll every Thursday.

Hoot by Loop - a modern voice messaging platform designed for fluid asynchronous conversation.

***** by Loop - coming soon.

Full-stack engineer, product manager, designer. Designed, built, optimized and maintained our people merge algorithm with a team of 3 others. Led a team of 4 that took our Birthdays product from brainstorming to launch in months, modularizing our existing infrastructure for cross-product use along the way. Led mobile engineering for 2 years.

Along the way I've: been on the core launch team for three products (Shine, Birthdays, Contacts), built an NLP multi-class name-classifier that achieved 90%+ accuracy and precision, integrated multiple external APIs (including handling data normalization and cleaning before incorporating into our contact enhancement pipelines), created an internal scripting 'API' to speed up developer iteration cycles and provide a home for common functions, built a prototype CardDAV server, reverse-engineered Apple's CardDAV protocol intricacies to develop a smart contact linking algorithm, built out an app health dashboard and user behaviour analytics funnels to iterate and improve our core flows, launched and managed digital ads campaigns, both designed and implemented multiple product redesigns (and designed a couple app logos), conducted user studies and technical interviews, onboarded and mentored new hires, modularized core client-side modules, built an experimental bump-to-share contact-sharing mechanism for iPhones, rebuilt our client CI/CD pipelines to improve flexibility and performance, developed bad data detection and contact quarantine algorithms, built a cross-platform fault-tolerant payments system and much more.

The core aspects of my work at Placemake.io involved algorithm development, data analysis and building data pipelines using custom API interfaces and automated web-scrapers to extract valuable data sources. Following this, I worked to combine and map these datasets to identify underlying socio-economic variables for use in Placemake’s location and mobility data platform (Javascript, Python, SQL, SPARQL).

Working on Placemake's small, dynamic team was a fascinating insight into the rewards and challenges of operating in the startup space. The team surrounding me were each experts in their field and learning from them was legitimately rewarding, if a little daunting at times. After working within the almost larger than life environment at IBM, my work at Placemake was fascinating, with each day a new challenge arose. This innately meant a fast-paced, highly reactive environment which demanded constant awareness of each team members blockers and how they can be alleviated.

I'm extremely grateful for the insights Placemake provided regarding operating in an early-stage startup, to have learned from a team littered with PhDs and for the chance to engage with the frameworks they use (including Docker, which was particularly timely as it was a core aspect of my Server Software class the following semester).

At IBM, I operated as the lead developer on an intern-led PoC project, transitioning to a co-op software development role in October 2017 on a larger team integrating the project into IBM’s core infrastructure in preparation for a company-wide rollout (Python, Java, SQL, Salesforce, Bash).

My work at IBM involved three core stages. During the proof-of-concept, I was developing the integration of Apttus Quote-to-Cash software with IBMs existing systems: building the bridge between Apttus’ Salesforce based platform and IBMs own DB2 based data. This involved a deep dive into Salesforce, a great deal of scripting utilizing Python, Batch Files and XML, and working within middleware tools such as CastIron utilizing Javascript to create custom functions.

Following my transition to a co-op role, and the projects' transition to a wider implementation, the work transitioned to developing a real-time link between Apttus and IBMs data. This largely involved development in Java working closely with the team developing IBMs internal API platform. Towards the end of my time at IBM, I was provided with a yet another useful experience: transitioning a codebase to a new team. During this process, I learned a great deal about code structure and persistent documentation as well as the challenges and best practices in educating new developers.

Think. Be essential. How to Stuff a Wild Duck. Three pillars of a simple ethos that represent the pivot points of IBMs journey into a fresh faced future. IBM represented my first real experience working within the technology industry, and I’m indebted to the development opportunities they continued to provide me. Having studied the Agile methodology during the previous year at Duke, working within it was a rewarding learning experience. IBMs transition to Agile gave myself and my team the opportunity to develop rapidly and iterate fast. With this speed came responsibility, and I sincerely appreciate the level of trust they put in us.