- At Prolifics, we are currently implementing multiple solutions in Software
- Development, and we are looking to hire a talented Senior MuleSoft Developer for our development center
- in India. This position would be based out of Hyderabad and is a permanent
- position.
- If you are looking for a high growth company with rock-solid stability,
- if you thrive in the energetic atmosphere of high-profile projects, we want to
- talk to you today! Let’s connect and explore the possibilities of having you
- onboard the Prolifics team!
- ·Job Title: Senior MuleSoft Developer
·Primary
- skills: MuleSoft Anypoint Platform, CloudHub and Runtime Fabric
- ·Secondary skills: Monitor MuleSoft APIs, applications, runtimes, workers, queues, schedulers and integration interfaces.
- ·Location: Hyderabad
(Mindspace#12B)
·Educational
Qualification: B.Tech/BE/M.Tech/MCA/M.Sc
·Experience: 4 to 5 yrs
Job Description
- The Junior MuleSoft Support Engineer will provide production
- and non-production operational support for MuleSoft APIs and integrations used
- by PG&E. The engineer will monitor platform and application health, and respond to alerts, manage incidents, service requests, changes and problem records,
- perform initial diagnosis and remediation, and escalate complex issues to
- senior MuleSoft engineers, infrastructure teams or product vendors.
- The role supports Development, Test, QA and Production
- environments across MuleSoft Runtime Fabric and CloudHub. Responsibilities
- include daily administration, configuration maintenance, release and deployment.
- Support, and monitoring for availability, performance and failures.
- Key Responsibilities
- 2.1 Monitoring and Event Management
- ·Monitor MuleSoft APIs, applications, runtimes,
- workers, queues, schedulers and integration interfaces.
- ·Review alerts and dashboards for availability,
- transaction failures, performance degradation, connectivity issues and resource
- utilization.
- ·Use Anypoint Monitoring, Runtime Manager,
- Splunk, ELK and PagerDuty to identify and respond to events.
- ·Validate alerts, assess customer impact, and
- create or update the appropriate incident record.
- ·Monitor failed transactions, retries,
- dead-letter queues, API response times, CPU, memory and runtime availability.
- ·Perform scheduled health checks and record
- outcomes in shift handover reports.
- ·Escalate critical alerts, service outages and
- potential security events using the agreed escalation matrix.
2.2 Incident Management
- ·Accept, acknowledge, categorize and prioritize
- incidents assigned to the MuleSoft support queue.
- ·Confirm the affected API or application,
- environment, business impact, urgency and assignment group.
- ·Perform initial diagnosis using application
- logs, correlation IDs, error messages, monitoring data and deployment history.
- ·Troubleshoot common issues including API
- unavailability, HTTP 4xx/5xx errors, DataWeave failures, message-processing
- errors, queue backlogs, scheduler failures, SFTP/HTTPS connectivity issues,
- certificate problems and downstream system failures.
- ·Apply approved runbooks, known-error procedures
- and documented workarounds.
- ·Reprocess transactions or restart applications
- only when authorized by an approved procedure.
- ·Maintain accurate, time-stamped ticket updates
- and escalate unresolved or high-priority incidents within SLA.
- ·Participate in major-incident bridges, provide
- factual updates, confirm restoration and obtain validation before closure.
2.3 Service Request Management
- ·Review and fulfill standard MuleSoft service
- requests according to approved procedures.
- ·Support access requests, log retrieval,
- non-production deployments, API status checks, restart or reprocessing
- requests, certificate validation and operational reporting.
- ·Verify approvals and required implementation
- information before fulfillment.
- ·Coordinate dependencies with application,
- security, network, database, cloud and business teams.
- ·Record fulfillment evidence and obtain requester
- confirmation before closure.
- ·Reclassify requests that are more appropriately
- managed as incidents, changes or enhancements.
- 2.4 Change and Deployment Support
- ·Assist with standard, normal, expedited and
- emergency changes affecting MuleSoft applications and environments.
- ·Confirm that change records include
- justification, scope, impact, risk, implementation steps, validation, rollback
- plan, window and approvals.
- ·Perform assigned pre-change checks,
- implementation activities and post-change validation under supervision.
- ·Verify runtime status, API connectivity, queues,
- schedulers, credentials and transaction flow after implementation.
- ·Attach logs, screenshots, test results and
- validation evidence to the change record.
- ·Escalate failed changes promptly and support
- rollback activities.
- ·Update related incidents, problems and
- configuration records after implementation.
2.5 Problem Management
- ·Identify recurring incidents and raise them with
- the MuleSoft Support Lead.
- ·Assist in creating and maintaining problem
- records and linking related incidents and changes.
- ·Gather logs, timelines, error samples,
- monitoring evidence, deployment history and affected transaction details.
- ·Contribute to root-cause analysis using the 5
- Whys technique.
- ·Document root cause, contributing factors,
- business impact, workaround, corrective action, preventive action, owner and
- target date.
- ·Track corrective and preventive actions to
- completion and convert repeat resolutions into knowledge articles or runbooks.
- 2.6 Ticket and SLA Management
- ·Continuously monitor the assigned queue and
- acknowledge tickets within contractual response targets.
- ·Maintain ownership until resolution,
- reassignment or formal handover.
- ·Ensure every ticket states categorization,
- priority, impact, investigation, evidence, next action, owner and expected
- update time.
- ·Follow up proactively on customer, vendor and
- cross-team dependencies.
- ·Escalate tickets at risk of SLA breach.
- ·Do not leave tickets on hold without a
- documented dependency owner, reason and next-action date.
- ·Support reporting on volume, ageing, SLA
- compliance, reopened tickets and recurring issues.
- 2.7 Shift Operations and Handover
- ·Work within a rotational-shift model supporting
- required US business hours and 24x7 coverage.
- ·Complete operational health checks at the
- beginning and end of each shift.
- ·Prepare a structured handover covering open
- incidents, SLA risks, production alerts, failed transactions, planned changes,
- monitoring observations and follow-up actions.
- ·Attend shift-handover and operational review
- calls.
- ·Remain reachable through agreed on-call and
- escalation channels during assigned coverage.
- 2.8 Documentation and Reporting
- ·Maintain standard operating procedures,
- runbooks, known-error records and support knowledge articles.
- ·Update application inventory and support
- contacts when changes are identified.
- ·Record incident details, resolution steps and
- lessons learned in a reusable form.
- ·Contribute to weekly and monthly reporting
- covering ticket volumes, priorities, SLA performance, ageing, recurring
- problems, change outcomes, alerts, availability and effort.
- ·Store documentation only in approved PG&E
- and Prolifics repositories.
- Required Technical Skills
Job description provided by Prolifics.
View the original posting