EXECUTIVE SUMMARY:

• Highly motivated, customer focused and career - oriented with about 11 years of professional experience.
• Extensive experience in architecture and software development of several different product areas such as billing, contracts, transaction processing systems and provisioning systems.
• Expertise in co-ordination between teams working in different geographical areas.
• Worked on architecture and development of state of the art server framework which forms the core transactional and data processing servers for the complex Confidential network infrastructure.
• Proficiency in Gathering Requirements, Functional Specifications, System Design, Prototypes, Development, Tuning, Testing, Release and Hand Off.

PROFESSIONAL SKILLS:

• Java (JSSE, JavaBeans, Applets), C/C++, Perl/CGI, XML, ASP, JavaScript, HTML, SQL, PL/SQL, UNIX Shell Scripting, Awk, Pascal
• JBoss, Tomcat, Apache, JServ, Jrun, JDBC, JNDI, JavaMail, Servlets, JSP, JSF, EJB3, Hibernate, JProbe, UML
• Oracle 9i, PL/SQL
• Perforce, RCS, CVS

PROFESSIONAL EXPERIENCE:

Confidential

Responsibilities:

• Services layer protected by RBAC for authorization.
• Hibernate layer extended to support iPass-specific requirements.

Technologies involved: Java, JDBC, PL/SQL, Hibernate3.0, JBOSS app server

Confidential

Responsibilities:

• Validates the files sent by the provider based on the specification.
• Performs duplicate detection to eliminate billing for transactions already billed.
• Allows for reverse/reprocess of transactions.
• Does daily aggregation of transactions, and generates the monthly Call Detail Records (CDRs) for customers.

Technologies involved: Java, JDBC, PL/SQL

Confidential

Responsibilities:

• Created a Confidential Web UI in Contracts system to define new products/bundles/services.
• Provided an infrastructure to do the following:
• Ability to specify list of applicable fee types for a product/bundle.
• Ability to set & customize revenue percentages for components within a bundle.
• Provided facility in Contracts system to allow customers order a product/bundle/service from the Confidential .
• Migrated data from the existing templates to the new database schema.

Technologies involved: Java, Struts, JSPs, Spring, Hibernate, JDBC, PL/SQL

Confidential

Responsibilities:

• Users can search for specific Combined Commit groups.
• Users can create new groups, edit existing groups, nested groups are also allowed.
• Several business rules were implemented that took care of the business constraints.

Technologies involved: Java, Struts, JSPs, Spring, Hibernate, JDBC, PL/SQL

Confidential

Responsibilities:

• The application was extended to allow Confidential customers and employees to track, manage, activate and deactivate cards for other network providers: Sprint, T-Mobile UK etc.
• Capability to store order information on the Portal system as opposed to being handled by email.
• Capability to store initial SIM and Card inventory.

Technologies involved: Oracle App Server 10.1.2, Oracle Portal, Java, JSPs, PL/SQL

Confidential

Responsibilities:

• Support for external interface plug-in modules: Today these include RADIUS, TACACS+, LDAP, UNIX Password, NT Domains, HTTPS and a database interface module. These modules are loaded based on configuration parameters and can be tailored to each particular server’s needs.
• Business Logic plug-in (control objects): Today these include routing, authentication, authorization, accounting, summarization, data processing logic (SQM), service definition logic for billing relationship decomposition (Clearinghouse) and connection policy. Again, these are configurable based on the business logic needs of a given server. This gives Confidential the ability to easily create new business logic plug-in.
• Database abstraction layer (entity objects). The DB abstraction layer provides caching, reporting, object mapping, and DB connection management.

Confidential

Responsibilities:

• The Confidential can receive RADIUS requests from either from the ISP’s Confidential servers (via RADIUS proxy mode) or directly from the ISP’s NAS or (WiFi) Gateway or (WiFi) Access Points.
• Confidential supports all RADIUS attributes defined in the RFCs 2865 and 2866.
• Since Provider’s Confidential servers may have very short timeouts, and RADIUS is a UDP based protocol, Confidential supports write-thru caching of authentication requests.
• Confidential uses a fail-over logic to maximize the likelihood of reaching an Confidential server successfully.
• Confidential supports automatic and manual software and configuration updates.

Confidential

Responsibilities:

• Confidential accepts both control and data messages on port configured port. All messages sent to this port are required to use SSL over TCP/IP.
• The client is required to present a valid Confidential signed certificate for authentication. In addition to the SSL server and client validation, the Confidential performs some additional checks to ensure validity of the client.
• Confidential catches all database tables used for lookup in memory. The cache is created when the Confidential starts up, and is kept in sync with the database subsequently. Triggers on these lookup tables in the database send messages to the cache component of the Confidential whenever the underlying data changes.
• It resolves the customer, verifies policy, transforms the packet and forwards the auth/acct packet to customers’ site.
• It stores accounting and statistical information in a database that is later collected by the Settlement System for customer billing and tracking of network statistics.

Confidential

Responsibilities:

• Confidential accepts both control and data messages on configured port. All messages sent to this port are required to use SSL over TCP/IP. The client is required to present a valid Confidential signed certificate for authentication.
• Confidential validates the request, verifies policy, checks for duplicates, and forwards the request to the Confidential servers in the order configured.
• Confidential supports many protocols like Radius authentication and accounting, windows authentication, LDAP.

Technologies involved: Java, SSL, JDBC, PL/SQL

Confidential

Responsibilities:

• Providers post their configuration files at frequent intervals, which can be viewed in the UI.
• The status of the providers server can be viewed in the status trace, which has the number of authentication/accounting/ping records received, and the success ratio of established connections.
• A new version of the server code and a new list of Confidential server ip-addresses can also be deployed to the remote server by using the Confidential UI.
• The remote servers version, and the logs recorded when the server downloads new software version, or a new Confidential server list can be viewed in the UI.

Technologies involved: Java, JSP, Javascript, JDBC, PL/SQL

Confidential

Responsibilities:

• The Confidential Clearinghouse performs real time retrieval of the accounting records from each of Transaction Centers.
• The accounting records are filtered, the records are resolved to a network provider and customer.
• The cost of goods and billable services are then calculated and Call Detail Records (CDRs) are generated for the customers and providers.
• Reverse and reprocess of transactions is submitted by the users through a Swing-based GUI, and are processed by the server.

Technologies involved: Java, JDBC, PL/SQL, Swing

Confidential, San Jose, CA

Responsibilities:

• It shows real-time inventory, does online credit card checking/approvals, incorporates shipping addresses and processes returns. Data is uploaded from the warehouse (Pacific data link), and read into Oracle database. Customer service personnel use this software to keep track of orders, inventory levels and customers.
• This is an application written in Java as the front-end and Oracle DBMS as the back-end. It has a 3-tier architecture with the middle-tier consisting of the RMI (Remote Method Invocation) server which constitutes the business logic.
• Developed a prototype for the order-entry and customer search screens using Oracle Forms 4.5.
• Wrote Database procedures to reduce the processing on the client.
• Ingres gateway to Oracle was used to integrate with the existing system.
• Used Servlets to generate reports for users.

Confidential

Responsibilities:

• Developed JAVA screens for the users to do assembly planning against Confidential suggestions, maintain assembly capacities, and lead times. These Java screens use a multi-threaded server which acts like a middle-tier that accepts the queries from clients and fetches the results from Ingres database.
• Set up data transfer mechanism between Ingres and Confidential database.
• Set up consolidated tables, views and crontabs for the tool to access Ingres.
• Wrote scripts (Perl) to check data transfer completion.

Confidential

Responsibilities:

• Worked with a group of consultants from TRW in preparing the SRS document.
• Played a key role in the team in making decisions about the desired enhancements in the new system.
• Available To Promise (ATP) .
• Built the interfaces between the Order entry system and Confidential for ATP.
• The software performs validations and checks the business rules of the suggested OS dates and writes it to the Order entry system.
• It allows the orders to be split and also keeps track of the history.