1. LandOffer
  2. Blog
  3. All articles
  4. Codility Live Interview in VS Code: Prepare for the Shared Project Environment

Job search

Codility Live Interview in VS Code: Prepare for the Shared Project Environment

Map the shared project, confirm the run route and tool rules, and distinguish VS Code Interview preparation from an older CodeLive tutorial or timed self-test.

10 min readLandOffer team

A Codility live interview in VS Code calls for more than rehearsing a single-file coding pad. Confirm that your invitation uses the shared VS Code environment, then identify the project files, working directory, documented run or test entry point, attached services and allowed tools. The interviewer’s configured session determines what is available. Having VS Code on your own computer does not confirm the shared runtime, files or permissions.

This guide reviews public Codility material checked on October 22, 2026, including its release article published October 16, 2026. We did not join a session, run code, install software or inspect a private project. The two worked records below use an original fictional practice project and invented administrative inputs. LandOffer publishes this guide and offers recent job listings; a listing does not establish an employer’s interview configuration.

Two empty chairs face a shared reading stand with project folios, an instruction booklet and a separate mechanical keyboard.

Confirm the environment, not just the product name

Codility’s VS Code Interview help page describes a shared project-oriented IDE with IntelliSense, debuggers and an integrated terminal. It says the VS Code environment exists alongside the Basic editor. The same Codility brand can therefore lead to different working arrangements.

Record three answers from the invitation or host: Basic editor or VS Code, the configured technology, and whether the supplied project comes from the interviewer or a library task. Do not assume you should bring your own repository because the product supports projects. A capability available to the hiring team is not an instruction for the candidate to upload code.

The older Interviews tutorial page retains “formerly CodeLive” in its title. That identifies a naming history; it does not establish that an older video or a remembered screen matches today’s configured workspace. We inspected the public tutorial page, not the embedded videos or an interview room.

Likewise, instructions for a timed self-administered Codility assessment do not automatically describe a live collaborative interview. Confirm the appointment, timezone, joining instructions and session expectations from your invitation. Do not transfer a self-test timer, start button or submission rule into a different product workflow.

Read the project before choosing a run action

The current online editor description says candidate and interviewer share a browser-based VS Code workspace, with multiple files, a terminal and package support. These are documented capabilities, not a guarantee about the packages or commands in your assigned project.

Start by identifying the project root and reading its instructions. Locate the source directory, tests, dependency declaration and any configuration files. A file named README can tell you how the supplied task is organized, while a package manifest may identify an entry point or test script. Neither file’s presence proves a command has been run successfully.

Confirm which directory a command expects. A correct command in the wrong directory can produce a different problem from a missing dependency or an unsupported runtime. Separating those observations helps the interviewer check the directory, dependency or runtime actually involved. It avoids treating three different setup problems as one unexplained editor failure.

If several run routes are visible, ask which one the task expects. An editor action, a terminal command and a test runner may serve different purposes. Do not assume a shortcut from your local setup has the same behavior in the shared environment.

This review has not executed any command. The public marketing page includes illustrative code and test output, but those displays are not our execution evidence or a candidate’s actual result. The examples here contain no copied task solution.

Worked project map: Ellis completes a paper walkthrough

Ellis’s practice material is an original fictional project called Label Harbor. It is not an interview task, downloaded repository or implemented application. The completed map shows how to read a small project’s structure before execution; it does not supply an answer to a real assessment.

The invented file tree is:

label-harbor/
  README.md
  requirements.txt
  label_harbor/
    __init__.py
    labels.py
  tests/
    test_labels.py

The fictional README contains this complete environment note:

Practice project: Label Harbor. Read the source and test descriptions before changing files. The example test command is python -m unittest discover -s tests, issued from the project root. Dependency availability, runtime version and permission to run must be checked in the actual practice environment. No external service or credential is included in this paper exercise.

Item inspected on paper Completed finding Execution boundary
Project root label-harbor/ is the root in the invented tree No actual directory opened
README Gives a root-relative test command Command described, not executed
Source label_harbor/labels.py is the named implementation file No implementation or assessment solution provided
Test file tests/test_labels.py identifies a separate test location No tests collected or passed
Dependency declaration requirements.txt is present in the invented tree Presence does not prove installed dependencies
Service needs Fictional note includes no external service or credential No database, network endpoint or secret accessed
Shared work plan Read instructions, identify files, confirm run route, then discuss changes No session, edits or run permission claimed

Ellis’s completed finding reads: “The invented file tree and README supply the root, source, tests and stated entry point for this paper map. No files exist in an interview session and no runtime output was collected. Before executing in a real authorized environment, the run route and permissions still need confirmation. No package installation, file change or interview action occurred.”

The map is useful because each file has a purpose before anyone reaches for Run. Ellis can point to the expected test location and identify which assumption needs checking without inventing a successful environment test.

Treat the terminal and attached services as shared task resources

The VS Code help page documents optional attached data services, including MongoDB, PostgreSQL, Redis and MySQL, selected by the interviewer. Their availability in the product does not mean that your session contains a database, requires an external account or permits connecting to a personal service.

Use the provided task instructions to identify any service and connection details. If something is absent or unclear, ask the interviewer which environment is intended. Do not paste a workplace credential, personal cloud key or confidential connection string into the interview terminal to make a project run.

The same restraint applies to dependencies. Package support means the environment can support that kind of work; it does not authorize arbitrary downloads, repository uploads or local machine changes. Confirm the intended setup and permitted actions rather than recreating your entire development environment from habit.

When working collaboratively, make changes understandable. Identify the file you intend to edit and the test you intend to use, then distinguish code changes from setup changes. This is general preparation advice, not a statement that a particular employer scores narration or uses a universal rubric.

Verify AI and installation rules separately

Codility’s AI Interview Assistance settings note describes team defaults, template overrides and an optional lock that can prevent changes during a session. A tool visible in a product description does not tell you whether it is enabled or permitted for your interview.

The October 16, 2026 release article describes newer interview features, including bringing earlier Screen work into a live interview and reviewer-facing AI capabilities. Use that October 16 update as dated product context, then ask whether your invitation uses the shared VS Code project, any earlier Screen work or enabled AI assistance. An older screenshot cannot answer those session-specific questions. This guide does not reproduce proprietary tasks or attempt to predict an interviewer’s hidden configuration.

Ask which built-in assistance and external references are allowed. Permission to use an integrated tool is not blanket permission to send project content to another service or use an unrelated assistant in another window. Follow the assigned rules and review any suggested change rather than assuming generated code is correct.

The current editor FAQ also distinguishes a standard browser session from an optional device check that requires the Codility desktop app. “It uses VS Code” therefore does not establish either that you must install desktop VS Code or that no installation can ever be requested. Confirm the invitation’s requirement and verified installer route; this article performs no installation, device check or permission change.

Worked reconciliation: Nadia separates setup unknowns from code results

Nadia’s fictional preparation record starts with an ambiguous description: “Codility live coding.” The exercise supplies no private invitation, code, terminal session or actual employer configuration. Nadia completes a reconciliation rather than claiming the environment has been tested.

Preparation question Completed fictional record Next clarification retained
Editor variant VS Code versus Basic not stated in the invented note Ask which environment is configured
Project source No repository or upload instruction supplied Ask whether files are provided; do not upload a private repo
Working directory Unknown until task instructions are read Identify the root before choosing an entry point
Run and test route No command or button confirmed Ask for the intended route; no “tests passed” status
Services None identified in the example materials Ask whether an attached service is part of the task
Tools AI and external-resource rules unspecified Keep permission unresolved, not assumed
Device requirement Standard browser versus optional device check unconfirmed Ask whether an app or additional setup is required

Nadia’s completed reconciliation reads: “The invented setup description leaves seven questions unresolved. Nothing in this record establishes an environment failure, test result or code evaluation. Clarifying the environment is the next administrative task; restarting a timed assessment or installing an unrelated local IDE would not resolve these unknowns.”

The full UNSENT invitation clarification is:

Subject: Shared project environment for the live interview

Hello Recruiting Team,

Could you confirm whether this invitation uses Codility Interview in VS Code or the Basic editor, along with the appointment time and timezone?

Please point me to the preparation instructions for the configured technology. Will the project files be provided in the shared workspace, and is there a documented working directory and run or test entry point I should follow? Please also clarify whether attached services are part of the task.

Which built-in AI tools and external resources, if any, are permitted? Does this session require the optional device check or a particular app, and where should I verify those setup instructions before joining?

I am requesting environment information, not interview questions or solutions. No private repository, credentials, invitation token or code is included in this draft. Please identify the correct support route if the provided preparation material leaves a setup question unresolved.

Thank you, Nadia

A project map notebook and grouped file folders remain separate from an untouched run lever and a sealed clarification envelope.

Keep environment preparation separate from interview completion

A prepared file map, a confirmed appointment, a successful run and a completed interview establish different things. If a setup issue occurs in a real session, describe the visible message, relevant file or run route and last action through the authorized channel. Do not turn a missing command into an assessment score or assume the employer has received a finished result.

For preparation, a small project you own and are permitted to use can help you rehearse locating instructions, source files and tests. Keep that rehearsal distinct from the employer’s shared environment: local behavior cannot prove that its runtime, services or permissions match.

No assessment, session, code execution, external test, signup, installation, project upload or employer contact has occurred for this article. Its completed outputs are the paper project map and setup-question record. If you are still exploring opportunities, browse recent roles on LandOffer.ai. For the invitation already in hand, complete the environment record and resolve its open permissions with the host. Prepare to locate the instructions, root, source and tests, then identify the intended run route before using it.

Sources and Further Reading