As a Software Engineer at Wunderflats, you play a pivotal role in redefining the housing market. Wunderflats is Germany's leading platform for temporary furnished housing, connecting tenants, landlords, and corporate clients through a seamless, digitized booking experience. The engineering team is responsible for building and maintaining the core platform, ensuring high availability, speed, and an intuitive user interface that simplifies complex real estate transactions. Your work directly impacts the platform's scalability, search capabilities, booking engine, and payment integrations. You will collaborate closely with cross-functional teams, including Product Managers, Designers, and Technical Program Managers, to translate business requirements into robust, clean, and maintainable code. Engineering at Wunderflats is characterized by a strong culture of collaboration, open communication, and high standards for code quality. The team values pragmatic problem-solving and clean architecture, making this role both highly collaborative and technically rewarding as you help scale a product used by thousands of people daily.
Application Review
reportedInitial review of submitted applications to assess qualifications and fit.
What to demonstrate
- Initial review of submitted applications to assess qualifications and fit
- Depth in JavaScript
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.
Recruiter Call
reportedDiscussion with a recruiter to go over the candidate's background and the role.
What to demonstrate
- Discussion with a recruiter to go over the candidate's background and the role
- Depth in JavaScript
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 Interview
reportedCoding interview focusing on core programming and React fundamentals.
What to demonstrate
- Coding interview focusing on core programming and React fundamentals
- Depth in JavaScript
How to prepare
- Answer aloud and timed: How do you manage loading and error states in a React component while fetching external data?
- Answer aloud and timed: Explain your approach to structuring CSS layout styles in a newly bootstrapped React application.
Behavioral Interview
reportedDiscussion of past experiences and behavioral fit within the team.
What to demonstrate
- Discussion of past experiences and behavioral fit within the team
- Depth in JavaScript
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral interview above and write down what you would ask to confirm before it.
Final Round
reportedFinal discussions with engineering leadership and team members.
What to demonstrate
- Final discussions with engineering leadership and team members
- Depth in JavaScript
How to prepare
- Answer aloud and timed: How do you collaborate with Product Managers and Technical Program Managers to scope out a new feature and manage trade-offs?
- Work JavaScript until you can explain it without notes
Offer Discussion
reportedDiscussion regarding the job offer and terms of employment.
What to demonstrate
- Discussion regarding the job offer and terms of employment
- Depth in JavaScript
How to prepare
- Work JavaScript until you can explain it without notes
- Work React until you can explain it without notes
PracHub editorial advice for the preparation topics above.
Plan Out Loud
Always start your technical challenges by writing down a brief plan in plain text. This shows the interviewers your structured thinking process before you write any code.
Brush Up on React Basics
Ensure you are comfortable bootstrapping a simple React app, fetching data, handling state, and writing basic CSS layouts without relying on heavy external libraries.
Show Your Seniority
When answering technical questions, avoid generic or textbook answers. Speak from your actual experience, highlighting trade-offs, edge cases, and architectural considerations.
Ask Thoughtful Questions
Use the final minutes of your interviews to ask about the team's processes, engineering culture, and upcoming product challenges. This demonstrates genuine interest and engagement.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function to manipulate an array of housing listings based on dynamic filter criteria.
Write a function to manipulate an array of housing listings based on dynamic filter criteria.
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?
How do you handle asynchronous operations in JavaScript, and what are the practical differences between Promis
How do you handle asynchronous operations in JavaScript, and what are the practical differences between Promises and async/await?
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?
Solve a series of short, framework-agnostic programming challenges to pass pre-written unit tests under a time
Solve a series of short, framework-agnostic programming challenges to pass pre-written unit tests under a time constraint.
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?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
Hold a per-tenant active cap against concurrent creates
A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.
Approach
- Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
- Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
- Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
- State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.
Follow-up
- A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
- The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?
Build a React application featuring a header, a sidebar, and a main content area that displays data fetched fr
Build a React application featuring a header, a sidebar, and a main content area that displays data fetched from a dummy API.
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 do you manage loading and error states in a React component while fetching external data?
How do you manage loading and error states in a React component while fetching external data?
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?
Explain your approach to structuring CSS layout styles in a newly bootstrapped React application.
Explain your approach to structuring CSS layout styles in a newly bootstrapped React application.
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?
p99 jumped on one listing filter while p50 stayed flat
After a release that added an owner_user_id filter to the resource listing, p99 rose from 90 ms to 1.9 s while p50 stayed at 40 ms. Traffic and row counts are unchanged. resource carries the index (tenant_id, status, updated_at DESC, resource_id DESC). The new query filters tenant_id and owner_user_id, orders by updated_at DESC, resource_id DESC, and takes 20 rows. On PostgreSQL, explain the shape of the regression, prove it from a query plan, and give the index you would add.
Approach
- Start from the shape. A flat p50 with a moved p99 means a subset of requests changed cost, not all of them, so the first job is naming the subset. Bucket the endpoint's latency by the tenant's row count; the natural hypothesis is that large tenants are a small share of requests and all of the tail.
- Get the plan for the new query on a large tenant with EXPLAIN (ANALYZE, BUFFERS). Expect an index scan over the tenant's range, a filter discarding most of it, then a Sort feeding the Limit, possibly reporting Sort Method: external merge Disk. Read actual rows on the scan node, not estimated.
- Explain why the existing index cannot serve it. A composite B-tree is seekable only as a left prefix, and with no equality predicate on status the scan cannot treat updated_at as an ordering, because rows in the tenant's range are ordered by status first. Everything matching must be read and sorted before LIMIT 20 can apply, so a tenant with 400,000 rows pays 400,000 rows to return 20.
- Add (tenant_id, owner_user_id, updated_at DESC, resource_id DESC). Equality on the first two columns leaves the index ordered by updated_at within that pair, so the plan becomes an index scan that stops after 20 rows with no Sort node. PostgreSQL can scan a B-tree backwards, so the DESC markers matter only if the two sort columns ever disagree in direction; keeping them explicit documents the order the keyset cursor depends on.
Follow-up
- The endpoint paginates with OFFSET. What does page 500 cost with your index, and what does the keyset version cost?
- How would you have caught this before release, given that a 10,000-row seed database produces the same plan shape at an unnoticeable cost?
Built from the rounds and topics Wunderflats candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Wunderflats loop
- Write out the reported sequence: Application Review, Recruiter Call, Technical Interview, Behavioral Interview, Final Round, Offer Discussion.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 6 reported rounds, with the weakest marked.
02Work JavaScript
- Spend the session on JavaScript, which Wunderflats candidates report being tested on.
- Write one worked example in JavaScript and time yourself on it.
Deliverable: One timed worked example in JavaScript.
03Work React
- Spend the session on React, which Wunderflats candidates report being tested on.
- Write one worked example in React and time yourself on it.
Deliverable: One timed worked example in React.
04Work Coding challenges
- Spend the session on Coding challenges, which Wunderflats candidates report being tested on.
- Write one worked example in Coding challenges and time yourself on it.
Deliverable: One timed worked example in Coding challenges.
05Answer out loud: JavaScript & Algorithm Fundamentals
- Answer aloud, timed: Write a function to manipulate an array of housing listings based on dynamic filter criteria.
- Answer aloud, timed: How do you handle asynchronous operations in JavaScript, and what are the practical differences between Promises and async/await?
Deliverable: Spoken answers to 2 reported JavaScript & Algorithm Fundamentals question(s), under time.
06Answer out loud: Frontend & React Development
- Answer aloud, timed: Build a React application featuring a header, a sidebar, and a main content area that displays data fetched from a dummy API.
- Answer aloud, timed: How do you manage loading and error states in a React component while fetching external data?
Deliverable: Spoken answers to 2 reported Frontend & React Development question(s), under time.
07Answer out loud: Behavioral & Team Collaboration
- Answer aloud, timed: Why are you interested in relocating to Germany, and how do you manage working with teams across different time zones?
- Answer aloud, timed: Describe a situation where you received constructive feedback on your code readability. How did you handle it?
Deliverable: Spoken answers to 2 reported Behavioral & Team Collaboration 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.
Why are you interested in relocating to Germany, and how do you manage working with teams across different tim
Why are you interested in relocating to Germany, and how do you manage working with teams across different time zones?
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 situation where you received constructive feedback on your code readability. How did you handle it?
Describe a situation where you received constructive feedback on your code readability. How did you handle it?
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 collaborate with Product Managers and Technical Program Managers to scope out a new feature and man
How do you collaborate with Product Managers and Technical Program Managers to scope out a new feature and manage trade-offs?
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
Why are you interested in relocating to Germany, and how do you manage working with teams across different time zones?
- 02
Describe a situation where you received constructive feedback on your code readability. How did you handle it?
- 03
How do you collaborate with Product Managers and Technical Program Managers to scope out a new feature and manage trade-offs?
How difficult is the technical interview at Wunderflats?
The technical interview is generally rated as average in difficulty. The focus is on practical, day-to-day coding skills rather than abstract, highly complex algorithmic puzzles.
Wunderflats Software Engineer candidate reports ↗What is the expectation regarding code style during the live coding challenge?
Wunderflats prioritizes clean, readable, and maintainable code. Avoid writing overly condensed "one-liners" that are difficult to read, and ensure you explain your planning process clearly before coding.
Wunderflats Software Engineer candidate reports ↗Does Wunderflats offer relocation and visa support for international candidates?
Yes, Wunderflats has a track record of supporting international candidates with the relocation process, including immigration assistance and guidance on moving to Germany. ##### Tip If you are interviewing from outside Germany, be prepared to discuss your motivation for relocating to Berlin and your timeline for moving.
Wunderflats Software Engineer candidate reports ↗How long does the entire interview process take?
The process is highly streamlined and typically takes around two to three weeks from the initial recruiter call to the final decision.
Wunderflats Software Engineer candidate reports ↗What topics does Wunderflats test in interviews?
Wunderflats interviews most often cover JavaScript, React, CSS, Marketing Analytics, and Collaboration with Cross-Functional Teams. The exact emphasis depends on the specific role you apply for.
Wunderflats 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.
- 01Wunderflats 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.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Shopify Software Engineer Interview Guide
Timed practice for Shopify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Ramp Software Engineer Interview Guide
Systems practice for Ramp software engineer candidates, weighted toward payments and lending work: the load that actually arrives, the failure modes that matter there, and the invariants a partial outage must not break.