G-P (Globalization Partners) - SWE2 Interview Experience June 2026

YoE: 3 years 11 months Current Job: SWE2 at a PBC (FinTech sector) MNC Tech Stack: Java / Spring Boot Backend Location: Hyderabad, Hybrid

Applied to G-P via close friend's referral (hiring was under the same manager) on 30th May 2026. Location: Remote (5 days wfh)

R-0 - HR Screening

Date: 4th June 2026 20 mins
Asked generic HR questions
Discussion about G-P, my current org, why switch, cctc vs ectc, roles expectations at G-P, work culture, etc.

R-1 - DSA

Date: 10th June 2026 3pm-4pm

1. https://leetcode.com/problems/recover-binary-search-tree/description/
   - Brute force - T.C.=O(n.logn) & S.C.=O(n)
   - Optimised - T.C.=O(n) & S.C.=O(h) where n = nodes, h = height of the tree/ recursive call stack.
   Only could explain the approach, skipped the coding.
   - Expectation was - T.C.=O(n) & S.C.=O(1)
2. https://leetcode.com/problems/maximum-number-of-fish-in-a-grid/description/
   Solved using DFS, T.C.=O(r.c) & S.C.=O(r.c)
   Wrote the pseudocode.

R-2 HLD + LLD (ChatGpt/Gemini assisted)

Date: 16th June 2026 3pm-4pm

Design a thread-safe, distributed rate limiter for multiple AI agents running across application servers and sharing a common LLM Gateway. Requirements: 1. Global Token Bucket: capacity 100, refill 10 tokens/sec
2. allowRequest(agentId) consumes 1 token
3. Lazy refill only; no background scheduler
4. Handle concurrent requests and distributed shared state
5. Agents have HIGH / MEDIUM / LOW priority tiers
6. Reserve 20% capacity for HIGH-priority agents; LOW agents cannot access it
7. HIGH agents can pre-empt/borrow from the general pool when necessary
8. Prevent high-priority agents from being starved by high-volume low-priority traffic

Discussed architecture, thread safety/distributed-concurrency, lazy-refill mathematics, resource allocation, and priority handling. Implemented/design classes such as MultiAgentRateLimiter, GlobalBucket, Agent, TokenConsumptionRate, priority queue, and Agent Factory.

Also asked questions on use of LLM in current work.

R-3 LLD

Date: 23rd June 1pm to 2pm

1. LLD of an extensible Role-Based Access Control system. Roles - (Extensible) BasicRole, AdminRole, SuperAdminRole, PlatformRole, CompanyRole, etc. Permissions - (Fixed) READ_REPORT, WRITE_REPORT, DELETE_USER, MAKE_ADMIN, APPROVE_INVOICE. Use of Decorator design pattern was expected.
2. Clean java code of singleton design pattern example and its real world use case, identify and fix the multi-threading issue and expectation was to solve using 'synchronized' keyword in java.
3. One DSA problem https://leetcode.com/problems/binary-tree-maximum-path-sum/ Pesudocode expected

R-4 HM / Bar Raiser

Date: 23rd June 3pm to 4pm

• Why are you looking to switch ?
• Explain your current team structure, responsibilities, work division, and how the team collaborates.
• How does peer/code review work? How frequently are architectural/design reviews done?
• Tell me about a time you had a tight deadline and had to stretch beyond your normal capacity/JD to deliver.
• Have you proposed any ideas or initiatives to senior leadership/bigger forums?
• What have you built or improved proactively, without being explicitly asked?
• What technical improvements have you identified, planned, and driven yourself?
• What have you learned from other engineers in your organization?
• Do you prefer structured/planned work or exploratory discussions? Why?
• What is a key personality trait that defines you? What makes you a good team player?
• How do you handle a bad/disagreeable idea from a colleague?
• If given a completely new task in your first week, how would you plan and deliver it within 5 days?
• Are you someone who is vocal about your work or prefers working silently?
• What AI/agentic AI initiatives have you worked on at your organization?
• How have you used Cursor? What has been your best use case and what challenges have you faced?
• How do you keep yourself updated with the rapidly changing AI landscape?
• What AI-based personal projects have you built outside your regular work?
• Have you introduced any initiative/process/technical practice that the team now follows?

Overall Result: Rejected
HR called on 24th June after team's debrief and said the open position's technical expectations bar were higher and I am not shortlisted. Also mentioned 6 months cool-off period to re-apply.