IntraEdge

✓ 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

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

Quality teams get space to improve test coverage and release readiness.

✕ CONS

Work-life balance can reduce when client deadlines compress release timelines.

✓ PROS

Managers in strong accounts encourage ownership and trust employees with responsibility.

✕ CONS

Performance recognition can be less visible when client feedback is not shared openly.

✓ PROS

The culture is generally supportive when managers communicate expectations clearly.

✕ CONS

Management communication may vary between locations and delivery units.

✓ 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

Developers can get client-facing exposure on modern applications and enterprise platforms.

✕ CONS

Long-term growth can feel unclear if career discussions are not proactively requested.

✓ PROS

The company is suitable for employees who prefer a flexible and professional environment.

✕ CONS

Benefits and policies may not feel as broad as very large IT organizations.

✓ PROS

Project teams are often collaborative and allow engineers to manage work responsibly.

✕ CONS

Project changes can create uncertainty if client scope shifts suddenly.

✓ PROS

Good exposure to Salesforce configuration, Apex/LWC, CRM workflows, integrations and demos in IntraEdge, 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 IntraEdge, 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 IntraEdge, 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 IntraEdge, 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

Good option for experienced engineers looking for steady client delivery work.

✕ CONS

Some roles become staff-augmentation heavy with less influence on product decisions.

✓ PROS

Work pressure is usually manageable when project scope is stable.

✕ CONS

Some support-heavy projects can limit development learning over time.

✓ PROS

Support roles help build strong production troubleshooting and incident communication skills.

✕ CONS

Resource planning can feel reactive when projects ramp up quickly.

✓ PROS

Business analysts can work closely with product and technology stakeholders.

✕ CONS

Promotion cycles may not always match the speed of individual contribution.

✓ PROS

Cloud and DevOps roles can get practical exposure to deployment, automation, and monitoring.

✕ CONS

Training programs could be more formal for employees moving into newer technologies.

✓ PROS

Full-stack developers can work across frontend, backend, APIs, and integrations.

✕ CONS

Compensation revisions may depend heavily on account budgets and timing.

✓ PROS

The company can be a good fit for employees valuing autonomy over micromanagement.

✕ CONS

Freshers may need more structured training before entering client-facing work.

✓ PROS

Good work-life balance in many technology teams with reasonable delivery expectations.

✕ CONS

Employee experience depends greatly on client account, project manager, and contract stability.

✓ PROS

Some projects offer good compensation compared with similar service delivery roles.

✕ CONS

Role clarity may blur between developer, support, and analyst tasks in small teams.

✓ PROS

Recruitment and internal teams are responsive in many employee interactions.

✕ CONS

Onsite or travel exposure is limited for many India-based delivery roles.

✓ PROS

Employees get exposure to US-style delivery rhythms and distributed team communication.

✕ CONS

Employees may need to self-drive internal networking to find better opportunities.

✓ PROS

Data engineering roles provide useful work around pipelines, warehousing, and analytics use cases.

✕ CONS

Some projects may offer limited internal visibility because work happens mainly with clients.

✓ PROS

Technical leads can take ownership of architecture, code reviews, and delivery planning.

✕ CONS

Documentation expectations can increase when working across distributed client teams.

✓ PROS

There is decent opportunity to learn through client systems and cross-functional work.

✕ CONS

Internal branding and employee engagement can be stronger across offices.