cswork / libraryOpen practice workspace

Interview guides · Sunbelt Controls

Sunbelt Controls Software Engineer Interview Guide

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

The 60-second brief

At Sunbelt Controls, a Software Engineer—more commonly designated internally as a Systems Software Engineer or Controls Design Engineer—occupies a highly specialized role at the convergence of software development, mechanical systems, and smart building technology. Unlike traditional software roles focused on SaaS or web applications, your work here directly impacts the physical world. You will design, program, and integrate Building Automation Systems (BAS) that control HVAC, lighting, and energy management systems for massive, mission-critical facilities. The systems you program are the brains behind modern, energy-efficient infrastructure. From data centers and healthcare complexes to biotech laboratories and commercial high-rises, your databases, custom graphical user interfaces, and control logic ensure optimal environmental conditions and minimized operational costs.

This guide is scoped to a Software Engineer candidate at Sunbelt Controls.

Focus areas

  • Building Automation Systems (BAS)
  • Control System Programming (Databases)
  • Commissioning

The Sunbelt Controls interview process

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

Initial Conversation

Begin with a conversational discussion about your background and experiences.

What to demonstrate

  • Begin with a conversational discussion about your background and experiences
  • Depth in Building Automation Systems (BAS)

How to prepare

  • Answer aloud and timed: Can you walk me through your experience with Building Automation Systems (BAS) and what drew you to this field?
  • Answer aloud and timed: Describe a time when you had to learn a new tool or system quickly to complete a project. What was your approach?

Technical Capabilities Discussion

Engage in discussions centered on your practical technical skills and familiarity with controls.

What to demonstrate

  • Engage in discussions centered on your practical technical skills and familiarity with controls
  • Depth in Building Automation Systems (BAS)

How to prepare

  • Answer aloud and timed: How do you prioritize your tasks when managing multiple project deadlines simultaneously?
  • Answer aloud and timed: Talk about a project where you had to work closely with a client or subcontractor. How did you ensure clear communication?

Collaboration Assessment

Evaluate your communication style and ability to collaborate with technicians in the field.

What to demonstrate

  • Evaluate your communication style and ability to collaborate with technicians in the field
  • Depth in Building Automation Systems (BAS)

How to prepare

  • Answer aloud and timed: How would you diagnose a communication loss between a controller and the main BAS server?
  • Answer aloud and timed: Explain the difference between BACnet IP and BACnet MS/TP.

Final Offer Stage

Conclude the process with a discussion regarding the job offer.

What to demonstrate

  • Conclude the process with a discussion regarding the job offer
  • Depth in Building Automation Systems (BAS)

How to prepare

  • Answer aloud and timed: What is your experience with configuring IP addresses, subnets, and default gateways on a local network?
  • Answer aloud and timed: How do you approach database programming for a new control system?

Where candidates lose points

Highlight your curiosity

The team highly values candidates who love to learn. Be ready to share examples of how you taught yourself a new technology or figured out a complex system on your own.

Understand the business

Show that you appreciate the value Sunbelt Controls delivers to its clients—specifically in reducing energy consumption, lowering operational costs, and supporting green building initiatives.

Be clear about your field comfort

Emphasize your willingness to work closely with field technicians and subcontractors. A great systems software engineer is someone who isn't afraid to put on safety gear and troubleshoot on-site.

Questions & practice

What steps do you take to verify that custom-designed graphics match the physical sequence of operations?

Medium · Troubleshooting and Field Operations

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?

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?

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?

Write the update path that detects a concurrent edit

Medium · optimistic concurrency · transactional outbox · audit history

resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.

Approach

  1. One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
  2. Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
  3. State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
  4. Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.

Follow-up

  • A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
  • Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?

Denormalise tenant onto revisions and backfill it live

Hard · denormalisation · online migration · backfill

resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.

Approach

  1. Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
  2. Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
  3. Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
  4. Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.

Follow-up

  • The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
  • How do you verify the backfill actually finished, given rows are still being inserted while it runs?

How do you prioritize your tasks when managing multiple project deadlines simultaneously?

Medium · Experience and Work Ethic

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?

Talk about a project where you had to work closely with a client or subcontractor. How did you ensure clear co

Medium · Experience and Work Ethic

Talk about a project where you had to work closely with a client or subcontractor. How did you ensure clear communication?

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?

How would you diagnose a communication loss between a controller and the main BAS server?

Medium · Systems and Networking

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 BACnet IP and BACnet MS/TP.

Medium · Systems and Networking

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?

How do you approach database programming for a new control system?

Medium · Systems and Networking

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?

Describe a scenario where a control system did not behave as expected during commissioning. How did you isolat

Medium · Troubleshooting and Field Operations

Describe a scenario where a control system did not behave as expected during commissioning. How did you isolate and resolve the issue?

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. 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?

How do you ensure compliance with energy codes such as Title 24 or LEED requirements during system testing?

Medium · Troubleshooting and Field Operations

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. 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 Sunbelt Controls candidates report.

Day 1 — Map the Sunbelt Controls loop

  • Write out the reported sequence: Initial Conversation, Technical Capabilities Discussion, Collaboration Assessment, Final Offer Stage.
  • 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 Building Automation Systems (BAS)

  • Spend the session on Building Automation Systems (BAS), which Sunbelt Controls candidates report being tested on.
  • Write one worked example in Building Automation Systems (BAS) and time yourself on it.

Deliverable: One timed worked example in Building Automation Systems (BAS).

Day 3 — Work Control System Programming (Databases)

  • Spend the session on Control System Programming (Databases), which Sunbelt Controls candidates report being tested on.
  • Write one worked example in Control System Programming (Databases) and time yourself on it.

Deliverable: One timed worked example in Control System Programming (Databases).

Day 4 — Work Commissioning

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

Deliverable: One timed worked example in Commissioning.

Day 5 — Answer out loud: Experience and Work Ethic

  • Answer aloud, timed: Can you walk me through your experience with Building Automation Systems (BAS) and what drew you to this field?
  • Answer aloud, timed: Describe a time when you had to learn a new tool or system quickly to complete a project. What was your approach?

Deliverable: Spoken answers to 2 reported Experience and Work Ethic question(s), under time.

Day 6 — Answer out loud: Systems and Networking

  • Answer aloud, timed: How would you diagnose a communication loss between a controller and the main BAS server?
  • Answer aloud, timed: Explain the difference between BACnet IP and BACnet MS/TP.

Deliverable: Spoken answers to 2 reported Systems and Networking question(s), under time.

Day 7 — Answer out loud: Troubleshooting and Field Operations

  • Answer aloud, timed: Describe a scenario where a control system did not behave as expected during commissioning. How did you isolate and resolve the issue?
  • Answer aloud, timed: How do you ensure compliance with energy codes such as Title 24 or LEED requirements during system testing?

Deliverable: Spoken answers to 2 reported Troubleshooting and Field Operations question(s), under time.

Behavioural preparation

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

Can you walk me through your experience with Building Automation Systems (BAS) and what drew you to this field

Medium · Experience and Work Ethic

Can you walk me through your experience with Building Automation Systems (BAS) and what drew you to this field?

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 learn a new tool or system quickly to complete a project. What was your approa

Medium · Experience and Work Ethic

Describe a time when you had to learn a new tool or system quickly to complete a project. What was your approach?

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?

What is your experience with configuring IP addresses, subnets, and default gateways on a local network?

Medium · Systems and Networking

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?