Mphasis

✓ PROS

The project structure helps employees understand governance, audits, and documentation discipline.

✕ CONS

Hikes may not feel competitive for employees who already have specialized skills.

✓ PROS

Some teams maintain a healthy schedule during non-release periods.

✕ CONS

Role clarity may become weak when one person handles support, testing, and coordination together.

✓ PROS

Employees can gain experience in multiple tools used for ITSM and managed services.

✕ CONS

Manual reporting expectations can consume time during governance cycles.

✓ PROS

The support ecosystem is useful for learning incident prioritization and root-cause analysis.

✕ CONS

The employee experience can vary sharply between accounts and business units.

✓ PROS

Client environments are large enough to understand real enterprise release processes.

✕ CONS

Learning paths exist, but project workload may not always allow consistent upskilling.

✓ PROS

The organization provides decent job stability for employees assigned to long-term accounts.

✕ CONS

Some managers focus more on utilization than long-term skill development.

✓ PROS

Good exposure to Salesforce implementation lifecycle from discovery workshops to configuration, testing, deployment, and hypercare. Client interaction helped improve consulting and communication skills.

✕ CONS

Project pressure increased near go-live when data migration, integrations, and user training happened together.

✓ PROS

Worked directly with sales and service teams to convert business requirements into Salesforce user stories. The best part was understanding real CRM problems before designing the solution.

✕ CONS

Stakeholders sometimes gave incomplete requirements, which caused rework during sprint demos and UAT.

✓ PROS

Good hands-on exposure to Salesforce admin work including user setup, permission sets, flows, reports, dashboards, page layouts, and approval processes. It is a good role to understand CRM from the business side.

✕ CONS

Admin work can become repetitive when every small access or layout change comes as an urgent request.

✓ PROS

There are opportunities to move from support into automation or testing if the project allows.

✕ CONS

Support projects can involve weekend checks during releases or production issues.