SKILLS

• Other Hands on experience with Stocks, Options and Equity Trading / Platform usability 8 years
• Technical: Extensive experience in Quality Assurance, Development and configuration/release management using streamlined AGILE methodologies such as SCRUM, XP, and RUP processes. Expertise in large scale enterprise environments. Expertise in build / release management methods and implementations. SCM software used: Team Foundation Server TFS , Perforce P4 , CVS, SubVersion, Microsoft Visual SourceSafe, and SourceGear Vault. Soft: Leading teams/departments, Motivating, Solving Issues, Decision Making, Excellent Communication written/verbal , Exceptional Listener, Coaching Operating Systems: UNIX AIX, Linux, Red Hat , Windows Vista/ 2000/XP/NT, DOS. CMS: WordPress, Joomla Programming Languages: .NET, SQL, Perl, C, C , C , Visual Basic, HTML, ASP, PHP, JAVA Tools: PowerShell, Selenium, Cruise Control, NAnt, Eclipse, Ant, FrontPage, Adobe Photoshop, PKWare software, Adobe Flash, Quicktime, Jira, Quality Center, Bugzilla, QTP, UFT, TeamCity, Electric Cloud Products Internal Apps / Servers: Apache, Weblogic, Tomcat. Hardware: Strong knowledge of PC upgrades and installation Server Administration Misc: Media creation spanning to the integration of video, audio, and CD technologies.
• OVERVIEW Years of experience in the software engineering arena. Managed multiple groups/departments onsite and off-shore Dev,QA,Release,Ops . As with most companies, communication and information transfer is one of the biggest hurdles to get over. Under my supervision and direction, departments were able to become more streamlined with tools to make communication fairly transparent. Worked in shrink-wrap environments, web environments, as well as a mixed environments. My background entails sectors in finance investment banking/online banking, Insurance , advertising, customer support, and services. I am extremely comfortable in both the WINDOWS and LINUX platforms.

WORK EXPERIENCE

Confidential

The main responsibility is to improve the Configuration and Release process. The current hand over from DEV to CM is via emails very outdated and not very streamlined . This is being changed by setting up a request system whereby request tracking will be in a centralized location. P4 streams are being set up in conjunction with the present source control system for ease of merges. The branching methodology is being changed to use the mainline methodology. With the use of labels, less branches will be needed which will reduce the number of possible merge errors that are occurring at the moment. In addition, the current setup contains over 50 branches for point releases that are essentially for one monolithically product line. Direction and advice is being provided to the DEV teams to componentized the product stream for an easier deployment strategy. From a release perspective, all processes are currently being done manually. The in-progress tasks are to automate the processes in order to reduce the number of errors relating to deployments. Consistency, repeatability and audit trails are a priority to ensure DR scenarios. Alongside these initiatives, normal day to day management efforts are conducted for direct reports who are physically situated in various regions. I am also in involved in what is called a COP Channel whereby training, knowledge transfer, and innovation is the goal. I have recently hosted an Agile fest event whereby company leadership personal were on a panel to talk about Agile and to promote the methodology across the firm. In parallel, demos session and speaker sessions were held by companies such as Microsoft, ThoughtWorks, and alike.

Confidenital Manager, QA/Release Financial

Oversaw and directed both the QA department as well as the Release department. Set process guidelines to be followed by all of the IT organization and insured proper adherence. Held daily scrum meetings to review open bugs and next steps for resolution. Created a global communication channel to track changes from inception to completion PROD . Set up an approval process to track business sign-off. Involved in ongoing initiatives to utilize just one set of software suites across the organization onsite offshore verses multiple suites. Worked with vendors such as HP to negotiate pricing on contractual software utilized within the organization and sets up the necessary budgets. Aligned business needs with AGILE scrum methodologies the use of sprints, user stories, iterative builds, project estimations and alike are used as part of the process. Mentored staff on best practices and held howto meetings with all engineers. In addition, brown bag sessions were held to promote knowledge transfer, creativity, and innovation.

Confidenital Manager, Release Management Internet Services Real Estate

Headed the efforts of setting up the Release Management team from the ground up. In addition to the day-to-day administration, management and builds software written in C using .NET 2.0 , the main responsibilities/duties at the firm were to standardize processes utilizing Rational Unified Process aka RUP across both the Dev, QA, Release departments. TFS was used as the bug tracking software as well as the source code repository. With my direction, the QA department improved greatly in writing clear, concise, and well-formed bug tickets. Before the process improvement, developers were constantly at a QA Engineers desk trying to understand the problem at hand. This improved communication between development and Quality Assurance. From a configuration/release standpoint, the first major change that was implemented was the TFS upgrade from 2008 to 2010. With the upgrade, project managers, dev managers, and upper management were able to gaze at one centralized location to obtain information on software timelines, completed work, and other aspects pertaining to the AGILE process. User stories were directly added to the portal verses having to manually create excel spreadsheets and sticky notes. Other improvements at the firm with my direction included automated build/compile processes, standardization of versioning as well as branching/merging, production calendar views, and a centralized DB for capturing requests for builds and deployments.

Confidenital Manager, Configuration QA Internet Services Marketing

• Established methodologies and processes for the software configuration management team main focus using the .NET platform . Brought in automation to the release and deployment cycles CruiseControl Nant . Worked closely with the development and QA management teams to create a streamlined way of handling requests for builds. Guided the developers in terms of CM best practices for labeling, branching, and working with source control. Some of the main accomplishments included the reduction in time for build compilations and deployments, the setup of multiple environments to support parallel development efforts, as well as a set system for disaster recovery DR and rollbacks.
• From a QA perspective, responsibilities included evaluating various testing tools and utilities. One of the initiatives was to install QTP hands-on and make recommendations on the usability/functionality. In addition, other responsibilities included hiring new QA staff members as well as managing the QA testing efforts from the perspective of test cases, automation, perf testing, and alike.

Confidenital Manager, Configuration Management Internet Services Financial

• Headed the efforts of standardizing all environments across multiple networks. These efforts were based on architecting a scheme in which the development, QA, and production regions looked similar.
• Managed a team of 7 Configuration Management engineers. Analyzed and directed the efforts to improve processes. Worked with VP's and SVP's on the SDLC model with emphasis on the roles and responsibilities within the CM Team.
• Involved to a great extent with auditing compliances SOX, internal, and third party .

Senior Configuration Engineer

• Responsibilities included creating daily builds for the various base line products. Advised the development teams on the proper way of utilizing the source control
• software Perforce SourceSafe for maximum productivity concurrent development branching, the use of labels and clients, etc . Other tasks included releasing builds to QA as well as production. Involved greatly with the configuration and troubleshooting of the QA environments. Created a qued build request tool. This tool was used by the development teams to notify CM that a build was ready to be compiled and moved to QA. Worked closely with systems engineering, architecture, networking, DBA's, and security to set the correct environments in production for new and existing product lines. The perl programming language was used extensively to create build automation as well as other various tasks.
• Headed the efforts to get the Lending products source controlled. Also, devised a system by which deployments to the java environments Weblogic, Tomcat were simplified.

Confidenital

Production Manager Internet Services

Supervised/Managed a team of 5 production engineers. Other responsibilities included generating weekly reports showing various statistics. Involved in daily meetings pertaining to the design and implementation of upcoming software builds. Implemented and directed the efforts of an automated system to produce build forms which were used in the production of cd customization. Also, traveled to companies such as Microsoft to learn about new technologies/software packages that can be utilized internally and/or by clients.