Citi

✓ PROS

Worked on Salesforce integrations with ERP, marketing, and support platforms using REST APIs and middleware. This gave practical understanding of data sync, error handling, and integration monitoring.

✕ CONS

Integration testing was blocked whenever external systems changed payloads or were unavailable.

✓ 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

Worked on SAP CPI integrations between SAP and third-party systems using mappings, APIs, error handling, and monitoring. It helped me understand how integration failures directly impact business operations.

✕ CONS

Testing was delayed whenever source or target systems were not ready, even when CPI development was completed.

✓ 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

Good exposure to banking technology, risk, compliance, production systems, and financial-services data, especially around Risk work and real client or business scenarios.

✕ CONS

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

✓ PROS

Good exposure to banking technology, risk, compliance, production systems, and financial-services data, 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.