After over 11 years at Twilio, it was time to take some time off and recharge. When I interviewed back in late 2010, Twilio were only about 15 people and now, well over 7000! Being part of this journey has been tremendously fun, rewarding and exhausting, all at the same time but ultimately, I will be forever grateful! Next – nothing! My only plan is to watch my daughter, who just turned one, grow to be two and then I may be ready for something new. Until then, I may be interested in shorter engagements or just a chat.In particular:Technical:* API design – in particular how to ensure your API can scale as your product becomes successful.* CPaaS – In general but in particular around VoIP (SIP, RTP) and how to scale such a system globally.* IoT – Mobile Core (EPS – Evolved Packet Core). Diameter, GTP, IP Breakout etc.* HTTP – REST, WebSocket – the normal stuff. In particular what not to do.* General Networking – managing permanent connections, TCP v.s. UDP v.s. SCTP. When to use what and why.* Building and scaling distributed systems.* SRE – Observability, Monitoring (they are not the same thing), SLI/SLO/SLA, Tracing, Logging, Events. In short – Operational Excellence.Non Technical:* Growing a team – who to hire.* Mentoring* The interplay between Product & Engineering.* How to run successful Game Days (Chaos Testing)

Since early 2016, I've been one of the Architects at Twilio and as an Architect, I try to help more teams across more areas to achieve their goals, as well as the overall goal of Twilio's technical approach and future.In particular:=== Video ===* Technically responsible for on-boarding our new Madrid office, who we acquired about a year ago for their video media expertise.* Helped design and implement the first version of our video recorder (implemented the first PoC).* Helped design and implement a new network architecture for the signaling to the media server.* Designed & deployed the video global low latency infrastructure. Based on my original design of how we do GLL for Voice.=== Voice ===Since I’ve designed and implemented most of the original globally spanning voice connectivity network, I am still very much involved in this never ending effort, in particular:* Working with the new Voice Insights team to guide them into how to interpret all the data we publish from everywhere.* Working with Voice Insights, Voice Connectivity & Video teams to revamp our collectors of data so we can get an even more real time streams of information, which goes both to end-customers but also feeds into our monitoring & alerting systems.* Re-designing some of our media flows for fewer hops, shorter latency and ultimately, a better experience for our customers.=== Twilio Wireless ===Working with the Twilio Wireless team to bring voice to our SIM cards. Since this is uncharted territory and carriers do not fully setup to make this happen, I am also, together with the entire team, working closely with carriers to build a new solutions for the future.=== Security ===There are many security concerns and regulations to follow so working with our Security & Legal teams is an ongoing effort in order to ensure that we follow industry best practices, the law, and ultimately ensure that the trust of our customers isn’t violated.

I am the SIP geek at Twilio and most of my projects fall within that area. Below are some of the bigger projects that I am/have been responsible for.= Project: Global Low Latency (GLL) (Dec 2011 – ongoing) =One of the challenges that we are facing at Twilio as we expand globally is audio quality. In order to maintain audio quality across the globe (and to keep the latency at a minimum), you need to keep the media as local to the end-points as possible and I am responsible for this project. I designed/implemented/deployed 100% of this project and as of now, it is deployed at 5 locations around the world and counting.At a technical level, the solution is essentially SIP B2BU:as with the ability to handle re-invite scenarios to change the media streams as we find better paths through our system. See Jeff introduce GLL in his keynote from TwilioCon 2012: tinyurl.com/mswjnsx @1:20:35= Project: Public SIP Out (April 2012 – ongoing) =Customer with existing legacy system can connect into Twilio using SIP and in that way bring new features to their old boxes using the Twilio communication stack. As the Tech Lead for SIP Out, I designed and wrote the majority of this system, in particularly, I wrote all the code for our SBC:s.See my presentations from TwilioCon regarding our Public SIP offering:- 2012: tinyurl.com/lua8rae (SIP Out) @23:39- 2013: tinyurl.com/ml8rp4d (SIP In)= Project: Twilio Client (Jan 2011 - Dec 2011) =I was hired to build and lead the team for Twilio Client. I was responsible for the successful delivery of the project as a whole and was the lead developer/architect for the solution. Since I am a backend guy (and protocol geek) I built 80% of the backend for this solution and directed the guys building our SDK:s for how to deal with signaling and media etc.See my presentations from TwilioCon regarding Twilio Client: - 2011: vimeo.com/31405272- 2012: tinyurl.com/krwxqwf