Interview practice plan

C

Software Engineer | Distributed System + Fullstack (Python,Go, Java) + AI - 4+ years

Cisco · Bengaluru

Data & AIMid level31 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.

PythonGoJavaGenerative AIDistributed systemsProduct managementUX designSRESystem designTypeScriptJavaScriptAgileCI/CDGitLLMsREST APIs

Also named in the description, not covered below: UX design, SRE, Agile, CI/CD, Git, Docker, Kubernetes, Redis. 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 31 questions practised

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

01Required skill0/3

Python

This role asks for Python.

  • What are generators, and when would you use one instead of building a list?

    What good looks like

    Lazy evaluation with yield, constant memory for large or infinite streams, and pipelines of generators; note they can only be iterated once.

  • Explain decorators. Write one that retries a function with exponential backoff.

    What good looks like

    A function that wraps another, functools.wraps to keep metadata, configurable retries and delays, and only retrying exceptions that are actually transient.

  • A Python data-processing script takes hours. How do you speed it up?

    What good looks like

    Profile first, replace row-by-row loops with vectorised NumPy or pandas operations, process in chunks, then consider multiprocessing or a distributed engine.

02Required skill0/3

Java

This role asks for Java.

  • How does HashMap work internally, and why do equals and hashCode matter?

    What good looks like

    Hashing into buckets, the equals/hashCode contract, resizing and load factor, and buckets turning into balanced trees after a threshold to cap worst-case lookups.

  • 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.

  • When are Java streams the wrong choice compared with a plain loop?

    What good looks like

    Readability and debugging trade-offs, checked exceptions inside lambdas, and parallel streams with shared state or the common fork-join pool.

03Required skill0/3

LLMs & GenAI

This role asks for Generative AI and LLMs. 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.

04Required skill0/3

Product management

This role asks for Product management.

  • How do you prioritise a roadmap when sales, engineering and leadership all want different things?

    What good looks like

    Tie decisions to strategy, use a transparent framework (impact, confidence, effort), share the trade-offs openly, and say no with reasons.

  • A key metric dropped right after your launch. What do you do?

    What good looks like

    Verify the data, check whether the launch caused it (cohorts, rollout groups), decide whether to roll back, and communicate a plan with timelines.

  • Engineering estimates a feature at three times what you expected. What do you do?

    What good looks like

    Understand what drives the estimate, look for a smaller version that tests the core value, revisit priority, and decide together rather than pushing back on the number.

05Required skill0/3

TypeScript

This role asks for TypeScript.

  • 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.

  • When is using any or a type assertion acceptable, and how do you keep a large codebase strictly typed?

    What good looks like

    Prefer unknown plus narrowing, enable strict mode, validate external data at the boundary, and tighten gradually with lint rules.

06Required skill0/3

JavaScript

This role asks for JavaScript.

  • 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.

  • How do you handle errors in async code? What happens to an unhandled promise rejection?

    What good looks like

    try/catch around await, .catch on chains, Promise.allSettled when partial failure is fine, and a global handler for logging unhandled rejections.

07Role function0/3

Machine Learning

This is a data science / ML role. Expect questions on modelling choices, evaluation and production ML.

  • Explain the bias-variance trade-off with an example from a model you built.

    What good looks like

    Underfitting versus overfitting, how you diagnosed it from training and validation curves, and what you changed (features, regularisation, data).

  • How do gradient-boosted trees work, and when would you prefer them over a neural network?

    What good looks like

    Sequential trees fitting residuals; strong on tabular data with modest size, fast to train and easier to explain. Neural nets win on images, text and huge datasets.

  • How do you choose evaluation metrics for a ranking or recommendation problem?

    What good looks like

    NDCG, MAP or recall@k depending on the use, aligned with a business metric, and awareness of the gap between offline and online results.

08Fundamentals0/3

Core programming

This role asks for Go. We do not have questions specific to it yet, so practise these fundamentals and answer them in that language.

  • How would you find and fix a memory leak in a long-running service?

    What good looks like

    Confirm with memory metrics over time, take and compare heap snapshots, look for unbounded caches, listeners and global collections, then add a regression check.

  • What makes code testable? Show how you would refactor a function to make it easier to test.

    What good looks like

    Separate pure logic from I/O, inject dependencies instead of constructing them inside, and keep functions small with clear inputs and outputs.

  • Walk me through what happens when you type a URL into a browser and press Enter.

    What good looks like

    DNS, TCP and TLS handshakes, the HTTP request, server processing, then parsing, rendering and loading sub-resources. Depth in one area beats a shallow list.

09Design round0/3

System design

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

  • Design a URL shortener that handles 100 million redirects a day.

    What good looks like

    Clarify the read/write ratio, design ID generation, storage and caching, then cover hot keys, analytics and expiry. Back-of-envelope numbers earn credit.

  • 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.

  • 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.

10Every 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.

  • Tell me about a time you had to learn something new quickly to deliver on a deadline.

    What good looks like

    Name the specific gap, show how you learned (sources, people, practice) and quantify what you shipped. Interviewers want a repeatable learning method, not heroics.

  • Tell me about a mistake you made at work and what happened next.

    What good looks like

    Own it without blaming others, explain how you contained the impact, and what you changed so it would not happen again.

  • 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.

  • Why do you want this role, and why now?

    What good looks like

    Connect two or three specific requirements of the role to your experience and to a direction you are deliberately moving in. Generic praise of the company scores poorly.

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

10

in Data & AI

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 Data & AI 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 Python and Go 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/9 done

Saved in this browser only.

Interview prep: Software Engineer | Distributed System + Fullstack (Python,Go, Java) + AI - 4+ years at Cisco | LYDJ