Job search
GitHub Codespaces for a Coding Interview: Confirm Access, Save Work, and Close the Environment
Confirm access, billing and the required branch; verify saved work, committed changes and submission separately, then stop the correct Codespace.
Use GitHub Codespaces for an interview when the invitation explicitly requires or permits that environment. Before starting, confirm repository access, who pays, the intended workspace and branch, and the employer’s submission route. At the end, check saved files, the local commit, the destination branch and the actual submission acknowledgment as separate facts. Then stop the correct environment and retain its status in your handoff record; closing its browser tab is a different action.
LandOffer publishes this guide and offers job-search tools. We checked current GitHub documentation on October 21, 2026 and ran an original Git example entirely on this computer, using a local bare repository as its destination. We did not create, access or stop a real Codespace, push to GitHub, open a pull request or submit interview work. Use these distinctions while finding recent technical roles on LandOffer.ai.

Confirm the invitation’s six-part handoff
Treat the employer’s invitation and repository README as the authority for this specific exercise. A generic GitHub tutorial describes possible workflows; it does not authorize a personal fork, a public repository, a pull request or an alternate submission route for confidential interview work.
Settle six questions before the appointment:
- Confirm the intended GitHub account and access to the exact repository or supplied environment.
- Identify the billable owner and any applicable usage or budget restrictions.
- Confirm the workspace, repository and starting branch named in the instructions.
- Determine which branch and destination should receive your finished work.
- Identify the required submission action and the acknowledgment that will establish receipt.
- Confirm how to stop the environment and who decides its later retention or deletion.
If access fails, preserve the error and ask the established interview contact for the intended route. Do not solve a permissions problem by making the material public, switching accounts without agreement or creating an unapproved copy. A successful login to GitHub does not establish access to the assigned repository.
Check permitted tools and assistance separately. An available editor extension or assistant is not permission to use it in this interview. This guide covers environment and delivery evidence; it does not replace the employer’s rules for solving the task.
Resolve ownership and read-only access before making changes
GitHub’s billing documentation distinguishes compute while active from storage while an environment exists. Usage can be assigned to the creating user or an owning organization, depending on configuration. An employer-owned repository does not, by itself, prove the employer pays for your Codespace. Personal included usage and budget availability also do not establish an unlimited interview allowance.
A fork can change the destination and billing context. GitHub documents that, for read-only source access, committing or pushing a branch can create or link a personal fork; the remote names and token permissions can then change. In the editor’s Source Control workflow, linking a fork can occur without the command-line confirmation described in the documentation. Read access is therefore not sufficient evidence that your finished work will reach the employer’s intended branch.
Before proceeding through that path, ask whether the employer expects a fork or will provide the specified write access or alternative delivery route. Keep confidential assessment material in the agreed location. Do not substitute a public fork because it seems easier to share.
The environment’s setup is another boundary. GitHub warns that devcontainer.json can install extensions and run arbitrary code through configuration such as postCreateCommand. Confirm the repository and requested access before executing its setup. Do not grant unrelated repository access or supply personal secrets simply because a setup step asks. The cloud environment does not establish that a repository instruction is trustworthy.
Separate editor persistence from the artifact you deliver
GitHub’s lifecycle guide says web-editor auto-save is enabled after a delay, while desktop Visual Studio Code requires auto-save to be enabled. Saved changes live in the cloud environment; they are not automatically a commit or an employer submission. Know which client you are using rather than transferring a browser assumption to desktop VS Code.
A useful record has separate fields for saved file state, local branch and commit, destination branch and commit, and submission receipt. A clean working tree can show that tracked edits are committed; it cannot prove those commits reached a remote. A successful push can show a repository update without establishing that the required portal, form or interview workflow has accepted it.
Read the README’s delivery section before the end of the session, so the final minutes are available for the required handoff rather than discovering an extra submission step. It may specify a branch, pull request, archive or another channel. Follow that actual instruction rather than inventing a universal Codespaces “Submit” step. Retain the expected acknowledgment separately from the Git evidence.
Do not leave the only copy of an important explanation in terminal scrollback. GitHub’s stop documentation distinguishes preserved terminal history from the visible terminal contents, which are not preserved between sessions. Save required notes through the agreed artifact route instead of assuming an old screen will be recoverable.
Worked Git trace: Pavel proves a destination commit without claiming submission
Pavel’s example is an original offline demonstration, not a real interview or a Codespaces test. We created an ordinary local repository and a separate bare repository under a local filesystem path. Every push in the demonstration stayed on this computer. No GitHub remote, account token, external network push or pull request was involved.
The repository contains answer.txt, an original short policy note about duration records. Its initial version leaves zero-length records unresolved. The revised text rejects negative durations, retains zero-length observations and documents that distinction. This is an artifact for tracing Git state, not an employer question or a program whose correctness we evaluated.
We initialized branch candidate/finish, committed the initial note and copied that commit to the local bare destination. The initial commit begins 5b392d84. Then we saved the revised file and inspected the following states:
| Executed local checkpoint | Local evidence | Destination evidence | Completed conclusion |
|---|---|---|---|
| Revised file saved | Working tree has changes; HEAD still begins 5b392d84 |
Destination still has the initial commit | File persistence is not a new commit |
| Revision committed | Clean tracked state; HEAD begins 8dd958a9 |
Destination remains at the initial commit | A local commit is not a completed push |
| Commit pushed to local bare path | Local HEAD begins 8dd958a9 |
Destination ref has the identical full commit ID | That destination contains this commit |
| Later local-only line saved | Working tree changes again | Destination remains at the previously verified commit | The later edit is outside the pushed artifact |
The actual result file retains both full commit IDs. We compared the destination ref with local HEAD and checked the destination’s answer.txt contents after the push. The committed revision matched. This comparison did not include future edits or prove that another system had accepted the work. After adding a later local-only draft line, our check detected the dirty working tree while both committed refs remained unchanged.
This last check catches a common handoff mistake: proving that an earlier version reached the destination does not prove that the latest visible file did. If you change the artifact after verification, repeat the relevant commit and delivery checks under the interview’s rules. Before committing, inspect the intended file list and the changes you mean to include. A branch name alone does not tell the reviewer which version you finished. Keep the destination repository and branch beside the commit ID in your handoff record. If the exercise requires several files, check that the required files are represented in the committed artifact rather than relying on one visible editor tab. Our example compares one deliberately small text file; it does not certify a multi-file assessment package.
Our completed conclusion is limited to local Git mechanics. The designated local destination held the specified committed note. There was no employer submission channel, so the submission-receipt field remains empty and the example does not claim an application task was delivered.

Worked access and shutdown ledger: Talia keeps an unknown payer visible
Talia is a fictional candidate whose invitation specifies Codespaces and a private employer repository. Her initial information is incomplete: she can read the repository, but the invitation does not identify the billable owner or authorize a fork. She records those gaps before creating an environment or committing anything through an automatic-fork workflow.
Her completed preparation decision is to ask through the established interview thread for the intended account, payer and delivery branch. She does not add a payment method, accept an access expansion or assume a repository logo establishes who will be billed. The policy is to resolve the missing facts, not to start and hope a personal allowance covers the session.
For the rest of this fictional scenario, stipulate that the organizer later clarifies the approved organization-paid setup and designated private branch, and that access has been provided. These are teaching assumptions, not permissions or billing settings we observed or changed. They allow the handoff ledger to illustrate the remaining distinctions.
| Fictional checkpoint | Talia’s recorded disposition |
|---|---|
| Read-only access; payer unknown; fork not authorized | Hold creation and fork-dependent changes; request clarification |
| Organizer’s approved setup and destination are stipulated | Record those instructions; do not substitute a personal repository |
| Finished work is stipulated to exist on the required branch | Retain branch and commit evidence; portal acknowledgment remains a separate field |
| Required submission acknowledgment is absent | Keep submission pending; a pushed branch alone does not settle receipt |
| Environment is stipulated to be stopped | Record compute stopped; saved environment and possible storage usage remain |
Talia’s final record can therefore say “stopped” while still saying “submission pending.” Those statements concern different systems. If the submission route is unavailable, she preserves the agreed artifact and reports the missing acknowledgment through the official interview contact. She does not fabricate a receipt or delete the remaining environment merely to make the record look closed.
Likewise, a stipulated organization-paid arrangement does not mean storage disappears when work stops. GitHub’s current billing guide measures storage while the environment exists. Whether included usage covers it and who bears a charge depend on the actual billable account and settings. This example supplies no personal bill, balance or guaranteed zero-cost estimate.
Stop the right environment after checking delivery evidence
GitHub explicitly says that closing the web tab does not stop the Codespace. Its documented browser route is the Your Codespaces page, the selected environment’s menu, then Stop codespace. Match the environment to the exercise before taking that action; a similar name is not enough to identify another project’s workspace safely.
Stopping ends running processes while saved changes remain available on a later start. It is different from deletion, which removes the environment and can destroy work that was not preserved elsewhere. Stopped environments can also be subject to retention and automatic-deletion policies. Treat “available later” as conditional on continued retention, not permanent backup.
Do not rely on an idle timeout to establish a specific stop time. Nor should you leave the environment running to compensate for an unclear submission route. Resolve receipt through that route, keep the artifact evidence and stop according to the interview’s instructions. No real start, stop or deletion was performed for this review.
Finish with a compact handoff record: exact repository and branch, committed version, verified destination version where required, submission acknowledgment or explicit pending state, and environment status. These facts let you describe what actually happened without collapsing every stage into “saved.” Continue exploring roles through LandOffer.ai while keeping environment access, work preservation, delivery and resource cleanup distinct.


