Interview practice plan

C

IT Software Engineer

Cisco · Bengaluru

EngineeringMid level25 practice questions

Practice content written by LYDJ for interview preparation. These are common questions for this kind of role, not this employer's actual interview questions.

What this role asks for

Skills we found in the job description. The plan below is built around them.

Supply chainAgileLangChainLLMsKubernetesREST APIsMicroservicesLinuxJavaScriptTypeScriptAngularNode.jsJavaPythonReactSpring Boot

Also named in the description, not covered below: Supply chain, Linux, Python, React, Kafka, Docker, Jenkins, CI/CD. Review these on your own.

Sign in to see your gap areas first. We compare this role with the skills on your profile.

0 of 25 questions practised

Answer each one out loud, then tick it. Progress is saved in this browser only.

01Required skill0/3

Agile

This role asks for Agile.

  • The team carries over stories every sprint. What do you do?

    What good looks like

    Look at story size, work in progress, interruptions and dependencies, agree retro actions with owners, and track flow metrics such as cycle time.

  • Scrum or Kanban: when would you use each?

    What good looks like

    Scrum for planned increments with a stable team; Kanban for continuous, interrupt-driven work such as support. Mention WIP limits.

  • How do you make retrospectives actually lead to change?

    What good looks like

    Vary the format, focus on one or two actions with owners and dates, review last retro's actions first, and make it safe to speak honestly.

02Required skill0/3

LLMs & GenAI

This role asks for LangChain, LLMs, Generative AI and RAG. These LLMs & GenAI questions cover the ground they share.

  • Explain retrieval-augmented generation. When does it beat fine-tuning?

    What good looks like

    RAG grounds answers in fresh, citable documents without retraining; fine-tuning changes style or format behaviour. Many systems use both.

  • How would you evaluate an LLM-powered feature before launch?

    What good looks like

    A golden dataset of real tasks, rubric-based and automated checks, human review of samples, a regression suite for prompt changes, and live feedback.

  • How do you reduce hallucinations in a question-answering system over company documents?

    What good looks like

    Improve retrieval (chunking, hybrid search, reranking), instruct the model to answer only from sources with citations, allow it to abstain, and measure with evals.

03Required skill0/3

Kubernetes

This role asks for Kubernetes.

  • Explain Pods, Deployments, Services and Ingress. How does a request reach a container?

    What good looks like

    Ingress routes to a Service, which load-balances across Pod endpoints selected by labels; Deployments manage ReplicaSets of Pods.

  • What are resource requests and limits, and what happens when a container exceeds them?

    What good looks like

    Scheduling uses requests; CPU is throttled at the limit while memory over the limit is OOMKilled; requests and limits set the QoS class.

  • How do you achieve zero-downtime deployments and safe rollbacks on Kubernetes?

    What good looks like

    Rolling update settings, readiness probes, PodDisruptionBudgets, graceful shutdown with preStop hooks, and canary releases with automated rollback.

04Required skill0/3

JavaScript

This role asks for JavaScript and Node.js. These JavaScript questions cover the ground they share.

  • Explain the event loop. In what order do setTimeout, a resolved Promise and code after await run?

    What good looks like

    Call stack, microtask queue (promises) drained before the next macrotask (timers), and how await splits a function into a microtask continuation.

  • What is a closure? Give a practical use and a bug closures can cause.

    What good looks like

    A function remembering its lexical scope; uses include private state and factories; classic bug is var in a loop or a stale value captured in a callback.

  • Implement debounce, and explain when you would use debounce versus throttle.

    What good looks like

    Debounce waits for a pause (search input), throttle limits the rate (scroll handlers). Handle this, arguments and clearing the timer.

05Required skill0/3

TypeScript

This role asks for TypeScript and Angular. These TypeScript questions cover the ground they share.

  • What is the difference between type and interface in TypeScript, and when does it matter?

    What good looks like

    Interfaces can be merged and extended; type aliases handle unions, mapped and conditional types. Pick one convention and be consistent.

  • Explain generics with constraints. Write a typed function that picks a set of keys from an object.

    What good looks like

    Use <T, K extends keyof T> returning Pick<T, K>, and explain how the constraint keeps callers from passing keys that do not exist.

  • What are discriminated unions, and how do they help with exhaustive checks?

    What good looks like

    A shared literal field narrows the type in a switch; assigning the default case to never makes the compiler flag any unhandled variant.

06Required skill0/3

Java

This role asks for Java and Spring Boot. These Java questions cover the ground they share.

  • What is the difference between checked and unchecked exceptions, and how do you decide which to throw?

    What good looks like

    Checked for recoverable conditions the caller must handle, unchecked for programming errors. Mention wrapping, not swallowing exceptions, and keeping the cause.

  • Your Java service throws OutOfMemoryError in production about once a week. How do you investigate?

    What good looks like

    Heap dump on OOM, analyse retained sizes and dominators, check caches and unbounded collections, and correlate with traffic or batch jobs.

  • How would you make a Spring Boot service production-ready?

    What good looks like

    Health and readiness endpoints, externalised config and secrets, structured logs, metrics and tracing, connection pool sizing and graceful shutdown.

07Design round0/3

System design

This role asks for REST APIs and Microservices, so expect an architecture round. State requirements and numbers first, then trade-offs.

  • Design a rate limiter for a public API.

    What good looks like

    Compare token bucket, fixed and sliding windows; decide where it lives (gateway or service), how counters are shared across nodes, and how clients learn they are limited.

  • Your service's p99 latency doubled after a release. Walk me through how you investigate.

    What good looks like

    Check what changed, compare dashboards and traces, isolate by endpoint and dependency, roll back first if users are hurting, then find the root cause with profiling.

  • Design the REST API for a multi-tenant SaaS product.

    What good looks like

    Resource modelling, versioning, pagination, authentication and tenant isolation, idempotent writes, and a consistent error contract.

08Every loop0/4

Behavioural

Every interview loop has a behavioural round. At mid level, expect questions on delivering independently, handling ambiguity and working through disagreement. Use the STAR structure.

  • Describe a piece of feedback that changed how you work.

    What good looks like

    State the feedback, your honest first reaction and the concrete behaviour you changed. Close with evidence that the change stuck.

  • Walk me through a project you are proud of and your specific role in it.

    What good looks like

    Separate "we" from "I". Cover the problem, the decisions you personally made, the trade-offs, and a measurable result.

  • Describe a time you had several urgent priorities at once. How did you decide what to do first?

    What good looks like

    Explain your criteria (impact, deadlines, dependencies), how you communicated the trade-offs, and what you deliberately dropped or delayed.

  • Tell me about a time you worked with unclear or changing requirements.

    What good looks like

    Show how you reduced ambiguity: clarifying questions, writing down assumptions, small experiments and getting explicit sign-off.

Company research brief: Cisco

From the roles we track on LYDJ, refreshed daily from the official careers page.

120

open roles

90

added in 30 days

71

in Engineering

Product & SoftwareGCCGreat Place to Work

Hiring most for

  • Engineering71
  • Other11
  • Data & AI10
  • QA & Testing10

Cities

Bengaluru · 116Hyderabad · 2Chennai · 1Pune · 1
See all 120 roles at Cisco →

Read before the interview

Questions to ask them

  • ›There are several open Engineering roles at Cisco right now. How is the team growing, and where does this role fit?
  • ›The company hires in Bengaluru, Hyderabad, Chennai. How do teams across locations work together day to day?
  • ›How does the team use Supply chain and Agile today, and what would you like to change?
  • ›What does success look like in this role after six months?
  • ›What is the biggest challenge the team is facing this year?

Preparation checklist

0/8 done

Saved in this browser only.

Interview prep: IT Software Engineer at Cisco | LYDJ