A Software Engineer at Alcorce Telecomunicaciones Sl plays a pivotal role in designing, developing, and maintaining the core systems that power telecommunications and IT infrastructure. Operating at the intersection of software development and communications technology, this role is critical to delivering reliable, high-performing services to clients. You will be responsible for building robust backend systems, developing intuitive user interfaces, and ensuring that integration with network systems is seamless and efficient. Your work directly impacts the scalability of products and the overall user experience. At Alcorce Telecomunicaciones Sl, software engineering is not just about writing clean code; it is about solving complex, real-world communication challenges. Whether you are optimizing a backend API or building interactive dashboards, your contributions will influence the technical trajectory of key client projects and internal tools. This position offers a unique blend of technical challenge and strategic influence. You will collaborate closely with cross-functional teams, including ICT managers, systems engineers, and product stakeholders. To succeed, you must bring a strong problem-solving mindset, a deep understanding of modern programming frameworks, and a passion for building high-quality technical solutions.
Initial Screening Call
reportedA conversation with Human Resources focusing on contractual topics, availability, salary expectations, and a high-level review of your professional profile.
What to demonstrate
- A conversation with Human Resources focusing on contractual topics, availability, salary expectations, and a high-level review of your professional profile
- Depth in Python
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.
Detailed Video Interview
reportedAn interactive interview with the ICT Manager or technical lead covering technical evaluations, competency-based questions, and project discussions.
What to demonstrate
- An interactive interview with the ICT Manager or technical lead covering technical evaluations, competency-based questions, and project discussions
- Depth in Python
How to prepare
- Answer aloud and timed: How do you ensure the security of backend APIs against common vulnerabilities?
- Answer aloud and timed: Can you describe a scenario where you had to optimize a slow-performing Python script or database query?
PracHub editorial advice for the preparation topics above.
Research the Company
Before your interview, make sure you understand Alcorce Telecomunicaciones Sl's business model, their main services, and the industries they serve. Showing that you understand their market position makes a strong impression.
Structure Your Presentation
If you are asked to present your profile or a past project, keep it structured. Start with the context, explain the technical challenges, detail your specific contributions, and highlight the final business outcome.
Retrying a write that is not safe to repeat
A timeout tells you nothing about whether the server applied the write, so a blind retry of a create or a charge can duplicate it. Either make the operation idempotent, with a caller-supplied key the server deduplicates on or a conditional update, or do not retry it; and use exponential backoff with jitter so the retries of many clients do not synchronise into a second outage.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Explain the difference between synchronous and asynchronous programming in Python, and when you would use each
Explain the difference between synchronous and asynchronous programming in Python, and when you would use each.
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?
Archive a resource graph without breaking live references or recursing
Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.
Approach
- Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
- Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
- Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
- Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.
Follow-up
- The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
- The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?
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?
Can you describe a scenario where you had to optimize a slow-performing Python script or database query?
Can you describe a scenario where you had to optimize a slow-performing Python script or database query?
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?
Hold a per-tenant active cap against concurrent creates
A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.
Approach
- Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
- Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
- Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
- State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.
Follow-up
- A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
- The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?
How do you manage database connections and migrations in a Python-based framework?
How do you manage database connections and migrations in a Python-based framework?
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 ensure the security of backend APIs against common vulnerabilities?
How do you ensure the security of backend APIs against common vulnerabilities?
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 application state in a large-scale React JS application?
How do you manage application state in a large-scale React JS application?
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?
Explain the lifecycle of a React component and how you optimize rendering performance.
Explain the lifecycle of a React component and how you optimize rendering performance.
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?
How do you handle API integration and error handling on the frontend?
How do you handle API integration and error handling on the frontend?
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 strategies do you use to ensure your user interfaces are responsive and cross-browser compatible?
What strategies do you use to ensure your user interfaces are responsive and cross-browser compatible?
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?
Walk me through a complex technical project you successfully delivered. What was your role, and what challenge
Walk me through a complex technical project you successfully delivered. What was your role, and what challenges did you overcome?
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 stay updated with the latest software development trends and technologies?
How do you stay updated with the latest software development trends and technologies?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What are your expectations regarding day-to-day tasks and technical growth in this role?
What are your expectations regarding day-to-day tasks and technical growth in this role?
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?
Read latency spikes on a sixty-second sawtooth
The cached listing read path serves about 14k reads/second at an 85% hit rate. p99 sits at 35 ms for 57 seconds, jumps to 900 ms for 3, and repeats. During each spike the primary shows several hundred identical listing queries starting within the same millisecond, all carrying one large tenant's id. Cache entries use a 60-second TTL. Give the mechanism, the ordered checks, the fix, and the correctness hazard your fix must not introduce.
Approach
- Match the period to a configured number before theorising about load. A spike every 60 seconds against a 60-second TTL is an entry expiring, and you confirm it by correlating spike timestamps with the entry's write time rather than with the traffic curve. If the period had matched a cron or a GC interval instead, this is a different investigation.
- Establish the concurrency of the miss. Several hundred identical queries in one millisecond means the miss path has no coalescing: every request that arrives between expiry and repopulation recomputes. The herd size is that key's arrival rate times its recompute time, so at 1.2k reads/second for the hot key and a 250 ms recompute you expect about 300 concurrent misses, which matches what is observed.
- Add single-flight on the miss path so one caller per key recomputes under a short-lived lock while the rest wait for its result. Prefer stale-while-revalidate where the read tolerates it: return the expired value immediately and refresh asynchronously, which removes the latency spike rather than serialising it into a queue of waiters.
- De-synchronise the keys. Write TTLs with jitter, for example 60 seconds plus or minus 10%, so a deploy or a mass invalidation does not align every key on the same second and turn a per-key herd into a fleet-wide one.
Follow-up
- The same sawtooth appears on a key that is invalidated on write rather than expired. Is that the same bug?
- How does your answer change if the recompute takes 4 seconds instead of 250 ms?
Built from the rounds and topics Alcorce Telecomunicaciones Sl candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Alcorce Telecomunicaciones Sl loop
- Write out the reported sequence: Initial Screening Call, Detailed Video 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 Python
- Spend the session on Python, which Alcorce Telecomunicaciones Sl candidates report being tested on.
- Write one worked example in Python and time yourself on it.
Deliverable: One timed worked example in Python.
03Work Backend Development
- Spend the session on Backend Development, which Alcorce Telecomunicaciones Sl candidates report being tested on.
- Write one worked example in Backend Development and time yourself on it.
Deliverable: One timed worked example in Backend Development.
04Work Cloud Computing
- Spend the session on Cloud Computing, which Alcorce Telecomunicaciones Sl candidates report being tested on.
- Write one worked example in Cloud Computing and time yourself on it.
Deliverable: One timed worked example in Cloud Computing.
05Answer out loud: Backend Development (Python)
- Answer aloud, timed: How do you manage database connections and migrations in a Python-based framework?
- Answer aloud, timed: Explain the difference between synchronous and asynchronous programming in Python, and when you would use each.
Deliverable: Spoken answers to 2 reported Backend Development (Python) question(s), under time.
06Answer out loud: Frontend Integration (React JS)
- Answer aloud, timed: How do you manage application state in a large-scale React JS application?
- Answer aloud, timed: Explain the lifecycle of a React component and how you optimize rendering performance.
Deliverable: Spoken answers to 2 reported Frontend Integration (React JS) question(s), under time.
07Answer out loud: Project Fit & Professional Experience
- Answer aloud, timed: Walk me through a complex technical project you successfully delivered. What was your role, and what challenges did you overcome?
- Answer aloud, timed: How do you stay updated with the latest software development trends and technologies?
Deliverable: Spoken answers to 2 reported Project Fit & Professional Experience question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
What is your experience with containerization tools like Docker for deploying Python applications?
What is your experience with containerization tools like Docker for deploying Python applications?
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 adapt to a major change in project requirements. How did you handle it?
Describe a time when you had to adapt to a major change in project requirements. How did you handle 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?
Tell callers you do not own that their integration breaks
A field in a write endpoint's response must change shape. You own the endpoint; you do not own the four internal callers or the outbound webhook consumers who read it. Describe a deprecation you were responsible for: what you shipped first, how you established who was actually reading the field, the window you gave and what set its length, what you did about the consumer who never moved, and how you decided removal was safe. Name the signal you used, not the announcement you sent.
Approach
- Establish the reader set empirically rather than from a wiki of owners: per-field usage counters keyed by principal, or access logs attributed to a consumer. State the blind spot of whichever you pick, since a consumer that reads the field only on a monthly job will not appear in a week of logs.
- Ship additive first. Populate the new field alongside the old one so no reader is forced to move, which is also what keeps a rolling deploy safe, because old and new instances answer the same requests at the same time and a rollback must still find the old shape present.
- Set the window from the slowest legitimate consumer's release cadence, not from your calendar, and decide separately what to do for a consumer with no release process at all, such as an external webhook endpoint you can only email.
- Convert silence into evidence before you rely on it: a short, low-traffic removal window that makes a still-dependent consumer fail visibly and loudly while you are watching, rather than at three in the morning after you have moved on.
Follow-up
- How would you detect a consumer that reads the field only during a monthly export?
- One caller refuses to move and has a commercial relationship behind it. What changes in your plan and what does not?
- 01
What is your experience with containerization tools like Docker for deploying Python applications?
- 02
Describe a time when you had to adapt to a major change in project requirements. How did you handle it?
- 03
A field in a write endpoint's response must change shape. You own the endpoint; you do not own the four internal callers or the outbound webhook consumers who read it. Describe a deprecation you were responsible for: what you shipped first, how you established who was actually reading the field, the window you gave and what set its length, what you did about the consumer who never moved, and how you decided removal was safe. Name the signal you used, not the announcement you sent.
What is the typical difficulty of the Software Engineer interview at Alcorce Telecomunicaciones Sl?
Candidates generally report the interview difficulty as average. The focus is on practical, role-related technical skills, clear communication, and how well your profile aligns with their current project needs.
Alcorce Telecomunicaciones Sl Software Engineer candidate reports ↗How long does the entire selection process take?
The process is relatively streamlined, often consisting of two main interview stages. Depending on scheduling and project urgency, the entire process from the initial HR screen to a final decision typically takes between two to four weeks.
Alcorce Telecomunicaciones Sl Software Engineer candidate reports ↗What technologies are most critical to master for this role?
Python is the primary language for backend development, and React JS is highly valued for frontend tasks. Demonstrating a strong understanding of how these two technologies interact via APIs is key to success.
Alcorce Telecomunicaciones Sl Software Engineer candidate reports ↗Is there a practical coding test during the interview?
While there may not always be a formal live coding test, you should expect detailed technical questions, scenario-based problem-solving, and potentially a discussion around a technical presentation or code samples from your portfolio.
Alcorce Telecomunicaciones Sl Software Engineer candidate reports ↗What topics does Alcorce Telecomunicaciones Sl test in interviews?
Alcorce Telecomunicaciones Sl interviews most often cover Python, Java, Problem Solving, Backend Engineering, and Backend Development. The exact emphasis depends on the specific role you apply for.
Alcorce Telecomunicaciones Sl 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.
- 01Alcorce Telecomunicaciones Sl 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.
Veem Software Engineer Interview Guide
What Veem asks Software Engineer candidates, from reported rounds and questions.
Sorint.SEC Software Engineer Interview Guide
What Sorint.SEC asks Software Engineer candidates, from reported rounds and questions.
Raytheon Technologies Corporate Headquarters Software Engineer Interview Guide
What Raytheon Technologies Corporate Headquarters asks Software Engineer candidates, from reported rounds and questions.
NeuroFlow Software Engineer Interview Guide
What NeuroFlow asks Software Engineer candidates, from reported rounds and questions.