The Manhattan Initiative
Client
Role
Date
Location
I am a Senior Software Engineer on the T-Mobile Manhattan Core Team. Our mission is to empower smartphone manufactures with the capacity to directly provision cellphone service on the devices they produce. Essentially, any store-bought device should have full service from day one. Simply unbox, turn on and enjoy service. In order to fulfill our mission, we are reconsolidating T-Mobile’s internal micro-services landscape into a single unified set of fifty high-quality self-describing fully distributed API’s and integrating this cryptographic device entitlement layer directly into the systems of Apple, Samsung and more.
My day to day consists of experimenting with techical POC’s, turning said POC’s into working solutions, guiding developers across teams and providing eye-in-the-sky support for anything related to Redis.
I am the Technical Champion of the Control Object Storage Engine, a proprietary implementation of the distributed live-object model, essentially using Redis as a shared heap for JVM’s running in different datacenters across the US.
Personal Achievements
- 🏆Reduced OP/s and memory footprint on Redis by 95% by singlehandedly implementing a custom Java serialization mechanism using Concise Binary Object Representation (CBOR), Google Snappy for compression and Redis Bucket-based Storage.
- 🏆Improved performance (max-RPS) of GraphQL API’s by a factor of 4 by multiplexing internal query resolvers. Inflight IO-sensitive operations are batched and subsequently dispatched using a custom mechanism I implemented, similar to the Node.js Event Loop model, but then for JVM-based applications.
- 🏆Singlehandedly built TDOG, a tool engineers use to manage the micro-service ecosystem, including homogeneity of dependencies, release train consistency, and analyzing runtime telemetry for failure.
- 🏆Lead the bi-weekly architectural forum for discussing technical challenges and direction (8 teams; 75 attendants)
I enjoy working on this project as I believe that internet access should be as frictionless as possible.