Interview guides · KeyLogic
KeyLogic Software Engineer Interview Guide
KeyLogic Software Engineer interview guide: reported rounds, questions and how candidates describe the process.
The 60-second brief
As a Software Engineer at KeyLogic, you play a pivotal role in designing, building, and maintaining robust software solutions that drive critical government and commercial operations. This position sits at the intersection of technical innovation and mission-critical reliability, requiring you to translate complex system requirements into scalable, high-performing applications. Whether you are developing enterprise workflows on platforms like ServiceNow, engineering real-time systems, or supporting advanced engineering domains, your work directly impacts operational efficiency and strategic outcomes for end users. The scope of this role at KeyLogic encompasses diverse technical environments, ranging from cloud-based platforms and custom application development to systems programming and hardware-software integration.
This guide is scoped to a Software Engineer candidate at KeyLogic.
Focus areas
- ServiceNow Development
- Software Engineering
- Guidance, Navigation, and Control (GN&C)
The KeyLogic interview process
KeyLogic candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.
Recruiter Screening
Initial conversation to discuss your professional background, compensation expectations, and alignment with the company.
What to demonstrate
- Initial conversation to discuss your professional background, compensation expectations, and alignment with the company
- Depth in ServiceNow Development
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 Evaluation
Includes remote technical assessments and deep-dive discussions with senior engineers.
What to demonstrate
- Includes remote technical assessments and deep-dive discussions with senior engineers
- Depth in ServiceNow Development
How to prepare
- Answer aloud and timed: Explain how you handle platform upgrades and manage update sets across multiple development, test, and production environments.
- Answer aloud and timed: How do you integrate third-party applications and external APIs with enterprise platforms securely and reliably?
Interviews with Hiring Managers
Final interviews focused on assessing your coding capabilities, system design skills, and cultural fit.
What to demonstrate
- Final interviews focused on assessing your coding capabilities, system design skills, and cultural fit
- Depth in ServiceNow Development
How to prepare
- Prepare two projects you led end to end, each with the decision you owned and what it cost.
- Have three questions about the team's roadmap and how success is measured in the first six months.
Where candidates lose points
Structure your answers
Use a clear, methodical framework when answering technical or behavioral questions, stating your assumptions and breaking down complex problems into manageable steps.
Highlight impact
Whenever you discuss past projects, emphasize the quantifiable business value, performance improvements, or operational efficiencies your code delivered.
Be ready for trade-off discussions
Interviewers frequently probe into why you chose a specific design pattern or configuration approach over alternatives, so be prepared to defend your technical decisions.
Communicate your thought process
Never sit in silence while working through a coding or design problem; talk through your ideas so the interviewer can follow your reasoning.
Align with company values
Emphasize qualities like accountability, teamwork, and a dedication to quality, which are highly valued across all engineering teams at KeyLogic.
Questions & practice
How do you handle concurrency, multithreading, or asynchronous operations in your preferred programming langua
Medium · Software Engineering Fundamentals
How do you handle concurrency, multithreading, or asynchronous operations in your preferred programming languages?
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 you approach monitoring system health, logging errors, and diagnosing runtime exceptions in a productio
Medium · Systems Programming and Operations
How do you approach monitoring system health, logging errors, and diagnosing runtime exceptions in a production environment?
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?
Archive a resource graph without breaking live references or recursing
Medium · graph traversal · topological order · tenant isolation
Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.
Approach
- Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
- Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
- Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
- Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.
Follow-up
- The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
- The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?
Hold a per-tenant active cap against concurrent creates
Hard · write skew · isolation levels · constraints
A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.
Approach
- Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
- Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
- Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
- State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.
Follow-up
- A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
- The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?
Find version gaps and relay lag with window functions
Medium · window functions · event tables · frame semantics
outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.
Approach
- Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
- Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
- Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
- Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.
Follow-up
- Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
- Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?
How do you approach writing clean, efficient server-side scripts, business rules, or client scripts while main
Medium · Platform Development and Customization
How do you approach writing clean, efficient server-side scripts, business rules, or client scripts while maintaining system performance?
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 how you handle platform upgrades and manage update sets across multiple development, test, and product
Medium · Platform Development and Customization
Explain how you handle platform upgrades and manage update sets across multiple development, test, and production environments.
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 integrate third-party applications and external APIs with enterprise platforms securely and reliabl
Medium · Platform Development and Customization
How do you integrate third-party applications and external APIs with enterprise platforms securely and reliably?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- 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?
What design patterns do you rely on most frequently when building scalable software architectures, and why?
Medium · Software Engineering Fundamentals
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?
How do you approach unit testing, integration testing, and automated deployment pipelines in your daily develo
Medium · Software Engineering Fundamentals
How do you approach unit testing, integration testing, and automated deployment pipelines in your daily development workflow?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- 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?
What strategies do you use for effective version control branching and managing collaborative codebases in a t
Medium · Software Engineering Fundamentals
What strategies do you use for effective version control branching and managing collaborative codebases in a team environment?
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?
Can you explain your process for securing application endpoints and managing sensitive user authentication or
Medium · Systems Programming and Operations
Can you explain your process for securing application endpoints and managing sensitive user authentication or authorization data?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- 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 ensure high availability and disaster recovery readiness for mission-critical software systems?
Medium · Systems Programming and Operations
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?
Walk through a scenario where you had to troubleshoot a critical performance bottleneck in a custom workflow o
Medium · Platform Development and Customization
Walk through a scenario where you had to troubleshoot a critical performance bottleneck in a custom workflow or application module.
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?
Walk through how you would diagnose a sudden memory leak or resource exhaustion issue in a deployed applicatio
Medium · Systems Programming and Operations
Walk through how you would diagnose a sudden memory leak or resource exhaustion issue in a deployed application.
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?
Suggested practice checklist
Built from the rounds and topics KeyLogic candidates report.
Day 1 — Map the KeyLogic loop
- Write out the reported sequence: Recruiter Screening, Technical Evaluation, Interviews with Hiring Managers.
- 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 ServiceNow Development
- Spend the session on ServiceNow Development, which KeyLogic candidates report being tested on.
- Write one worked example in ServiceNow Development and time yourself on it.
Deliverable: One timed worked example in ServiceNow Development.
Day 3 — Work Software Engineering
- Spend the session on Software Engineering, which KeyLogic 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 4 — Work Guidance, Navigation, and Control (GN&C)
- Spend the session on Guidance, Navigation, and Control (GN&C), which KeyLogic candidates report being tested on.
- Write one worked example in Guidance, Navigation, and Control (GN&C) and time yourself on it.
Deliverable: One timed worked example in Guidance, Navigation, and Control (GN&C).
Day 5 — Answer out loud: Platform Development and Customization
- Answer aloud, timed: Can you describe your experience configuring and customizing enterprise platform modules, such as ServiceNow, to meet complex business requirements?
- Answer aloud, timed: How do you approach writing clean, efficient server-side scripts, business rules, or client scripts while maintaining system performance?
Deliverable: Spoken answers to 2 reported Platform Development and Customization question(s), under time.
Day 6 — Answer out loud: Software Engineering Fundamentals
- Answer aloud, timed: What design patterns do you rely on most frequently when building scalable software architectures, and why?
- Answer aloud, timed: How do you approach unit testing, integration testing, and automated deployment pipelines in your daily development workflow?
Deliverable: Spoken answers to 2 reported Software Engineering Fundamentals question(s), under time.
Day 7 — Answer out loud: Systems Programming and Operations
- Answer aloud, timed: How do you approach monitoring system health, logging errors, and diagnosing runtime exceptions in a production environment?
- Answer aloud, timed: Can you explain your process for securing application endpoints and managing sensitive user authentication or authorization data?
Deliverable: Spoken answers to 2 reported Systems Programming and Operations question(s), under time.
Behavioural preparation
Behavioural rounds judge the decision you made and what it cost.
Can you describe your experience configuring and customizing enterprise platform modules, such as ServiceNow,
Medium · Platform Development and Customization
Can you describe your experience configuring and customizing enterprise platform modules, such as ServiceNow, to meet complex business 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?
Describe a time when you had to refactor legacy code to improve readability, performance, and maintainability.
Medium · Software Engineering Fundamentals
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?
Describe your experience working with relational and non-relational databases, including schema design and que
Medium · Systems Programming and Operations
Describe your experience working with relational and non-relational databases, including schema design and query optimization.
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 manage competing priorities when balancing feature development requests with critical bug fixes and
Medium · Behavioral and Collaboration
How do you manage competing priorities when balancing feature development requests with critical bug fixes and technical debt?
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?
Describe a situation where you had to explain a complex technical problem to a non-technical stakeholder or cl
Medium · Behavioral and Collaboration
Describe a situation where you had to explain a complex technical problem to a non-technical stakeholder or client.
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?
Tell me about a time when you disagreed with a teammate on an architectural decision. How did you resolve the
Medium · Behavioral and Collaboration
Tell me about a time when you disagreed with a teammate on an architectural decision. How did you resolve the conflict?
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 stay current with emerging software engineering trends, tools, and platform updates?
Medium · Behavioral and Collaboration
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 build your career at KeyLogic, and how do your professional goals align with our mission?
Medium · Behavioral and Collaboration
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?