As a Software Engineer at SRM Tech, you are at the heart of our mission to deliver high-performance digital solutions. This role is pivotal in bridging the gap between complex client requirements and scalable technical execution. You will be expected to contribute to the full software development lifecycle, ensuring that our products not only meet current industry standards but also provide long-term value to our diverse portfolio of clients. The environment at SRM Tech is fast-paced and collaborative, often involving specialized platforms like ServiceNow or modern web stacks like the MERN suite. You will work within teams that value precision, clear communication, and the ability to adapt to varying project domains—from technical product development to enterprise-level business solutions. This is an opportunity to influence the technical direction of our projects while honing your skills in a professional, growth-oriented atmosphere. ##### Tip SRM Tech values candidates who demonstrate both technical depth and a strong sense of ownership over their project outcomes.
Initial Screening
reportedGauge your background and interest in the position.
What to demonstrate
- Gauge your background and interest in the position
- Depth in MERN Stack
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
reportedIncludes project presentations or coding evaluations to test technical skills.
What to demonstrate
- Includes project presentations or coding evaluations to test technical skills
- Depth in MERN Stack
How to prepare
- Answer aloud and timed: How do you optimize Database queries for performance in high-traffic applications?
- Answer aloud and timed: What are the key differences between various architectural patterns you have used in past projects?
Discussion of Past Work
reportedDiscuss your previous projects to provide insight into your practical engineering skills.
What to demonstrate
- Discuss your previous projects to provide insight into your practical engineering skills
- Depth in MERN Stack
How to prepare
- Answer aloud and timed: How do you ensure code quality and maintainability in a collaborative team environment?
- Answer aloud and timed: Can you walk us through a specific college or professional project and the technical hurdles you overcame?
Situational Assessments
reportedFinal HR round focusing on your fit with the team culture and potential for growth.
What to demonstrate
- Final HR round focusing on your fit with the team culture and potential for growth
- Depth in MERN Stack
How to prepare
- Answer aloud and timed: How do you approach debugging a complex issue that you have never encountered before?
- Answer aloud and timed: Describe a time you had to learn a new technology on the fly to meet a project deadline.
PracHub editorial advice for the preparation topics above.
Structure your answers
Use the STAR method (Situation, Task, Action, Result) to keep your behavioral answers concise and impactful.
Be honest about your limits
If you don't know an answer, explain how you would go about finding it rather than guessing.
Review your resume
Be prepared to discuss every single project or skill you have listed; nothing is off-limits.
Research the company
Understand our focus on enterprise solutions and digital transformation to show that you are aligned with our business goals.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Can you walk us through a specific college or professional project and the technical hurdles you overcame?
Can you walk us through a specific college or professional project and the technical hurdles you overcame?
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?
Diff a projection against the primary without per-row point reads
The listing projection has drifted and some rows show a stale version. The primary holds 40,000,000 resource rows across 12,000 tenants while serving 1,200 writes and 14,000 reads per second. The obvious repair, reading each resource row and comparing its version against the projection, is correct and would eventually finish. Explain precisely why it is unacceptable here, then give a diff that finds the differing rows, state its complexity, and make it safe to run against a live primary. Replication lag is usually under 100 ms and is not bounded.
Approach
- Quantify the naive cost rather than calling it slow: 40,000,000 point reads at even 0.5 ms each is over five hours serialised, and the only lever is concurrency, which is exactly what you cannot spend. The primary's pool is sized for the write path, and 40,000,000 random reads evict the buffer cache that sustains the 85 percent cache hit rate, so the audit degrades the system it is auditing.
- Replace random access with one ordered pass per side. Both sides can be read in (tenant_id, resource_id) order, which is a sequential scan on each and a merge join in O(n) time and O(1) memory. For a dense diff that is the whole answer, and it reads the primary once instead of 40,000,000 times.
- For the expected sparse case, compare range hashes instead of rows: partition the key space, compute per range an order-independent aggregate over hash(resource_id, version), compare aggregates, and descend only into ranges that differ. With d differing rows and branching factor B, at most d ranges mismatch per level, so the drill-down examines O(d log_B(n/d)) ranges and reads full rows only in mismatching leaves.
- Aggregate with a sum modulo 2^64 or a multiset hash, never XOR. XOR is order-independent but self-cancelling, so two rows wrong in the same way, or a row duplicated on one side, leave the range aggregate matching and the range is declared clean.
Follow-up
- The diff reports 900 stale rows. How do you decide between patching those rows and rebuilding the projection from resource_revision?
- Same job, but the projection lives in a search index that cannot be scanned in key order. What changes?
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?
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?
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?
Can you explain the core concepts of the MERN stack and how you manage state in Express.js?
Can you explain the core concepts of the MERN stack and how you manage state in Express.js?
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 optimize Database queries for performance in high-traffic applications?
How do you optimize Database queries for performance in high-traffic applications?
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 differences between various architectural patterns you have used in past projects?
What are the key differences between various architectural patterns you have used in past projects?
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 in a collaborative team environment?
How do you ensure code quality and maintainability in a collaborative team 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 approach debugging a complex issue that you have never encountered before?
How do you approach debugging a complex issue that you have never encountered before?
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 SRM Tech candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the SRM Tech loop
- Write out the reported sequence: Initial Screening, Technical Assessments, Discussion of Past Work, Situational Assessments.
- 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 MERN Stack
- Spend the session on MERN Stack, which SRM Tech candidates report being tested on.
- Write one worked example in MERN Stack and time yourself on it.
Deliverable: One timed worked example in MERN Stack.
03Work ServiceNow (platform)
- Spend the session on ServiceNow (platform), which SRM Tech candidates report being tested on.
- Write one worked example in ServiceNow (platform) and time yourself on it.
Deliverable: One timed worked example in ServiceNow (platform).
04Work Systematic Problem Solving
- Spend the session on Systematic Problem Solving, which SRM Tech candidates report being tested on.
- Write one worked example in Systematic Problem Solving and time yourself on it.
Deliverable: One timed worked example in Systematic Problem Solving.
05Answer out loud: Technical Proficiency and Domain Knowledge
- Answer aloud, timed: Can you explain the core concepts of the MERN stack and how you manage state in Express.js?
- Answer aloud, timed: What is your experience with ServiceNow development, specifically regarding CSA (Certified System Administrator) or CAD (Certified Application Developer) certifications?
Deliverable: Spoken answers to 2 reported Technical Proficiency and Domain Knowledge question(s), under time.
06Answer out loud: Project Experience and Problem Solving
- Answer aloud, timed: Can you walk us through a specific college or professional project and the technical hurdles you overcame?
- Answer aloud, timed: How do you approach debugging a complex issue that you have never encountered before?
Deliverable: Spoken answers to 2 reported Project Experience and Problem Solving question(s), under time.
07Answer out loud: Behavioral and Soft Skills
- Answer aloud, timed: How do you handle feedback from senior engineers or project managers?
- Answer aloud, timed: Tell us about a time you had to explain a complex technical concept to a non-technical stakeholder.
Deliverable: Spoken answers to 2 reported Behavioral and Soft Skills 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.
What is your experience with ServiceNow development, specifically regarding CSA (Certified System Administrato
What is your experience with ServiceNow development, specifically regarding CSA (Certified System Administrator) or CAD (Certified Application Developer) certifications?
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 time you had to learn a new technology on the fly to meet a project deadline.
Describe a time you had to learn a new technology on the fly to meet a project deadline.
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 situations where requirements change mid-sprint?
How do you handle situations where requirements change mid-sprint?
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 managers?
How do you handle feedback from senior engineers or project managers?
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 us about a time you had to explain a complex technical concept to a non-technical stakeholder.
Tell us about a time you had to explain a complex technical concept 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 manage your time when juggling multiple tasks or project components?
How do you manage your time when juggling multiple tasks or project components?
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 had to collaborate with a difficult team member to reach a common goal.
Describe a situation where you had to collaborate with a difficult team member to reach a common goal.
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
What is your experience with ServiceNow development, specifically regarding CSA (Certified System Administrator) or CAD (Certified Application Developer) certifications?
- 02
Describe a time you had to learn a new technology on the fly to meet a project deadline.
- 03
How do you handle situations where requirements change mid-sprint?
- 04
How do you handle feedback from senior engineers or project managers?
How long does the entire interview process usually take?
The timeline varies, but we aim for efficiency. Some candidates have experienced same-day interview-to-result processes, while others may take a few weeks depending on the role level and team availability.
SRM Tech Software Engineer candidate reports ↗What is the most common reason candidates do not pass the interview?
Often, it is a lack of depth regarding their own project experience or an inability to communicate their thought process clearly during technical problem-solving sessions.
SRM Tech Software Engineer candidate reports ↗Does SRM Tech support remote or hybrid work?
Expectations around location depend on the specific project and team needs; these are typically discussed during the initial screening round.
SRM Tech Software Engineer candidate reports ↗How should I prepare for the technical round if I am not familiar with ServiceNow?
Focus on your core engineering fundamentals—data structures, algorithms, and software design principles—as these are transferable across any platform we use.
SRM Tech Software Engineer candidate reports ↗What topics does SRM Tech test in interviews?
SRM Tech interviews most often cover MERN Stack, ServiceNow (platform), Systematic Problem Solving, ServiceNow CSA Certification (Core System Admin), and ServiceNow CAD Certification (Developer). The exact emphasis depends on the specific role you apply for.
SRM Tech 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.
- 01SRM Tech 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.