cswork / libraryOpen practice workspace

Interview guides · NetImpact Strategies

NetImpact Strategies Software Engineer Interview Guide

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

The 60-second brief

At NetImpact Strategies, a Software Engineer plays a pivotal role in driving digital transformation and IT modernization across various mission-critical environments, particularly within the federal and public sectors. You will be responsible for designing, developing, and deploying robust software solutions that solve complex operational challenges. The engineering team focuses on building secure, scalable, and highly available applications that directly impact public services and enterprise-level operations. This role is highly dynamic, spanning multiple modern technology stacks and platforms. Whether you are developing enterprise applications in Java and.NET, building cloud-native solutions on AWS, managing enterprise content with Drupal, or modernizing workflows within the ServiceNow ecosystem, your work will directly influence how organizations operate.

This guide is scoped to a Software Engineer candidate at NetImpact Strategies.

Focus areas

  • Software Engineering
  • Full-Stack Development
  • AWS Cloud Services

The NetImpact Strategies interview process

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

Initial Conversation

Initial phone screen with a recruiter focusing on background, technical experience, and role alignment.

What to demonstrate

  • Initial phone screen with a recruiter focusing on background, technical experience, and role alignment
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: Explain the differences between abstract classes and interfaces in Java or C#, and when you would choose one over the other.
  • Answer aloud and timed: How do you manage dependency injection in a.NET Core or Spring Boot application, and what are the primary benefits?

Resume Review

Hiring team conducts a detailed review of your resume after the initial screen.

What to demonstrate

  • Hiring team conducts a detailed review of your resume after the initial screen
  • Depth in Software Engineering

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.

Panel Interview

Core evaluation with a panel of three to four stakeholders assessing technical depth and behavioral alignment.

What to demonstrate

  • Core evaluation with a panel of three to four stakeholders assessing technical depth and behavioral alignment
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: Explain the MVC architecture and how you decouple business logic from the presentation layer.
  • Answer aloud and timed: Describe a scenario where you had to migrate an on-premise application to AWS. What services did you use, and how did you minimize downtime?

Follow-up Conversations

Additional discussions may occur, particularly for candidates transitioning into specialized platforms.

What to demonstrate

  • Additional discussions may occur, particularly for candidates transitioning into specialized platforms
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: What are the differences between AWS Lambda and EC2, and how do you decide which compute option is appropriate for a microservice?
  • Answer aloud and timed: How do you secure application secrets and API keys in a cloud-native AWS environment?

Where candidates lose points

Highlight federal or public sector experience

If you have worked on federal contracts, understand compliance standards (like Section 508 accessibility), or hold an active security clearance, make sure to highlight this early in your conversations.

Prepare for a diverse panel

Your panel interviewers will have varying levels of technical expertise. Practice explaining your technical achievements in a way that highlights business value for project managers, while still providing enough depth for senior engineers.

Be ready to discuss platform adaptability

Show enthusiasm for learning new platforms. If you are a.NET developer, express your willingness to apply those architectural concepts to cloud-native AWS environments or enterprise workflow platforms like ServiceNow.

Questions & practice

Explain the differences between abstract classes and interfaces in Java or C#, and when you would choose one o

Medium · Full-Stack & Language-Specific Developme

Explain the differences between abstract classes and interfaces in Java or C#, and when you would choose one over the other.

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?

How do you manage dependency injection in a.NET Core or Spring Boot application, and what are the primary bene

Medium · Full-Stack & Language-Specific Developme

How do you manage dependency injection in a.NET Core or Spring Boot application, and what are the primary benefits?

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?

Stop tag and share joins from fanning out a page

Medium · join fan-out · semi-joins · many-to-many

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

  1. 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.
  2. 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.
  3. 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.
  4. 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?

Keep soft-deleted accounts from blocking re-registration

Easy · soft delete · unique constraints · engine differences

app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.

Approach

  1. Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
  2. Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
  3. For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
  4. State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.

Follow-up

  • A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
  • How do you honour an erasure request while resource_revision.actor_user_id still references this table?

Explain the MVC architecture and how you decouple business logic from the presentation layer.

Medium · Full-Stack & Language-Specific Developme

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?

Describe a scenario where you had to migrate an on-premise application to AWS. What services did you use, and

Medium · Cloud & Infrastructure

Describe a scenario where you had to migrate an on-premise application to AWS. What services did you use, and how did you minimize downtime?

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 are the differences between AWS Lambda and EC2, and how do you decide which compute option is appropriate

Medium · Cloud & Infrastructure

What are the differences between AWS Lambda and EC2, and how do you decide which compute option is appropriate for a microservice?

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 secure application secrets and API keys in a cloud-native AWS environment?

Medium · Cloud & Infrastructure

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?

How do you design an application to be highly available and fault-tolerant across multiple AWS Availability Zo

Medium · Cloud & Infrastructure

How do you design an application to be highly available and fault-tolerant across multiple AWS Availability Zones?

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?

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 NetImpact Strategies candidates report.

Day 1 — Map the NetImpact Strategies loop

  • Write out the reported sequence: Initial Conversation, Resume Review, Panel Interview, Follow-up Conversations.
  • 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.

Day 2 — Work Software Engineering

  • Spend the session on Software Engineering, which NetImpact Strategies candidates report being tested on.
  • Write one worked example in Software Engineering and time yourself on it.

Deliverable: One timed worked example in Software Engineering.

Day 3 — Work Full-Stack Development

  • Spend the session on Full-Stack Development, which NetImpact Strategies candidates report being tested on.
  • Write one worked example in Full-Stack Development and time yourself on it.

Deliverable: One timed worked example in Full-Stack Development.

Day 4 — Work AWS Cloud Services

  • Spend the session on AWS Cloud Services, which NetImpact Strategies candidates report being tested on.
  • Write one worked example in AWS Cloud Services and time yourself on it.

Deliverable: One timed worked example in AWS Cloud Services.

Day 5 — Answer out loud: Full-Stack & Language-Specific Development

  • Answer aloud, timed: Explain the differences between abstract classes and interfaces in Java or C#, and when you would choose one over the other.
  • Answer aloud, timed: How do you manage dependency injection in a.NET Core or Spring Boot application, and what are the primary benefits?

Deliverable: Spoken answers to 2 reported Full-Stack & Language-Specific Development question(s), under time.

Day 6 — Answer out loud: Cloud & Infrastructure

  • Answer aloud, timed: Describe a scenario where you had to migrate an on-premise application to AWS. What services did you use, and how did you minimize downtime?
  • Answer aloud, timed: What are the differences between AWS Lambda and EC2, and how do you decide which compute option is appropriate for a microservice?

Deliverable: Spoken answers to 2 reported Cloud & Infrastructure question(s), under time.

Day 7 — Answer out loud: Behavioral & Stakeholder Collaboration

  • Answer aloud, timed: Tell me about a time when you had to work with a stakeholder who had conflicting technical requirements. How did you resolve it?
  • Answer aloud, timed: Describe a situation where you had to learn a new framework or technology quickly to meet a project deadline.

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

Behavioural preparation

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

Describe your experience with state management on the front end. How do you ensure optimal performance when re

Medium · Full-Stack & Language-Specific Developme

Describe your experience with state management on the front end. How do you ensure optimal performance when rendering large datasets?

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 asynchronous programming in your language of choice, and what are the common pitfalls to avo

Medium · Full-Stack & Language-Specific Developme

How do you handle asynchronous programming in your language of choice, and what are the common pitfalls to avoid?

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?

Explain your experience with infrastructure as code (IaC) tools like Terraform or CloudFormation.

Medium · Cloud & Infrastructure

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 when you had to work with a stakeholder who had conflicting technical requirements. How d

Medium · Behavioral & Stakeholder Collaboration

Tell me about a time when you had to work with a stakeholder who had conflicting technical requirements. How did you resolve 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?

Describe a situation where you had to learn a new framework or technology quickly to meet a project deadline.

Medium · Behavioral & Stakeholder Collaboration

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 code reviews when you disagree with a peer's architectural approach?

Medium · Behavioral & Stakeholder Collaboration

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 identified a critical bug or performance bottleneck in production. How did you addres

Medium · Behavioral & Stakeholder Collaboration

Tell me about a time you identified a critical bug or performance bottleneck in production. How did you address it and prevent it from happening again?

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?