As a Software Engineer at Droisys, you serve as a core technical contributor in an organization that operates at the intersection of enterprise consulting and technology delivery. Your role is pivotal in translating complex business requirements into scalable software solutions. You will be expected to demonstrate technical versatility, moving fluidly between core development tasks and problem-solving exercises that validate your engineering fundamentals. The work environment at Droisys is fast-paced and requires a high degree of autonomy. You will contribute to projects that demand both depth in programming and the ability to articulate technical concepts clearly to cross-functional teams. Success in this role is defined by your ability to deliver high-quality code, maintain rigorous standards in your development lifecycle, and effectively navigate the technical challenges presented by diverse client engagements. ##### Tip Given the distributed nature of the company’s operations, your ability to communicate effectively in remote or hybrid settings is just as critical as your technical proficiency.
Recruiter Screening
reportedInitial contact with a recruiter to assess candidate fit for the role.
What to demonstrate
- Initial contact with a recruiter to assess candidate fit for the role
- Depth in SQL
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 Assessments
reportedCandidates complete assessments that may include SQL or coding challenges.
What to demonstrate
- Candidates complete assessments that may include SQL or coding challenges
- Depth in SQL
How to prepare
- Answer aloud and timed: Describe the principles of Object-Oriented Programming (OOP) and how you apply them in your daily work.
- Answer aloud and timed: What are the common pitfalls in memory management for the language you use most?
Technical Deep-Dives
reportedIn-depth discussions with technical managers about technical skills and knowledge.
What to demonstrate
- In-depth discussions with technical managers about technical skills and knowledge
- Depth in SQL
How to prepare
- Answer aloud and timed: Explain how you handle exceptions and errors in a production-grade application.
- Answer aloud and timed: Walk me through the steps you take when debugging a complex issue in a legacy codebase.
Managerial Discussions
reportedConversations with managerial staff to evaluate fit within the team and company culture.
What to demonstrate
- Conversations with managerial staff to evaluate fit within the team and company culture
- Depth in SQL
How to prepare
- Answer aloud and timed: How would you design a system that needs to handle high concurrency?
- Answer aloud and timed: Describe a situation where you had to choose between two different technical implementations; what was your decision criteria?
PracHub editorial advice for the preparation topics above.
Get it in writing
If you discuss specific compensation or project details, ensure you have a written record of these commitments.
Master the fundamentals
Do not over-rely on frameworks; ensure your core understanding of logic and data structures is sharp.
Prepare for remote interviews
Practice talking through your screen or using a whiteboard tool, as many interviews are conducted via video conferencing.
Be proactive
If you haven't heard back within a reasonable timeframe, send a polite, professional follow-up email to your recruiter.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Can you explain the difference between a process and a thread?
Can you explain the difference between a process and a thread?
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?
What are the common pitfalls in memory management for the language you use most?
What are the common pitfalls in memory management for the language you use most?
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?
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?
How do you optimize a slow-running SQL query?
How do you optimize a slow-running SQL query?
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?
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?
Describe the principles of Object-Oriented Programming (OOP) and how you apply them in your daily work.
Describe the principles of Object-Oriented Programming (OOP) and how you apply them in your daily work.
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 how you handle exceptions and errors in a production-grade application.
Explain how you handle exceptions and errors in a production-grade 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?
How would you design a system that needs to handle high concurrency?
How would you design a system that needs to handle high concurrency?
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 a situation where you had to choose between two different technical implementations; what was your de
Describe a situation where you had to choose between two different technical implementations; what was your decision criteria?
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 do you ensure your code is scalable and maintainable?
How do you ensure your code is scalable and maintainable?
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?
Walk me through the steps you take when debugging a complex issue in a legacy codebase.
Walk me through the steps you take when debugging a complex issue in a legacy codebase.
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 Droisys candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Droisys loop
- Write out the reported sequence: Recruiter Screening, Technical Assessments, Technical Deep-Dives, Managerial Discussions.
- 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 SQL
- Spend the session on SQL, which Droisys candidates report being tested on.
- Write one worked example in SQL and time yourself on it.
Deliverable: One timed worked example in SQL.
03Work Assessment Testing
- Spend the session on Assessment Testing, which Droisys candidates report being tested on.
- Write one worked example in Assessment Testing and time yourself on it.
Deliverable: One timed worked example in Assessment Testing.
04Work Problem Solving
- Spend the session on Problem Solving, which Droisys 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.
05Answer out loud: Technical Fundamentals
- Answer aloud, timed: Can you explain the difference between a process and a thread?
- Answer aloud, timed: How do you optimize a slow-running SQL query?
Deliverable: Spoken answers to 2 reported Technical Fundamentals question(s), under time.
06Answer out loud: Problem-Solving and Logic
- Answer aloud, timed: Walk me through the steps you take when debugging a complex issue in a legacy codebase.
- Answer aloud, timed: How would you design a system that needs to handle high concurrency?
Deliverable: Spoken answers to 2 reported Problem-Solving and Logic question(s), under time.
07Answer out loud: Behavioral and Professional
- Answer aloud, timed: Describe a time you disagreed with a technical decision made by a manager or peer. How did you resolve it?
- Answer aloud, timed: Tell me about a project where you had to meet a tight deadline under pressure.
Deliverable: Spoken answers to 2 reported Behavioral and Professional 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 disagreed with a technical decision made by a manager or peer. How did you resolve it?
Describe a time you disagreed with a technical decision made by a manager or peer. How did you resolve 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?
Tell me about a project where you had to meet a tight deadline under pressure.
Tell me about a project where you had to meet a tight deadline under pressure.
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 keep your technical skills updated in such a fast-evolving industry?
How do you keep your technical skills updated in such a fast-evolving industry?
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 are you interested in joining Droisys specifically?
Why are you interested in joining Droisys specifically?
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 disagreed with a technical decision made by a manager or peer. How did you resolve it?
- 02
Tell me about a project where you had to meet a tight deadline under pressure.
- 03
How do you keep your technical skills updated in such a fast-evolving industry?
- 04
Why are you interested in joining Droisys specifically?
How long does the entire process take?
Timelines vary. It is best to remain engaged but keep your options open.
Droisys Software Engineer candidate reports ↗How difficult are the technical rounds?
The difficulty is generally considered average. The focus is usually on core concepts and practical application rather than obscure, overly complex algorithmic puzzles.
Droisys Software Engineer candidate reports ↗Is everything negotiable?
Be cautious. Ensure that all aspects of your offer, especially compensation and benefits, are provided to you in writing before you commit to any next steps.
Droisys Software Engineer candidate reports ↗What topics does Droisys test in interviews?
Droisys interviews most often cover SQL, Assessment Testing, Problem Solving, Basic Concepts (Core Knowledge), and Technical Interviewing. The exact emphasis depends on the specific role you apply for.
Droisys 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.
- 01Droisys 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.
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.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai 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.
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.