SUMMARY

• Results - driven, customer-focused, articulate, and analytical Web Project Manager/Senior Software Developer with over 20 years of experience who can think “out of the box”. Strong design and integration problem solving skills. Skilled in various programming languages, platforms, and technologies. Possesses excellent leadership skills and a highly analytical focus.
• Sound communication skills and good ability to multitask to allow for skilled delivery of IT solutions.
• Utilizes the Software Development Life Cycle to turn business ideas into real-life IT Solutions.
• Design, develop, implement, and maintain numerous applications that support day-to-day operations
• Develop technical solutions that definitively improve scalability, performance, and profits
• Discern key business requirements and objectives by interfacing with stakeholders
• Plan, develop, implement, and support successful large-scale projects from conception to completion
• Proficient in Java development and object-oriented analysis/design
• Superior analytical, time management, collaboration, and problem-solving skills
• Takes a collaborative approach to problem solving
• Involves IT team members in planning
• Adaptable with frequently changing requirements
• Has excellent communication skills
• Great leadership and supervisory abilities
• Skilled in managing teams to deliver high quality, timely IT solutions of various scope and priority

TECHNICAL SKILLS

Languages: Java, J2EE, HTML, JSP, JAVASCRIPT, CSS, AJAX, VB,VB.Net, ASP.NET, C#, C, C++, XML, Shell Scripts, ArcGIS, CICS, COBOL

Operating Systems: UNIX ( Solaris, AIX, Sun), Windows

Servers: Oracle VM, WebLogic, WebSphere, Apache, Entera, CORBA

Frameworks: MVC, Struts, .NET

Databases: Oracle, Confidential SQL Server, DB2, SQL, PL/SQL,ETL,DTS

Tools: Eclipse, Visual Age For Java, WebSphere Studio Application Developer, JBuilder, NetBeans, Visual Studio, Oracle DB Suite, Confidential DB Suite, Toad, SQL Developer, SQL Navigator, DB2 Command Center, PVCS, Team Connect, Subversion, Team Foundation Server (TFS), ESRI WebAppBuilder

PROFESSIONAL EXPERIENCE

Confidential, Edgewood, MD

IT Team Lead

Responsibilities:

• Responsible for overseeing the day to day operations of the team.
• Responsible for managing numerous work orders and projects to ensure their timely assignment, progress, delivery, and support.
• His current team supports over 50 custom built web applications coded in a variety of languages/technologies on multiple platforms (primarily .NET with SQL Server DB).
• Evaluates performance, motivates the team and assigns tasks based on areas of expertise to help facilitate their completion.
• Assists team members in their growth by giving them opportunities in new technologies that are of interest to them.
• Generates reports to summarize the work/activity of the team and reports directly to Site Management on the contractor side and the Chief IT Officer/PMO Office on the government side.
• Performs the administrative functions of a team manager such as: approving time, managing PTO, performing employee evaluations, ensuring team members follow company policy, distributing pertinent corporate information, etc.
• Additionally, Mr. Confidential still serves as a developer on various applications that the team supports.
• He codes in various web/front-end (Java, JSP, JavaScript, .NET, HTML, CSS, Adobe, etc) and database technologies (SQL Server, Oracle, MS Access, etc)

Confidential

Senior Software Developer

Responsibilities:

• In addition to his current developer role of supporting the Confidential .NET applications as detailed above; Mr. Confidential currently designs, codes, implements, maintains and supports a Java/J2EE Oracle-based application integral to the processing of Confidential Data (formerly Confidential - Confidential ).
• He has converted the old application to one common code base (previously consisted of multiple versions of code running on multiple platforms), migrated it to WebLogic Server 11g (from Oracle Application Server) on an all Solaris platform running jdk 1.6.x (previously ran on a combination of Windows and Solaris machines), redesigned it to fit in the new Confidential architecture (both look/feel and functionality), and developed new portions of the system (including Bulk Upload which allows users to bulk upload and edit documents through the web as opposed to manually loading outside of the application.
• Additionally, the new parts of the Bulk Upload system also read emails on a nightly (or on demand) basis and automatically processes them and their attachments so that they are available for viewing, editing, and processing in the new portion of the system).
• The front end (display) of the application consists of HTML, cascading style sheets, Java server pages, Ajax, and JavaScript. The back end is Java/J2EE-based with Oracle 11g as the database. Mr. Confidential uses STRUTS as the framework to control the processing/flow of the application.
• The application currently runs on Oracle WebLogic Server 11g on a jdk 1.6.x Solaris platform.
• Mr. Confidential is also responsible for the installation, maintenance, and support of production WebLogic application servers to ensure the highest standards of availability, resilience, integrity, security and performance required by the business. He applies patches and other necessary updates (Oracle PSUs, JDK upgrades, etc) to the WebLogic Application Servers.
• Mr. Confidential also documents and develops "standards" for supporting the Confidential application, WebLogic Servers, and developer's software.
• He maintains Subversion code repository for all Confidential related code. Mr. Confidential mentors less experienced developer team members and cross-trains them.
• Finally, he serves as the team lead and as main POC for management for both the government and contractor.

Confidential

Vice President

Responsibilities:

• Mr. Confidential established numerous contacts with government agencies, commercial companies, and prime contractors.
• He researched approaches to market Confidential USA's services and vision.
• He also provided extensive direction and development on the content of the corporate website and other websites created for numerous clients.
• Mr. Confidential was responsible for providing business and technical development and support for internal and external functions.
• He was involved in requirements analysis and design, development, testing, implementation, and supporting of systems on web and mid-tier platforms.
• He was also responsible for management of existing resources for client projects, including the recruiting, interviewing, and placing of individuals on projects. Another of Mr. Confidential ’s primary roles included business development in general (bringing in new clients/projects/contracts and maintaining existing ones).
• As part of this process, he developed effort estimates, schedules, pricing, and proposals to acquire new projects/clients.
• Mr. Confidential interacted directly with clients on a regular basis providing status updates and acquiring feedback before, during, and after project.
• He worked on developing the company web site, developing client web sites, and establishing of internal databases and applications necessary for running the company.
• As one of the four founders of the company, he helped to develop the company from the ground up.
• His activities included establishing of business plan, organizational structure, books, company policies, infrastructure, recruiting, managing, marketing and other activities necessary to the creation and survival of the corporation. He also designed and developed company customer tracking system and campaign e-mail system.
• His systems included friendly UIs, relational database, automated email process, and reporting system (written using various SQL scripts/statements) for aiding with both potential new and existing business customers and contacts.

Confidential

Software Developer

Responsibilities:

• Mr. Confidential was responsible for the design, coding, implementation, and support of a Java/J2EE based application integral to the processing of online rollovers for RPS participants.
• His system consisted of an HTML, JSP, XML, CSS, and JavaScript web-based front-end and three separate back-end Java applications responsible for the receiving, processing, and re-routing of the online rollovers.
• These back-end applications were scheduled to run at various intervals on a daily basis through a mainframe scheduler (using Autosys), which in turn called UNIX-based shell scripts to execute the actual standalone Java programs. This project was a high-profile project (responsible for the rolling over of millions of dollars) and involved development and coordination between eight different systems and project teams.
• Mr. Confidential was also responsible for re-writing and creating new portions of a financial-based retirement system used for the managing of 401K and retirement data for clients by customer representatives.
• The re-written system was to be entirely a WebSphere web-based application using Java, JSP, HTML, Ajax, JavaScript, CSS, and a STRUTS configuration. STRUTS was used to divide complex applications into a series of basic components: Views, Action Classes, and Model components (MVC approach).
• STRUTS provided a common starting point and allowed Mr. Confidential to have five to ten developers (some from various teams and even new hires) work on various parts of the system with little to no learning curve involved. Ajax was heavily used in modules upon which Mr. Confidential worked to limit the amount of data that was returned and needed to be refreshed.
• The financial summary hub was in essence four screens in one (a main screen, with three tabs).
• Therefore, he used Ajax to bring back only the main screen and first tab on load, and then made subsequent Ajax calls as needed when the user selected other tabs to retrieve that tab-specific data.
• Subversion was also used to control source code prior to checking into the main version control PVCS.
• Subversion allowed all the developers to easily maintain the common code base and plug in independent modules with very little impact (if any) to other developers.
• Developers were easily able to obtain and check in the latest code through Subversion without overlaying or interfering with others’ code (as could happen with an ordinary version control system); and thus he was able to have five to ten developers simultaneously developing the system.
• Mr. Confidential wrote numerous PL/SQL scripts for business analysts to identify and set up test data.
• He also wrote numerous PL/SQL scripts to help identify production data and code issues and to aid in the maintenance (addition, updating, deletion) of production data. Additionally, he assisted in creating columns and new relational tables for projects where such functionality was needed (new status code based series, new services, etc).
• Mr. Confidential logged and tracked bugs using a custom-built Confidential Access-based bug-tracking system and a corporate-based system as well: PL assigned bugs to developers and developers updated status (review, design, development, in test, ready for UAT) and comments throughout the life cycle until ready for UAT, at which point a QA individual either passed (status of: ready for production) or failed (status of: failed UAT) the fix. A developer then changed the status to Fixed: In Production once fix was rolled out.

Confidential

Software Developer

Responsibilities:

• Mr. Confidential was responsible for the maintenance, enhancing, developing and supporting of a financial-based retirement system used primarily for the managing of 401K and retirement data for clients.
• The system was written across multiple platforms using various technologies and languages.
• The front end was a combination of Visual C++ 6.0 and JSPs.
• The middleware was written with a combination of C++, C, and Unix COBOL code residing on Entera servers; Java code residing on CORBA servers; and Java code using IBM WebSphere servers.
• The back end was primarily a DB2 database (relationally designed with PK, FK, RI, and indexes) which was accessed by creating and maintaining stored procedures and scripts typically in DB Visualizer; however, certain functions accessed a VSAM-based record keeping file (Omni) and an Oracle-based database as well (accessed and maintained through scripts and stored procedures using SQL Navigator and DB Visualizer).
• Mr. Confidential also assisted in creating the documentation, conversion strategy, and estimates for reengineering/rewriting the entire system into an entirely web-based (front-end) and Java WebSphere based (middleware) system.
• Additionally, he wrote a batch-based Java system utilizing shell scripting, Java, Autosys, and ETL (Informatica) technologies.
• The mainframe scheduler (using Autosys) called a UNIX-based shell script which started a standalone Java program.
• The Java program then tied into a WebSphere 5.x-based project for accessing and updating the account status of users in DB2 and a separate record keeper (using both new and existing java classes).
• These records were then picked up by multiple new ETL processes for insertion into Oracle tables. From here, these records were picked up by the new company e-mail shared service program (Strong Mail) to send out e-mails to customers.
• Mr. Confidential also assisted in creating columns and new relational tables for projects where such functionality was needed (new status code based series, new services, etc).
• He also wrote numerous PL/SQL scripts to help identify production data and code issues and to aid in the maintenance (addition, updating, deletion) of production data.
• He logged and tracked bugs using a custom-built Confidential Access-based bug-tracking system and a corporate-based system as well: PL assigned bugs to developers and developers updated status (review, design, development, in test, ready for UAT) and comments throughout the life cycle until ready for UAT, at which point a QA individual either passed (status of: ready for production) or failed (status of: failed UAT) the fix.
• A developer then changed the status to Fixed: In Production once fix was rolled out.

Confidential

Senior Systems Analyst

Responsibilities:

• Mr. Confidential gathered requirements, analyzed, developed, and supported ITOPS mid-tier and web-based applications.
• His roles included requirements gathering, development, and maintenance on a front-end Visual Basic-based ITOPS application, a front-end Crystal Reports-based ITOPS reports application, back-end C++-based ITOPS (EDI, fax, RF, and print manager), SQL server 7.0 and 2000, and Oracle 8i-based ITOPS database.
• The ITOPS systems were Tier 1 systems vital to the railroad terminals for the running of trains and management of equipment on those trains and at the terminals.
• Mr. Confidential was instrumental in developing and supporting web-based ITOPSWEB and Web Terminal Inventory Systems.
• ITOPSWEB is an internal intranet-based application whereas Web Terminal Inventory Systems is an external web system residing on Confidential ’s corporate website
• Both web-based systems were Java-based in which XML was used to control the background actions (including verification, screen flow, etc.); JSP, HTML, CSS, and JavaScript were used as the presentation layer; and Oracle tables and stored procedures/packages were used as the back-end database layer.
• ITOPSWEB was developed and maintained using Visual Age for Java and Web Terminal Inventory Systems was developed and maintained using WebSphere Studio Application Developer (WSAD).
• Mr. Confidential used MVC architecture and some STRUTS as the framework for developing the applications.
• He used SQL Navigator to develop, modify, and manage stored procedures, triggers, and data in the Oracle warehouse tables.
• He was also involved in designing the database for this new Oracle warehouse.
• Mr. Confidential created normalized tables and views using PK, FK, RI, and indexing. He heavily used the Software Development Life Cycle.
• He was also responsible for gathering and defining requirements, coding, testing, and assisting in implementation of projects.
• Requirements gathering and definition included meeting with end users to determine their needs, and the creation of business cases and functional and technical documents.
• Mr. Confidential wrote specifications for the systems in the documents and then coded and served as main technical lead for the development and implementation of the systems.
• He also served as the main technical contact for all ITOPS systems and as the primary on call support person.
• He served as the person responsible for training and mentoring new team members and as technical advisor for new ITOPS projects.
• Mr. Confidential was involved in the creation and maintenance of DTS packages to transmit data from local SQL Server sites to a central Oracle ODS, to load data to test databases, and to export, correct, and reload data into production databases.
• Additionally, he was involved in the creation of an RF system utilizing .NET technologies.
• Mr. Confidential coded a Gate Inspection piece for use on handheld TekLogic applications using Visual Studio.NET. This RF system allowed for a “paperless” work order system for the entrance/exiting of equipment to the terminal, the loading and unloading of trains, parking, and other yard functions.
• He created and maintained extensive stored procedures for the systems to access and update data. SQL Server stored procedures often housed detailed business logic and complex routines, using Confidential Visual Source Safe as the source control for managing the code of all the systems.
• Mr. Confidential developed various projects under the main ITOPS folder to house the code for each subsystem (EDI folder to house C++ EDI code, ITOPS VB to house front-end Visual Basic code, ITOPs web to house Java, HTML, JSP, etc. web-based code, etc.).
• He also wrote numerous SQL scripts to help identify production data and code issues and to aid in the maintenance (addition, updating, deletion) of production data.
• He logged and tracked bugs using a custom-built bug-tracking system: PL assigned bugs to developers and developers updated status (review, design, development, in test, ready for UAT) and comments throughout the life cycle until ready for UAT at which point a QA individual either passed (status of: ready for production) or failed (status of: failed UAT) fix.
• A developer then changed the status to Fixed: In Production once a fix was rolled out.

Confidential

Systems Analyst

Responsibilities:

• Mr. Confidential gathered requirements, analyzed, developed, and supported ITOPS mid-tier applications.
• His roles included requirements gathering, development, and maintenance on a front-end Visual Basic-based ITOPS application, back-end C++-based ITOPS (EDI, fax, RF, and print manager), SQL server 7.0-based ITOPS database.
• The ITOPS systems were Tier 1 systems vital to the railroad terminals for the running of trains and management of equipment on those trains.
• Mr. Confidential was involved in the planning and development of web-based ITOPS applications using MVC architecture.
• The planning included meeting with end users to determine their needs, and the creation of business and planning documents.
• Java and XML were used to control the background actions (including verification, screen flow, etc.); JSP, HTML, and JavaScript were used as the presentation layer; and Oracle tables and stored procedures/packages were used as the back-end database layer in the development of the web-based ITOPS applications.
• One web-based ITOPS application (ITOPSWEB) was prototyped and developed in Visual Age for Java and the other web-based ITOPS application (Web Terminal Inventory Systems) was prototyped and developed in WebSphere Studio Application Developer.
• Mr. Confidential ’s contributions were vital in the rewriting of the terminal-based ITOPS system from Visual Basic 3 to Visual Basic 6.
• He assumed the main technical contact role for ITOPS in 2002.
• He also created and maintained extensive stored procedures for the systems to access and update data.
• SQL Server stored procedures often housed detailed business logic and complex routines.
• He used Confidential Visual Source Safe as the source control for managing the code of all the systems.
• Mr. Confidential developed various projects under the main ITOPS folder to house the code for each subsystem (EDI folder to house C++ EDI code, ITOPS VB to house front-end Visual Basic code, etc.).
• He also wrote numerous SQL scripts to help identify production data and code issues and to aid in the maintenance (addition, updating, deletion) of production data.
• He logged and tracked bugs using a custom-built bug-tracking system: PL assigned bugs to developers and developers updated status (review, design, development, in test, ready for UAT) and comments throughout the life cycle until ready for UAT at which point a QA individual either passed (status of: ready for production) or failed (status of: failed UAT) fix.
• A developer then changed the status to Fixed: In Production once a fix was rolled out.