SUMMARY

• Experienced in designing and developing J2EE web applications in Business Intelligence, E - Commerce, Multimedia and Billing/Subscription Management.
• Experienced in designing and developing SOAP and REST web services.
• Experienced in Agile, Waterfall and Test Driven Development methodologies.
• Experienced in working with various testing platforms and code profiling toolkits, e.g., JUnit, Selenium, JMeter, Klocwork and YourKit.
• Experienced in UML modeling and UML modeling tools, e.g., Microsoft Visio and Enterprise Architect.
• Experienced in working with various version control systems such as CVS, SVN, Gradle and Git.
• Experienced in all phases of SDLC.
• Outstanding presentation, communication, analytical, and problem-solving skills.

TECHNICAL SKILLS

Programming Languages: Java (expert).

Web Technologies: HTML/HTML5, CSS, JavaScript, JQuery, Ajax, AngularJS, React.

Web Services Technologies: Axis, CXF, JAX-WS, JAX-RS.

Databases: Oracle, MongoDB.

Operating Systems: Windows, UNIX, Linux.

PROFESSIONAL EXPERIENCE

Confidential, New York, NY

Senior Java Developer

Responsibilities:

• Meet with project stakeholders as well as business analysts during the inception phase in order to gather and determine the high-level functional requirements (FRs) and consequently create the artifacts that describe the business-oriented vision of the system/project such as use case diagrams, use case scenarios and use case description for both the functional requirements (FRs) as well as non-functional requirements (NFRs).
• Analyze, refine, and model the requirements as well as the existing business processes during the requirements analysis phase. The activities performed include determining the detailed behavior of each use case, analyzing the use case scenarios to discover more detail, the creation of activity diagrams - if needed - in order to provide a visual view of the flow of events and augment and verify the textual use case forms, identifying the key abstractions that exist in the current increment of the problem domain, representing the relationships of the key abstractions in a domain model and creating the business domain class diagram.
• Model the high-level system structure to satisfy the non-functional requirements (NFRs) during the elaboration phase. The activities performed include selecting the architecture type - e.g. standalone, client/server, App-centric n-tier, Web-centric n-tier, or Enterprise n-tier -- that best satisfies the high-level constraints and non-functional requirements (NFRs), producing the list of known risks, an assessment of the risks, and the mitigation plans intended to address the risks, creating a detailed deployment diagram for the architecturally significant use cases, creating and testing the architecture baseline by implementing the architecturally significant use cases in an evolutionary prototype and documenting the technology choices in a Tiers and Layers diagram.
• Use the functional requirements (FRs) as well as other business solution documents to provide senior management with an the estimated Level of Effort (LOE) for the project on hand, thus allowing project managers to plan projects accordingly, meet milestones deadlines, as well as staying within the allocated budget for each project.
• Model how the system will support the use cases during the construction phase. The activities performed include creating a design model for a use case using interaction (or Robustness analysis) diagrams, identifying and modelling of objects with non-trivial states using a state machine diagram, applying design patterns to the design model, creating the solution model by merging the design and architecture models, and finally, refining the domain model to satisfy the solution model.
• Meet with the development team assigned to each project and review the detailed design, and if needed, mentor other team members in the proper use of the technologies that have been chosen to implement a solution and then answer any questions that may arise.
• Review all code submissions by developers to ensure adherence to technical design and coding best practices, application of business rules, as well as PII (Personally Identifiable Information) compliance.
• Coordinate with project managers, QA, and UAT teams to support release builds and prepare released notes.
• Lead the design and development efforts - during Sirius/XM merger - to seamlessly integrate Sirius and XM platforms into a single platform, thus eliminating the overhead resulting from maintaining multiple, incompatible databases, improving performance and maximizing subscribers' overall experience.
• Designed and developed Sirius XM Customer Care site (rewrite). The entire site was migrated from a .Net platform into an enterprise-level, scalable J2EE environment. The new site is currently being used by 2000+ Customer Care representatives and processes 700,000 to 1,500,000 requests monthly
• Designed and developed Self Care site (rewrite). The new site replaced the Struts2 MVC framework with responsive pages, thus providing Sirius XM subscribers with a rich and robust functional experience.
• Designed a Disaster Recovery site for Sirius XM Customer Care. Disaster Recovery site is an alternate Customer Care site, temporarily replaces the main site during outages. Disaster Recovery was designed as a light-weight tool with only a subset of the functionality and services provided by Sirius XM Customer Care’s main site, such as creating accounts, adding receivers and/or sending provision signals.
• Designed and developed a web services suite that allows supply chain, partners and 3RD party vendors to interface with Sirius XM’s Subscriber Management Systems (SMS), and consequently enable service consumers to – among other facilities – create accounts, add subscriptions, cancel services and quote plans.