Author Image

Hi, I am Alan

Alan Hawrylyshen

Staff Site Reliability Engineer / Staff Site Reliability Engineering Manager at Google - most recently

I am a passionate software engineer and manager with over 35 years experience. I help organisations tell stories with data that drive and align teams, products and the business. I help teams develop engineering process improvements that make development faster and joyful.

Skills

Experiences

1
Google

2017.01 - 2025.04

London, UK

Google Cloud - Serverless Compute SRE

Staff Site Reliability Engineering Manager

2017.01 - 2025.04


Microsoft

2011.1 - 2016.1

Palo Alto, US & London, UK

Skype Engineering Operations

Principal Software Engineer - Skype Internal Engineering Systems

2015.07 - 2016.1

Principal Group Manager - Skype Continual Improvement Program

2013.04 - 2015.07

Product Unit Manager - SDK Portfolio

2011.1 - 2013.04

2

3
Skype

2010.01 - 2011.1

Palo Alto, US

Platform and SDKs

Director, Engineering Portfolio - Software Development Kits

2010.09 - 2011.1

Director, Plaform Products & Engineering

2010.01 - 2010.09

Responsibilities:
  • todo1
Director, Platform Products & Engineering

2010.01 - 2010.09


Ditech Networks Inc.

2006.07 - 2009.12

Mountain View, US

Strategic Technology Applications and VoIP Products

Director, Strategic Technology Applications

2008.01 - 2009.12

Director, VoIP Protocols and SBC Development

2006.07 - 2008.01

Director, VoIP Protocols

2006.07 - 2008.01

4

5
Jasomi Networks Inc.

2002.01 - 2005.06

VoIP Security and Access Products

Chief Technology Officer

2002.01 - 2005.06


Raytheon Systems Canada Ltd. (Consultant)

1995.08 - 2001.08

Canadian Advanced Air-Traffic System (CAATS)

Sr. Software Engineer

1995.08 - 2001.08

6

Education

Department of Computer Science

Publications

Authenticating an Application to Access a Communications System

Embodiments describe transmitting authentication data from an application to a communication system. The communication system verifies the authentication data transmitted from the application, and on the basis that the authentication data is verified, the communication system authenticates the application for accessing the communication system on behalf of a user. Prior to the transmitting step the authentication data is provided from the communication system to the client, and then from the client to the application. The verifying step comprises determining that the authentication data transmitted from the application corresponds to the authentication data provided from the communication system to the client, such that the application is authenticated for accessing the communication system on behalf of the user on the basis of the client’s authentication with the communication system.

Voice activated application service architecture and delivery
USPTO 8301452 2012-10-30
Todd Simpson Nathan Chandler Alan Hawrylyshen Chad Madison Mike Lambert Karl Brown

A system and method for retrieving distributed content responsive to voice data are disclosed. Voice data is transmitted from a source client device to media server which applies a mixing table to route the voice data to one or more destinations described by the mixing table. The media server also analyzes the received voice data for one or more events. Responsive to detecting an event, the media server communicates with an application server, which modifies the mixing table so that subsequent data is also routed to a media generator which analyzes voice data received after detection of the event for a command. The media generator communicates with the application server to retrieve data from a user data source, such as a website, associated with a detected command. The media generator produces an audio representation of the retrieved data which is communicated to the source client device via the media server.

Requirements from SIP (Session Initiation Protocol) Session Border Control Deployments.
RFC 5853 2010.04
Hautakorpi, J. Camarillo, G. Penfield, R. Hawrylyshen, A. Bhatia, M.

This document describes functions implemented in Session Initiation Protocol (SIP) intermediaries known as Session Border Controllers (SBCs). The goal of this document is to describe the commonly provided functions of SBCs. A special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. This document also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or if additional standards work is required.

Session Initiation Protocol (SIP) Torture Test Messages
RFC 4475 2006.05
Sparks, R. (Ed) Hawrylyshen, A. Johnston, A. Rosenberg, J. Schulzrinne, H.

Examples of Session Initiation Protocol (SIP) test messages designed to exercise and thoroughly check a SIP implementation.

Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies - Updates for RFC 3261
RFC 5393 2008.12
Sparks, R. (Ed.) Lawrence, S. Hawrylyshen, A. Campen, B.

Recent Posts