As a Software Engineer at Kraken, you are at the absolute center of the global green energy transition. Kraken (the technology platform powering Octopus Energy) is not a typical utility company; it is an operating system for the energy sector, managing millions of customer accounts globally. Your work directly impacts how energy grids operate, how renewable resources are integrated, and how consumers interact with their energy footprints. You will be building and scaling a highly sophisticated platform that processes massive volumes of real-time data, manages complex API integrations, and automates energy market communications. Whether you are optimizing backend pipelines for billing, building smart grid management systems, or parsing intricate energy market flow files, your code will solve real-world physical and environmental challenges. The engineering culture at Kraken is highly pragmatic, collaborative, and mission-driven. We value clean code, strong architectural principles, and the ability to navigate ambiguity over raw speed or dogmatic adherence to specific frameworks. It is a challenging but deeply rewarding environment where you can see the direct environmental and societal impact of your commits.
Recruiter Call
reportedInitial screening call with a recruiter to discuss your background and the role.
What to demonstrate
- Initial screening call with a recruiter to discuss your background and the role
- Depth in Problem Solving
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.
Take-Home Coding Challenge
reportedComplete a coding challenge that reflects realistic work scenarios.
What to demonstrate
- Complete a coding challenge that reflects realistic work scenarios
- Depth in Problem Solving
How to prepare
- Answer aloud and timed: Explain how Python's memory management works, specifically concerning garbage collection and reference counting.
- Answer aloud and timed: How would you structure a custom Django management command to run as a scheduled background cron job?
Technical Discussion
reportedInteractive discussion where you review your code with Kraken engineers.
What to demonstrate
- Interactive discussion where you review your code with Kraken engineers
- Depth in Problem Solving
How to prepare
- Answer aloud and timed: How would you design a Python script to parse a large, malformed CSV or energy industry flow file efficiently?
- Answer aloud and timed: How do you manage rate limits and error handling when orchestrating multiple third-party API calls?
Team Fit Interview
reportedFinal interview focusing on team compatibility and management fit.
What to demonstrate
- Final interview focusing on team compatibility and management fit
- Depth in Problem Solving
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.
Collaborative Design Session
reportedOptional session for specialized departments involving system design whiteboarding.
What to demonstrate
- Optional session for specialized departments involving system design whiteboarding
- Depth in Problem Solving
How to prepare
- Answer aloud and timed: How would you design a scalable logging system to track real-time energy consumption across millions of smart meters?
- Answer aloud and timed: Describe how you would approach scaling a system that experiences massive, unpredictable spikes in traffic (e.g., dynamic energy pricing events).
PracHub editorial advice for the preparation topics above.
Document Everything in Your README
This is the single most important tip for the take-home challenge. Since the requirements are intentionally vague, use your README to explicitly state your assumptions, describe your architectural choices, and list what you would have built next if you had more time.
The take-home challenge instructions are purposefully ambiguous
Interviewers are actively looking to see how you define boundaries, make sensible assumptions, and communicate them clearly in writing.
Prioritize Test-Driven Development (TDD)
Do not treat testing as an afterthought. Kraken engineers place a massive premium on robust, clean testing. Ensure your take-home code includes well-structured unit tests that cover both happy paths and edge cases.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Explain how Python's memory management works, specifically concerning garbage collection and reference countin
Explain how Python's memory management works, specifically concerning garbage collection and reference counting.
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?
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?
Merge partitioned event streams into one ordered feed with bounded lateness
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
- 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.
- 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.
- 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.
- 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?
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?
Stop tag and share joins from fanning out a page
resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.
Approach
- Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
- Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
- Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
- Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.
Follow-up
- The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
- A resource can be shared with the same user twice under different permissions. Does your count change, and should it?
What are the performance implications of Django's ORM `select_related` vs. `prefetch_related`?
What are the performance implications of Django's ORM select_related vs. prefetch_related?
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 would you structure a custom Django management command to run as a scheduled background cron job?
How would you structure a custom Django management command to run as a scheduled background cron job?
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 would you design a Python script to parse a large, malformed CSV or energy industry flow file efficiently?
How would you design a Python script to parse a large, malformed CSV or energy industry flow file efficiently?
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 manage rate limits and error handling when orchestrating multiple third-party API calls?
How do you manage rate limits and error handling when orchestrating multiple third-party API calls?
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?
Explain how you would handle data validation and serialization when building a tool that fetches and transform
Explain how you would handle data validation and serialization when building a tool that fetches and transforms raw external data for a client.
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 to ensure data integrity when importing high-frequency electricity meter readings?
What strategies do you use to ensure data integrity when importing high-frequency electricity meter readings?
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 would you design a scalable logging system to track real-time energy consumption across millions of smart
How would you design a scalable logging system to track real-time energy consumption across millions of smart meters?
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 how you would approach scaling a system that experiences massive, unpredictable spikes in traffic (e.
Describe how you would approach scaling a system that experiences massive, unpredictable spikes in traffic (e.g., dynamic energy pricing events).
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?
What trade-offs do you consider when choosing between synchronous API communication and asynchronous event-dri
What trade-offs do you consider when choosing between synchronous API communication and asynchronous event-driven architectures?
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 fault-tolerant system to process financial transactions and billing cycles for millions
How would you design a fault-tolerant system to process financial transactions and billing cycles for millions of customers?
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?
Listing latency scales with page size, not with filters
The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.
Approach
- Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
- Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
- Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
- Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.
Follow-up
- The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
- How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?
Built from the rounds and topics Kraken candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Kraken loop
- Write out the reported sequence: Recruiter Call, Take-Home Coding Challenge, Technical Discussion, Team Fit Interview, Collaborative Design Session.
- 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 5 reported rounds, with the weakest marked.
02Work Problem Solving
- Spend the session on Problem Solving, which Kraken candidates report being tested on.
- Write one worked example in Problem Solving and time yourself on it.
Deliverable: One timed worked example in Problem Solving.
03Work System Design
- Spend the session on System Design, which Kraken candidates report being tested on.
- Write one worked example in System Design and time yourself on it.
Deliverable: One timed worked example in System Design.
04Work Python
- Spend the session on Python, which Kraken candidates report being tested on.
- Write one worked example in Python and time yourself on it.
Deliverable: One timed worked example in Python.
05Answer out loud: Python & Django Backend Core
- Answer aloud, timed: What are the performance implications of Django's ORM `select_related` vs. `prefetch_related`?
- Answer aloud, timed: How do you handle migrations in a large-scale Django application with zero-downtime requirements?
Deliverable: Spoken answers to 2 reported Python & Django Backend Core question(s), under time.
06Answer out loud: Data Processing & API Management
- Answer aloud, timed: How would you design a Python script to parse a large, malformed CSV or energy industry flow file efficiently?
- Answer aloud, timed: How do you manage rate limits and error handling when orchestrating multiple third-party API calls?
Deliverable: Spoken answers to 2 reported Data Processing & API Management question(s), under time.
07Answer out loud: System Design & Architecture
- Answer aloud, timed: How would you design a scalable logging system to track real-time energy consumption across millions of smart meters?
- Answer aloud, timed: Describe how you would approach scaling a system that experiences massive, unpredictable spikes in traffic (e.g., dynamic energy pricing events).
Deliverable: Spoken answers to 2 reported System Design & Architecture 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.
How do you handle migrations in a large-scale Django application with zero-downtime requirements?
How do you handle migrations in a large-scale Django application with zero-downtime 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?
Why do you want to work at Kraken, and what does our mission of a green energy transition mean to you?
Why do you want to work at Kraken, and what does our mission of a green energy transition mean to you?
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 you had to work with highly ambiguous or incomplete requirements. How did you proceed?
Describe a time you had to work with highly ambiguous or incomplete requirements. How did you proceed?
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 handle receiving critical feedback on your code or architectural decisions from team members?
How do you handle receiving critical feedback on your code or architectural decisions from team members?
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 to coordinate with cross-functional teams to deliver a highly complex backend fea
Tell me about a time you had to coordinate with cross-functional teams to deliver a highly complex backend 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
How do you handle migrations in a large-scale Django application with zero-downtime requirements?
- 02
Why do you want to work at Kraken, and what does our mission of a green energy transition mean to you?
- 03
Describe a time you had to work with highly ambiguous or incomplete requirements. How did you proceed?
- 04
How do you handle receiving critical feedback on your code or architectural decisions from team members?
How difficult is the Kraken interview process, and how much prep time is needed?
The process is widely regarded as average to difficult, but highly practical. Instead of cramming complex Leetcode algorithms, you should spend 10 to 15 hours reviewing Django best practices, TDD patterns, and clean code architecture to prepare for the take-home challenge.
Kraken Software Engineer candidate reports ↗What is the expectation for the 3-4 hour take-home challenge?
While we suggest spending 3 to 4 hours on the task, we value quality over speed. It is highly recommended to take a bit of extra time to write a comprehensive README, document your assumptions, and add robust unit tests, as this is often what sets successful candidates apart.
Kraken Software Engineer candidate reports ↗How quickly does Kraken make a hiring decision?
Kraken is known for a relatively fast and efficient process. Many candidates receive feedback within a few days of each stage, and final offers are often extended within 24 to 48 hours after the final round.
Kraken Software Engineer candidate reports ↗Does Kraken offer remote or hybrid working arrangements?
Yes, Kraken supports flexible working models, including hybrid and fully remote setups depending on the team, role level, and geographic location. These details are typically discussed and aligned during your initial recruiter call.
Kraken Software Engineer candidate reports ↗What topics does Kraken test in interviews?
Kraken interviews most often cover Python, Time Management, SQL, Django, and Case Study Analysis. The exact emphasis depends on the specific role you apply for.
Kraken 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.
- 01Kraken 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.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Rystad Energy Software Engineer Interview Guide
Prepare for Rystad Energy software interviews with worked Python validation, OOP and decorator examples, plus an ingestion case and practical checks.
Zoom Video Communications Software Engineer Interview Guide
What Zoom Video Communications asks Software Engineer candidates, from reported rounds and questions.