A Software Engineer at Telefónica plays a crucial role in driving the technological advancements that keep the company at the forefront of telecommunications and digital services. This position is integral to the development and enhancement of platforms that serve millions of users globally, impacting everything from communication to entertainment. As a Software Engineer, you will be responsible for designing, building, and maintaining software systems that are critical to the company's operations. The role involves working on complex projects that require innovative solutions and a deep understanding of software development principles. You will collaborate with cross-functional teams, including product management, UX/UI design, and network engineering, to deliver high-quality software that aligns with business goals. Whether you are contributing to cloud solutions, mobile applications, or backend services, your work will directly enhance user experiences and operational efficiencies. Being a Software Engineer at Telefónica offers the opportunity to engage in diverse technical challenges, leveraging cutting-edge technologies to solve real-world problems. You'll be part of a dynamic environment that values continuous learning and collaboration, making it an exciting time to join a company that is shaping the future of connectivity.
Phone Screen
reportedInitial phone screen with an HR representative to discuss background and role fit.
What to demonstrate
- Initial phone screen with an HR representative to discuss background and role fit
- Depth in Networking Fundamentals
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 Interviews
reportedTechnical interviews with team members assessing your technical expertise and problem-solving abilities.
What to demonstrate
- Technical interviews with team members assessing your technical expertise and problem-solving abilities
- Depth in Networking Fundamentals
How to prepare
- Answer aloud and timed: Describe a challenging technical problem you faced and how you solved it.
- Answer aloud and timed: What are design patterns, and when would you use them?
Final Interview
reportedFinal interview with management to evaluate cultural fit and overall alignment with the company's values.
What to demonstrate
- Final interview with management to evaluate cultural fit and overall alignment with the company's values
- Depth in Networking Fundamentals
How to prepare
- Answer aloud and timed: How do you ensure the quality of your code?
- Answer aloud and timed: Describe a time when you had to work with a difficult team member. How did you handle the situation?
1 candidate reports. Individual accounts describe a particular role and hiring cycle.
Telefónica Software Engineer interview: mobile architecture and offer
After I sent my CV, they called to ask about my experience and studies. I then went to a personal interview at the office. They told me there that I had been selected, so I did not have to wait or chase an answer. That part was quick and direct. In another part of the process, I first had an introductory interview, then an aptitude check and an English test. I later met the team to discuss the ro…
Read full experiencePracHub editorial advice for the preparation topics above.
Practice Coding
Regularly engage in coding exercises and challenges to sharpen your problem-solving skills and prepare for technical assessments.
Research the Company
Familiarize yourself with Telefónica's products, services, and culture to demonstrate your interest and alignment during interviews.
Prepare Questions
Have thoughtful questions ready for your interviewers about the role, team dynamics, and company culture to show your engagement.
Be Authentic
Authenticity matters. Share your experiences and motivations genuinely, as this builds rapport with interviewers.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function to reverse a linked list.
Write a function to reverse a linked list.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you find the longest substring without repeating characters in a given string?
How would you find the longest substring without repeating characters in a given string?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Can you explain the time complexity of your solution?
Can you explain the time complexity of your solution?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Given an array of integers, write a method to find two numbers that add up to a specific target.
Given an array of integers, write a method to find two numbers that add up to a specific target.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
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?
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?
What programming languages are you proficient in, and how have you applied them in past projects?
What programming languages are you proficient in, and how have you applied them in past projects?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Can you explain the differences between REST and SOAP web services?
Can you explain the differences between REST and SOAP web services?
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?
Describe a challenging technical problem you faced and how you solved it.
Describe a challenging technical problem you faced and how you solved 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?
What are design patterns, and when would you use them?
What are design patterns, and when would you use them?
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 quality of your code?
How do you ensure the quality of your code?
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 would you approach designing a scalable system for a new application?
How would you approach designing a scalable system for a new application?
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?
If you encounter a bug in production, what steps would you take to diagnose and resolve the issue?
If you encounter a bug in production, what steps would you take to diagnose and resolve the issue?
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 situation where you had to make a trade-off between quality and speed in a project.
Describe a situation where you had to make a trade-off between quality and speed in a project.
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?
If tasked with improving an existing feature, what metrics would you consider to measure success?
If tasked with improving an existing feature, what metrics would you consider to measure success?
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?
Imagine the application you developed is experiencing performance issues. How would you go about investigating
Imagine the application you developed is experiencing performance issues. How would you go about investigating the root cause?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Describe how you would approach debugging a slow-running query in a database.
Describe how you would approach debugging a slow-running query in a database.
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Telefónica candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Telefónica loop
- Write out the reported sequence: Phone Screen, Technical Interviews, Final 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 3 reported rounds, with the weakest marked.
02Work Networking Fundamentals
- Spend the session on Networking Fundamentals, which Telefónica candidates report being tested on.
- Write one worked example in Networking Fundamentals and time yourself on it.
Deliverable: One timed worked example in Networking Fundamentals.
03Work Routing
- Spend the session on Routing, which Telefónica candidates report being tested on.
- Write one worked example in Routing and time yourself on it.
Deliverable: One timed worked example in Routing.
04Work Python
- Spend the session on Python, which Telefónica candidates report being tested on.
- Write one worked example in Python and time yourself on it.
Deliverable: One timed worked example in Python.
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: What programming languages are you proficient in, and how have you applied them in past projects?
- Answer aloud, timed: Can you explain the differences between REST and SOAP web services?
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: Behavioral / Leadership
- Answer aloud, timed: Describe a time when you had to work with a difficult team member. How did you handle the situation?
- Answer aloud, timed: What motivates you to work in software engineering, and how do you align your goals with team objectives?
Deliverable: Spoken answers to 2 reported Behavioral / Leadership question(s), under time.
07Answer out loud: Problem-Solving / Case Studies
- Answer aloud, timed: How would you approach designing a scalable system for a new application?
- Answer aloud, timed: If you encounter a bug in production, what steps would you take to diagnose and resolve the issue?
Deliverable: Spoken answers to 2 reported Problem-Solving / Case Studies 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.
Describe a time when you had to work with a difficult team member. How did you handle the situation?
Describe a time when you had to work with a difficult team member. How did you handle the situation?
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 motivates you to work in software engineering, and how do you align your goals with team objectives?
What motivates you to work in software engineering, and how do you align your goals with team objectives?
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 prioritize tasks when faced with multiple deadlines?
How do you prioritize tasks when faced with multiple deadlines?
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?
Can you provide an example of a project where you demonstrated leadership?
Can you provide an example of a project where you demonstrated leadership?
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 role do you typically take on in team projects?
What role do you typically take on in team projects?
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
Describe a time when you had to work with a difficult team member. How did you handle the situation?
- 02
What motivates you to work in software engineering, and how do you align your goals with team objectives?
- 03
How do you prioritize tasks when faced with multiple deadlines?
- 04
Can you provide an example of a project where you demonstrated leadership?
What is the typical interview difficulty and preparation time?
The interview process for a Software Engineer at Telefónica is generally considered average in difficulty, with candidates typically preparing for a few weeks. Focus on technical skills, problem-solving, and demonstrating cultural fit.
Telefónica Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates often showcase a strong balance of technical expertise, problem-solving abilities, and effective communication skills. Demonstrating a passion for technology and how it aligns with Telefónica's mission can set you apart.
Telefónica Software Engineer candidate reports ↗How does the culture at Telefónica impact the work style?
Telefónica promotes a collaborative and innovative work environment, where team members are encouraged to share ideas and work together to solve problems. Emphasizing teamwork and adaptability will resonate well in interviews.
Telefónica Software Engineer candidate reports ↗What is the typical timeline from the initial screen to an offer?
The timeline can vary, but candidates usually receive feedback within a few weeks after initial interviews. The process may take longer if multiple interviews are required.
Telefónica Software Engineer candidate reports ↗Are there opportunities for remote work or hybrid arrangements?
Telefónica offers flexible work arrangements, including remote and hybrid options, depending on the team and role requirements.
Telefónica Software Engineer candidate reports ↗What topics does Telefónica test in interviews?
Telefónica interviews most often cover Stakeholder Management, Python, Problem Solving, Leadership, and Network Planning. The exact emphasis depends on the specific role you apply for.
Telefónica 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.
- 01Telefónica 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.
MSD Software Engineer Interview Guide
What MSD asks Software Engineer candidates, from reported rounds and questions.
Glassdoor Software Engineer Interview Guide
What Glassdoor asks Software Engineer candidates, from reported rounds and questions.
AIM Consulting Group Software Engineer Interview Guide
What AIM Consulting Group asks Software Engineer candidates, from reported rounds and questions.
Accenture Federal Services Software Engineer Interview Guide
What Accenture Federal Services asks Software Engineer candidates, from reported rounds and questions.