Delhivery

✓ PROS

Good exposure to Salesforce CPQ configuration, product rules, pricing rules, quote templates, approvals, and quote-to-cash processes. The project helped me understand complex sales operations.

✕ CONS

CPQ defects were tricky because small pricing-rule changes affected multiple products and approval paths.

✓ PROS

Worked on Salesforce testing covering sales processes, service flows, reports, role-based access, and integration scenarios. It helped me understand CRM workflows beyond simple test-case execution.

✕ CONS

Testing became difficult when flows changed late or test data was not prepared properly.

✓ 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

Good exposure to SuccessFactors Employee Central, workflow approvals, employee data changes, role permissions, and HR process discussions. The role improved both functional understanding and client communication.

✕ CONS

HR policy exceptions created repeated configuration changes because different business units followed different rules.

✓ PROS

Worked on SAP EWM warehouse flows involving inbound, outbound, picking, packing, staging, and stock movement scenarios. Exposure to warehouse users made the project more practical and less theoretical.

✕ CONS

Warehouse testing became difficult when master data, storage bins, and scanner-related scenarios were not ready on time.

✓ 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

Young teams in many locations make the work environment energetic and action-oriented.

✕ CONS

Role boundaries between hub, transport, and last-mile teams may blur during pressure.

✓ PROS

Good exposure to operations, supply chain, service delivery, analytics, and customer-facing processes, especially around Service work and real client or business scenarios.

✕ CONS

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