Timothy Calabro

Lehman Brothers: where mobile became engineering

I managed the BlackBerry Support team at Lehman Brothers. The work was not just fixing phones. It meant improving the way customer service moved, streamlining repeatable support processes, certifying mobile devices, and certifying the applications allowed into an enterprise environment.

That was where I first learned application development. The support side showed me what users, administrators, and a large organization actually needed. The development side let me build it.

Enterprise mobility, from support floor to architecture

Between Lehman Brothers and Wells Fargo, I led one of Bloomberg's Global Technical Support teams. I then became the lead Mobility Engineer at Nomura Securities, where I built and managed the BlackBerry and Good Technology infrastructure serving the Americas.

Wells Fargo: self-service mobility at enterprise scale

At Wells Fargo I learned C# and Microsoft SQL Server and built a self-service mobile-device provisioning and management solution. I also consulted internally on how lines of business could build their own applications, led development of a mobile compliance solution, and performed technical evaluation of line-of-business applications as part of the certification process.

Three platforms. Three native stacks.

I learned J2ME for BlackBerry, Objective-C for iOS, and Java for Android. I used those languages to build the Random Events mobile applications across all three platforms.

Will Petz owned Random Events and the operation behind it. EAS owned the multi-platform applications and the infrastructure that supported those applications. That distinction matters: the live business, logistics, and events were Will's; the mobile software was ours.

Quiet Events: the whole application stack

When I built the Quiet Events applications, I learned MySQL, PHP, and Cordova hybrid app development. That expanded the work from native phone code into the data, server, and application layer behind the experience.

For Quiet Events 2.0, I learned Swift and Kotlin and rebuilt for modern iOS and Android. The technology changed; the operating requirement did not. The software still had to support people doing real work in live environments.

What I actually own

The real architecture: how it is built, how it scales, and what does not break. Enterprise solution design, backend systems, and the infrastructure decisions that are expensive to reverse. I would rather spend a week on the shape of a system than a month undoing it.

Beyond the phone

For the past five years I have worked as a senior pre-sales engineer, building proofs of concept on Android, iOS, Wear OS, and Android XR. I also help customers and partners integrate Samsung technologies into their daily workflows.

Cloud services, wearable development, mobile-device management, VR, XR, and computer vision all follow the same rule: build the system so people can depend on it when nobody is watching.

Where I have carried it

Support management, global technical support, mobility infrastructure, enterprise engineering, compliance, app certification, technical consulting, pre-sales engineering, and proof-of-concept development. I also held CTO and CIO roles at other companies while continuing to build EAS from another state.

EAS was never the thing we did instead of the industry. It was the thing we kept building while operating inside it.

Now

I am the CPU: engineering, systems, and the architecture underneath the work. Cap drives the ship forward: product direction, hard calls, client momentum, and the push from idea to deployed work. The projects we parked for years are the roadmap, and EAS clients get both of us.