A Software Engineer at Span plays a critical role in transforming how humanity accesses and uses clean energy. Span is reinventing the core of home energy management by replacing the traditional electrical panel with a smart, connected gateway. As a software engineer, you will design, build, and optimize the software systems that orchestrate this hardware, enabling real-time monitoring, dynamic load shedding, and seamless integration with solar, battery storage, and electric vehicle charging systems. The impact of this position spans across multiple layers of the technology stack. Whether you are developing highly optimized firmware-adjacent services, scaling cloud infrastructure to handle high-frequency IoT telemetry, or craft accessible, intuitive user interfaces for homeowners and installers, your code directly influences the transition to a decentralized, electrified grid. The work is technically challenging, requiring a deep appreciation for system reliability, real-time data processing, and physical-digital system interactions. Success in this role requires not only technical excellence but also a strong sense of product ownership. You will collaborate closely with hardware, firmware, product, and operations teams to deliver features that are robust, safe, and highly performant. It is a unique opportunity to solve complex optimization problems that have a tangible, physical impact on energy conservation and climate change.
Recruiter Screen
reportedDiscuss your background, location, and alignment with the role.
What to demonstrate
- Discuss your background, location, and alignment with the role
- Depth in Platform Engineering (Role Alignment)
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 Screen
reportedInterview with a hiring manager or senior engineer focusing on domain expertise and technical approach.
What to demonstrate
- Interview with a hiring manager or senior engineer focusing on domain expertise and technical approach
- Depth in Platform Engineering (Role Alignment)
How to prepare
- Answer aloud and timed: If a background process on an edge device is consuming too many CPU cycles and impacting safety-critical operations, how do you go about debugging and resolving the issue?
- Answer aloud and timed: Describe the architectural trade-offs between processing energy data on an edge device versus processing it in the cloud.
Virtual Onsite Loop
reportedPresent a past project and engage in interactive sessions with engineering pairs.
What to demonstrate
- Present a past project and engage in interactive sessions with engineering pairs
- Depth in Platform Engineering (Role Alignment)
How to prepare
- Answer aloud and timed: How do you approach building highly accessible and scalable user interfaces using modern React and ES6+?
- Answer aloud and timed: Explain how you manage complex, real-time state updates in a web application when receiving continuous data streams via WebSockets.
PracHub editorial advice for the preparation topics above.
Structure Your Presentation
Spend time refining your past project presentation. Ensure it has a clear narrative arc: define the problem, explain the constraints, detail the architecture, highlight your specific contributions, and discuss the final outcome and lessons learned.
Focus on Trade-offs
In system design and technical discussions, avoid presenting any solution as "perfect." Every engineering decision has trade-offs. Explicitly state what you are sacrificing (e.g., latency, consistency, development speed) to achieve your primary goal.
Never running a concrete value through the code
Trace one small input and one edge input by hand, index by index, out loud. Re-reading your own code catches design mistakes; walking a real value through it catches the off-by-one, the uninitialised accumulator and the loop that never advances.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Canonicalise a request body into a stable idempotency fingerprint
idempotency_key.request_fingerprint is a SHA-256 over the method, path and canonicalised body, and a retry whose fingerprint differs must be rejected with 422 rather than served the stored response. Write the canonicaliser. Bodies are JSON up to 256 KB nested at most 32 levels; clients vary key order, whitespace and unicode escaping, and some send 64-bit ids as JSON numbers. Produce a deterministic byte string such that semantically identical bodies match and any semantic difference does not. State your complexity and name two normalisations you refuse to perform.
Approach
- Parse once into a tree, then re-serialise under fixed rules: object keys sorted, array order preserved, one escaping convention, no insignificant whitespace. Parsing is O(n) and sorting keys is O(k log k) per object, so O(n log n) overall with O(depth) stack, and the 32-level cap is enforced during parsing because hostile nesting is how a canonicaliser becomes a stack overflow.
- Sort keys by their UTF-8 bytes and say why the obvious implementation is wrong in some runtimes: a default string comparison that orders by UTF-16 code units places surrogate pairs, meaning code points from U+10000 up, below U+E000 to U+FFFF, which is not UTF-8 byte order, so two services written in different languages disagree on the same document.
- Do not re-encode numbers through a double. IEEE-754 binary64 represents integers exactly only up to 2^53, so normalising a 19-digit id through a float changes it, and 1 against 1.0 cannot be reconciled without deciding whether they are the same value. Preserve the literal token, and require ids as strings at the API boundary if you want them comparable.
- Reject duplicate keys rather than picking one. JSON permits them and parsers disagree, most keeping the last, so any choice you make ties the fingerprint to a parser detail that the code handling the request does not necessarily share.
Follow-up
- A client sends the same logical request with an extra field your API ignores. Same key, different fingerprint, so you return 422. Is that the right answer?
- Where does the fingerprint get computed relative to request decompression and the body-size limit?
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
Identify the heaviest tenants in a five-minute window under memory pressure
The edge service handles about 3,000 requests per second across roughly 50,000 tenants, peaking near 9,000. Expose the 50 heaviest tenants by request count over the trailing five minutes so limits can be tightened before one tenant's backfill starves the fleet. You may not retain five minutes of raw records. Give the exact solution and its memory, then the bounded-memory approximation with its error stated as a formula, and say which you would ship and at what tenant cardinality that choice changes.
Approach
- Do the exact version first, because it is affordable at this cardinality: a ring of 300 one-second counters per tenant, advanced lazily, is 1,200 bytes of counters per tenant and roughly 60 to 90 MB for 50,000 tenants with overhead. Carry a running total and subtract the bucket you overwrite so a window read is O(1) rather than 300 adds.
- Extract the top 50 with a size-k min-heap over the tenant sums: O(d log k) for d tenants, against O(d log d) to sort them all. Maintaining the heap continuously instead of on query requires a tenant-to-heap-index map, because incrementing a count already inside the heap means sifting from a known position, and without that map you rebuild the heap on every request.
- State the approximation precisely rather than gesturing at sketches. Misra-Gries with m counters retains every item whose true count exceeds N/(m+1), and each retained count underestimates the truth by at most N/(m+1). With m = 1,000 and N = 900,000 requests in the window the error is roughly 900 requests, which is fine for spotting a tenant sending 50,000 and useless for ranking two tenants 200 apart.
- Say what breaks when the window slides: Misra-Gries and Space-Saving are insert-only and cannot be decremented as records age out. The workable construction is one summary per sub-window, say ten seconds, with 30 summaries merged at query time, and the merged error is the sum of the per-summary errors, so the bound degrades linearly in the number of sub-windows.
Follow-up
- The heaviest tenant is heavy because of one export job rather than user traffic. Should the limiter treat those as the same tenant?
- Two tenants sit tied at the boundary of the top 50. Does your answer flap, and does the flapping matter?
Denormalise tenant onto revisions and backfill it live
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
- 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.
- 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.
- 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.
- 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?
Keep soft-deleted accounts from blocking re-registration
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
- 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.
- 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.
- 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.
- 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?
Walk me through a complex technical optimization challenge you faced in a past project. How did you identify t
Walk me through a complex technical optimization challenge you faced in a past project. How did you identify the bottleneck, and what metrics did you use to measure success?
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 would you design a telemetry ingestion system that can handle real-time data from hundreds of thousands of
How would you design a telemetry ingestion system that can handle real-time data from hundreds of thousands of smart home devices without dropping packets?
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?
Describe the architectural trade-offs between processing energy data on an edge device versus processing it in
Describe the architectural trade-offs between processing energy data on an edge device versus processing it in the cloud.
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 building highly accessible and scalable user interfaces using modern React and ES6+?
How do you approach building highly accessible and scalable user interfaces using modern React and ES6+?
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?
Explain how you manage complex, real-time state updates in a web application when receiving continuous data st
Explain how you manage complex, real-time state updates in a web application when receiving continuous data streams via WebSockets.
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?
What strategies do you use to optimize the rendering performance of data-heavy dashboards on mobile browsers?
What strategies do you use to optimize the rendering performance of data-heavy dashboards on mobile browsers?
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?
If a background process on an edge device is consuming too many CPU cycles and impacting safety-critical opera
If a background process on an edge device is consuming too many CPU cycles and impacting safety-critical operations, how do you go about debugging and resolving the issue?
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?
Built from the rounds and topics Span candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Span loop
- Write out the reported sequence: Recruiter Screen, Technical Screen, Virtual Onsite Loop.
- 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.
02Work Platform Engineering (Role Alignment)
- Spend the session on Platform Engineering (Role Alignment), which Span candidates report being tested on.
- Write one worked example in Platform Engineering (Role Alignment) and time yourself on it.
Deliverable: One timed worked example in Platform Engineering (Role Alignment).
03Work Recruiting/Interview Process Design
- Spend the session on Recruiting/Interview Process Design, which Span candidates report being tested on.
- Write one worked example in Recruiting/Interview Process Design and time yourself on it.
Deliverable: One timed worked example in Recruiting/Interview Process Design.
04Work Communication Skills
- Spend the session on Communication Skills, which Span candidates report being tested on.
- Write one worked example in Communication Skills and time yourself on it.
Deliverable: One timed worked example in Communication Skills.
05Answer out loud: System Architecture & Optimization
- Answer aloud, timed: Walk me through a complex technical optimization challenge you faced in a past project. How did you identify the bottleneck, and what metrics did you use to measure success?
- Answer aloud, timed: How would you design a telemetry ingestion system that can handle real-time data from hundreds of thousands of smart home devices without dropping packets?
Deliverable: Spoken answers to 2 reported System Architecture & Optimization question(s), under time.
06Answer out loud: Front-End & Interface Engineering
- Answer aloud, timed: How do you approach building highly accessible and scalable user interfaces using modern React and ES6+?
- Answer aloud, timed: Explain how you manage complex, real-time state updates in a web application when receiving continuous data streams via WebSockets.
Deliverable: Spoken answers to 2 reported Front-End & Interface Engineering question(s), under time.
07Answer out loud: Behavioral & Situational Knowledge
- Answer aloud, timed: Tell me about a time you had a strong technical disagreement with a peer or manager. How did you handle the situation, and what was the outcome?
- Answer aloud, timed: Describe a past project that failed or did not meet expectations. What did you learn, and how did you apply those lessons to subsequent work?
Deliverable: Spoken answers to 2 reported Behavioral & Situational Knowledge question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Describe a time you had to implement a highly customized and reusable UI component from scratch. How did you e
Describe a time you had to implement a highly customized and reusable UI component from scratch. How did you ensure its maintainability?
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 you had a strong technical disagreement with a peer or manager. How did you handle the si
Tell me about a time you had a strong technical disagreement with a peer or manager. How did you handle the situation, and what was the outcome?
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 past project that failed or did not meet expectations. What did you learn, and how did you apply th
Describe a past project that failed or did not meet expectations. What did you learn, and how did you apply those lessons to subsequent work?
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 prioritize technical debt when working under tight product delivery deadlines?
How do you prioritize technical debt when working under tight product delivery deadlines?
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?
Talk about a time when you had to ramp up on an unfamiliar technology or domain quickly to deliver a critical
Talk about a time when you had to ramp up on an unfamiliar technology or domain quickly to deliver a critical feature.
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?
- 01
Describe a time you had to implement a highly customized and reusable UI component from scratch. How did you ensure its maintainability?
- 02
Tell me about a time you had a strong technical disagreement with a peer or manager. How did you handle the situation, and what was the outcome?
- 03
Describe a past project that failed or did not meet expectations. What did you learn, and how did you apply those lessons to subsequent work?
- 04
How do you prioritize technical debt when working under tight product delivery deadlines?
What is the typical technical stack for Software Engineers at Span?
Span utilizes a modern, service-oriented stack. The frontend and mobile apps are heavily built on React and React Native with TypeScript. Backend services are primarily written in Go and Python, deployed on cloud infrastructure, and integrated with IoT devices communicating via protocols like MQTT and gRPC.
Span Software Engineer candidate reports ↗How heavily does Span focus on LeetCode-style algorithmic questions?
Span's interview process focuses much more on practical domain knowledge, system design, and situational engineering experience. While you should be comfortable with basic coding and problem-solving, you are highly unlikely to face abstract, competitive-programming style puzzle questions.
Span Software Engineer candidate reports ↗How should I handle a situation where an interviewer strongly disagrees with my technical approach?
Remain professional, open-minded, and collaborative. Treat the disagreement as an opportunity to discuss engineering trade-offs. Acknowledge the interviewer's perspective, explain the rationale behind your choice, and demonstrate that you can take constructive feedback and adapt your solution.
Span Software Engineer candidate reports ↗Is there an onsite presentation required for all software engineering roles?
Yes, presenting a past technical project is a core component of the onsite interview loop for most software engineering positions at Span. It is highly valued as a way to assess your communication, depth of ownership, and architectural decision-making.
Span Software Engineer candidate reports ↗What topics does Span test in interviews?
Span interviews most often cover Account Management, Platform Engineering (Role Alignment), Deal Negotiation, Sales Strategy, and Recruiting/Interview Process Design. The exact emphasis depends on the specific role you apply for.
Span Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Span Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Steampunk Software Engineer Interview Guide
What Steampunk asks Software Engineer candidates, from reported rounds and questions.
Snap-on Software Engineer Interview Guide
What Snap-on asks Software Engineer candidates, from reported rounds and questions.
Fieldai Software Engineer Interview Guide
What Fieldai asks Software Engineer candidates, from reported rounds and questions.
Disney Experiences Software Engineer Interview Guide
What Disney Experiences asks Software Engineer candidates, from reported rounds and questions.