Airtel

✓ PROS

Large operations footprint gives practical understanding of service delivery beyond classroom theory.

✕ CONS

Work-life balance is uneven because some teams follow strict shifts while others extend often.

✓ PROS

Support functions are structured with clear escalation paths for customer and technical issues.

✕ CONS

Compensation may not always match the workload in field, retail, or support-heavy roles.

✓ PROS

Strong brand value makes field interactions and enterprise customer conversations easier.

✕ CONS

Sales roles can become stressful because targets change with market and territory pressure.

✓ PROS

There are opportunities to learn cybersecurity, cloud operations, and monitoring in telecom context.

✕ CONS

Some tools feel process-heavy, especially when quick issue resolution is needed.

✓ 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.