Astreya Software Engineer Interview Guide

The 60-second brief

At Astreya, a Software Engineer plays a unique and dynamic role that sits at the intersection of core software development, systems engineering, and IT service delivery. As a premier provider of technology enablement services for some of the world's most recognizable enterprises, Astreya deploys engineers to build, optimize, and support the critical infrastructure and applications that keep global businesses running. In this role, you are not just writing isolated code; you are architecting solutions that directly impact scale, reliability, and user experience. Many software engineering positions at Astreya are embedded directly within client environments—including major tech giants like Google—or focused on internal service delivery platforms.

This guide is scoped to a Software Engineer candidate at Astreya.

Focus areas

• Spring Boot
• SQL
• Network Support

The Astreya interview process

Astreya candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Talent Acquisition Screen

Initial contact to align on basic qualifications, compensation, and role expectations.

What to demonstrate

• Initial contact to align on basic qualifications, compensation, and role expectations
• Depth in Spring Boot

How to prepare

• Answer aloud and timed: Explain the lifecycle of a bean in Spring Boot.
• Answer aloud and timed: How do you optimize a slow-performing SQL query in a production database?

Technical and Behavioral Evaluations

Candidates transition into evaluations that may include a comprehensive technical interview or multiple rounds.

What to demonstrate

• Candidates transition into evaluations that may include a comprehensive technical interview or multiple rounds
• Depth in Spring Boot

How to prepare

• Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
• Re-read the description of the technical and behavioral evaluations above and write down what you would ask to confirm before it.

Client Leadership Interview

For client-embedded roles, candidates interview directly with the client's engineering leadership.

What to demonstrate

• For client-embedded roles, candidates interview directly with the client's engineering leadership
• Depth in Spring Boot

How to prepare

• Answer aloud and timed: What is the difference between a container and a virtual machine?
• Answer aloud and timed: How do you manage secrets and configuration patterns in Kubernetes?

Final Offer Stage

The process wraps up with a final decision and offer discussion.

What to demonstrate

• The process wraps up with a final decision and offer discussion
• Depth in Spring Boot

How to prepare

• Answer aloud and timed: Explain the role of a Dockerfile and how you would optimize it to create smaller, more secure container images.
• Answer aloud and timed: Have you used Docker and Kubernetes together in a production environment? Describe your deployment workflow.

Where candidates lose points

Clarify the Role Scope Early

Because Astreya supports a wide variety of client contracts, the title Software Engineer can sometimes encompass aspects of network engineering, systems administration, or application development. Use your initial call with the recruiter to clarify the exact technical focus of the role you are interviewing for.

Be sure to ask the recruiter if your role is client-embedded

If it is, research the client's engineering culture and prepare for an interview round that aligns with their specific standards and technical stack.

Highlight Your Troubleshooting Methodology

When answering technical questions, don't just jump to the solution. Clearly walk the interviewer through your diagnostic process. Explain how you isolate variables, what logs you would check, and how you verify your hypotheses.

Questions & practice

Identify the heaviest tenants in a five-minute window under memory pressure

Medium · top-k · heavy hitters · streaming

The edge service handles about 3,000 requests per second across roughly 50,000 tenants, peaking near 9,000. Expose the 50 heaviest tenants by request count over the trailing five minutes so limits can be tightened before one tenant's backfill starves the fleet. You may not retain five minutes of raw records. Give the exact solution and its memory, then the bounded-memory approximation with its error stated as a formula, and say which you would ship and at what tenant cardinality that choice changes.

Approach

1. Do the exact version first, because it is affordable at this cardinality: a ring of 300 one-second counters per tenant, advanced lazily, is 1,200 bytes of counters per tenant and roughly 60 to 90 MB for 50,000 tenants with overhead. Carry a running total and subtract the bucket you overwrite so a window read is O(1) rather than 300 adds.
2. Extract the top 50 with a size-k min-heap over the tenant sums: O(d log k) for d tenants, against O(d log d) to sort them all. Maintaining the heap continuously instead of on query requires a tenant-to-heap-index map, because incrementing a count already inside the heap means sifting from a known position, and without that map you rebuild the heap on every request.
3. State the approximation precisely rather than gesturing at sketches. Misra-Gries with m counters retains every item whose true count exceeds N/(m+1), and each retained count underestimates the truth by at most N/(m+1). With m = 1,000 and N = 900,000 requests in the window the error is roughly 900 requests, which is fine for spotting a tenant sending 50,000 and useless for ranking two tenants 200 apart.
4. Say what breaks when the window slides: Misra-Gries and Space-Saving are insert-only and cannot be decremented as records age out. The workable construction is one summary per sub-window, say ten seconds, with 30 summaries merged at query time, and the merged error is the sum of the per-summary errors, so the bound degrades linearly in the number of sub-windows.

Follow-up

• The heaviest tenant is heavy because of one export job rather than user traffic. Should the limiter treat those as the same tenant?
• Two tenants sit tied at the boundary of the top 50. Does your answer flap, and does the flapping matter?

Diff a projection against the primary without per-row point reads

Hard · reconciliation · range hashing · throttling

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

1. 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.
2. 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.
3. 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.
4. 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?

Find overlapping job attempts and peak concurrency from lease records

Medium · sweep line · intervals · leases

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

1. 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.
2. 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.
3. 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.
4. 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?

How do you optimize a slow-performing SQL query in a production database?

Medium · Backend Development & Databases

Approach

1. Name the grain you start from and join outward from it.
2. Check whether any join is one-to-many before aggregating, or the sums inflate.
3. Say which index the query would use, and what makes it unusable.
4. 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?

What are the primary differences between SQL and NoSQL databases, and when would you choose one over the other

Medium · Backend Development & Databases

What are the primary differences between SQL and NoSQL databases, and when would you choose one over the other?

Approach

1. Name the grain you start from and join outward from it.
2. Check whether any join is one-to-many before aggregating, or the sums inflate.
3. Say which index the query would use, and what makes it unusable.
4. 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?

Explain the lifecycle of a bean in Spring Boot.

Medium · Backend Development & Databases

Approach

1. Clarify what is being asked and what a complete answer contains.
2. State your assumptions explicitly before working the problem.
3. Say what you would check first and why it is the highest-information step.
4. Work from the requirement backwards to the design.

Follow-up

• What assumption would you test first?
• How would you know your answer was wrong?

Walk me through how you would design a RESTful API endpoint to handle bulk data uploads.

Medium · Backend Development & Databases

Approach

1. Say who the caller is and what they do when the call fails halfway.
2. Define the identity of a request so a retry cannot double-apply it.
3. Separate accepted, pending, failed and confirmed; they are different facts.
4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

• What happens if the caller retries after a timeout?
• How does a client discover it is on an old version of this contract?

What is the difference between a container and a virtual machine?

Medium · Systems & Containerization

Approach

1. Clarify what is being asked and what a complete answer contains.
2. State your assumptions explicitly before working the problem.
3. Say what you would check first and why it is the highest-information step.
4. 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 manage secrets and configuration patterns in Kubernetes?

Medium · Systems & Containerization

Approach

1. Clarify what is being asked and what a complete answer contains.
2. State your assumptions explicitly before working the problem.
3. Say what you would check first and why it is the highest-information step.
4. 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 role of a Dockerfile and how you would optimize it to create smaller, more secure container images

Medium · Systems & Containerization

Explain the role of a Dockerfile and how you would optimize it to create smaller, more secure container images.

Approach

1. Clarify what is being asked and what a complete answer contains.
2. State your assumptions explicitly before working the problem.
3. Say what you would check first and why it is the highest-information step.
4. Work from the requirement backwards to the design.

Follow-up

• What assumption would you test first?
• How would you know your answer was wrong?

Have you used Docker and Kubernetes together in a production environment? Describe your deployment workflow.

Medium · Systems & Containerization

Approach

1. Clarify what is being asked and what a complete answer contains.
2. State your assumptions explicitly before working the problem.
3. Say what you would check first and why it is the highest-information step.
4. Work from the requirement backwards to the design.

Follow-up

• What assumption would you test first?
• How would you know your answer was wrong?

Walk me through your step-by-step process for troubleshooting a network connection timeout between two microse

Medium · Infrastructure & Network Troubleshooting

Walk me through your step-by-step process for troubleshooting a network connection timeout between two microservices.

Approach

1. Establish what changed and when, before forming any theory.
2. Pick a bisection that eliminates candidates whichever way it turns out.
3. Check the instrumentation before believing the symptom.
4. 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?

What happens at the network level when you type a URL into a browser and press Enter?

Medium · Infrastructure & Network Troubleshooting

Approach

1. Establish what changed and when, before forming any theory.
2. Pick a bisection that eliminates candidates whichever way it turns out.
3. Check the instrumentation before believing the symptom.
4. 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?

Explain the difference between TCP and UDP, and provide a scenario where you would favor UDP.

Medium · Infrastructure & Network Troubleshooting

Approach

1. Establish what changed and when, before forming any theory.
2. Pick a bisection that eliminates candidates whichever way it turns out.
3. Check the instrumentation before believing the symptom.
4. 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?

How do you diagnose a DNS resolution issue on a Linux-based server?

Medium · Infrastructure & Network Troubleshooting

Approach

1. Establish what changed and when, before forming any theory.
2. Pick a bisection that eliminates candidates whichever way it turns out.
3. Check the instrumentation before believing the symptom.
4. 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?

Suggested practice checklist

Built from the rounds and topics Astreya candidates report.

Day 1 — Map the Astreya loop

• Write out the reported sequence: Talent Acquisition Screen, Technical and Behavioral Evaluations, Client Leadership Interview, Final Offer Stage.
• 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.

Day 2 — Work Spring Boot

• Spend the session on Spring Boot, which Astreya candidates report being tested on.
• Write one worked example in Spring Boot and time yourself on it.

Deliverable: One timed worked example in Spring Boot.

Day 3 — Work SQL

• Spend the session on SQL, which Astreya candidates report being tested on.
• Write one worked example in SQL and time yourself on it.

Deliverable: One timed worked example in SQL.

Day 4 — Work Network Support

• Spend the session on Network Support, which Astreya candidates report being tested on.
• Write one worked example in Network Support and time yourself on it.

Deliverable: One timed worked example in Network Support.

Day 5 — Answer out loud: Backend Development & Databases

• Answer aloud, timed: Explain the lifecycle of a bean in Spring Boot.
• Answer aloud, timed: How do you optimize a slow-performing SQL query in a production database?

Deliverable: Spoken answers to 2 reported Backend Development & Databases question(s), under time.

Day 6 — Answer out loud: Systems & Containerization

• Answer aloud, timed: What is the difference between a container and a virtual machine?
• Answer aloud, timed: How do you manage secrets and configuration patterns in Kubernetes?

Deliverable: Spoken answers to 2 reported Systems & Containerization question(s), under time.

Day 7 — Answer out loud: Infrastructure & Network Troubleshooting

• Answer aloud, timed: Walk me through your step-by-step process for troubleshooting a network connection timeout between two microservices.
• Answer aloud, timed: What happens at the network level when you type a URL into a browser and press Enter?

Deliverable: Spoken answers to 2 reported Infrastructure & Network Troubleshooting question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe a time when you had to resolve a critical system issue with very little documentation or guidance.

Medium · Behavioral & Client Interaction

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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 tasks and prioritize deliverables when working on multiple projects simultaneously?

Medium · Behavioral & Client Interaction

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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 explain a complex technical issue to a non-technical stakeholder or client.

Medium · Behavioral & Client Interaction

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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 a situation where a client or manager requests a feature that conflicts with best engineerin

Medium · Behavioral & Client Interaction

How do you handle a situation where a client or manager requests a feature that conflicts with best engineering practices?

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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?