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.