A Software Engineer at i2c is responsible for building, optimizing, and maintaining one of the most reliable and high-performance digital banking and payment processing engines in the world. The systems you build will process millions of financial transactions daily, demanding sub-second latency, robust security, and near-zero downtime. This role sits at the intersection of complex financial technology and high-scale system architecture, making it both highly critical and intellectually challenging. In this position, you will work on core transactional systems, multi-currency wallet solutions, and API integrations that power global financial institutions. The engineering team at i2c prioritizes deep foundational knowledge of computer science, clean code practices, and database optimization. Your work will directly impact millions of end-users globally who rely on i2c’s infrastructure for seamless, secure payment processing. To succeed as a Software Engineer at i2c, you must possess a strong analytical mind, a passion for solving complex architectural puzzles, and a highly resilient attitude. The company values engineers who do not just write code, but who understand how their code interacts with the underlying operating system and database layers. It is a demanding environment, but it offers unparalleled growth for engineers looking to master high-transaction backend systems.
Initial Screening
reportedA quick telephonic conversation with HR to verify basic credentials, GPA, and salary expectations.
What to demonstrate
- A quick telephonic conversation with HR to verify basic credentials, GPA, and salary expectations
- Depth in Interview Process (multi-round screening)
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Computer-Based Assessment
reportedA comprehensive assessment designed to test overall intelligence, technical knowledge, and communication skills.
What to demonstrate
- A comprehensive assessment designed to test overall intelligence, technical knowledge, and communication skills
- Depth in Interview Process (multi-round screening)
How to prepare
- Answer aloud and timed: How do you determine if polymorphism has been implemented correctly in a software module?
- Answer aloud and timed: Explain the SOLID principles and provide a scenario where you would apply the Single Responsibility Principle.
Technical Panel Interviews
reportedInterviews conducted by senior engineers or technology directors focusing on academic projects and core computer science concepts.
What to demonstrate
- Interviews conducted by senior engineers or technology directors focusing on academic projects and core computer science concepts
- Depth in Interview Process (multi-round screening)
How to prepare
- Answer aloud and timed: What is the difference between an abstract class and an interface, and when would you use each?
- Answer aloud and timed: What is the difference between a clustered and a non-clustered index, and how do they affect read/write performance?
Management Interview
reportedFinal interview with a Vice President or Global Head discussing long-term career goals and cultural fit.
What to demonstrate
- Final interview with a Vice President or Global Head discussing long-term career goals and cultural fit
- Depth in Interview Process (multi-round screening)
How to prepare
- Answer aloud and timed: Explain database transactions and the importance of ACID properties in a payment processing system.
- Answer aloud and timed: Write a SQL query to find duplicate records in a transaction table and optimize it using joins.
PracHub editorial advice for the preparation topics above.
Dress Formally
I2c maintains a highly professional corporate environment. Arrive for your onsite assessments and interviews in formal business attire (e.g., a buttoned, tucked-in shirt and formal shoes) to make a strong, positive first impression.
Bring Physical CVs
Always carry two printed copies of your resume in a clean folder. Even if the interviewers have digital copies, presenting a physical resume demonstrates preparation, organization, and professional maturity.
Master Your Final Year Project (FYP)
Be ready for a highly detailed, deep-dive discussion about your FYP or past professional projects. You must be able to explain the architecture, the database design (including ERDs), the specific technologies used, and the logical reasoning behind your technical decisions.
Use the 3-Second Pause Rule
When asked a complex technical or behavioral question, take a deliberate 2 to 3-second pause before answering. This helps you structure a coherent, logical response in your head rather than rushing into an unorganized explanation.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
What is the difference between a clustered and a non-clustered index, and how do they affect read/write perfor
What is the difference between a clustered and a non-clustered index, and how do they affect read/write performance?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain database transactions and the importance of ACID properties in a payment processing system.
Explain database transactions and the importance of ACID properties in a payment processing system.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
What are database triggers and views? Explain their pros and cons.
What are database triggers and views? Explain their pros and cons.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Solve the classic Two-Sum problem and explain its time and space complexity.
Solve the classic Two-Sum problem and explain its time and space complexity.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How do you find all permutations of a given string using recursion?
How do you find all permutations of a given string using recursion?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain how you would detect a cycle in a singly linked list.
Explain how you would detect a cycle in a singly linked list.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
What are the differences between stacks and queues, and how would you implement a queue using two stacks?
What are the differences between stacks and queues, and how would you implement a queue using two stacks?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain the time complexity of quicksort in its best, average, and worst cases.
Explain the time complexity of quicksort in its best, average, and worst cases.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain the difference between a process and a thread.
Explain the difference between a process and a thread.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
How do semaphores and mutexes work to resolve race conditions?
How do semaphores and mutexes work to resolve race conditions?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Describe context switching and how it impacts system performance during heavy multiprocessing.
Describe context switching and how it impacts system performance during heavy multiprocessing.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Explain different CPU scheduling algorithms and their trade-offs.
Explain different CPU scheduling algorithms and their trade-offs.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Write a SQL query to find duplicate records in a transaction table and optimize it using joins.
Write a SQL query to find duplicate records in a transaction table and optimize it using joins.
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Write the update path that detects a concurrent edit
resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.
Approach
- One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
- Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
- State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
- Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.
Follow-up
- A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
- Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?
Explain the four pillars of OOP with real-world examples.
Explain the four pillars of OOP with real-world examples.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is the difference between aggregation and composition? Provide a code implementation example.
What is the difference between aggregation and composition? Provide a code implementation example.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you determine if polymorphism has been implemented correctly in a software module?
How do you determine if polymorphism has been implemented correctly in a software module?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Explain the SOLID principles and provide a scenario where you would apply the Single Responsibility Principle.
Explain the SOLID principles and provide a scenario where you would apply the Single Responsibility Principle.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is the difference between an abstract class and an interface, and when would you use each?
What is the difference between an abstract class and an interface, and when would you use each?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Design an Entity-Relationship Diagram (ERD) for a university enrollment system and write the join queries to r
Design an Entity-Relationship Diagram (ERD) for a university enrollment system and write the join queries to retrieve student courses.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
What is a deadlock, what are its four necessary conditions, and how can you prevent it?
What is a deadlock, what are its four necessary conditions, and how can you prevent it?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics i2c candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the i2c loop
- Write out the reported sequence: Initial Screening, Computer-Based Assessment, Technical Panel Interviews, Management Interview.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.
02Work Interview Process (multi-round screening)
- Spend the session on Interview Process (multi-round screening), which i2c candidates report being tested on.
- Write one worked example in Interview Process (multi-round screening) and time yourself on it.
Deliverable: One timed worked example in Interview Process (multi-round screening).
03Work SQL
- Spend the session on SQL, which i2c candidates report being tested on.
- Write one worked example in SQL and time yourself on it.
Deliverable: One timed worked example in SQL.
04Work Database Fundamentals
- Spend the session on Database Fundamentals, which i2c candidates report being tested on.
- Write one worked example in Database Fundamentals and time yourself on it.
Deliverable: One timed worked example in Database Fundamentals.
05Answer out loud: Object-Oriented Programming (OOP) & Design
- Answer aloud, timed: Explain the four pillars of OOP with real-world examples.
- Answer aloud, timed: What is the difference between aggregation and composition? Provide a code implementation example.
Deliverable: Spoken answers to 2 reported Object-Oriented Programming (OOP) & Design question(s), under time.
06Answer out loud: Databases & SQL Optimization
- Answer aloud, timed: What is the difference between a clustered and a non-clustered index, and how do they affect read/write performance?
- Answer aloud, timed: Explain database transactions and the importance of ACID properties in a payment processing system.
Deliverable: Spoken answers to 2 reported Databases & SQL Optimization question(s), under time.
07Answer out loud: Data Structures & Algorithms (DSA)
- Answer aloud, timed: Solve the classic Two-Sum problem and explain its time and space complexity.
- Answer aloud, timed: How do you find all permutations of a given string using recursion?
Deliverable: Spoken answers to 2 reported Data Structures & Algorithms (DSA) question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Describe your Final Year Project (FYP) in detail, focusing on the technical challenges you faced and how you o
Describe your Final Year Project (FYP) in detail, focusing on the technical challenges you faced and how you overcame them.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What are your greatest strengths and weaknesses? Provide real-world professional examples for both.
What are your greatest strengths and weaknesses? Provide real-world professional examples for both.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Why do you want to work at i2c, and where do you see yourself in the next five years?
Why do you want to work at i2c, and where do you see yourself in the next five years?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle working under tight deadlines or dealing with ambiguous requirements?
How do you handle working under tight deadlines or dealing with ambiguous requirements?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Describe your Final Year Project (FYP) in detail, focusing on the technical challenges you faced and how you overcame them.
- 02
What are your greatest strengths and weaknesses? Provide real-world professional examples for both.
- 03
Why do you want to work at i2c, and where do you see yourself in the next five years?
- 04
How do you handle working under tight deadlines or dealing with ambiguous requirements?
What is the passing criteria for the initial technical assessment?
The computer-based assessment is highly selective. For the technical MCQ section, candidates generally need to score at least 70% to 75% (for example, correctly answering at least 34 out of 50 questions) to progress to the interview stages.
i2c Software Engineer candidate reports ↗How critical is the essay writing section of the assessment?
Extremely critical. i2c uses the essay writing test to evaluate your analytical thinking, written communication, and English proficiency. A poor performance on the essay can result in rejection, even if your technical MCQ score is exceptionally high.
i2c Software Engineer candidate reports ↗How long does the entire hiring process typically take?
The process can vary from highly accelerated (completed within a few weeks) to more deliberate, sometimes taking 1 to 2 months from the initial application to the final offer letter, depending on departmental scheduling and hiring volume.
i2c Software Engineer candidate reports ↗Does i2c require engineers to work night shifts?
Because i2c serves global clients across multiple time zones, some teams operate on rotating or dedicated night shifts. You should be prepared to discuss your flexibility regarding shift timings during your initial HR screening. ##### Tip i2c operates globally across multiple time zones. Be prepared to discuss your flexibility regarding shift timings, including night shifts, during your initial screening call.
i2c Software Engineer candidate reports ↗What topics does i2c test in interviews?
i2c interviews most often cover Object-Oriented Programming (OOP), SQL, Database Fundamentals, Data Structures and Algorithms (DSA), and Communication Skills. The exact emphasis depends on the specific role you apply for.
i2c Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01i2c Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.