As a Software Engineer at SRP, you play a vital role in building, maintaining, and modernizing the core software systems that power essential utility infrastructure and business operations. Your work directly impacts millions of customers across the region by ensuring reliable delivery of power, water, and enterprise services. Whether you are developing robust backend applications, integrating enterprise platforms like SAP, or engineering cloud-native infrastructure, your code directly supports mission-critical operations. This position bridges complex enterprise requirements with modern engineering practices, requiring you to navigate both large-scale legacy systems and cutting-party tooling. You will collaborate closely with cross-functional teams, including product managers, system architects, and operations specialists, to design scalable solutions. The environment balances stability and innovation, giving you the opportunity to influence strategic technology decisions while maintaining high standards of system reliability. Expect a collaborative workplace culture where engineering rigor meets public service utility missions. While the technical stacks often involve enterprise frameworks, databases, and cloud platforms, the primary focus remains on creating maintainable, high-impact software. You'll find that success at requires a blend of solid technical execution, clear communication, and a genuine interest in solving real-world utility and operational challenges. SRP
Initial Screening
reportedA recruiter or team lead reviews your background and general qualifications.
What to demonstrate
- A recruiter or team lead reviews your background and general qualifications
- 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.
Comprehensive Panel Interview
reportedCandidates participate in a multi-person panel discussion with hiring managers, senior developers, and principal engineers.
What to demonstrate
- Candidates participate in a multi-person panel discussion with hiring managers, senior developers, and principal engineers
- Depth in Software Engineering (General)
How to prepare
- Answer aloud and timed: Can you describe a complex software project you delivered from conception to production?
- Answer aloud and timed: What is your experience working within Agile methodologies and sprint cycles?
PracHub editorial advice for the preparation topics above.
Emphasize maintainability
When discussing past projects, highlight how you ensured your code was readable, testable, and maintainable by other engineers. SRP values long-term system stability over quick hacks.
Prepare STAR-format stories
For behavioral questions regarding teamwork, conflict, or ambiguity, structure your answers using the Situation, Task, Action, Result framework to keep your responses concise and impactful.
Ask insightful questions
Use the panel interview at the end of your sessions to ask about team tech debt, deployment cadences, and how engineering interacts with operations. It demonstrates genuine professional curiosity.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
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?
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?
Why did you decide to move away from using certain query patterns, such as LINQ queries, in specific performan
Why did you decide to move away from using certain query patterns, such as LINQ queries, in specific performance-critical scenarios?
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?
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?
Walk me through your resume and highlight your most relevant development projects.
Walk me through your resume and highlight your most relevant development projects.
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 did you find out about this role and what specifically interests you in working at SRP?
How did you find out about this role and what specifically interests you in working at SRP?
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 describe a complex software project you delivered from conception to production?
Can you describe a complex software project you delivered from conception to production?
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 your approach to writing unit tests and maintaining code coverage in a legacy codebase?
Can you explain your approach to writing unit tests and maintaining code coverage in a legacy codebase?
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 design for high availability and fault tolerance in enterprise software architectures?
How do you design for high availability and fault tolerance in enterprise software architectures?
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 approach debugging a performance bottleneck in a distributed application?
How do you approach debugging a performance bottleneck in a distributed application?
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 SRP candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the SRP loop
- Write out the reported sequence: Initial Screening, Comprehensive Panel Interview.
- 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 2 reported rounds, with the weakest marked.
02Work Software Engineering (General)
- Spend the session on Software Engineering (General), which SRP 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 Behavioral Interview Skills
- Spend the session on Behavioral Interview Skills, which SRP candidates report being tested on.
- Write one worked example in Behavioral Interview Skills and time yourself on it.
Deliverable: One timed worked example in Behavioral Interview Skills.
04Work Communication Skills
- Spend the session on Communication Skills, which SRP candidates report being tested on.
- Write one worked example in Communication Skills and time yourself on it.
Deliverable: One timed worked example in Communication Skills.
05Answer out loud: Background and Experience
- Answer aloud, timed: Walk me through your resume and highlight your most relevant development projects.
- Answer aloud, timed: How did you find out about this role and what specifically interests you in working at SRP?
Deliverable: Spoken answers to 2 reported Background and Experience question(s), under time.
06Answer out loud: Behavioral and Situational
- Answer aloud, timed: What would you consider to be your greatest strength and your greatest weakness as a developer?
- Answer aloud, timed: Tell me about a time you experienced a conflict or disagreement with a coworker and how you resolved it.
Deliverable: Spoken answers to 2 reported Behavioral and Situational question(s), under time.
07Answer out loud: Technical and Domain-Specific
- Answer aloud, timed: What is your experience working with enterprise platforms like Microsoft Dynamics or SAP integration frameworks?
- Answer aloud, timed: How do you approach debugging a performance bottleneck in a distributed application?
Deliverable: Spoken answers to 2 reported Technical and Domain-Specific 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 working within Agile methodologies and sprint cycles?
What is your experience working within Agile methodologies and sprint cycles?
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 would you consider to be your greatest strength and your greatest weakness as a developer?
What would you consider to be your greatest strength and your greatest weakness as a developer?
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 experienced a conflict or disagreement with a coworker and how you resolved it.
Tell me about a time you experienced a conflict or disagreement with a coworker and how you resolved 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 situations where you are given a task with a lack of information or unclear requirements?
How do you handle situations where you are given a task with a lack of information or unclear requirements?
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 is your experience working with enterprise platforms like Microsoft Dynamics or SAP integration framework
What is your experience working with enterprise platforms like Microsoft Dynamics or SAP integration frameworks?
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 working within Agile methodologies and sprint cycles?
- 02
What would you consider to be your greatest strength and your greatest weakness as a developer?
- 03
Tell me about a time you experienced a conflict or disagreement with a coworker and how you resolved it.
- 04
How do you handle situations where you are given a task with a lack of information or unclear requirements?
How difficult is the interview process at SRP?
The overall interview process is generally rated as average in difficulty, focusing heavily on clear communication, practical experience, and cultural alignment rather than grueling live coding drills. Expect conversational panel interviews where your background and problem-solving mindset take center stage.
SRP Software Engineer candidate reports ↗How much preparation time should I plan for?
Aim for at least one to two weeks of focused preparation, reviewing your past resume projects, brushing up on system design fundamentals, and practicing behavioral stories using structured formats. Understanding your own past technical decisions is more valuable here than cramming algorithms.
SRP Software Engineer candidate reports ↗What differentiates successful candidates from others?
Successful candidates demonstrate a strong sense of ownership, genuine curiosity about utility technology domains, and the ability to explain complex technical concepts simply. Showing that you care deeply about code maintainability and team collaboration sets you apart.
SRP Software Engineer candidate reports ↗What is the typical timeline from initial application to offer?
The timeline can vary, ranging from a few weeks to over a month depending on scheduling coordination with the hiring panel. Communication from recruiters and team leads is generally steady, though some steps may move at a deliberate enterprise pace.
SRP Software Engineer candidate reports ↗Are remote or hybrid work options available?
Work arrangements depend heavily on the specific engineering team and business unit, with many roles offering hybrid schedules based out of the Phoenix and Tempe, Arizona metropolitan areas. Be sure to clarify location expectations with your recruiter early in the process.
SRP Software Engineer candidate reports ↗What topics does SRP test in interviews?
SRP interviews most often cover Problem Solving, Stakeholder Management, Communication Skills, SIEM (Security Information and Event Management), and Data Analysis. The exact emphasis depends on the specific role you apply for.
SRP 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.
- 01SRP 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.
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.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
Booking.com Software Engineer Interview Questions & Guide 2026
Systems practice for Booking.com software engineer candidates, weighted toward travel and hospitality work: the load that actually arrives, the failure modes that matter there, and the invariants a partial outage must not break.
Zebra Technologies Software Engineer Interview Guide
What Zebra Technologies asks Software Engineer candidates, from reported rounds and questions.