Microsoft Research (eXtreme Computing Group)

Software Architect

Working as a Software Architect on the Cloud Research Engagements initiative in Cloud Computing Futures (CCF) team, part of eXtreme Computing Group (XCG) of Microsoft Research. My current responsibilities include investigating new technologies to leverage Windows Azure as a viable platform for research, and I outline software architecture and high-level designs for our development efforts.

Microsoft Research (External Research)

Technical Development Lead

Responsible for the architecture of the Trident Workflow system, an e-Science workbench offering to increase researchers’ productivity and collaboration. Based on Windows Workflow foundation and “cloud” services, Silverlight and Windows Communication Foundation we are leveraging top company products to add value to customers. The system is now being produced by an offshore team, and one of my responsibilities is to oversee the design and architecture of the solution while they are being extended by the external parties, making sure they fit together nicely, correctly and meets long term goals. The system design accomplishes a virtual storage system that customer and developers can plug various data backends to our systems. A few example of data stores already produced using the infrastructure I designed: SQL Server, MS SSDS “cloud”, Amazon S3, XML file. Everything in the system is automatically generated by a code compiler and takes input from the user and build runnable and extensible code that our developers build on top of.

Designed the Power Management architecture for the Singularity Operating System, a managed operating system being developed by Microsoft Research. Responsible for all areas of the subsystem, from hardware level device drivers, ACPI, all the way in the stack through user mode frameworks and tools. Singularity is currently released as open source and the power architecture is part of the 2.0 release of the product. To accomplish such big goals, heavy team collaboration skills were necessary, to bring various teams together and deliver the necessary modules (hardware team, I/O subsystem team, shell, etc). Also managed contractor to help in the coding phase.

Also responsible for defining the scope of 2 Ph.D. students internship goals and integrating them with our platform, while working as a mentor for them (technically and career wise.)

Virtual Manager (WEMD)

Technical Development Lead

Responsible for 2 feature areas of the product, Virtual Machine creation and management of virtual machine library, with a team of 2 other developers. Able to deliver all work assigned to my team. Among other tasks, the following skills were leveraged in the job: Architecture Design, Security Design & Review, Management of scheduling, Feature/Bug Triage.

In addition, I was also responsible for the security architecture of the product.

Intellectual Property & Patents: Since I joined the team, 5 patent applications were created to protect the innovative work I’ve done. From those, 4 patents were filed and others are in preparation. I brought a lot of IP and field knowledge of my previous project VSDM that is currently available on Download Center for external customers.

Code quality and testing: The feature teams under my responsibility exceeded the code coverage goals for the modules we delivered. We also provided component test cases to be run by Test Team. We worked very closely with fellow testers assigned to our feature areas.

Cross-team work and collaboration: Working with PM to address cross-team issues between my project and Windows, Virtual Server/Viridian projects. Issues that were addressed include Windows (Sysprep, PID generation and validation), Virtual Server/Viridian (device drivers), etc. Worked with product management (GM & PUM) to be a reference for technical analysis and reviews.

Virtual Server Deployment Manager (VSDM)

In my own time invented, designed and developed a deployment tool that augments Virtual Server 2005, which was responsible for huge cost savings across all Microsoft, and Microsoft subsequently decided to release it to customers. The entire product was designed and written by myself. Many internals teams and divisions (including MBSA and SBTU) completely virtualized their operations, solely relying on VSDM system as their primary development and/or test systems.

http://www.microsoft.com/downloads/details.aspx?FamilyID=ff59c543-5107-42f6-9252-a8cde3b53915&DisplayLang=en http://blogs.msdn.com/nelson_araujo/archive/category/9970.aspx

Security Protection Product Team (SPPT / SBTU)

Worked as a developer for the Microsoft Baseline Security Analyzer (MBSA) tool. During the upcoming version 2.0 product cycle, stepped up as the lead developer for the team. Responsibilities of the new role included: Feature definition, design and architecture, creation and management of the development schedule, management of developers, establishing and maintaining cross group relationship, interacting with other teams, driving requirements to their product teams, receiving and managing requirements from partners. Also participates on management “WAR” meetings to approve/reject DCR and bug fixes.

Participated in all phases of development from conception up to publishing bits live, including code reviews, privacy, geopolitical, clipart, code signing, virus verification, release management. Actively participated in security code reviews (security pushes) for MBSA 2.0.

Source Depot: installed and maintenance of team’s source control infrastructure; Build Environment (CoreXT, NT): designed the team’s build system and extended the CoreXT infrastructure (driving requirements back to CoreXT product) to include automatic pseudo-localization, multiple web application localization, automatic build and “dot” builds, check-in mails, etc. Managed the Virtual Servers for the team.