Cognizant

✓ PROS

Managed delivery, customer escalations, account governance, team utilization, and service improvement initiatives. Good exposure to large client delivery management.

✕ CONS

Stakeholder pressure is high and internal reporting can be heavy.

✓ PROS

Support role gave exposure to user issues, ticketing tools, SLA discipline, and troubleshooting across enterprise applications.

✕ CONS

The work can become repetitive if there is limited opportunity to move into development or automation.

✓ PROS

Worked with client stakeholders to gather requirements, document user stories, support UAT, and coordinate with development teams.

✕ CONS

Requirement changes late in the cycle create rework for both BA and engineering teams.

✓ PROS

Handled network monitoring, incident response, change windows, and client coordination. Good exposure to infrastructure operations.

✕ CONS

Night shifts and weekend change windows can be tiring.

✓ PROS

Worked on security monitoring, incident review, vulnerability tracking, and compliance reporting. Good long-term domain for career growth.

✕ CONS

Shift-based monitoring and urgent incidents can impact work-life balance.

✓ PROS

Good exposure to banking and insurance systems, COBOL, JCL, batch jobs, and production support. Stable domain with large clients.

✕ CONS

Technology can feel legacy-heavy and internal movement to modern stacks may be difficult.

✓ PROS

Worked on catalog items, workflows, incident/change modules, client scripts, and integrations. Good market-relevant skillset with enterprise demand.

✕ CONS

Workflow requirements change frequently when process owners refine approvals.

✓ PROS

Handled Oracle ERP support issues, report checks, data corrections, user access, and coordination with business users. Good exposure to ERP operations.

✕ CONS

ERP support can become repetitive when permanent fixes are not prioritized.

✓ PROS

Worked on PL/SQL, packages, reports, data fixes, and production support for enterprise applications. Strong learning for database fundamentals.

✕ CONS

Late-night production issues can happen when business-critical jobs fail.

✓ PROS

Worked on Apex, LWC, flows, permissions, and integration support for CRM projects. Good learning when the project has implementation or enhancement work.

✕ CONS

Some projects are more support-heavy than development-heavy.

✓ PROS

Worked on Marketing Cloud journeys, automation, data extensions, integrations, and campaign support. Good exposure to customer engagement technology.

✕ CONS

Campaign timelines can become tight when marketing stakeholders change requirements late.

✓ PROS

Worked on Salesforce Data Cloud use cases involving customer data, segmentation, integration, and platform configuration. Strong CRM and data exposure.

✕ CONS

Requirements can change quickly because business teams are still refining data-cloud use cases.

✓ PROS

Worked on ABAP reports, SmartForms, enhancements, IDoc issues, debugging, and performance fixes. Useful for building SAP technical fundamentals.

✕ CONS

Legacy objects are difficult when documentation is missing or old code is not clean.

✓ PROS

Worked on procurement, inventory, purchase orders, goods movement, and integration with finance. Good role for understanding end-to-end business processes.

✕ CONS

Master-data and approval issues can create repeated support tickets.

✓ PROS

Good exposure to SAP finance processes, GL, AP, AR, controlling, product costing, reporting, and month-end close support.

✕ CONS

Close periods and UAT cycles can create urgent work and late defect resolution.

✓ PROS

Worked on AI proof-of-concepts, data preparation, model evaluation, and automation use cases. Good exposure as Cognizant is pushing AI-led transformation.

✕ CONS

Not every AI use case moves to production, so actual impact depends on client maturity.

✓ PROS

Worked on SQL, ETL pipelines, data validation, reporting feeds, and business data quality issues. Data projects offer better learning than generic support work.

✕ CONS

Source data issues from client systems create repeated rework and delay reports.

✓ PROS

Worked on cloud monitoring, access management, deployment support, incident handling, and automation opportunities. Good exposure to managed cloud operations.

✕ CONS

Critical incidents and change windows can affect work-life balance.

✓ PROS

Got hands-on work on frontend screens, backend APIs, deployment support, and client demos. Good project helped improve both technical and communication skills.

✕ CONS

Delivery timelines can become tight when requirements are finalized late by the client.

✓ PROS

Worked on Java, Spring Boot, REST APIs, SQL changes, and production fixes. Good experience if the client project has active development work.

✕ CONS

Technology stack can become stagnant if allocated to a long-running support project.

✓ PROS

Good exposure to project governance, client reporting, delivery planning, resource management, and large enterprise accounts.

✕ CONS

Administrative reviews and internal reporting can consume too much time away from actual delivery improvements.

✓ PROS

Led a team handling development, code reviews, production defects, release planning, and client communication. The role builds strong delivery ownership.

✕ CONS

Too many parallel responsibilities across delivery, reporting, mentoring, and escalation management can create pressure.

✓ PROS

Worked on enterprise application delivery with client ownership, defect triage, release support, and mentoring junior engineers. Good exposure for service-delivery leadership.

✕ CONS

Growth and compensation are not always aligned with market demand for experienced engineers.

✓ PROS

Good learning resources, large client projects, hybrid work culture, and exposure to production systems. Strong place to understand enterprise delivery at scale.

✕ CONS

Too many trackers and micro-management in some accounts. Tech leads may get pushed into non-technical coordination work.

✓ PROS

Good work culture in the team and decent exposure to automation frameworks, test strategy, and client-facing defect discussions.

✕ CONS

Some managers can be difficult and work-life balance depends completely on the account and release pressure.

✓ PROS

Good environment to learn automation testing, API validation, regression planning, and release discipline. Team members were supportive during critical testing cycles.

✕ CONS

Work-life balance can become difficult during release weeks and automation maintenance is sometimes pushed aside.

✓ PROS

Got exposure to a client project using newer technologies and learned delivery process, documentation, sprint updates, and offshore-onshore coordination.

✕ CONS

Knowledge transfer was not always proper and late evening client meetings affected work-life balance.

✓ PROS

Good client exposure, hybrid working model, and chances to work on different enterprise systems. The company is stable and useful for building corporate IT experience.

✕ CONS

Work-life balance is project-dependent and career progression discussions are not always proactive once deployed to a client.

✓ PROS

Decent work culture with exposure to enterprise applications, documentation, tickets, and structured delivery. Work pressure is manageable when the project is stable.

✕ CONS

Hikes and appraisals can feel low compared with the effort, and growth depends heavily on project and manager.

✓ PROS

Good company to start as a fresher because training, client exposure, and internal learning platforms help understand how large IT delivery works.

✕ CONS

Salary growth is slow at the early level and project allocation decides the quality of learning.

✓ PROS

For lateral joiners, some roles offer good client visibility and delivery responsibility.

✕ CONS

Benefits are decent, but compensation growth may not feel competitive.

✓ PROS

The company provides practical exposure to production issue handling.

✕ CONS

Bench or allocation changes may create uncertainty during account transitions.

✓ PROS

Employees can learn both support and development activities in the same client ecosystem.

✕ CONS

Technology modernization depends more on client roadmap than employee preference.

✓ PROS

Large account sizes create opportunities to understand multi-team coordination.

✕ CONS

Some employees feel career planning is not proactive from management.

✓ PROS

Some managers give enough ownership to solve issues independently.

✕ CONS

Project documentation and reporting can take significant time.

✓ PROS

There are multiple internal platforms for training and skill development.

✕ CONS

Work-life balance can become poor in teams with understaffed support coverage.

✓ PROS

Cognizant is a decent place to learn enterprise processes and client communication.

✕ CONS

Certain business process roles can feel repetitive after the initial learning phase.

✓ PROS

Internal learning portals and certifications

✕ CONS

Career growth depends heavily on project

✓ PROS

Strong learning opportunities

✕ CONS

Promotion is very rare.

✓ 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

Employees in technical tracks can move into automation or cloud work with the right project.

✕ CONS

Employees seeking fast salary growth may need to switch companies.

✓ 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

Worked on Salesforce custom development using Apex, Lightning Web Components, validation rules, flows, and custom objects. The project gave good exposure to both technical development and business-user expectations.

✕ CONS

Requirements changed during UAT when users started testing actual screens and automation flows.

✓ 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

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

Worked closely with finance users on SAP FICO configuration, month-end close issues, GL/AP/AR testing, and reconciliation activities. This gave practical exposure to how finance teams actually use SAP during closing cycles.

✕ CONS

The difficult part was handling urgent defects during UAT and month-end because every small posting or tax issue needed quick validation from business users.

✓ 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

Benefits like insurance and corporate policies are helpful for long-term employees.

✕ CONS

Appraisal communication can feel generic in large accounts.

✓ PROS

Good exposure to enterprise clients

✕ CONS

Promotion cycles can feel delayed

✓ PROS

Team environments can be friendly when the account has stable leadership.

✕ CONS

Internal mobility can be slow when the current project has delivery dependency.

✓ PROS

The company provides useful exposure to structured delivery, SLAs, and client reporting.

✕ CONS

Some teams have less innovation work and more operational follow-up.

✓ PROS

Stable work culture

✕ CONS

Weekend support may be required in some teams

✓ PROS

Employees can gain hands-on experience with application maintenance and digital transformation work.

✕ CONS

Onsite opportunities are selective and can be limited by account budgets.

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

✓ PROS

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

✕ CONS

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

✓ PROS

Supportive teammates and managers

✕ CONS

Salary growth is slower than market

✓ PROS

Certain projects provide good work-from-home flexibility based on client policy.

✕ CONS

Freshers may not always get the technology stack they were trained for.

✓ PROS

Good exposure to Salesforce configuration, Apex/LWC, CRM workflows, integrations and demos in Cognizant, with practical client-facing delivery and business process learning.

✕ CONS

Salesforce Consultant work can become demanding when client requirements change late or testing timelines are compressed.

✓ PROS

Good exposure to Salesforce configuration, Apex/LWC, CRM workflows, integrations and demos in Cognizant, with practical client-facing delivery and business process learning.

✕ CONS

Salesforce Developer work can become demanding when client requirements change late or testing timelines are compressed.

✓ PROS

Good exposure to SAP configuration, process workshops, UAT, cutover and support in Cognizant, with practical client-facing delivery and business process learning.

✕ CONS

Senior SAP Consultant work can become demanding when client requirements change late or testing timelines are compressed.

✓ PROS

Good exposure to SAP configuration, process workshops, UAT, cutover and support in Cognizant, with practical client-facing delivery and business process learning.

✕ CONS

SAP Consultant work can become demanding when client requirements change late or testing timelines are compressed.

✓ PROS

There are opportunities to work with international stakeholders and offshore delivery teams.

✕ CONS

Upskilling does not always translate into immediate project movement.

✓ PROS

The organization offers a recognized brand for employees starting in IT services.

✕ CONS

Some roles involve long calls with offshore clients due to time-zone overlap.

✓ PROS

Good teams provide supportive peer networks and practical guidance during onboarding.

✕ CONS

Manager quality varies, which can affect feedback, visibility, and work-life balance.

✓ PROS

Employees can build strong domain knowledge in healthcare and insurance projects.

✕ CONS

Promotion decisions may feel delayed for employees stuck in large delivery teams.

✓ PROS

The company has a wide role mix across development, testing, support, data, and business process delivery.

✕ CONS

Work pressure can increase sharply during releases, audits, or client escalations.

✓ PROS

Some accounts provide balanced workloads and predictable schedules outside release periods.

✕ CONS

Some employees may get repetitive support work with limited technical advancement.

✓ PROS

Excellent onboarding for freshers

✕ CONS

Work pressure increases during release cycles

✓ PROS

Cognizant can be suitable for employees who want steady enterprise delivery experience.

✕ CONS

Internal policies can be difficult to navigate without manager support.

✓ PROS

Freshers can learn corporate delivery practices through real client projects early in their career.

✕ CONS

Growth depends strongly on the project, manager, and available role openings.

✓ PROS

Cross-functional roles help employees understand operations, technology, and client needs together.

✕ CONS

Support-heavy accounts can require weekend attention during incidents.

✓ PROS

Cognizant gives employees exposure to large global accounts, especially in healthcare, BFSI, and digital operations.

✕ CONS

Salary hikes can be limited and may not always match the workload handled by employees.

✓ PROS

Employees can build domain-specific resumes through long-term industry accounts.

✕ CONS

Employees may need to push continuously to get challenging assignments.

✓ PROS

The work environment is stable in mature accounts with established processes.

✕ CONS

Some teams have limited visibility into future role progression.