The Software Engineer role at HOSTECH PMC is a critical function that bridges the gap between complex engineering requirements and scalable technical solutions. As a member of our engineering team, you are responsible for designing, implementing, and maintaining systems that support our large-scale infrastructure projects. You will not just be writing code; you will be architecting solutions that ensure efficiency, safety, and precision in our project delivery lifecycle. This role is inherently collaborative, requiring you to work closely with cross-functional teams, including project managers, civil engineers, and MEP specialists. You will be expected to translate high-level technical requirements into actionable development plans, ensuring that our software products remain robust in a demanding, fast-paced environment. At HOSTECH PMC, we value engineers who possess both strong technical foundations and a deep understanding of the practical challenges our industry faces.
Initial Screening
reportedAssess your background to determine fit for the role.
What to demonstrate
- Assess your background to determine fit for the role
- Depth in Software Engineering (General)
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 Interviews
reportedEvaluate your coding ability and architectural design skills.
What to demonstrate
- Evaluate your coding ability and architectural design skills
- Depth in Software Engineering (General)
How to prepare
- Answer aloud and timed: How do you ensure code quality and maintainability when working in a collaborative environment?
- Answer aloud and timed: Describe your experience with version control and documentation practices.
Cultural Fit Assessment
reportedEnsure alignment with the collaborative, project-focused environment.
What to demonstrate
- Ensure alignment with the collaborative, project-focused environment
- Depth in Software Engineering (General)
How to prepare
- Answer aloud and timed: How do you handle integration challenges between software tools and physical infrastructure data?
- Answer aloud and timed: Tell me about a time you had to manage conflicting project requirements from different stakeholders.
PracHub editorial advice for the preparation topics above.
Review your project history
Be prepared to discuss the most challenging technical project you have worked on in detail, focusing on your specific contributions.
Be ready for ambiguity
In our industry, requirements can change. Show that you can handle uncertainty by asking clarifying questions before jumping into a solution.
Align with our values
Research HOSTECH PMC to understand our commitment to engineering excellence. Reflecting this in your answers will set you apart.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
How do you prioritize your tasks when multiple high-impact projects are running concurrently?
How do you prioritize your tasks when multiple high-impact projects are running concurrently?
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?
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?
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?
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?
How would you approach designing a scalable database structure for a multi-disciplinary project?
How would you approach designing a scalable database structure for a multi-disciplinary project?
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 ensure code quality and maintainability when working in a collaborative environment?
How do you ensure code quality and maintainability when working in a collaborative 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?
Explain your process for debugging a complex system failure under tight project deadlines.
Explain your process for debugging a complex system failure under tight project deadlines.
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 HOSTECH PMC candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the HOSTECH PMC loop
- Write out the reported sequence: Initial Screening, Technical Interviews, Cultural Fit Assessment.
- 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 Software Engineering (General)
- Spend the session on Software Engineering (General), which HOSTECH PMC candidates report being tested on.
- Write one worked example in Software Engineering (General) and time yourself on it.
Deliverable: One timed worked example in Software Engineering (General).
03Work QS Engineering (Quantity Surveying)
- Spend the session on QS Engineering (Quantity Surveying), which HOSTECH PMC candidates report being tested on.
- Write one worked example in QS Engineering (Quantity Surveying) and time yourself on it.
Deliverable: One timed worked example in QS Engineering (Quantity Surveying).
04Work Estimation & Costing
- Spend the session on Estimation & Costing, which HOSTECH PMC candidates report being tested on.
- Write one worked example in Estimation & Costing and time yourself on it.
Deliverable: One timed worked example in Estimation & Costing.
05Answer out loud: Technical Foundations
- Answer aloud, timed: How would you approach designing a scalable database structure for a multi-disciplinary project?
- Answer aloud, timed: Explain your process for debugging a complex system failure under tight project deadlines.
Deliverable: Spoken answers to 2 reported Technical Foundations question(s), under time.
06Answer out loud: Behavioral and Problem Solving
- Answer aloud, timed: Tell me about a time you had to manage conflicting project requirements from different stakeholders.
- Answer aloud, timed: How do you prioritize your tasks when multiple high-impact projects are running concurrently?
Deliverable: Spoken answers to 2 reported Behavioral and Problem Solving question(s), under time.
07Dry run for HOSTECH PMC
- 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.
Describe your experience with version control and documentation practices.
Describe your experience with version control and documentation practices.
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 integration challenges between software tools and physical infrastructure data?
How do you handle integration challenges between software tools and physical infrastructure data?
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 manage conflicting project requirements from different stakeholders.
Tell me about a time you had to manage conflicting project requirements from different stakeholders.
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 identified a technical bottleneck and implemented a solution to resolve it.
Describe a situation where you identified a technical bottleneck and implemented a solution to 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?
How do you handle feedback from senior engineers or project leads on your technical designs?
How do you handle feedback from senior engineers or project leads on your technical designs?
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 your experience with version control and documentation practices.
- 02
How do you handle integration challenges between software tools and physical infrastructure data?
- 03
Tell me about a time you had to manage conflicting project requirements from different stakeholders.
- 04
Describe a situation where you identified a technical bottleneck and implemented a solution to resolve it.
How long does the entire interview process usually take?
The process typically spans a few weeks, depending on your availability and the specific team's requirements. We aim to keep the process efficient while ensuring you have enough time to meet the team and understand our culture.
HOSTECH PMC Software Engineer candidate reports ↗What is the most important thing to emphasize during the interview?
Focus on your ability to solve complex problems and your capacity for cross-functional collaboration. We value engineers who can connect their code to the real-world impact on our projects.
HOSTECH PMC Software Engineer candidate reports ↗Is the work environment at HOSTECH PMC highly collaborative?
Yes, collaboration is fundamental to our success. You will work daily with diverse teams, making communication skills just as important as your technical coding ability.
HOSTECH PMC Software Engineer candidate reports ↗What topics does HOSTECH PMC test in interviews?
HOSTECH PMC interviews most often cover Software Engineering (General), QS Engineering (Quantity Surveying), Estimation & Costing, Measurement & Quantification, and Civil Engineering Domain (Software/Engineering Context). The exact emphasis depends on the specific role you apply for.
HOSTECH PMC 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.
- 01HOSTECH PMC 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.
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.
Lambda Software Engineer Interview Guide
Failure-handling practice for Lambda 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.
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.