ORACLE BRM ARCHITECT / LEAD DEVELOPER (Support)

ORACLE BRM ARCHITECT / LEAD DEVELOPER (Support)

Must have's:
1. Technical expertise in Oracle Billing and Revenue Management (BRM)
2. Problem solving and troubleshooting skills
3. Communication and Collaboration

Team player - collaborate with offshore team in India to ensure 24X7 support.

Oracle BRM (Billing and Revenue Management) 24x7 Architect / Lead Developer responsibilities:

1. System Architecture and Design: Lead the design and architecture of the Oracle BRM system, ensuring it meets business requirements and industry standards.
2. Development Leadership: Oversee the development team, providing technical guidance and ensuring best practices are followed in coding, testing, and deployment.
3. Customization and Configuration: Develop and customize BRM modules to meet specific business needs, including creating configuration scripts and custom workflows.
4. Performance Optimization: Continuously monitor and optimize system performance to ensure high availability and reliability.
5. Strategic Planning: Participate in strategic planning and decision-making processes to align BRM initiatives with business goals.
6. Training and Mentorship: Provide training and mentorship to junior developers and support engineers, fostering a culture of continuous learning and improvement.
7. Round-the-Clock Monitoring: Continuously monitor the BRM system to detect and address issues promptly, ensuring minimal downtime.
8. Incident Management: Respond to and resolve incidents and service requests within agreed service levels, providing timely updates to stakeholders.
9. System Maintenance: Perform regular maintenance tasks such as patching, upgrades, and performance tuning to keep the system running smoothly.
10. Troubleshooting and Problem Resolution: Diagnose and resolve technical issues, working closely with other IT teams and vendors as needed.
11. Data Integrity and Security: Ensure the integrity and security of customer data, implementing necessary measures to protect against data breaches and loss.
12. Documentation: Maintain detailed documentation of incidents, resolutions, system configurations, and procedures to ensure knowledge sharing and continuity.