I architected and, with a team of three engineers, delivered the Interact Content Repository (ICR,) which is a server side system to manage and store content for campaigns in a multi-tenant fashion behind a Jersey/REST subsystem.I am in charge of the architecture and design of the Programs platform. This platform is a workflow engine that drives a set of interactions for a given individual, through which you can perform follow up conversations via email, SMS, or push to the user devices.Architected the AppCloud subsystem, as a way to integrate applications into the Responsys product.I also architect the Audience engine, a platform for filtering individual through a visual workflow interface.I architect the multi-channel initiative. Through this, we can target individuals in their mobile devices, or multiple addresses, without duplication.I architected and implemented the Responsys Personalization Language, or RPL. This is the language used to embed in personalization templates for email, SMS and Push. It is a derivative of freemarker, with significant additions to the language itself.As an architect of the Applications team I manage the architecture for multiple UI products, including the Email Message Designer, Campaign Workbook, Content Library, and others.

Helped define the new direction of the architecture, and pioneer in new technologies (i.e. analytics, recommendations, etc.)Implemented the analytics subsystem based on Hadoop, Hive, Cascading, HDFS, S3, EC2, Elastic MapReduce and MySQL. Created a cascading tap (driver) for SQL access to hadoop.

Site development, architecture and ownership for three properties in Yahoo!: Yahoo! Groups - development and site management - 2009 to 2011Yahoo! Pulse - revitalization and management of entire site - 2011Delicious - site management and transition to Avos.com - 2011

I led the technical team throughout 2001 creating the first wave of the newScale flagship product RequestCenter. Included responsibilities: Architect the application, Database model, management of both development teams and the QA manager, and affecting directly the product direction, while developing a great deal of the application.

I led the UI mobilization to Windiows, and later transferred to lead the Process Builder product in C++ in Windows, in a client/server architecture. I was then in charge of architecting the user interface of all the products, while architecting the Exchange server workflow extensions of Action Technologies.I then moved to lead to produce the proper architecture after some failed attempts for the Web front end language and engine for ActionWorks Metro, which became the flagship product of Action Technologies, a workflow company.

I taught the Parsing and Compiler Construction course for the 9th/10th semester Computer Science students.

Led the development team and the product architecture, in C and assembly language in Windows 1.03. My first interview after school, and I was hired right after it finished. Thanks to my extensive knowledge of the Windows and PC architectures I was hired by an american organization to lead their efforts to convert their text-based UI into Windows 3.0Here is where I wrote the programmable Windows Printer Driver named Generic/Text Only, which shipped with standard Microsoft Windows 3.1, and ships to this day (Last I checked is there in XP, 2003 Server)The products produced directly by me and my team included: PACO, an accounting system, PAC, a sales front end and relationship management with inventory, invoice management, etc.I learned all 737 APIs of Windows almost by memory. Problem is, I still remember a good bunch of it.