LTIMindtree

✓ PROS

Led Salesforce technical design for objects, sharing rules, Apex services, integrations, and deployment planning. The role gave strong ownership and visibility with business and technical stakeholders.

✕ CONS

Technical leads can get stretched between code review, design discussions, production defects, and release planning.

✓ 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

Good experience with SAP Basis activities like transport management, system monitoring, user support, performance checks, and environment readiness during releases. It builds strong discipline around enterprise system stability.

✕ CONS

Cutover and production release windows can require late-night availability, especially when multiple teams depend on SAP system readiness.

✓ PROS

Strong hands-on exposure to ABAP reports, enhancements, user exits, forms, interfaces, and performance tuning. The best learning came from debugging real production issues instead of only working on small change requests.

✕ CONS

ABAP work can become support-heavy when the project has many old custom objects and limited modernization scope.

✓ PROS

Worked on order-to-cash processes covering sales orders, pricing, delivery, billing, and customer master issues. It helped me understand how SAP SD connects with finance, warehouse, and logistics teams.

✕ CONS

Integration defects with FI and MM could take longer to close because multiple module owners were involved.

✓ PROS

Good exposure to SAP MM procurement flows, purchase requisitions, purchase orders, vendor master data, inventory movement, and integration with finance. The learning was useful because the work was not limited to ticket resolution.

✕ CONS

Requirement changes from procurement teams sometimes came late after users saw the configured process during testing.

✓ PROS

Good exposure to digital engineering, application development, data, cloud, and enterprise client delivery, especially around Cloud work and real client or business scenarios.

✕ CONS

Workload, growth, and learning can vary depending on project allocation, manager support, and delivery timelines for cloud engineer roles.

✓ PROS

Good exposure to digital engineering, application development, data, cloud, and enterprise client delivery, especially around Data work and real client or business scenarios.

✕ CONS

Workload, growth, and learning can vary depending on project allocation, manager support, and delivery timelines for data engineer roles.