What interviewers test in Python, Java, C++, C#, Go and SQL interviews, in one place: the language features that come up, the questions to expect, what a strong answer shows and where to focus your preparation. Each section links to a longer question list for that language, and the plan at the end turns it into a week of practice. For the roles that use these languages, see interview help by role.
How language rounds work
Language-specific questions show up in two places: as a short block of knowledge questions in a technical screen, and inside coding rounds, where interviewers notice whether you use the language well. The second matters more. Pick the language you are fastest in, know its standard library and its traps, and be ready to explain what your code costs. For the coding patterns themselves, see our LeetCode patterns guide, and for the rounds as a whole, our coding interview help.
Python and Go
Python interview help
What gets tested: core data structures and their costs, mutability and references, comprehensions and generators, decorators and context managers, how the interpreter handles memory, and concurrency (threads, processes and asyncio, and why the global interpreter lock matters for CPU-bound work).
Questions to expect:
- What is the difference between a list and a tuple, and when would you use each?
- Why is a mutable default argument a bug, and how do you fix it?
- What does a generator give you that a list does not?
- Threads, processes or asyncio: which would you use for an I/O-heavy scraper, and why?
What a strong answer shows: that you know what the code costs, not just what it does: a dictionary lookup is O(1) on average, slicing copies, and a generator trades memory for single use.
Prep focus: know the standard library that saves time in coding rounds (collections, heapq, bisect, itertools, functools), and read our Python interview questions.
Go interview help
What gets tested: goroutines and channels, select, the sync package (WaitGroup and Mutex), context for cancellation and timeouts, implicit interfaces, error handling with wrapping, slices and their backing arrays, maps and concurrency, defer, generics, and the race detector.
Questions to expect:
- What is the difference between buffered and unbuffered channels?
- How do you stop a goroutine cleanly?
- Why can appending to a slice change another slice?
- What happens if two goroutines write to the same map?
What a strong answer shows: concurrency you can reason about: who owns a channel, who closes it, and how cancellation reaches every goroutine.
Prep focus: write one worker-pool example with context cancellation from memory, then read our Go interview questions.
Java and C#
Java interview help
What gets tested: object-oriented design, the collections framework and how HashMap works inside, the equals and hashCode contract, concurrency (synchronized, volatile, the java.util.concurrent package, executors and virtual threads in recent Java versions), JVM memory and garbage collection basics, exceptions, and streams.
Questions to expect:
- How does HashMap store and find entries, and what happens on a collision?
- Why must equals and hashCode be overridden together?
- What does volatile guarantee, and what does it not?
- When would virtual threads help, and when would they not?
What a strong answer shows: that you can connect a language rule to its consequence, such as a broken hashCode making map lookups silently fail.
Prep focus: rehearse one concurrency explanation end to end and review our Java interview questions.
C# interview help
What gets tested: the .NET runtime and garbage collection, value and reference types (structs, classes and boxing), LINQ and deferred execution, async and await with Task, interfaces and abstract classes, IDisposable and the using statement, delegates and events, generics, and for web roles ASP.NET Core and dependency injection.
Questions to expect:
- What is boxing, and why can it hurt performance?
- What is the difference between IEnumerable and IQueryable?
- How does async and await work, and how can it deadlock?
- When do you implement IDisposable?
What a strong answer shows: that you understand what runs when: deferred LINQ queries, continuations after await, and when the garbage collector is involved.
Prep focus: build one small async example you can talk through and read our C# interview questions.
C++
C++ interview help
What gets tested: memory management (stack and heap, RAII, unique_ptr, shared_ptr and weak_ptr), move semantics and the rule of five, templates, virtual functions and how dispatch works, undefined behavior, STL containers and iterator invalidation, const correctness and multithreading with mutexes and atomics.
Questions to expect:
- Explain RAII and why it makes exception-safe code easier.
- When would you choose unique_ptr over shared_ptr?
- What actually happens when you call std::move on an object?
- Which operations invalidate iterators in a vector?
What a strong answer shows: precise language, because C++ interviewers probe details: an answer that says what the standard guarantees, what it leaves undefined, and what a typical compiler does.
Prep focus: game, trading and systems teams test C++ hardest, so practice explaining ownership in your own code; see our C++ interview questions.
SQL
SQL interview help
What gets tested: joins (inner, left, full and self joins), GROUP BY and HAVING, window functions (ROW_NUMBER, RANK, DENSE_RANK, LAG, LEAD and running totals), common table expressions, NULL handling, indexes and reading a query plan, and for senior roles transactions and isolation levels.
Questions to expect:
- Find the second-highest salary in each department.
- Return the top three products by revenue per month.
- Find customers who have never placed an order.
- Explain why a query is slow and how an index would help.
What a strong answer shows: correct handling of ties and NULLs, which is where most SQL answers fail, plus a sentence on how the query would perform on a large table.
Prep focus: practice the ten classic patterns until you write them without looking up syntax; our SQL interview questions and LeetCode SQL 50 guide cover them.
A one-week plan for a language round
- Day 1: write out the language features from the section above from memory and mark the ones you cannot explain.
- Days 2 and 3: answer the four questions for your language out loud, timing each answer at two minutes.
- Day 4: solve three coding problems using the standard library features you marked.
- Day 5: read one piece of your own code and explain its memory and performance as if to an interviewer.
- Days 6 and 7: run a mock interview, then review by role with interview help by role.
Where CoPilot Interview fits
The quickest way to find the gaps in your preparation is to answer real questions out loud and hear how they land. CoPilot Interview is an AI interview assistant; its free AI mock interview builds language-specific technical questions from your résumé and the job description, reads them aloud, scores each spoken answer out of ten and shows a model answer to compare. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included, and the browser demo at /try has 145 practice questions with no signup. If you are considering live help in a real interview, follow your employer's rules, and remember that online assessments and AI-led screens usually forbid it.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
Which language should I use in coding interviews?
The one you write fastest and most accurately. Python is the most common choice because it is concise, but interviewers at most companies accept any mainstream language. Teams that work in C++ or Java may expect depth in that language.
How deep do language questions go?
For general software roles, expect the features in this page and why they behave as they do. For specialist roles, such as C++ on a game engine or Java on a high-throughput service, expect follow-ups on memory, concurrency and performance.
Do SQL interviews allow looking things up?
Usually not in live rounds. Take-home exercises sometimes do. Practice writing joins and window functions without references so syntax does not slow you down.
Is it worth learning a second language for interviews?
Rarely. Depth in one language beats a shallow second one, unless the role requires a specific language, in which case practice your solutions in it.
Where are the old language help pages?
Each language that used to have its own help page now has a section here, and the old addresses redirect to the matching section.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview