Infor Software Engineer Interview Guide

The 60-second brief

As a Software Engineer at Infor, you are at the heart of building industry-specific cloud applications that power the world’s largest enterprises. You aren't just writing code; you are solving complex, real-world business challenges—from supply chain optimization and financial reconciliation to manufacturing efficiency. Your work directly impacts how organizations manage their data, operations, and resources on a global scale. The role demands a balance of deep technical proficiency and a pragmatic, business-first mindset. Because Infor operates within specialized sectors, you will often find yourself working on high-impact projects that require not only strong software development fundamentals but also an ability to understand the underlying architecture of enterprise-grade systems.

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

Focus areas

• Data Structures & Algorithms (DSA)
• Coding Practice (Write Code / Simple Programs)
• Resume-Based Technical Interview (Explaining Projects & Skil

The Infor interview process

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

Recruiter Screening

Initial screening conducted by a recruiter to assess candidate fit and qualifications.

What to demonstrate

• Initial screening conducted by a recruiter to assess candidate fit and qualifications
• Depth in Data Structures & Algorithms (DSA)

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

One or more technical assessments or interviews to evaluate technical skills and knowledge.

What to demonstrate

• One or more technical assessments or interviews to evaluate technical skills and knowledge
• Depth in Data Structures & Algorithms (DSA)

How to prepare

• Answer aloud and timed: What are the key features of OOP, and can you provide real-time examples of encapsulation and polymorphism?
• Answer aloud and timed: Explain the difference between ArrayList and LinkedList.

Managerial Discussion

Final round discussion with a manager focusing on past project work and team fit.

What to demonstrate

• Final round discussion with a manager focusing on past project work and team fit
• Depth in Data Structures & Algorithms (DSA)

How to prepare

• Answer aloud and timed: Describe the core concepts of SQL, including joins, indexing, and stored procedures.
• Answer aloud and timed: Find the missing and repeating numbers in an array.

Where candidates lose points

Own your resume

Every line on your resume is fair game. If you list a skill, be prepared to discuss it in depth.

Practice communication

Focus on being articulate. Even if you have the right technical answer, the ability to explain it clearly is what differentiates top candidates.

Prepare for "What-If" scenarios

Think about how you would handle production bugs or shifting project requirements.

Be professional but authentic

Infor interviewers generally appreciate candidates who are humble, professional, and genuinely curious about the technology they are building.

Questions & practice

How do you handle memory management and garbage collection in Java?

Medium · Technical & Core CS Concepts

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?

Find the missing and repeating numbers in an array.

Medium · Coding & Problem Solving

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Detect a cycle in a linked list.

Medium · Coding & Problem Solving

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Implement basic sorting algorithms or string manipulation (e.g., reversing a string).

Medium · Coding & Problem Solving

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Describe the core concepts of SQL, including joins, indexing, and stored procedures.

Medium · Technical & Core CS Concepts

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?

Write a SQL query to solve a specific data retrieval problem.

Medium · Coding & Problem Solving

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?

Explain the difference between an interface and an abstract class in Java.

Medium · Technical & Core CS Concepts

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?

What are the key features of OOP, and can you provide real-time examples of encapsulation and polymorphism?

Medium · Technical & Core CS Concepts

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?

Explain the difference between ArrayList and LinkedList.

Medium · Technical & Core CS Concepts

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?

Explain your approach to refactoring legacy code or optimizing API performance.

Medium · Coding & Problem Solving

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?

One log partition stops advancing while the others drain

Easy · poison message · head-of-line blocking · consumer lag

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

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

Suggested practice checklist

Built from the rounds and topics Infor candidates report.

Day 1 — Map the Infor loop

• Write out the reported sequence: Recruiter Screening, Technical Assessments, Managerial Discussion.
• 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 Data Structures & Algorithms (DSA)

• Spend the session on Data Structures & Algorithms (DSA), which Infor candidates report being tested on.
• Write one worked example in Data Structures & Algorithms (DSA) and time yourself on it.

Deliverable: One timed worked example in Data Structures & Algorithms (DSA).

Day 3 — Work Coding Practice (Write Code / Simple Programs)

• Spend the session on Coding Practice (Write Code / Simple Programs), which Infor candidates report being tested on.
• Write one worked example in Coding Practice (Write Code / Simple Programs) and time yourself on it.

Deliverable: One timed worked example in Coding Practice (Write Code / Simple Programs).

Day 4 — Work Resume-Based Technical Interview (Explaining Projects & Skills)

• Spend the session on Resume-Based Technical Interview (Explaining Projects & Skills), which Infor candidates report being tested on.
• Write one worked example in Resume-Based Technical Interview (Explaining Projects & Skills) and time yourself on it.

Deliverable: One timed worked example in Resume-Based Technical Interview (Explaining Projects & Skills).

Day 5 — Answer out loud: Technical & Core CS Concepts

• Answer aloud, timed: Explain the difference between an interface and an abstract class in Java.
• Answer aloud, timed: How do you handle memory management and garbage collection in Java?

Deliverable: Spoken answers to 2 reported Technical & Core CS Concepts question(s), under time.

Day 6 — Answer out loud: Coding & Problem Solving

• Answer aloud, timed: Find the missing and repeating numbers in an array.
• Answer aloud, timed: Detect a cycle in a linked list.

Deliverable: Spoken answers to 2 reported Coding & Problem Solving question(s), under time.

Day 7 — Answer out loud: Behavioral & Leadership

• Answer aloud, timed: Describe a difficult situation you encountered in a project and how you resolved it.
• Answer aloud, timed: How do you handle disagreements within a technical team?

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

Behavioural preparation

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

Describe a difficult situation you encountered in a project and how you resolved it.

Medium · Behavioral & Leadership

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 disagreements within a technical team?

Medium · Behavioral & Leadership

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?

If you were given a specific budget or resource, how would you prioritize tasks for a project?

Medium · Behavioral & Leadership

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 us about a time you had to learn a new technology on the fly to complete a task.

Medium · Behavioral & Leadership

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 feedback from a senior developer or manager regarding your code?

Medium · Behavioral & Leadership

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?