At G R Infraprojects, the Software Engineer role—often aligned with Senior Engineer responsibilities—is a critical bridge between advanced engineering principles and large-scale infrastructure execution. As a leader in the road and highway construction sector, G R Infraprojects relies on engineers who can translate technical specifications into tangible, high-quality results. You will be expected to apply your expertise in structural integrity, material science, and project estimation to support complex, high-stakes infrastructure projects across India. This role is not merely about writing code or performing calculations; it is about ensuring that the digital and structural foundations of our projects remain robust and reliable. You will work within multidisciplinary teams, collaborating with project managers and site engineers to drive efficiency in construction workflows. Given the nature of our work, the role demands high adaptability, a willingness to travel to project sites, and the ability to maintain rigorous safety and quality standards under field conditions.
Computer-Based Test
reportedInitial screening to evaluate core technical knowledge.
What to demonstrate
- Initial screening to evaluate core technical knowledge
- Depth in Highway/Road Engineering
How to prepare
- Answer aloud and timed: What are the different layers of a road and their respective thicknesses?
- Answer aloud and timed: Explain the meaning of M20 or M35 in the context of concrete technology.
Technical Discussion
reportedIn-depth conversation with subject matter experts about technical competencies.
What to demonstrate
- In-depth conversation with subject matter experts about technical competencies
- Depth in Highway/Road Engineering
How to prepare
- Answer aloud and timed: Define Bending Moment and explain the difference between Bending Moment and Moment of Resistance.
- Answer aloud and timed: What are the key control measures required when working at height?
HR Conversation
reportedDiscussion with the human resources team to assess fit within the company culture.
What to demonstrate
- Discussion with the human resources team to assess fit within the company culture
- Depth in Highway/Road Engineering
How to prepare
- Answer aloud and timed: Can you explain concepts like CBR (California Bearing Ratio), Bar Bending Schedules, and BMD diagrams?
- Answer aloud and timed: Why did you choose civil engineering as your career path?
PracHub editorial advice for the preparation topics above.
Review your resume
Ensure you can explain every project mentioned in your documentation with technical precision.
Focus on basics
Many candidates struggle with fundamental questions like concrete grades or road layers; do not skip the basics in your review.
Show enthusiasm
Our team values candidates who are genuinely excited about the impact of road and infrastructure development.
Prepare for behavioral questions
Be ready to discuss your career motivations and how you handle professional challenges.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
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?
Archive a resource graph without breaking live references or recursing
Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.
Approach
- Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
- Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
- Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
- Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.
Follow-up
- The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
- The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?
Canonicalise a request body into a stable idempotency fingerprint
idempotency_key.request_fingerprint is a SHA-256 over the method, path and canonicalised body, and a retry whose fingerprint differs must be rejected with 422 rather than served the stored response. Write the canonicaliser. Bodies are JSON up to 256 KB nested at most 32 levels; clients vary key order, whitespace and unicode escaping, and some send 64-bit ids as JSON numbers. Produce a deterministic byte string such that semantically identical bodies match and any semantic difference does not. State your complexity and name two normalisations you refuse to perform.
Approach
- Parse once into a tree, then re-serialise under fixed rules: object keys sorted, array order preserved, one escaping convention, no insignificant whitespace. Parsing is O(n) and sorting keys is O(k log k) per object, so O(n log n) overall with O(depth) stack, and the 32-level cap is enforced during parsing because hostile nesting is how a canonicaliser becomes a stack overflow.
- Sort keys by their UTF-8 bytes and say why the obvious implementation is wrong in some runtimes: a default string comparison that orders by UTF-16 code units places surrogate pairs, meaning code points from U+10000 up, below U+E000 to U+FFFF, which is not UTF-8 byte order, so two services written in different languages disagree on the same document.
- Do not re-encode numbers through a double. IEEE-754 binary64 represents integers exactly only up to 2^53, so normalising a 19-digit id through a float changes it, and 1 against 1.0 cannot be reconciled without deciding whether they are the same value. Preserve the literal token, and require ids as strings at the API boundary if you want them comparable.
- Reject duplicate keys rather than picking one. JSON permits them and parsers disagree, most keeping the last, so any choice you make ties the fingerprint to a parser detail that the code handling the request does not necessarily share.
Follow-up
- A client sends the same logical request with an extra field your API ignores. Same key, different fingerprint, so you return 422. Is that the right answer?
- Where does the fingerprint get computed relative to request decompression and the body-size limit?
Why do you want to join G R Infraprojects?
Why do you want to join G R Infraprojects?
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?
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?
What are the different layers of a road and their respective thicknesses?
What are the different layers of a road and their respective thicknesses?
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 the meaning of M20 or M35 in the context of concrete technology.
Explain the meaning of M20 or M35 in the context of concrete technology.
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?
Define Bending Moment and explain the difference between Bending Moment and Moment of Resistance.
Define Bending Moment and explain the difference between Bending Moment and Moment of Resistance.
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 key control measures required when working at height?
What are the key control measures required when working at height?
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?
Can you explain concepts like CBR (California Bearing Ratio), Bar Bending Schedules, and BMD diagrams?
Can you explain concepts like CBR (California Bearing Ratio), Bar Bending Schedules, and BMD diagrams?
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?
Every query on one table stalls for forty seconds mid-deploy
During a release on PostgreSQL, every query touching resource times out for about 40 seconds and then recovers with no intervention. The release ran one migration, ALTER TABLE resource ADD COLUMN archived_reason TEXT, and the migration log shows it completing in 6 ms. Unrelated tables showed no change in error rate. Explain how a 6 ms statement caused a 40-second stall, give the ordered checks you would run on a live system to confirm it, and give the migration procedure that prevents a repeat.
Approach
- Separate the statement's duration from the lock's duration. ADD COLUMN with no default is a catalogue-only change and genuinely runs in milliseconds, but it requires ACCESS EXCLUSIVE, and it cannot acquire that until every transaction already touching the table has finished.
- Account for the queueing, which is the part that surprises people. A lock request that is waiting blocks later requests for conflicting modes behind it rather than letting them overtake, so one long-open transaction holds the DDL and the DDL holds all the traffic. The stall length is set by the longest open transaction, not by the size of the change.
- Confirm on a live system in this order: pg_stat_activity for that table ordered by xact_start, looking for the oldest transaction and specifically for state = idle in transaction; then pg_locks where granted = false to find the waiter; then join them on pid to name blocker and blocked. pg_blocking_pids() does that join for you and is the fastest single call.
- Prevent rather than merely time it better. Set lock_timeout to a second or two on the migration session so the DDL abandons the queue after a bounded wait and is retried, instead of holding it for as long as the oldest transaction lives. Be exact about what that buys: queries arriving during the wait still queue behind the pending ACCESS EXCLUSIVE request, so each attempt costs them up to one lock_timeout of added latency. The outage goes from 40 seconds to about one second per attempt, not to zero. Also run migrations away from deploy-time peaks, and put a statement timeout and an idle-in-transaction timeout on the analytics role that opens the long transactions.
Follow-up
- The same release also wants NOT NULL on that column. What is the sequence that gets there without a long lock?
- Your lock_timeout retry fails ten times in a row because the analytics transaction is always open. What do you change?
Built from the rounds and topics G R Infraprojects candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the G R Infraprojects loop
- Write out the reported sequence: Computer-Based Test, Technical Discussion, HR Conversation.
- 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 Highway/Road Engineering
- Spend the session on Highway/Road Engineering, which G R Infraprojects candidates report being tested on.
- Write one worked example in Highway/Road Engineering and time yourself on it.
Deliverable: One timed worked example in Highway/Road Engineering.
03Work Civil Engineering Fundamentals
- Spend the session on Civil Engineering Fundamentals, which G R Infraprojects candidates report being tested on.
- Write one worked example in Civil Engineering Fundamentals and time yourself on it.
Deliverable: One timed worked example in Civil Engineering Fundamentals.
04Work Pavement Structure / Road Layers
- Spend the session on Pavement Structure / Road Layers, which G R Infraprojects candidates report being tested on.
- Write one worked example in Pavement Structure / Road Layers and time yourself on it.
Deliverable: One timed worked example in Pavement Structure / Road Layers.
05Answer out loud: Technical Engineering Fundamentals
- Answer aloud, timed: What are the different layers of a road and their respective thicknesses?
- Answer aloud, timed: Explain the meaning of M20 or M35 in the context of concrete technology.
Deliverable: Spoken answers to 2 reported Technical Engineering Fundamentals question(s), under time.
06Answer out loud: Behavioral and Professional Motivation
- Answer aloud, timed: Why did you choose civil engineering as your career path?
- Answer aloud, timed: Why do you want to join G R Infraprojects?
Deliverable: Spoken answers to 2 reported Behavioral and Professional Motivation question(s), under time.
07Dry run for G R Infraprojects
- 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.
Why did you choose civil engineering as your career path?
Why did you choose civil engineering as your career path?
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?
What are your primary strengths and weaknesses?
What are your primary strengths and weaknesses?
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 can your experience from previous firms benefit this organization?
How can your experience from previous firms benefit this organization?
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 did you choose civil engineering as your career path?
- 02
What are your primary strengths and weaknesses?
- 03
How can your experience from previous firms benefit this organization?
How difficult are the technical interviews?
The difficulty is moderate to high, depending on your experience level. We focus on fundamental concepts, so if you have a strong grasp of your core curriculum and can explain your past work clearly, you will be well-positioned.
G R Infraprojects Software Engineer candidate reports ↗Is it common to be asked about my previous employers?
Yes. We value candidates who can bridge the gap between past experience and our current needs. Be ready to explain what you learned in previous roles and how that specific knowledge will help G R Infraprojects succeed.
G R Infraprojects Software Engineer candidate reports ↗What is the company culture like for engineers?
The culture is results-oriented and field-focused. We value engineers who are proactive, enthusiastic about physical construction, and capable of working in team-based environments.
G R Infraprojects Software Engineer candidate reports ↗How long does the hiring process usually take?
While timelines can vary, the process is generally efficient. Candidates who clear the initial CBT are usually moved through the interview rounds in a timely manner.
G R Infraprojects Software Engineer candidate reports ↗How many interview rounds does G R Infraprojects have for Software Engineer roles, and what are they?
For Software Engineer hiring at G R Infraprojects, the process runs from a Computer-Based Test, then a Technical Discussion with subject matter experts, and finally an HR Conversation. Candidates typically move forward after the initial CBT screening, then complete the technical discussion before the HR fit check.
G R Infraprojects Software Engineer candidate reports ↗How difficult are the interviews for G R Infraprojects Software Engineer roles, and how often do candidates get offers?
Candidates report the overall difficulty as average for G R Infraprojects Software Engineer interviews. Reported offer rates are high, at 75%, based on candidate-reported outcomes across interviews.
G R Infraprojects Software Engineer candidate reports ↗What technical topics are tested for G R Infraprojects Software Engineer interviews?
Expect technical questions that focus on highway and civil engineering fundamentals, especially road layers and thickness. The tested areas also include concrete technology, concrete mix design and grade notation like M20 and M35, quantity estimation, and bending moment, including the difference between bending moment and moment of resistance.
G R Infraprojects Software Engineer candidate reports ↗What should I prioritize when preparing for the Computer-Based Test and technical discussion at G R Infraprojects for Software Engineer?
Prioritize core engineering fundamentals tied to infrastructure execution, since the first step is a Computer-Based Test screening core technical knowledge. Then be ready to discuss applied engineering using topics like road layers and thickness, concrete grades, quantity estimation, and bending moment, and connect your past work to real constraints and decisions.
G R Infraprojects Software Engineer candidate reports ↗What pay range do candidates report for G R Infraprojects Software Engineer roles?
The provided materials do not include specific pay figures for G R Infraprojects Software Engineer roles, so pay is not stated here. You will need to rely on level and location differences, but the exact reported dollar amounts are not available in the supplied data.
G R Infraprojects Software Engineer candidate reports ↗What kinds of questions show up in public sample questions for G R Infraprojects Software Engineer interviews?
Public sample questions include “Your Strengths and Weaknesses” and “Road Layers and Thickness.” This aligns with the process combining a technical evaluation with behavioral and professional motivation, so prepare to cover both your engineering knowledge and your fit and communication style.
G R Infraprojects 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.
- 01G R Infraprojects 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.