Coforge Interview Questions & Answers 2026

Coforge (formerly NIIT Technologies) is a Noida-headquartered IT services company specializing in BFSI, travel and transportation, and insurance. Owned by Baring Private Equity Asia. Acquired SLK Global in 2023 strengthening BPM. Strong in low-code platforms (Pega, Appian) and digital transformation.

Coforge's domain depth in travel/insurance is unique - they work with airlines and major insurers globally. Strong product partnerships (Pega, Salesforce, Duck Creek). Focused growth strategy under PE ownership. Smaller than tier-1 means more responsibility, faster career growth, and direct client interaction earlier in your career.

S - Single Responsibility (one reason to change), O - Open/Closed (open for extension, closed for modification), L - Liskov Substitution (subtypes replaceable), I - Interface Segregation (specific over general interfaces), D - Dependency Inversion (depend on abstractions). These principles lead to maintainable, testable code essential for Coforge enterprise projects.

Pega is a low-code BPM (Business Process Management) and CRM platform used heavily in BFSI and insurance for case management, customer journey orchestration, and decisioning. Coforge has one of the largest Pega practices in India with thousands of certified developers. Knowledge of Pega 8.x, decision rules, and case lifecycle is valuable.

Use proper HTTP verbs (GET/POST/PUT/DELETE), nouns in URLs (/users not /getUsers), versioning (/v1/users), pagination (limit/offset or cursor), filtering and sorting via query params, consistent error responses, proper status codes, HATEOAS for discoverability, authentication (OAuth 2.0/JWT), rate limiting.

Maintain currentSum and maxSum. For each element: currentSum = max(arr[i], currentSum + arr[i]); maxSum = max(maxSum, currentSum). Initialize both with arr[0]. Handles negative numbers correctly. Time O(n), Space O(1). Classic dynamic programming problem.

Engage stakeholders early to clarify scope. Document assumptions in writing (RAID log). Build prototypes to validate understanding. Break work into small iterations with frequent feedback. Use techniques like 5-Whys to uncover real needs. Be transparent about risks and timeline impact.