Wise. Energy hires Software Engineers; this guide collects what candidates report about the process.
Application Screening
reportedInitial review of applications to assess candidate qualifications.
What to demonstrate
- Initial review of applications to assess candidate qualifications
- Depth in Algorithms
How to prepare
- Answer aloud and timed: Implement a sliding window algorithm to find the maximum sum of a contiguous subarray of size K.
- Answer aloud and timed: Write a program to parse a large file containing transaction logs and aggregate the total volume processed per currency.
Automated Assessment
reportedIncludes a timed technical test on HackerRank and a cognitive/cultural assessment on Maki.
What to demonstrate
- Includes a timed technical test on HackerRank and a cognitive/cultural assessment on Maki
- Depth in Algorithms
How to prepare
- Answer aloud and timed: Design and implement a basic Tic-Tac-Toe game engine, ensuring clean object-oriented design and validation of win conditions.
- Answer aloud and timed: Write a function that calls a paginated REST API endpoint, filters the results based on specific criteria, and returns the aggregated data.
Live Virtual Interviews
reportedInterviews with the engineering team focusing on collaborative coding, system design, and product engineering fit.
What to demonstrate
- Interviews with the engineering team focusing on collaborative coding, system design, and product engineering fit
- Depth in Algorithms
How to prepare
- Answer aloud and timed: Implement an algorithm to find the shortest path in a currency conversion graph using a Breadth-First Search (BFS) approach.
- Answer aloud and timed: Design a highly scalable rate limiter that can handle millions of requests per minute across multiple regions.
Final Offer Stage
reportedDiscussion of the final offer after successful completion of previous steps.
What to demonstrate
- Discussion of the final offer after successful completion of previous steps
- Depth in Algorithms
How to prepare
- Answer aloud and timed: How would you design a real-time client support chat widget and distribute it efficiently to millions of client applications?
- Answer aloud and timed: Describe how you would implement a resilient Circuit Breaker pattern for an HTTP client calling an unreliable third-party payment service.
2 candidate reports. Individual accounts describe a particular role and hiring cycle.
Wise. Energy Software Engineer interview with pair programming
I went through a standard multi-stage loop. It started with a recruiter conversation, then a 30-minute coding interview, followed by a longer technical session with system design and another coding segment with two engineers. After that came a product interview and a final conversation with managers and a lead. The exercises felt practical rather than contrived. In the pair-programming portion, c…
Read full experienceWise. Energy Software Engineer Interview Experience: Rigid technical screens and contradictory role expectations
The vibe and fairness felt off from the start. In a technical round where I filled in parts of a skeleton script, the session felt rushed and rigid, as if I were being judged against a memorized approach instead of how I reasoned. The scope changed at the last minute because they could not define what they wanted. There was also a mismatch in fundamentals: state-machine concepts were not handled…
Read full experiencePracHub editorial advice for the preparation topics above.
Do Not Use AI Tools During Live Coding
During the live pair programming session, you may be asked to share your screen. Even if you are not sharing your full screen, do not use AI code assistants. Interviewers expect you to write the code yourself and explain your logic step-by-step.
Prepare for Behavioral Questions in Technical Rounds
Be aware that some technical rounds, including the live pair programming session, may begin with 10 to 15 minutes of behavioral questions about your background, motivations, and experience. Do not let this catch you off guard.
Clarify Requirements Before Coding
In both the coding and system design rounds, avoid jumping straight into implementation. Take a few minutes to ask clarifying questions, define the scope of the problem, and align with your interviewer on the expected outcomes.
Follow Up Proactively
Because the recruitment team can sometimes experience high volumes, do not hesitate to reach out to your recruiter if you do not receive feedback within a week of completing an interview stage. Polite, proactive communication is always appreciated.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Implement a sliding window algorithm to find the maximum sum of a contiguous subarray of size K.
Implement a sliding window algorithm to find the maximum sum of a contiguous subarray of size K.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Write a program to parse a large file containing transaction logs and aggregate the total volume processed per
Write a program to parse a large file containing transaction logs and aggregate the total volume processed per currency.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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 an algorithm to find the shortest path in a currency conversion graph using a Breadth-First Search (
Implement an algorithm to find the shortest path in a currency conversion graph using a Breadth-First Search (BFS) approach.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Write a SQL query using complex joins and window functions to identify users who made more than three transact
Write a SQL query using complex joins and window functions to identify users who made more than three transactions within a five-minute window.
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- 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 query to find the top-performing corridors (sending to receiving currency pairs) based on weekly volum
Write a query to find the top-performing corridors (sending to receiving currency pairs) based on weekly volume, filtering out system test accounts.
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- 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 trade-offs between using a SQL database versus a NoSQL database for storing user profile data and
Explain the trade-offs between using a SQL database versus a NoSQL database for storing user profile data and transaction ledgers.
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- 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?
What do you anticipate will be your biggest challenge if you join Wise. Energy, and how do you plan to address
What do you anticipate will be your biggest challenge if you join Wise. Energy, and how do you plan to address it?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- 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?
Design and implement a basic Tic-Tac-Toe game engine, ensuring clean object-oriented design and validation of
Design and implement a basic Tic-Tac-Toe game engine, ensuring clean object-oriented design and validation of win conditions.
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?
Write a function that calls a paginated REST API endpoint, filters the results based on specific criteria, and
Write a function that calls a paginated REST API endpoint, filters the results based on specific criteria, and returns the aggregated data.
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Design a highly scalable rate limiter that can handle millions of requests per minute across multiple regions.
Design a highly scalable rate limiter that can handle millions of requests per minute across multiple regions.
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 real-time client support chat widget and distribute it efficiently to millions of clien
How would you design a real-time client support chat widget and distribute it efficiently to millions of client applications?
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 implement a resilient Circuit Breaker pattern for an HTTP client calling an unreliable
Describe how you would implement a resilient Circuit Breaker pattern for an HTTP client calling an unreliable third-party payment service.
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?
Design a data migration strategy to transition a high-traffic transactional database from a legacy monolithic
Design a data migration strategy to transition a high-traffic transactional database from a legacy monolithic system to a microservices architecture with minimal downtime.
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 handle distributed transactions and ensure eventual consistency across multiple microservices wh
How would you handle distributed transactions and ensure eventual consistency across multiple microservices when a transfer fails midway?
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 database locks (optimistic vs. pessimistic locking) work, and how would you prevent deadlocks in a high
How do database locks (optimistic vs. pessimistic locking) work, and how would you prevent deadlocks in a high-concurrency transaction processing system?
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 Wise. Energy candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Wise. Energy loop
- Write out the reported sequence: Application Screening, Automated Assessment, Live Virtual Interviews, 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.
02Work Algorithms
- Spend the session on Algorithms, which Wise. Energy candidates report being tested on.
- Write one worked example in Algorithms and time yourself on it.
Deliverable: One timed worked example in Algorithms.
03Work SQL
- Spend the session on SQL, which Wise. Energy candidates report being tested on.
- Write one worked example in SQL and time yourself on it.
Deliverable: One timed worked example in SQL.
04Work Data Structures
- Spend the session on Data Structures, which Wise. Energy candidates report being tested on.
- Write one worked example in Data Structures and time yourself on it.
Deliverable: One timed worked example in Data Structures.
05Answer out loud: Coding & Algorithm Questions
- Answer aloud, timed: Implement a sliding window algorithm to find the maximum sum of a contiguous subarray of size K.
- Answer aloud, timed: Write a program to parse a large file containing transaction logs and aggregate the total volume processed per currency.
Deliverable: Spoken answers to 2 reported Coding & Algorithm Questions question(s), under time.
06Answer out loud: System Design & Architecture Questions
- Answer aloud, timed: Design a highly scalable rate limiter that can handle millions of requests per minute across multiple regions.
- Answer aloud, timed: How would you design a real-time client support chat widget and distribute it efficiently to millions of client applications?
Deliverable: Spoken answers to 2 reported System Design & Architecture Questions question(s), under time.
07Answer out loud: SQL & Database Questions
- Answer aloud, timed: Write a SQL query using complex joins and window functions to identify users who made more than three transactions within a five-minute window.
- Answer aloud, timed: How do database locks (optimistic vs. pessimistic locking) work, and how would you prevent deadlocks in a high-concurrency transaction processing system?
Deliverable: Spoken answers to 2 reported SQL & Database Questions 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 when you made a significant technical mistake or failed at a project. How did you identify the
Describe a time when you made a significant technical mistake or failed at a project. How did you identify the issue, rectify it, and what did you learn?
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 a situation where a product manager proposes a feature that you believe is technically unfea
How do you handle a situation where a product manager proposes a feature that you believe is technically unfeasible or detrimental to system performance?
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?
Give an example of how you have demonstrated extreme ownership over a service or feature, from conception to p
Give an example of how you have demonstrated extreme ownership over a service or feature, from conception to post-launch monitoring.
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 approach giving and receiving tough constructive feedback within a highly collaborative engineering
How do you approach giving and receiving tough constructive feedback within a highly collaborative engineering team?
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 when you made a significant technical mistake or failed at a project. How did you identify the issue, rectify it, and what did you learn?
- 02
How do you handle a situation where a product manager proposes a feature that you believe is technically unfeasible or detrimental to system performance?
- 03
Give an example of how you have demonstrated extreme ownership over a service or feature, from conception to post-launch monitoring.
- 04
How do you approach giving and receiving tough constructive feedback within a highly collaborative engineering team?
What is the hybrid work policy at Wise. Energy?
Wise. Energy operates on a hybrid model, requiring employees to be in the office 3 days per week. This policy is highly valued by the team to foster collaboration and strong working relationships, and there is very little room for flexibility on this requirement.
Wise. Energy Software Engineer candidate reports ↗How long does the entire recruitment process typically take?
The process generally takes between 1 to 2 months from the initial application to the final offer. This timeline can sometimes be extended during peak holiday seasons or when scheduling interviews across different time zones.
Wise. Energy Software Engineer candidate reports ↗Do I need to know a specific programming language for the coding interviews?
For the online assessments and live coding rounds, you can typically use any modern programming language you are comfortable with, such as Java, Python, or JavaScript. However, because much of the core infrastructure is built on Java, having a strong grasp of Java-specific concurrency and design patterns is highly advantageous.
Wise. Energy Software Engineer candidate reports ↗What is the most common reason candidates fail the technical rounds?
Many candidates struggle because they focus too much on memorizing LeetCode algorithms and fail to demonstrate practical, clean software design. At Wise. Energy, interviewers care deeply about how you structure your code, handle edge cases, write tests, and communicate your design decisions in real time.
Wise. Energy Software Engineer candidate reports ↗How should I prepare for the Maki assessment?
The Maki assessment includes cognitive tests, attention-to-detail puzzles, and behavioral video recordings. The best way to prepare is to thoroughly research the company's core values, practice answering questions using the STAR method (Situation, Task, Action, Result), and ensure you are in a quiet environment with a stable internet connection.
Wise. Energy Software Engineer candidate reports ↗What topics does Wise. Energy test in interviews?
Wise. Energy interviews most often cover SQL, Stakeholder Management, Behavioral Interviewing, Communication Skills, and Problem Solving. The exact emphasis depends on the specific role you apply for.
Wise. Energy Software Engineer candidate reports ↗What roles can I prepare for at Wise. Energy?
Energy, including Backend Engineer, Business Analyst, Data Analyst, and Data Engineer, and more.
Wise. Energy 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.
- 01Wise. Energy 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.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
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.
Aerospike Software Engineer Interview Questions & Guide 2026
Aerospike database-engine preparation through an original single-owner Python key-value store with bounded logical index accounting, disk-offset reads, conditional writes, tombstones, process-restart recovery and 3,240 checks. Existing 14 p