Sorint.SEC · Software Engineer
Updated · 2026-09-22

Sorint.SEC Software Engineer
Interview Guide

THE 60-SECOND BRIEF

As a Software Engineer at Sorint.SEC, you are at the intersection of high-end cybersecurity and cutting-edge software development. Sorint.SEC operates as the dedicated Cybersecurity division of the Sorint.Lab Group, meaning your work directly influences how complex enterprises defend themselves against evolving digital threats. This role is not just about writing code; it is about building the robust, scalable, and secure infrastructure that protects critical business assets. You will join a team focused on innovation, working with modern stacks like Python, FastAPI, and React, while orchestrating services within Azure and Kubernetes. Whether you are optimizing database queries for PostgreSQL or integrating advanced AI Agents, your contributions will directly impact the efficiency and security posture of our clients.

This guide is scoped to a Software Engineer candidate at Sorint.SEC.

Sorint.SEC candidates report 2 rounds over 2-4 weeks. The stages below are what candidates describe, not a published process.

Python 3.xPostgreSQLFastAPI

20 min read

Practice 15 Software Engineer prompts
15Practice promptsAcross five skill areas

As a Software Engineer at Sorint.SEC, you are at the intersection of high-end cybersecurity and cutting-edge software development. Sorint.SEC operates as the dedicated Cybersecurity division of the Sorint.Lab Group, meaning your work directly influences how complex enterprises defend themselves against evolving digital threats. This role is not just about writing code; it is about building the robust, scalable, and secure infrastructure that protects critical business assets. You will join a team focused on innovation, working with modern stacks like Python, FastAPI, and React, while orchestrating services within Azure and Kubernetes. Whether you are optimizing database queries for PostgreSQL or integrating advanced AI Agents, your contributions will directly impact the efficiency and security posture of our clients. We look for engineers who are eager to push the boundaries of traditional development, bringing a proactive, problem-solving mindset to a dynamic, collaborative environment.

01

Initial Screening

reported

An opportunity to frame your narrative and discuss your background.

What to demonstrate

  • An opportunity to frame your narrative and discuss your background
  • Depth in Python 3.x

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.
Sorint.SEC Software Engineer candidate reports
02

Technical Assessments

reported

One or more rounds focusing on your technical capabilities and engineering logic.

What to demonstrate

  • One or more rounds focusing on your technical capabilities and engineering logic
  • Depth in Python 3.x

How to prepare

  • Answer aloud and timed: What are the key differences between monolithic and microservices architectures in an Azure environment?
  • Answer aloud and timed: How do you handle containerization and orchestration challenges using Docker and Kubernetes?
Sorint.SEC Software Engineer candidate reports

PracHub editorial advice for the preparation topics above.

01

Going into the loop without having done this.

Review your projects: Be prepared to discuss the specific technical challenges you encountered in your previous roles.

02

Going into the loop without having done this.

Understand our stack: Even if you haven't used FastAPI or Azure extensively, demonstrate that you have the foundational knowledge to learn them quickly.

03

Going into the loop without having done this.

Be ready to talk about security: As a cybersecurity company, even our engineers should show an interest in secure development practices.

04

Going into the loop without having done this.

Ask questions: Use the interview to learn about the team's current challenges and how you could contribute to solving them.

Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.

9 technical prompts0 include a worked solution

Find overlapping job attempts and peak concurrency from lease records

medium
sweep lineintervalsleases

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?

Track a rolling failure rate per destination for circuit decisions

easy
sliding windowring buffercircuit breaker

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

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

medium
top-kheavy hittersstreaming

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?

Built from the rounds and topics Sorint.SEC candidates report.

Small steps. Visible outcomes.0 / 7 completed
ONE WEEK · YOUR PACE

Prepare, practise & reflect

One practical outcome each day. Spend longer where you need it.

0 / 7 done
01Map the Sorint.SEC loop
  • Write out the reported sequence: Initial Screening, Technical 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 2 reported rounds, with the weakest marked.

02Work Python 3.x
  • Spend the session on Python 3.x, which Sorint.SEC candidates report being tested on.
  • Write one worked example in Python 3.x and time yourself on it.

Deliverable: One timed worked example in Python 3.x.

03Work PostgreSQL
  • Spend the session on PostgreSQL, which Sorint.SEC candidates report being tested on.
  • Write one worked example in PostgreSQL and time yourself on it.

Deliverable: One timed worked example in PostgreSQL.

04Work FastAPI
  • Spend the session on FastAPI, which Sorint.SEC candidates report being tested on.
  • Write one worked example in FastAPI and time yourself on it.

Deliverable: One timed worked example in FastAPI.

05Answer out loud: Technical & Domain Expertise
  • Answer aloud, timed: Can you walk me through a complex project where you utilized Python and FastAPI?
  • Answer aloud, timed: How do you approach database schema design and performance optimization in PostgreSQL?

Deliverable: Spoken answers to 2 reported Technical & Domain Expertise question(s), under time.

06Answer out loud: Behavioral & Professional Alignment
  • Answer aloud, timed: What draws you specifically to the intersection of Software Engineering and Cybersecurity?
  • Answer aloud, timed: Can you describe a time you faced a significant technical roadblock and how you overcame it?

Deliverable: Spoken answers to 2 reported Behavioral & Professional Alignment question(s), under time.

07Dry run for Sorint.SEC
  • Run one full mock under time, then write down the two questions you most want to ask your interviewers.

Deliverable: A completed timed mock and two questions to ask.

Expand any day for tasks and deliverables. Your progress is saved on this device.

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

How do you handle containerization and orchestration challenges using Docker and Kubernetes?

medium
Technical & Domain Expertise

How do you handle containerization and orchestration challenges using Docker and Kubernetes?

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?

Can you explain your experience with React and how you ensure seamless integration with backend services?

medium
Technical & Domain Expertise

Can you explain your experience with React and how you ensure seamless integration with backend services?

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?

What draws you specifically to the intersection of Software Engineering and Cybersecurity?

medium
Behavioral & Professional Alignment

What draws you specifically to the intersection of Software Engineering and Cybersecurity?

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?

Can you describe a time you faced a significant technical roadblock and how you overcame it?

medium
Behavioral & Professional Alignment

Can you describe a time you faced a significant technical roadblock and how you overcame it?

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 prioritize tasks when working in a fast-paced, high-innovation environment?

medium
Behavioral & Professional Alignment

How do you prioritize tasks when working in a fast-paced, high-innovation environment?

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 us about a time you had to explain a complex technical concept to a non-technical stakeholder.

medium
Behavioral & Professional Alignment

Tell us about a time you had to explain a complex technical concept to a non-technical stakeholder.

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?
  • 01

    How do you handle containerization and orchestration challenges using Docker and Kubernetes?

  • 02

    Can you explain your experience with React and how you ensure seamless integration with backend services?

  • 03

    What draws you specifically to the intersection of Software Engineering and Cybersecurity?

  • 04

    Can you describe a time you faced a significant technical roadblock and how you overcame it?

PracHub preparation framework
How long does the interview process typically take?

Most candidates complete the process within a few weeks, though this can vary based on scheduling. We aim to keep the process "snello" (streamlined) to respect your time.

Sorint.SEC Software Engineer candidate reports
What differentiates successful candidates?

Successful candidates demonstrate a blend of technical depth and curiosity. We look for people who are not just experts in a language, but who understand the "why" behind their architectural choices.

Sorint.SEC Software Engineer candidate reports
Is the interview process mostly remote or in-person?

The process is primarily conducted via video calls to ensure efficiency and accessibility, though the role itself offers hybrid flexibility.

Sorint.SEC Software Engineer candidate reports
What is the company culture like?

We foster an inclusive and dynamic environment where learning is continuous. We value people who are not afraid to share knowledge and who contribute to a positive, collaborative spirit.

Sorint.SEC Software Engineer candidate reports
How hard is the Sorint.SEC interview?

Candidates most commonly rate Sorint.SEC interviews as medium, based on 22 reported interviews.

Sorint.SEC Software Engineer candidate reports
What topics does Sorint.SEC test in interviews?

Sorint.SEC interviews most often cover Python 3.x, PostgreSQL, FastAPI, REST API design, and Architetture a microservizi. The exact emphasis depends on the specific role you apply for.

Sorint.SEC Software Engineer candidate reports
Where is Sorint.SEC headquartered?

Sorint.SEC is headquartered in Turin, Italy.

Sorint.SEC Software Engineer candidate reports
Sources & methodology 3 sources ↗

Official role evidence, timestamped platform data and clearly labeled preparation advice.