Cloud Architect Resume
4.00/5 (Submit Your Rating)
SUMMARY
- 10+ years of professional experience in the IT industry with designing and developing Enterprise Integration Applications and Java/J2EE based applications.
- Almost 5+ years of Java development experience in backend implementation and front end design.
- Around 4+ years of experience as MuleSoft Developer working on complex integrations using MuleSoft Platform.
- MuleSoft certified API Designer and MuleSoft certified Integration and API developer
- Responsible to Architect/develop/deploy/configure RESTful/SOAP web services in Mule ESB based on API - led connectivity both on-prem and cloudhub.
- Successfully handled all assignments with a sense of responsibility and commitment. Client-centered, self-motivated and able to work both independently and within a team environment effectively.
TECHNICAL SKILLS
- MuleSoft Enterprise Runtime 4.2/3.9/3.8
- Anypoint Platform, Design Center, Runtime Manager, CloudHub, API Manager, Exchange,
- RAML 1.0
- Java,
- JavaScript,
- SQL
- Oracle, MySQL
- Mulesoft Anypoint Studio
- Jenkins, Nexus
- Maven 3
- JIRA
- Munit
PROFESSIONAL EXPERIENCE
Confidential
Cloud Architect
Responsibilities:
- Guided teams across enterprises to evolve and implement C4E (center for enablement) as per guidelines from Mulesoft for better management of applications and services.
- Educate leaders and stakeholders on how API-led connectivity creates value for the organization by building a discoverable, self-serviceable and reusable application network .
- Understand the integration requirements from various Stakeholders and shape the requirement by producing implementation road map including Architecture Blueprint Document - Reference Architecture, Network Architecture, Security Architecture, HLD/LLD etc.
- Build and guide a delivery team with necessary skills to deliver the integration solution
- Design/build the reusable framework to enable enterprise-wide integration standard.
- Build delivery road-map and help with the sprint planning exercise for B2B and enterprise applications
Confidential
Mulesoft Architect/lead
Responsibilities:
- Playing a major role in establishing Mulesoft best practice and guidance in designing/delivering reusable assets for Confidential .
- Design/Build Reusable framework and accelerators to be used across projects and best practices frameworks/capability models that will control costs, provide higher quality & business value, and/or increase predictability of service delivery.
- Develop Implementation road map including Architecture Blueprint Document - Reference Architecture, Network Architecture, Security Architecture.
- Implement roadmap for development process - Functional Requirement doc, High level design doc, Technical design doc for each API
- Low level requirement analysis and implementing API contact based on requirement analysis
- Maintaining API version
- Architect OnPrem & Cloud Solutions using MuleSoft
- Build delivery road-map and help with the sprint planning exercise for B2B and enterprise applications
Confidential
Mule ESB lead/Sr. Developer
Responsibilities:
- Understand the requirements by going through a discovery process where I interviewed different stakeholders including Head of Dept / Business Units / SMEs
- Understanding the requirements from the client, creating the HLD and LLD, implementing and releasing to UAT and Production.
- Worked with the team to setup and put the guidelines document - will be used for further development.
- Evangelized API Led connectivity and helped the business unit understand API Development Life cycle.
- Evangelized design first approach using Design Center (RAML), building the API’s, managing them through API Manager and eventually reusability, discoverability, self-serviceability of the APIs.
- Built 20+ APIs end to end from RAML specification, implementation to deployment to higher environment.
- Used Design Center to build the RAMLs
- Used API Manager to manage the APIs. Wrote custom security policies using Mule-PingFederate OAuth 2.0 policy.
- Apply the policies and did Rate-limiting on the API’s in API Manager.
- Implemented high security starting from RAML design to APIs to flow level.
- Designed and implemented custom security in flow levels.
- Wrote various Java modules and custom reusable modules like email, auditing etc
- Did thread management in Mule flows for optimum performance tuning
Confidential
Mule ESB Developer
Responsibilities:
- Work on Sprint activities to break down the work to different tasks.
- Worked with the offshore team to setup their processes.
- Developed Mule flows.
- Implemented exception strategies in Mule ESB flows.
- Performed Database batch operations using Mule ESB.
- Implemented complex DataWeave transformations.
- Integrated with third-party systems Salesforce..
- Maintained different versions of the code base using repository and change tracking tools like bitbucket, git.
- Developed MUnits.
- Use Runtime Manager to deploy applications into servers.
Confidential
Mule ESB Developer
Responsibilities:
- Built frameworks - Logging & Exception handling frameworks
- Interact with Salesforce team and identifying API’s to migrate into Mulesoft platform.
- Testing backend services and preparing postman test scripts
- Developing unit test cases for the developed applications.
- Used mainly Postman to test the Web services.
- Testing end to end Integration/handshaking between other interfaces.
- Coordinated with onshore and offshore team members for easy integration of the messages and alignment to timelines for delivery
Confidential
JAVA/J2EE/MuleSoft Developer
Responsibilities:
- Designed and Developed SOA based integration solutions for client’s various business requirements using IBM ESB.
- Integrated different modules using Mule ESB connectors.
- Worked on Mule - ESB Java Component to implement the business logic.
- Implemented different EAI pattern like scatter-gather, Splitter, Service Proxy, Service Gateway.
- Deep diagnosed and resolved high complexity issues.
- Worked on preparation of different standards and patterns which can be followed by other project teams in client IT landscape.