A Software Engineer at Sii Group Italy occupies a highly versatile and impactful role within one of Europe's fastest-growing technology consulting and engineering firms. Unlike traditional product-focused engineering positions, engineers here are the primary drivers of digital transformation and technical execution for a diverse portfolio of prestigious clients. This means you will contribute directly to critical systems across key industries, including aerospace, automotive, telecommunications, energy, and financial services. Your work directly influences the success of high-stakes, real-world applications. For instance, you might find yourself designing robust full-stack enterprise systems, developing embedded software for automotive control units, or validating automated systems for aviation leaders like Airbus. Because Sii Group Italy operates on a consulting model, your technical contributions are coupled with a strategic business impact. You will help clients solve complex architectural bottlenecks, modernize legacy codebases, and accelerate their time-to-market. What makes this role exceptionally rewarding is the sheer variety of technical challenges and the rapid professional growth it offers. You are not locked into a single product lifecycle; instead, you have the opportunity to transition across different project domains, master new technology stacks, and collaborate with multidisciplinary teams.
HR Screening Call
reportedConversational call focused on your background, career aspirations, and salary expectations.
What to demonstrate
- Conversational call focused on your background, career aspirations, and salary expectations
- Depth in Testing methodologies
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 Evaluation
reportedIncludes automated coding assessments and a deep-dive technical interview with a Tech Lead or Project Manager.
What to demonstrate
- Includes automated coding assessments and a deep-dive technical interview with a Tech Lead or Project Manager
- Depth in Testing methodologies
How to prepare
- Answer aloud and timed: Walk me through how you would design and optimize a database schema for a high-traffic application tracking flights, planes, and cities.
- Answer aloud and timed: What are the key features of Angular that you rely on for state management and modular development in enterprise applications?
Client Alignment
reportedMeeting with technical representatives of the client company to ensure alignment of technical capabilities and personality.
What to demonstrate
- Meeting with technical representatives of the client company to ensure alignment of technical capabilities and personality
- Depth in Testing methodologies
How to prepare
- Answer aloud and timed: In C++ or embedded development, how do you manage memory allocation to prevent leaks and ensure real-time performance?
- Answer aloud and timed: Describe a complex technical challenge you faced in a previous project and the step-by-step methodology you used to resolve it.
2 candidate reports. Individual accounts describe a particular role and hiring cycle.
Sii Group Italy Software Engineer interview: a fast client-project process
The process was fast and strongly oriented around the assignment. I started with a conversation with a business manager or sales representative. The next day I had a technical interview, followed immediately by another step that moved very quickly. The format surprised me because it was so conventional: direct questions centered on the role. The role was tied to a client project, but I did not ha…
Read full experienceSii Group Italy Software Engineer interview: client preparation
A recruiter contacted me on LinkedIn, and the first steps moved quickly. After an HR interview, I spoke with several business managers who handled group work for different clients. The conversations helped me understand the assignments and what they expected. I then had a client-side technical interview after preparing with a business manager who knew the client's way of working. That preparation…
Read full experiencePracHub editorial advice for the preparation topics above.
Tailor Your CV for Client Presentation
Your CV is the primary tool that Business Managers use to pitch your profile to clients. Ensure your resume clearly highlights your technical stack, your specific contributions to past projects, and the business impact of your work.
Be Ready for a Live Code Walkthrough
During the technical interview, be prepared to share your screen and walk the interviewers through your past code or explain how you would structure a basic application. Focus on explaining your thought process clearly as you design the solution.
Emphasize Your Testing and DevOps Awareness
Even if you are applying for a pure development role, demonstrating that you understand how to write unit tests and how your code integrates into a CI/CD pipeline will set you apart from other candidates.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
In C++ or embedded development, how do you manage memory allocation to prevent leaks and ensure real-time perf
In C++ or embedded development, how do you manage memory allocation to prevent leaks and ensure real-time performance?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
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?
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?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
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?
Explain the differences between interface-based programming and abstract classes in Java or C#, and when you w
Explain the differences between interface-based programming and abstract classes in Java or C#, and when you would choose one over the other.
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 manage dependency injection in.NET Core or Spring Boot applications, and what are the architectural
How do you manage dependency injection in.NET Core or Spring Boot applications, and what are the architectural benefits?
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?
Walk me through how you would design and optimize a database schema for a high-traffic application tracking fl
Walk me through how you would design and optimize a database schema for a high-traffic application tracking flights, planes, and cities.
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?
What are the key features of Angular that you rely on for state management and modular development in enterpri
What are the key features of Angular that you rely on for state management and modular development in enterprise 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?
Describe a complex technical challenge you faced in a previous project and the step-by-step methodology you us
Describe a complex technical challenge you faced in a previous project and the step-by-step methodology you used to resolve it.
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 designing a CRUD API from scratch when given a set of relational database tables and minim
How do you approach designing a CRUD API from scratch when given a set of relational database tables and minimal requirements?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- 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 testing methodologies and automation tools have you integrated into your previous development workflows t
What testing methodologies and automation tools have you integrated into your previous development workflows to ensure code reliability?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- 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?
Edge instances grow 400 MB per hour until the nightly restart
Edge API instances start at 700 MB resident and grow about 400 MB/hour; a nightly rolling restart has hidden it for weeks. Growth continues unchanged when request rate halves overnight, p99 degrades in the last hours before an instance is recycled, and heap used immediately after a forced full GC rises monotonically. The service holds no product state. Name the discriminating measurement that separates the plausible causes, give the most likely cause, and give the fix and how you would verify it.
Approach
- Separate resident memory from live heap first, because they fail differently. Resident size can grow from fragmentation, native buffers or thread stacks while the heap is flat; heap used after a full GC rising monotonically is the measurement that says objects are reachable and not being released. You already have it, so this is retention, not fragmentation, and that closes off half the candidate list.
- Use the rate's independence from traffic as the discriminator. Growth that continues at half the request rate rules out per-request objects that are merely slow to collect and points at a structure that grows with distinct values observed rather than with call volume. Write the candidates that have that property: a metrics registry keyed on a high-cardinality label, an unevicted cache, an interner, a per-key lock map.
- Take two heap snapshots an hour apart and diff by retained size, reading the dominator tree, not by allocation count or instance count. Expect one root holding a map with millions of entries, then follow the reference chain to the code that inserts and never removes. Allocation profilers point at churn, which is the wrong signal here.
- The candidate that fits this service is an observability label carrying an identifier, such as a request path recorded before templating so that /v1/resources/48213 becomes its own metric series. That grows with distinct ids seen, is independent of rate, and explains the late p99 degradation, since GC cost rises with the size of the live set.
Follow-up
- Post-GC heap is now flat but resident size still creeps. What are you looking at, and does it matter?
- How would you have detected this before an OOM, given the nightly restart masked the trend?
Built from the rounds and topics Sii Group Italy candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Sii Group Italy loop
- Write out the reported sequence: HR Screening Call, Technical Evaluation, Client Alignment.
- 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 Testing methodologies
- Spend the session on Testing methodologies, which Sii Group Italy candidates report being tested on.
- Write one worked example in Testing methodologies and time yourself on it.
Deliverable: One timed worked example in Testing methodologies.
03Work Writing test cases
- Spend the session on Writing test cases, which Sii Group Italy candidates report being tested on.
- Write one worked example in Writing test cases and time yourself on it.
Deliverable: One timed worked example in Writing test cases.
04Work Defect identification
- Spend the session on Defect identification, which Sii Group Italy candidates report being tested on.
- Write one worked example in Defect identification and time yourself on it.
Deliverable: One timed worked example in Defect identification.
05Answer out loud: Technical & Core Programming
- Answer aloud, timed: Explain the differences between interface-based programming and abstract classes in Java or C#, and when you would choose one over the other.
- Answer aloud, timed: How do you manage dependency injection in.NET Core or Spring Boot applications, and what are the architectural benefits?
Deliverable: Spoken answers to 2 reported Technical & Core Programming question(s), under time.
06Answer out loud: Project & Experience Walkthroughs
- Answer aloud, timed: Describe a complex technical challenge you faced in a previous project and the step-by-step methodology you used to resolve it.
- Answer aloud, timed: How do you approach designing a CRUD API from scratch when given a set of relational database tables and minimal requirements?
Deliverable: Spoken answers to 2 reported Project & Experience Walkthroughs question(s), under time.
07Answer out loud: Consulting & Behavioral Alignment
- Answer aloud, timed: How do you handle a situation where a client requests a feature or technical approach that you believe is suboptimal or technically flawed?
- Answer aloud, timed: Describe a time when you had to quickly ramp up on a completely new programming language or framework to meet a project deadline.
Deliverable: Spoken answers to 2 reported Consulting & Behavioral Alignment 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.
Walk me through your experience with CI/CD pipelines. How do you automate testing and deployment for the appli
Walk me through your experience with CI/CD pipelines. How do you automate testing and deployment for the applications you build?
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 a situation where a client requests a feature or technical approach that you believe is subo
How do you handle a situation where a client requests a feature or technical approach that you believe is suboptimal or technically flawed?
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 when you had to quickly ramp up on a completely new programming language or framework to meet
Describe a time when you had to quickly ramp up on a completely new programming language or framework 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 structure your communication when presenting technical concepts or project progress to non-technica
How do you structure your communication when presenting technical concepts or project progress to non-technical stakeholders or clients?
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 expectations regarding project variety, and how do you stay motivated when transitioning between
What are your expectations regarding project variety, and how do you stay motivated when transitioning between different client environments?
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
Walk me through your experience with CI/CD pipelines. How do you automate testing and deployment for the applications you build?
- 02
How do you handle a situation where a client requests a feature or technical approach that you believe is suboptimal or technically flawed?
- 03
Describe a time when you had to quickly ramp up on a completely new programming language or framework to meet a project deadline.
- 04
How do you structure your communication when presenting technical concepts or project progress to non-technical stakeholders or clients?
How difficult is the Software Engineer interview process at Sii Group Italy?
Candidates generally report the interview difficulty as easy to average. The technical questions focus on practical, day-to-day engineering concepts rather than highly abstract theoretical puzzles. The most challenging aspect is often aligning your specific technical experience with the precise needs of the active client mission.
Sii Group Italy Software Engineer candidate reports ↗What is the typical timeline from the first call to an official offer?
The process is relatively fast, often taking between 10 to 20 days. Because Sii Group Italy wants to staff active client projects quickly, they move candidates who pass the initial stages through the technical and client rounds with minimal delay.
Sii Group Italy Software Engineer candidate reports ↗Will I be working on-site at the client's office or remotely?
This depends heavily on the specific client and project requirements. Sii Group Italy supports hybrid and remote working models where possible, but certain industries (such as aerospace, defense, or hardware-integrated automotive systems) may require regular on-site presence at the client's facilities or SII local offices.
Sii Group Italy Software Engineer candidate reports ↗What happens if a specific client project ends?
As a permanent employee of Sii Group Italy, you will transition to a bench period where you focus on internal training, upskilling, and preparing for your next client assignment. The company's Business Managers work proactively to match you with a new project that aligns with your career goals.
Sii Group Italy Software Engineer candidate reports ↗How can I stand out during the client interview phase?
The best way to stand out is to show genuine curiosity about the client's business domain. Ask insightful questions about their technical challenges, their team structure, and their definition of project success. Show them that you are not just a coder, but a collaborative partner ready to add value.
Sii Group Italy Software Engineer candidate reports ↗What topics does Sii Group Italy test in interviews?
Sii Group Italy interviews most often cover Problem Solving, Stakeholder Communication, SQL, Requirements Gathering, and Communication Skills. The exact emphasis depends on the specific role you apply for.
Sii Group Italy 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.
- 01Sii Group Italy 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.
Zoom Video Communications Software Engineer Interview Guide
What Zoom Video Communications asks Software Engineer candidates, from reported rounds and questions.
Zebra Technologies Software Engineer Interview Guide
What Zebra Technologies asks Software Engineer candidates, from reported rounds and questions.
Wizeline Software Engineer Interview Guide
What Wizeline asks Software Engineer candidates, from reported rounds and questions.
YES Software Engineer Interview Guide
What YES asks Software Engineer candidates, from reported rounds and questions.