The role of a Software Engineer at Viventis Search Asia is central to the firm’s ability to bridge the gap between high-level business strategy and technical execution. As a partner to diverse clients, the firm relies on engineering professionals who can translate complex data requirements and software needs into scalable, reliable, and high-performance solutions. Whether you are working on.Net Application Development or specialized Report Development using platforms like Tableau, your work directly impacts how organizations visualize their success and maintain their operational infrastructure. This position is particularly critical because it requires a hybrid skill set: deep technical proficiency combined with the consultative mindset necessary to thrive in an agency environment. You will be tasked with building systems that drive efficiency, automate reporting, and provide the clarity stakeholders need to make informed decisions. Expect to work on projects that demand both rigorous attention to detail and the ability to adapt quickly to the varying technical landscapes of the firm’s partners. ##### Tip Your success in this role depends on your ability to demonstrate both technical mastery and a strong service-oriented mindset, as you will often be acting as a bridge between technical requirements and business outcomes.
Initial Screening
reportedDiscuss your background and interest in the role.
What to demonstrate
- Discuss your background and interest in the role
- Depth in Tableau
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 Evaluation
reportedDeep-dive technical evaluations including problem-solving and project discussions.
What to demonstrate
- Deep-dive technical evaluations including problem-solving and project discussions
- Depth in Tableau
How to prepare
- Answer aloud and timed: Describe the lifecycle of a.Net application and how you manage memory leaks.
- Answer aloud and timed: What are the advantages of using a specific framework or library within your preferred development environment?
Behavioral Round
reportedPrepare meaningful anecdotes to demonstrate professional maturity and team integration.
What to demonstrate
- Prepare meaningful anecdotes to demonstrate professional maturity and team integration
- Depth in Tableau
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 round above and write down what you would ask to confirm before it.
PracHub editorial advice for the preparation topics above.
Structure your answers
Use the STAR method (Situation, Task, Action, Result) for all behavioral questions to ensure your responses are concise and impactful.
Show your work
When answering technical questions, explain your thought process. Even if you don't reach the "perfect" solution immediately, showing a logical approach is highly valued.
Know your resume
Be prepared to dive into the technical details of any project you list on your CV. You should be able to justify every tool and methodology you claim to have used.
Research the firm
Understand the position Viventis Search Asia holds in the market. Knowing their business model will help you frame your technical contributions as value-adds for their clients.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Describe a challenging project where the requirements were ambiguous; how did you proceed?
Describe a challenging project where the requirements were ambiguous; how did you proceed?
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?
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?
Find overlapping job attempts and peak concurrency from lease records
A day of job_run history yields about 50,000,000 attempt records: (job_run_id, job_type, attempt, started_at, finished_at which is NULL when the worker died, lease_expires_at). Leases expire on a clock, so a job that outran its lease ran twice. Produce (a) every job_run_id whose attempts overlapped in wall-clock time and (b) the peak number of simultaneously running attempts per job_type with the minute it occurred. Target O(n log n). State how you treat a NULL finished_at and what clock skew does to your answer.
Approach
- Define the interval before sorting anything: an attempt occupies [started_at, COALESCE(finished_at, lease_expires_at)). finished_at is observed and lease_expires_at is only a promise, so every attempt without a finish contributes an estimate and the whole result is a lower bound on overlap rather than an exact count.
- For peak concurrency, sweep: emit 2n endpoints, sort by (timestamp, kind) with ends ordered before starts at equal timestamps, then walk the sequence maintaining a counter per job_type and record each type's maximum with its timestamp. O(n log n) dominated by the sort, O(n) space, or O(1) extra if the sort is external and the walk streams.
- For overlap detection, do not compare attempts pairwise. A single global sort by (job_run_id, started_at) gives both the grouping and the order; within a group, keep the maximum end seen so far and report an overlap exactly when the next start is less than that running maximum, which is one linear pass after the sort.
- Half-open intervals matter and are easy to get wrong: with closed intervals an attempt ending at the same millisecond another begins reads as concurrency two, and across 50,000,000 records that artefact swamps the real signal.
Follow-up
- A handler is not idempotent and you have found 400 overlapping jobs. Which of them actually caused damage, and what would you query to find out?
- Peak concurrency for one job_type is 4 against a configured cap of 4. Is the cap working, or is the data hiding attempts that never started?
Explain the difference between various join types in a database and how they impact report performance.
Explain the difference between various join types in a database and how they impact report performance.
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 the update path that detects a concurrent edit
resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.
Approach
- One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
- Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
- State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
- Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.
Follow-up
- A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
- Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?
How do you optimize a Tableau dashboard that is experiencing slow load times?
How do you optimize a Tableau dashboard that is experiencing slow load times?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What are the advantages of using a specific framework or library within your preferred development environment
What are the advantages of using a specific framework or library within your preferred development environment?
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 data integrity when migrating or transforming large datasets?
How do you ensure data integrity when migrating or transforming large datasets?
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?
Describe the lifecycle of a.Net application and how you manage memory leaks.
Describe the lifecycle of a.Net application and how you manage memory leaks.
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 Viventis Search Asia candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Viventis Search Asia loop
- Write out the reported sequence: Initial Screening, Technical Evaluation, Behavioral Round.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 3 reported rounds, with the weakest marked.
02Work Tableau
- Spend the session on Tableau, which Viventis Search Asia candidates report being tested on.
- Write one worked example in Tableau and time yourself on it.
Deliverable: One timed worked example in Tableau.
03Work .NET
- Spend the session on .NET, which Viventis Search Asia candidates report being tested on.
- Write one worked example in .NET and time yourself on it.
Deliverable: One timed worked example in .NET.
04Work Report Development
- Spend the session on Report Development, which Viventis Search Asia candidates report being tested on.
- Write one worked example in Report Development and time yourself on it.
Deliverable: One timed worked example in Report Development.
05Answer out loud: Technical Proficiency and Domain Knowledge
- Answer aloud, timed: Explain the difference between various join types in a database and how they impact report performance.
- Answer aloud, timed: How do you optimize a Tableau dashboard that is experiencing slow load times?
Deliverable: Spoken answers to 2 reported Technical Proficiency and Domain Knowledge question(s), under time.
06Answer out loud: Behavioral and Situational Scenarios
- Answer aloud, timed: Tell me about a time you had to explain a complex technical issue to a non-technical stakeholder.
- Answer aloud, timed: How do you prioritize your tasks when handling multiple reporting or development requests simultaneously?
Deliverable: Spoken answers to 2 reported Behavioral and Situational Scenarios question(s), under time.
07Dry run for Viventis Search Asia
- Run one full mock under time, then write down the two questions you most want to ask your interviewers.
Deliverable: A completed timed mock and two questions to ask.
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.
Tell me about a time you had to explain a complex technical issue to a non-technical stakeholder.
Tell me about a time you had to explain a complex technical issue to a non-technical stakeholder.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you prioritize your tasks when handling multiple reporting or development requests simultaneously?
How do you prioritize your tasks when handling multiple reporting or development requests simultaneously?
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 a time you received critical feedback on your code or design and how you handled it.
Give an example of a time you received critical feedback on your code or design and how you handled 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?
- 01
Tell me about a time you had to explain a complex technical issue to a non-technical stakeholder.
- 02
How do you prioritize your tasks when handling multiple reporting or development requests simultaneously?
- 03
Give an example of a time you received critical feedback on your code or design and how you handled it.
How long does the interview process typically take?
The timeline can vary depending on the specific team and seniority of the role, but most candidates complete the process within a few weeks. Consistency and responsiveness during the scheduling phases will help keep the process moving efficiently.
Viventis Search Asia Software Engineer candidate reports ↗What is the company culture like?
Viventis Search Asia values professionalism, collaboration, and a results-driven mindset. You will find that the culture emphasizes taking ownership of your work and being a reliable partner to your team and clients.
Viventis Search Asia Software Engineer candidate reports ↗How should I prepare for the technical assessment?
Focus on the fundamentals of your primary technology stack. Practice explaining your code out loud as you write it, as the "why" behind your technical decisions is often as important as the code itself.
Viventis Search Asia Software Engineer candidate reports ↗What topics does Viventis Search Asia test in interviews?
Viventis Search Asia interviews most often cover Credit Risk Analysis, Tableau, Pricing Strategy Development, Cost Accounting Management, and Credit Underwriting. The exact emphasis depends on the specific role you apply for.
Viventis Search Asia 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.
- 01Viventis Search Asia 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.