As a Software Engineer at Nisum, you are a critical driver of digital transformation for a diverse portfolio of enterprise clients. You will not just be writing code; you will be architecting scalable, high-impact solutions that solve complex business challenges. The role demands a balance of technical precision and the ability to thrive in a consulting-oriented environment where your work directly influences the end-user experience. Your impact at Nisum spans the full development lifecycle. You will collaborate with cross-functional teams, including product managers and client stakeholders, to deliver robust software solutions. Whether you are working on modernizing legacy systems or building new, cloud-native applications, your ability to translate business requirements into efficient, maintainable code is what makes this role both challenging and strategically significant. ##### Tip Nisum operates as a technology consultancy. Candidates who demonstrate a "client-first" mindset and the ability to articulate the business value of their technical decisions often stand out significantly during the evaluation process.
Initial Screening
reportedCandidates begin with a review of fundamentals to assess basic qualifications.
What to demonstrate
- Candidates begin with a review of fundamentals to assess basic qualifications
- Depth in Java
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.
Technical Assessments
reportedCandidates undergo a series of technical assessments to evaluate their technical competency.
What to demonstrate
- Candidates undergo a series of technical assessments to evaluate their technical competency
- Depth in Java
How to prepare
- Answer aloud and timed: Describe the lifecycle of a Hibernate entity and how you handle database session management.
- Answer aloud and timed: How do you implement Multithreading in Java to improve application performance?
Interpersonal Interviews
reportedCandidates participate in interviews focused on cultural alignment and behavioral aspects.
What to demonstrate
- Candidates participate in interviews focused on cultural alignment and behavioral aspects
- Depth in Java
How to prepare
- Answer aloud and timed: What are the key advantages of using Microservices over a monolithic architecture?
- Answer aloud and timed: What is the difference between a Controller, a Service, and a View in frontend frameworks like Angular?
Client-Facing Interview
reportedDepending on the project assignment, candidates may have a final interview with a client.
What to demonstrate
- Depending on the project assignment, candidates may have a final interview with a client
- Depth in Java
How to prepare
- Answer aloud and timed: How would you handle asynchronous operations in JavaScript using
setTimeoutor Promises? - Answer aloud and timed: Explain the best practices for manipulating the DOM using native JavaScript or jQuery.
Final Decision-Making
reportedThe hiring team reviews all assessments and interviews to make a final decision.
What to demonstrate
- The hiring team reviews all assessments and interviews to make a final decision
- Depth in Java
How to prepare
- Answer aloud and timed: How do you optimize CSS and HTML for performance in complex web layouts?
- Answer aloud and timed: Design a system to handle high-concurrency requests in a distributed environment.
PracHub editorial advice for the preparation topics above.
Master the Basics
Many candidates fail by over-preparing for complex algorithms and forgetting to review basic OOP or collection methods in Java.
Be Ready for "Why
Don't just show how to code a feature; be prepared to explain why you chose a specific design pattern or library.
Own Your Resume
Be prepared to discuss every project listed on your resume in detail, including your specific role and the technologies used.
Practice Virtual Presence
Since many Nisum interviews are conducted via video call, ensure your environment is professional and your communication is clear and concise.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
How do you implement Multithreading in Java to improve application performance?
How do you implement Multithreading in Java to improve application performance?
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 would you handle asynchronous operations in JavaScript using `setTimeout` or Promises?
How would you handle asynchronous operations in JavaScript using setTimeout or Promises?
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 would you reverse a string or an array using recursion?
How would you reverse a string or an array 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?
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?
Stop tag and share joins from fanning out a page
resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.
Approach
- Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
- Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
- Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
- Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.
Follow-up
- The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
- A resource can be shared with the same user twice under different permissions. Does your count change, and should it?
Explain the difference between Spring IOC and Dependency Injection.
Explain the difference between Spring IOC and Dependency Injection.
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 does Java Class Loading work, and why is it important in enterprise applications?
How does Java Class Loading work, and why is it important in enterprise applications?
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?
Describe the lifecycle of a Hibernate entity and how you handle database session management.
Describe the lifecycle of a Hibernate entity and how you handle database session management.
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 are the key advantages of using Microservices over a monolithic architecture?
What are the key advantages of using Microservices over a monolithic architecture?
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 the difference between a Controller, a Service, and a View in frontend frameworks like Angular?
What is the difference between a Controller, a Service, and a View in frontend frameworks like Angular?
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 best practices for manipulating the DOM using native JavaScript or jQuery.
Explain the best practices for manipulating the DOM using native JavaScript or jQuery.
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 optimize CSS and HTML for performance in complex web layouts?
How do you optimize CSS and HTML for performance in complex web layouts?
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 a system to handle high-concurrency requests in a distributed environment.
Design a system to handle high-concurrency requests in a distributed environment.
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?
One log partition stops advancing while the others drain
Search results for a subset of tenants are hours stale; the rest are current. The projection consumer reports lag of zero on 15 of 16 partitions and 400,000 on one. Its error rate is flat and its CPU is idle. outbox_event has no pending rows older than a second, so the relay has published everything it holds. Identify the mechanism, give the ordered checks, and state what you do in the first ten minutes versus what you change permanently.
Approach
- Read the lag distribution first. A slow consumer lags everywhere; zero on fifteen partitions and 400,000 on one is not throughput. Idle CPU on the stuck partition means the consumer is not advancing its offset at all, which points at one message it cannot get past rather than at a rate problem.
- Exonerate the producer before touching the consumer. No pending outbox rows older than a second means the relay published, so the event exists in the log. This separates never sent from sent and never applied, which are different code paths and usually different owners.
- Read the message at the stuck offset and the handler's log lines for its event_id. A flat error rate with no progress has two explanations and you must distinguish them: the handler is throwing and the retry loop is swallowing it, or the handler is blocking on something and never returning. Idle CPU with no error lines favours the second.
- Mitigate before diagnosing further. Move the offending event to a dead-letter store and commit the offset past it. Adding consumers does nothing here, because a partition is consumed by exactly one member of the group, and the blast radius is every aggregate hashed to that partition, not only the aggregate that produced the bad event.
Follow-up
- The dead-lettered event carried aggregate_version 7 and the projection had applied 6. What must the replay do differently if 8 and 9 landed in the meantime?
- How do you show staleness to the user while the partition is behind, given the API already returns the projection's watermark?
Built from the rounds and topics Nisum candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Nisum loop
- Write out the reported sequence: Initial Screening, Technical Assessments, Interpersonal Interviews, Client-Facing Interview, Final Decision-Making.
- 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 5 reported rounds, with the weakest marked.
02Work Java
- Spend the session on Java, which Nisum candidates report being tested on.
- Write one worked example in Java and time yourself on it.
Deliverable: One timed worked example in Java.
03Work Spring Boot
- Spend the session on Spring Boot, which Nisum candidates report being tested on.
- Write one worked example in Spring Boot and time yourself on it.
Deliverable: One timed worked example in Spring Boot.
04Work Coding Challenges / Programming Assessments
- Spend the session on Coding Challenges / Programming Assessments, which Nisum candidates report being tested on.
- Write one worked example in Coding Challenges / Programming Assessments and time yourself on it.
Deliverable: One timed worked example in Coding Challenges / Programming Assessments.
05Answer out loud: Core Java & Backend Development
- Answer aloud, timed: Explain the difference between Spring IOC and Dependency Injection.
- Answer aloud, timed: How does Java Class Loading work, and why is it important in enterprise applications?
Deliverable: Spoken answers to 2 reported Core Java & Backend Development question(s), under time.
06Answer out loud: Frontend & Web Technologies
- Answer aloud, timed: What is the difference between a Controller, a Service, and a View in frontend frameworks like Angular?
- Answer aloud, timed: How would you handle asynchronous operations in JavaScript using `setTimeout` or Promises?
Deliverable: Spoken answers to 2 reported Frontend & Web Technologies question(s), under time.
07Answer out loud: System Design & Problem Solving
- Answer aloud, timed: Design a system to handle high-concurrency requests in a distributed environment.
- Answer aloud, timed: How would you reverse a string or an array using recursion?
Deliverable: Spoken answers to 2 reported System Design & Problem Solving 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 a time you faced a difficult technical challenge; what was your approach to the solution?
Describe a time you faced a difficult technical challenge; what was your approach to the solution?
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?
Unblock an engineer without taking the keyboard
A teammate has spent two days on a job handler that occasionally writes duplicate rows. They are certain the queue is delivering twice by mistake. You suspect a lease expiring under a slow handler, so the job is running concurrently with itself. Describe how you have unblocked someone in this position: what you asked before offering a hypothesis, what you showed them rather than told them, and what you left them owning. Then say what you would do if their theory turned out to be the right one.
Approach
- Ask before diagnosing, and ask for things answerable from data they already have: the attempt count on the job rows that produced duplicates, the handler's observed duration against its lease expiry, and whether the duplicate rows share a natural key that a unique constraint could have caught.
- Teach the shape rather than the answer. A lease cannot distinguish a dead worker from a slow one, so a handler that outruns its lease is running twice by design, and deploys deliver the other half by killing handlers mid-run on every rollout. Both of their candidate theories produce identical duplicate rows, which is why the evidence has to come from timings rather than from argument.
- Hand over a checklist they execute: a natural key on every write the handler performs so the second copy collides rather than appends, the record of intent written before any external effect, a lease heartbeat while running, and the metric that shows it working.
- Keep ownership with them deliberately. Pair on the first write, then step back; if you finish it yourself you have closed one ticket and left the same person stuck on the next redelivery.
Follow-up
- How would you distinguish a genuine double-delivery from a lease expiry using only the data already stored?
- Their handler calls an external endpoint before recording that it did. What do you tell them to change first?
Estimate work you have never done and defend the range
You are asked to estimate a change you have never attempted: add a column to a 100-million-row table, populate it, move reads across, and drop the old shape. Give a range with the assumptions that generate it, including batch size, the signal your backfill throttles on, and wall-clock hours, and name the three unknowns that would move the number most. Then describe a real estimate you gave under comparable ignorance: how you expressed its uncertainty, what you committed to, and how wrong you turned out to be.
Approach
- Decompose into independently deployable steps before estimating anything: add the column nullable, write both shapes, backfill in batches, verify, move reads, stop writing the old shape, drop it. That is four deploys spread over days, and the calendar estimate is dominated by them rather than by the loop's runtime.
- Do the arithmetic aloud for the part that has arithmetic in it: batch size times number of batches times per-batch duration, at a write rate the primary can absorb alongside roughly 1.2k writes per second of production traffic. The loop is throttled by replication lag and lock waits, not by how fast it can issue statements.
- Price the schema step by its lock rather than its statement duration. In PostgreSQL an ALTER TABLE taking ACCESS EXCLUSIVE waits for every open transaction on that table while later queries queue behind it, so a millisecond change issued during a thirty-second analytics query stalls that table for thirty seconds. Adding a nullable column with a non-volatile default avoids a rewrite from version 11; a new index wants CREATE INDEX CONCURRENTLY, which cannot run inside a transaction block and leaves an invalid index behind if it fails.
- Express the answer as a range whose endpoints each trace to a stated assumption, then name the cheapest experiment that collapses it, which is almost always running one real batch against the real table and multiplying.
Follow-up
- How do you verify the backfill genuinely finished, given rows written by production traffic while it ran?
- Where does the backfill resume from after a worker is killed mid-batch, and what makes that resume point trustworthy?
- 01
Describe a time you faced a difficult technical challenge; what was your approach to the solution?
- 02
A teammate has spent two days on a job handler that occasionally writes duplicate rows. They are certain the queue is delivering twice by mistake. You suspect a lease expiring under a slow handler, so the job is running concurrently with itself. Describe how you have unblocked someone in this position: what you asked before offering a hypothesis, what you showed them rather than told them, and what you left them owning. Then say what you would do if their theory turned out to be the right one.
- 03
You are asked to estimate a change you have never attempted: add a column to a 100-million-row table, populate it, move reads across, and drop the old shape. Give a range with the assumptions that generate it, including batch size, the signal your backfill throttles on, and wall-clock hours, and name the three unknowns that would move the number most. Then describe a real estimate you gave under comparable ignorance: how you expressed its uncertainty, what you committed to, and how wrong you turned out to be.
How difficult are the technical interviews?
Difficulty varies, but the process is generally moderate. Most rounds focus on practical application rather than "trick" questions; focus on mastering the fundamentals of your primary language and common design patterns.
Nisum Software Engineer candidate reports ↗What is the typical timeline for the process?
While some candidates experience a single-day process, others may wait several weeks due to client-side scheduling. Remain patient and prepared for variations in the timeline.
Nisum Software Engineer candidate reports ↗Does Nisum require a degree?
Educational background is valued, especially for certain client portfolios where a degree may be a prerequisite. Emphasize your academic and professional achievements clearly.
Nisum Software Engineer candidate reports ↗What topics does Nisum test in interviews?
Nisum interviews most often cover Java, Problem Solving, JavaScript, Agile Methodology, and Object-Oriented Programming (OOP). The exact emphasis depends on the specific role you apply for.
Nisum 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.
- 01Nisum 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.
GitHub Software Engineer Interview Questions & Guide 2026
Testing exercises for GitHub software engineer prep: choosing boundary cases over repetition, isolating tests from shared clock and ordering, and treating an intermittent failure as a defect rather than noise.
Zoom Communications Software Engineer Interview Guide
What Zoom Communications asks Software Engineer candidates, from reported rounds and questions.
Zemoso Technologies Software Engineer Interview Guide
What Zemoso Technologies asks Software Engineer candidates, from reported rounds and questions.
YASH Technologies Software Engineer Interview Guide
What YASH Technologies asks Software Engineer candidates, from reported rounds and questions.