Fujitsu

✓ PROS

Managed global delivery teams, SLA reporting, service governance, and customer escalations. The role gave strong exposure to enterprise managed services leadership.

✕ CONS

Balancing stakeholder expectations, escalations, and internal reporting can be demanding.

✓ PROS

Strong exposure to enterprise infrastructure, incident management, server operations, and ITIL-based support. Good learning for managed-services professionals.

✕ CONS

Process-heavy approvals can slow standard infrastructure changes.

✓ PROS

Worked on enterprise cloud operations, monitoring, automation, backup checks, and managed services support. Good exposure to structured global IT delivery.

✕ CONS

Operational support can extend beyond normal hours during critical incidents.

✓ PROS

Led Salesforce design for role hierarchy, sharing rules, Apex services, integrations, and deployment planning. The role provided strong technical ownership.

✕ CONS

Technical leads can get stretched across design, code review, defects, and release planning.

✓ PROS

Worked with sales and service teams to convert business needs into Salesforce user stories. Process mapping and UAT involvement helped build practical CRM knowledge.

✕ CONS

Incomplete requirements created rework during sprint demos.

✓ PROS

Managed users, permission sets, flows, reports, dashboards, page layouts, and support requests. Good role for understanding CRM from the business side.

✕ CONS

High volume of access and report requests can reduce time for process optimization.

✓ PROS

Participated in Salesforce implementation lifecycle from discovery workshops to configuration, testing, deployment, and hypercare support. Client-facing work improved consulting skills.

✕ CONS

Go-live pressure increases when training, migration, and final fixes happen together.

✓ PROS

Worked on Apex classes, Lightning Web Components, flows, validation rules, and integrations with external systems. The project gave solid CRM customization exposure.

✕ CONS

Requirements changed during UAT when business users tested real screens and flows.

✓ PROS

SAP support role provided exposure to tickets, enhancements, user training, transport coordination, and production issue resolution across modules.

✕ CONS

Support workload can spike during period-end and post-release phases.

✓ PROS

Worked on production planning, BOM, routing, MRP, and manufacturing-user testing. It gave a practical understanding of plant-level business processes.

✕ CONS

Manufacturing master data issues can delay end-to-end test execution.

✓ PROS

Good exposure to Employee Central, workflows, permissions, employee data changes, and HR-process discussions. The role improved both functional and consulting skills.

✕ CONS

Different HR policy rules across units can create repeated configuration changes.

✓ PROS

Worked on warehouse flows like inbound, outbound, picking, packing, staging, and stock movement scenarios. Direct interaction with warehouse users made the project practical.

✕ CONS

UAT becomes difficult when storage bins, devices, and master data are not ready.

✓ PROS

Strong hands-on exposure to ABAP reports, forms, enhancements, user exits, and performance fixes. Debugging real business issues helped improve technical depth.

✕ CONS

Old custom objects can make support work repetitive if documentation is missing.

✓ PROS

Worked on SAP CPI interfaces, mappings, APIs, error handling, and monitoring between SAP and external systems. It gave good exposure to enterprise integration patterns.

✕ CONS

Testing gets blocked when connected systems or sample payloads are not ready.

✓ PROS

Hands-on experience in system monitoring, transport management, performance checks, environment readiness, and production releases. Basis work gives strong enterprise-system discipline.

✕ CONS

Release weekends and cutover windows can require extended availability.

✓ PROS

Worked on order-to-cash processes including sales orders, pricing, delivery, billing, and customer master issues. It helped understand how sales, warehouse, and finance teams connect.

✕ CONS

Cross-module defects with FI and MM can take longer to close.

✓ PROS

Good exposure to procurement flows, purchase orders, vendor master, inventory movements, and integration with finance. Business users were actively involved throughout testing.

✕ CONS

Procurement approval changes can come late and impact configuration timelines.

✓ PROS

Worked closely with finance teams on month-end close, reconciliation issues, tax posting checks, GL/AP/AR testing, and reporting requirements. The role gave realistic finance-domain exposure.

✕ CONS

Financial close periods can be stressful because defects need quick validation and resolution.

✓ PROS

Good exposure to Core HR, employee data, approvals, and HR process configuration. Business-user discussions helped understand HR policy variations in real projects.

✕ CONS

Policy exceptions across business units can create repeated configuration changes.

✓ PROS

Worked on FBDI loads, data mapping, reconciliation, and validation with business teams. It gave strong exposure to how poor legacy data impacts ERP implementation.

✕ CONS

Data cleansing delays can push mock load and final migration timelines.

✓ PROS

Led technical delivery for Oracle reports, conversions, integrations, and issue triage. The role gave ownership across design, review, and production readiness.

✕ CONS

Technical leads can get stretched across multiple modules during cutover and hypercare.

✓ PROS

Support work gave exposure to real production problems across reports, workflows, integrations, and user access. It helped build troubleshooting confidence.

✕ CONS

Repeated tickets can reduce learning when permanent fixes are not prioritized.

✓ PROS

Worked on roles, privileges, data access, security console, and UAT access issues. The role gave good understanding of Oracle Cloud security and business access controls.

✕ CONS

Access issues become urgent during testing when users are blocked from completing scenarios.

✓ PROS

Hands-on exposure to BI Publisher, OTBI, SQL data models, bursting, and layout changes. Business users were directly involved, which made reporting work more realistic.

✕ CONS

Report formats changed frequently after user review, creating rework close to delivery.

✓ PROS

Good experience in designing integration flows, monitoring failed instances, handling business errors, and supporting production interfaces. The work was practical and business-impact driven.

✕ CONS

Production integration failures can create pressure when downstream business processes are blocked.

✓ PROS

Worked on OIC integrations between Oracle ERP, HCM, and external applications using REST, SOAP, schedules, mappings, and error handling. It helped build strong production integration skills.

✕ CONS

Testing gets delayed when third-party endpoints are not stable or payloads change late.

✓ PROS

Strong exposure to GL, AP, AR, assets, accounting rules, and month-end close issues. Working with finance teams gave practical knowledge beyond configuration screens.

✕ CONS

Close-period support can be demanding because small accounting or tax issues need quick resolution.

✓ PROS

Worked on procurement, inventory, supplier setup, and order management scenarios in Oracle Cloud SCM. The best part was understanding end-to-end supply chain flows with real users.

✕ CONS

Cross-module issues with finance and approvals can take time when multiple owners are involved.

✓ PROS

Good exposure to Oracle Cloud ERP implementation activities including CRP sessions, configuration support, UAT coordination, and go-live hypercare. Client workshops helped build real functional understanding.

✕ CONS

Requirement changes during UAT can increase rework because business users often refine processes after seeing the configured system.

✓ PROS

Worked on Oracle Fusion Financials reports, approval issues, BI Publisher layouts, and OTBI dashboards for global business users. The role gave strong exposure to enterprise ERP processes instead of only backend development.

✕ CONS

Quarter-end reporting and approval workflow issues can become urgent when finance users are closing books.