Nathan Peck Email & Phone Number

Auckland, Nz

Seattle, Wa, Us

Seattle, Wa, Us

Responsible for educating existing and potential AWS customers about the suite of container services on AWS by writing blog posts, coding demo applications, and speaking publicly at conferences, on Twitch, and at the AWS loft. Engages potential and current AWS customers on social media platforms like Twitter, Stack Overflow, and Github with the intent of gathering feedback on potential improvements to the container service platform at AWS. As part of the product management team, drives roadmap items, including coding prototypes and contributing to design documents, as well as providing customer focused feedback on development proposals.

Seattle, Wa, Us

Developer advocate on the container services team at Amazon Web Services. Responsible for building the community around Amazon Elastic Container Service, Kubernetes on AWS, and AWS Fargate. Created projects such as the Awesome ECS list and Containers on AWS minisite for sample container architectures. Wrote blogs for the official AWS compute blog, as well as a dedicated container focused Medium blog.

Sunnyvale , California, Us

Lead engineer on the team builing Airtime's Node.js API. Team lead responsibilities included communication and coordination with client team leaders, as well as working with product leaders to plan engineering efforts that maintained high development velocity.Responsible for improving reliability of the Node.js API that powers Airtime's social communication platform, through the implementation of best practices to avoid security holes and performance issues. Also reorganized the backend to break up a formerly monolithic service into scalable and maintainable Docker microservices deployed on AWS ECS, and linked by a pubsub messaging backbone built on Amazon SNS and SQS.Gave technical talks at General Assembly and Capital One explaining Airtime's microservice architecture with the aim of educating attendees on microservice deployments and optimization strategies. Also contributed to the Airtime tech blog, to share detailed info about how Airtime runs its microservice backend on AWS ECS.

New York, New York, Us

Lead system architect and engineer behind the API that powered the StoryDesk presentation app. The API used clustered Node.js infrastructure to maintain its high 99.99% uptime and 98+ Apdex score. It processed image, pdf, and video uploads from clients, then delivered these business assets to iPads all over the world.Developed the proprietary algorithms used to power StoryDesk's real time analytics platform, which gathered thousands of metrics about how viewers view and interact with StoryDesk presentations, then turned these metrics into easily read reports that gave content creators a detailed understanding of how their presentations were being utilized.Also designed and developed StoryDesk Roundtable, a realtime collaboration layer for the StoryDesk iPad app that allowed one broadcaster to control many iPads simultaneously. Roundtable was built with Socket.io and Node.js for fast, efficient communication between thousands of iPads.Architect responsibilities also included presenting StoryDesk architecture and security mechanisms to VC's and to customers who wanted to do due diligence.

Created Bookflavor, a book search engine that "beat Amazon.com" according to The Next Web. Bookflavor utilized web crawling technology to compile book reviews and book information from numerous sources. It gave users beautiful summary pages that helped readers discover and learn about new books, then buy them through Amazon.com

Worked as a web developer with design studio Made By Argon (madebyargon.com) creating many HTML websites, including the website of VideoLAN, makers of VLC, the world's most popular video player with more than 1 billion downloads and counting.

An ad service for injecting relevant, localized Amazon affiliate ads into webpages.At the time the Amazon affiliate program had a critical flaw: if someone from Europe or Asia clicked on an affiliate link which took them to the US Amazon website the visitor would be redirected to the appropriate regional Amazon store and all attribution would be lost. The website owner wouldn't make any money even if the visitor bought products from Amazon.Affiliate Script solved this problem by allowing website owners to specify a product ID, or search by keyword to find a product ID. Then it used geoip detection to adjust the affiliate link to point to the correct Amazon website based on each web visitors IP address.Later I built a feature inspired by Google Adwords that read the web page title, headings, and other body text, and used the Amazon API to automatically find matching products across all regions. This allowed website owners to drop in one simple script and automatically place relevant localized affiliate links in their webpages.

Worked as a freelance web consultant doing varied work such as developing WordPress blog designs for many popular, high traffic blogs, administrating large online forums, and creating Google Blogger plugins.