cswork / libraryOpen practice workspace

Interview guides · Nexlogica

Nexlogica Software Engineer Interview Guide

Nexlogica Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

At Nexlogica, a Software Engineer plays a pivotal role in designing, modernizing, and maintaining critical enterprise infrastructure. Rather than working on a single SaaS product, engineers here are aligned with specialized technology stacks that support complex, large-scale systems for enterprise clients, healthcare networks, and public sector organizations. Your work will directly impact millions of end-users who rely on the stability, security, and efficiency of these mission-critical applications. The engineering landscape at Nexlogica is uniquely diverse. Depending on your alignment, you may find yourself architecting modern cloud solutions using.NET or Power Apps, customizing enterprise portals with Adobe Experience Manager (AEM) and Salesforce, or maintaining and modernizing robust legacy systems running on Mainframe/COBOL and HP3000 architectures.

This guide is scoped to a Software Engineer candidate at Nexlogica.

Focus areas

  • .NET (C#/.NET Framework/.NET Core/modern.NET)
  • Database Administration (DBA)
  • COBOL

The Nexlogica interview process

Nexlogica candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Initial Conversation

Discussion with a talent acquisition partner to align on background, career goals, and technology track.

What to demonstrate

  • Discussion with a talent acquisition partner to align on background, career goals, and technology track
  • Depth in .NET (C#/.NET Framework/.NET Core/modern.NET)

How to prepare

  • Answer aloud and timed: How would you design a secure, high-throughput API layer to connect a modern cloud frontend with a legacy mainframe backend?
  • Answer aloud and timed: Describe your approach to database normalization versus denormalization in high-transaction enterprise applications.

Technical Evaluations

Includes a deep-dive technical discussion with senior engineers and a scenario-based architectural review.

What to demonstrate

  • Includes a deep-dive technical discussion with senior engineers and a scenario-based architectural review
  • Depth in .NET (C#/.NET Framework/.NET Core/modern.NET)

How to prepare

  • Answer aloud and timed: How do you handle state management and caching in a distributed system to ensure high availability?
  • Answer aloud and timed: Explain how you would architect a disaster recovery and data replication strategy for a mission-critical database.

Behavioral Interview

Focus on collaboration, delivery, and culture fit.

What to demonstrate

  • Focus on collaboration, delivery, and culture fit
  • Depth in .NET (C#/.NET Framework/.NET Core/modern.NET)

How to prepare

  • Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
  • Re-read the description of the behavioral interview above and write down what you would ask to confirm before it.

Where candidates lose points

Align with the Client Mindset

Many of Nexlogica's projects support public sector, healthcare, or enterprise clients. Show that you understand the importance of compliance, security, and minimal operational disruption in these environments.

Be Honest About Your Technical Boundaries

If you encounter a question about a technology or framework you haven't worked with, be upfront about it. Explain how you would go about researching and learning it, rather than trying to guess.

Use the STAR Method for Behavioral Questions

When answering situational questions, structure your responses using the Situation, Task, Action, and Result framework. Be specific about your individual contribution and the business impact of your work.

Questions & practice

How do you optimize batch processing jobs on a Mainframe/COBOL system to minimize CPU usage and runtime?

Medium · Platform-Specific & Domain Technical Que

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. 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?

Collapse a redelivered event batch into per-aggregate high-water marks

Easy · hashing · at-least-once · aggregation

You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.

Approach

  1. One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
  2. Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
  3. Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
  4. If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.

Follow-up

  • The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
  • How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?

Merge partitioned event streams into one ordered feed with bounded lateness

Hard · k-way merge · watermarks · out-of-order streams

The read-model service consumes 64 log partitions carrying about 4,000 events per second in total. Each partition is ordered within itself, but partitions drift by up to 30 seconds, and the activity feed must present a tenant's events in occurred_at order. Produce the merge. State its complexity, the buffer it requires in events and in bytes, what happens when one partition is idle, and what you do with an event that arrives after you have already emitted its position. Payloads average 1 KB.

Approach

  1. Merge with a min-heap over the 64 partition heads keyed on (occurred_at, event_id): O(log P) per event and O(n log P) overall. The tie-break on event_id is what makes the output deterministic when two partitions carry the same millisecond, which matters because the feed is paginated and a non-deterministic order reorders pages under the reader.
  2. Emitting the heap head is only correct once every partition has produced everything up to that timestamp, so the emit condition is a watermark: the minimum across partitions of the highest occurred_at seen, less the allowed lateness. Events are held until the watermark passes them, which is what turns individually ordered streams into a jointly ordered one.
  3. Size the buffer from the lateness rather than guessing: 4,000 events per second times 30 seconds is 120,000 buffered events, and at 1 KB each about 120 MB of heap. That number is the real price of the ordering guarantee and belongs in front of whoever asked for it.
  4. Handle the idle partition explicitly, because it fails the feed rather than corrupting it: a partition with no traffic never advances its own maximum, so the watermark freezes and output stops entirely. Either every partition emits a periodic idle marker carrying the broker's current time, or the watermark falls back to wall clock for a partition silent beyond a threshold.

Follow-up

  • The lateness budget is raised to five minutes. What is the new buffer, and what besides memory changes?
  • The consumer restarts. Where does it resume from, and what does the feed look like for the first 30 seconds?

Describe your approach to database normalization versus denormalization in high-transaction enterprise applica

Medium · Architecture & System Design

Describe your approach to database normalization versus denormalization in high-transaction enterprise applications.

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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?

Describe how you would configure a custom canvas app in Power Apps to write data back to an on-premises SQL Se

Medium · Platform-Specific & Domain Technical Que

Describe how you would configure a custom canvas app in Power Apps to write data back to an on-premises SQL Server via an enterprise gateway.

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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?

How would you design a secure, high-throughput API layer to connect a modern cloud frontend with a legacy main

Medium · Architecture & System Design

How would you design a secure, high-throughput API layer to connect a modern cloud frontend with a legacy mainframe backend?

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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?

How do you handle state management and caching in a distributed system to ensure high availability?

Medium · Architecture & System Design

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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?

Explain how you would architect a disaster recovery and data replication strategy for a mission-critical datab

Medium · Architecture & System Design

Explain how you would architect a disaster recovery and data replication strategy for a mission-critical database.

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 strategies do you use to secure sensitive data both at rest and in transit within an enterprise applicati

Medium · Architecture & System Design

What strategies do you use to secure sensitive data both at rest and in transit within an enterprise application?

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

In a.NET environment, what is the difference between deferred execution and immediate execution in LINQ, and w

Medium · Platform-Specific & Domain Technical Que

In a.NET environment, what is the difference between deferred execution and immediate execution in LINQ, and when would you use each?

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

In AEM, explain the relationship between Sightly (HTL), Sling Models, and JCR nodes.

Medium · Platform-Specific & Domain Technical Que

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Listing latency scales with page size, not with filters

Easy · n+1 · latency · query batching

The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.

Approach

  1. Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
  2. Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
  3. Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
  4. Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.

Follow-up

  • The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
  • How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?

Suggested practice checklist

Built from the rounds and topics Nexlogica candidates report.

Day 1 — Map the Nexlogica loop

  • Write out the reported sequence: Initial Conversation, Technical Evaluations, Behavioral 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 3 reported rounds, with the weakest marked.

Day 2 — Work .NET (C#/.NET Framework/.NET Core/modern.NET)

  • Spend the session on .NET (C#/.NET Framework/.NET Core/modern.NET), which Nexlogica candidates report being tested on.
  • Write one worked example in .NET (C#/.NET Framework/.NET Core/modern.NET) and time yourself on it.

Deliverable: One timed worked example in .NET (C#/.NET Framework/.NET Core/modern.NET).

Day 3 — Work Database Administration (DBA)

  • Spend the session on Database Administration (DBA), which Nexlogica candidates report being tested on.
  • Write one worked example in Database Administration (DBA) and time yourself on it.

Deliverable: One timed worked example in Database Administration (DBA).

Day 4 — Work COBOL

  • Spend the session on COBOL, which Nexlogica candidates report being tested on.
  • Write one worked example in COBOL and time yourself on it.

Deliverable: One timed worked example in COBOL.

Day 5 — Answer out loud: Architecture & System Design

  • Answer aloud, timed: How would you design a secure, high-throughput API layer to connect a modern cloud frontend with a legacy mainframe backend?
  • Answer aloud, timed: Describe your approach to database normalization versus denormalization in high-transaction enterprise applications.

Deliverable: Spoken answers to 2 reported Architecture & System Design question(s), under time.

Day 6 — Answer out loud: Platform-Specific & Domain Technical Questions

  • Answer aloud, timed: In a.NET environment, what is the difference between deferred execution and immediate execution in LINQ, and when would you use each?
  • Answer aloud, timed: For Salesforce development, how do you handle governor limits when writing custom Apex triggers and batch classes?

Deliverable: Spoken answers to 2 reported Platform-Specific & Domain Technical Questions question(s), under time.

Day 7 — Answer out loud: Behavioral & Client Delivery

  • Answer aloud, timed: Describe a time when you had to work with a highly complex legacy codebase that lacked documentation. How did you navigate it?
  • Answer aloud, timed: How do you handle a situation where a client or stakeholder requests a feature that conflicts with technical best practices or system stability?

Deliverable: Spoken answers to 2 reported Behavioral & Client Delivery question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

For Salesforce development, how do you handle governor limits when writing custom Apex triggers and batch clas

Medium · Platform-Specific & Domain Technical Que

For Salesforce development, how do you handle governor limits when writing custom Apex triggers and batch classes?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?

Describe a time when you had to work with a highly complex legacy codebase that lacked documentation. How did

Medium · Behavioral & Client Delivery

Describe a time when you had to work with a highly complex legacy codebase that lacked documentation. How did you navigate it?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 a situation where a client or stakeholder requests a feature that conflicts with technical b

Medium · Behavioral & Client Delivery

How do you handle a situation where a client or stakeholder requests a feature that conflicts with technical best practices or system stability?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?

Tell me about a time you had to collaborate with a cross-functional team (such as network engineers or databas

Medium · Behavioral & Client Delivery

Tell me about a time you had to collaborate with a cross-functional team (such as network engineers or database administrators) to resolve a critical production outage.

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 prioritize technical debt when working under tight project deadlines?

Medium · Behavioral & Client Delivery

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?

Give an example of how you translated a complex technical limitation into business-friendly language for a non

Medium · Behavioral & Client Delivery

Give an example of how you translated a complex technical limitation into business-friendly language for a non-technical stakeholder.

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?