Developer Resume
UsA
Objective:
Seeking a challenging position where my analytical and problem solving skills can be put in for the successful execution of the organisations projects.
Summary:
- Having 3+ years of experience, involved in all stages of Software development life cycle with extensive experience in e-business development with J2EE.
- Worked extensively in Core Java & J2EE Technologies.
Education:
- M.B.A from Confidential
- B.Sc Computer Science from Confidential
Professional Experience:
- Currently Employed With Confidential, Bangalore from Sep’ 07 to till date.
- Work Experience in Servlets, JSP, JDBC, Struts Framework.
Technical skills:
Operating Systems : Windows.
Languages : Java, J2EE (JDBC, Servlets, JSP)
Frameworks : Struts, Springs and Hibernate Frameworks
Tools : ILOG Jrules 5.0.3, ILOG JRules 6.x and 7.x, Weblogic WorkShop.
RDBMS : Oracle.
Servers : Tomcat, WebLogic and WebSphere.
IDE Tools : Eclipse.
PROJECT EXPERIENCE
Project #1
Project Name : Confidential
Client : Confidential, USA.
Duration : Oct’ 10 to till date.
Environment : Core Java, J2EE, JMS, GWT, JAXB, Struts, Hibernate,
Springs Oracle, Websphere and Windows.
Description:
The Clarity Upload Tool provides real-time validation and a batch processing infrastructure, primarily in support of the 2011 planning cycle. Authorized users may submit input data (Excel files) for upload into Clarity and subsequently PAR. Prior to processing, the files submitted will be pre-validated and validated against Clarity and PAR business rules, and the user will be notified of the status of the validation on the same screen. Upon errors, a brief description of the error will be displayed and detailed error messages pertaining to the data submitted will be available to the user.Upon validation success, the data will be eligible for submission for batch processing.Once submitted, the batch upload will be placed in a queue of other Clarity Upload Tool submissions. The status of the job shall be traceable via a link that is emailed to the user. Time to process the job will be driven by a number of factors, including but not limited to, the type of the data submitted, the size of the job and any previously submitted pending jobs
Roles:
Involving in Development and Enhancements.
Involving in Clarity Configurations as well as Back end uploads.
Working on Proposal Preparations and Development of POC (proof of concept) across the TCS for ILOG Based Projects.
Participating the Client calls to give demo on the POC and ILOG.
Project #2
Project Name : Confidential
Client : Confidential, USA.
Duration : Nov’ 09 to Sep’ 10.
Environment : Core Java, J2EE, ALBPM (Fuego), Weblogic Portals,
Weblogic Workshop, Weblogic, Oracle and Windows.
Description:
The Market Risk Business Process Monitoring (BPM) capability will process LoB Supply data and associated Market and Reference data on a daily (Mon-Fri) basis. Once a supply has landed it will be processed straight through to report generation assuming all dependencies have been met. The daily process will be as follows:
- Position supplies will be supplied by the PPB and loaded by DAC into the ODS, using the most recent official instance of Reference Data
- After they are loaded into the ODS, PPB supplies will be consumed for P/L vector calculation once the associated Market Data has also arrived and been processed (Composite context is available).
a. For each supply, the most recent supply instance received for the COB date being processed will be used unless it has not arrived or is otherwise unfit for use. Rollback and substitution processes will be available for MR Operations to utilize the best alternative.
b. The "latest" official Reference Data context will be used unless otherwise requested by MR Operations to use the "latest" available context.
c. If Market Data needed to consume a supply is not yet available, processing will be held until that data arrives, subject to a cutoff time. - Immediately upon completion of the P/L vector a VaR is calculated.
a. The "latest" official Reference Data context or the "latest" available context will be used.
b. Some VaR calculations require two or more P/L vectors to have been processed, thus in such cases processing will be held up until all dependencies have been met, subject to cutoff time.
Roles:
Involving in CRI Console UI Scheduler Screens Enhancements
Involved in MRI Console UI Screens Enhancements
Involved in MRI BPM for PFC Development using ALBPM.
Project #3
Project Name : Confidential
Client : Confidential, USA.
Duration : Sep’ 09 to Oct’ 09.
Environment : HTML, DHTML, Java Script, Core Java, Servlets,
JSP, ILOG 6.6.3, Webservices, Weblogic and Windows.
Description:
JPMC has DRI Application which is developed in c language, now they started Reengineering of the DRI Application by using Java API’s with Rule Engine (ILOG). During this process, First Iteration they declared as a POC (Proof of Concept), in this Project having modules like
- Foreclosure
- Loss Mitigation
- Mitigation
- Claims etc.,
For Iteration-I scope is Foreclosure Module, foreclosure is a process which starts if any loan is pending, even though show causes are sending to the corresponding customer, after crossing the limited time, then that loan hits the foreclosure process.
Roles:
- Involved in Development of Mockups using HTML, Java Script and DHTML.
- Involved in Development of Field Level Information for all Setup Modules.
Project #4
Project Name : Confidential
Client : Confidential, USA.
Duration : Feb’ 08 to Aug’ 09.
Environment : Core Java, ILOG JRules 6.5.2, ILOG JRules 5.0.5,
Weblogic 8.1, Weblogic 9.2 and Windows XP.
Description:
JPMC IB Tech C-Clear group as part of its application server upgrade from Weblogic 8.1 to Weblogic 9.2 is planning to upgrade its Business Rules Engine ILOG Jrules 5.5 to ILOG Jrules 6.5. The ILOG Jrules 6.5 will be running on Weblogic 9.2 infrastructure. TCS understands that the application RBRM uses the ILOG rules engine for its business rules integration. As part of this migration initiative, JPMC would also like to have an automated regression test pack created which would enable faster and extensive testing of the migrated rule engine through the RBRM rule engine.
Roles:
- Involved in Migration of 900 Rule Project.
- Involved in SIT, Regression Testing, UAT and Production.
- Involved in Development of 225 Rules Development.
- Involved in Environment setups for deploying the Rule Apps in Weblogic 8.1 and Weblogic 9.2 server.
- Responsible for Deployment of Rule set in Rule Team Server and Rule Execution Server (RES and RTS).
Project #5
Project Name : IB Rates Market Data System.
Client : Confidential, USA.
Duration : Sep’ 07 to Jan’ 08.
Environment : Core Java, Springs, Struts, Oracle, Websphere and Windows.
Description:
Confidential is a leader in wholesale financial services, serving one of the largest client franchises in the world. Our clients include corporations, institutional investors, hedge funds, governments and affluent individuals in more than 100 countries. Clients turn to JPMorgan for its complete platform of financial services combined with seamless execution.
The Global Rates Strategy (GRS) is designed to enhance the current JPMC technology platforms and streamline the operational process for the Global Interest Rates Derivatives (GIRD) business. The aim of this project is to analyze and build a new market data application which would serve as a dependable source, for End of The Day (EOD) Market Data snapshots, create a central repository to create and manage curve definitions, automate the current fragmented manual spread sheet based End of The Day data capture modes apart from deploying a well defined sign off process.
The Scope of this market data is North America and remaining regions for all major currencies.
Roles:
- Involved in Development of Curve Definition Module.
- Involved in Development of Springs with Struts Integration.