Yes, for some languages. As of September 9, 2026, CoderPad documents autocomplete for C, C#, C++, Java, JavaScript, Kotlin, Python, Ruby, and Swift 5 in CoderPad Interview. It is not an AI completion; it is editor-level suggestion triggered by a dot or Ctrl + Space, and you can turn it off in your own settings without affecting anyone else in the pad. AI code generation exists in CoderPad, but as a separate AI Assist panel that the interviewer controls and whose prompts are saved. This article covers what the editor gives you by default, what you can change, and how that differs from the IDE you use every day.
Which languages get autocomplete
CoderPad's pad settings documentation lists code autocompletion for "C, C#, C++, Java, JavaScript, Kotlin, Python, Ruby, and Swift 5." The code editor documentation names the same set, plus TypeScript, as the languages with enhanced support, out of "over 60 programming languages" the editor runs.
For everything else, syntax highlighting and execution work, but do not expect suggestions. If your interview language is Go, Rust, PHP, Scala, or a framework outside the enhanced list, plan to type full identifiers.
How it triggers, and how to switch it off
The code editor documentation describes the mechanics: "autocomplete is triggered whenever . is pressed. You can also use Ctrl + Space." Suggestions appear in a list, "start typing and the editor will make suggestions," and you scroll with the arrow keys and accept with Tab or Enter.
If that gets in the way, CoderPad's candidate preparation guide says "For the languages that support autocomplete, you may need to toggle autocomplete to 'Disabled' from the Settings menu during your interview if you want to turn it off." The settings documentation confirms this is private: "The Editor Settings will only affect your particular view of the pad. They will not affect how others in the pad will see it." Turning it off is not a signal to the interviewer.
The rest of the editor
The same documentation lists what else the editor does, and most of it is closer to a local IDE than candidates expect.
- Run. Cmd + Enter or Cmd + S on macOS, Ctrl + Enter or Ctrl + S on Windows. Highlight a block to run only that part.
- Key bindings. Standard, Emacs, or Vim, set per user.
- Brackets and quotes. Auto-closed by default, with a setting to disable.
- Multi-cursor. Alt + Click and Alt + Shift + Click.
- Errors. Red underlines inline.
- Command palette. F1.
- Multi-file projects. Frontend and backend interfaces with a shell, and a
.cpadfile for formatting rules.
Two things a local IDE has that CoderPad does not document: a step debugger and inline AI completion. CoderPad's advice for the first is to "just run the code and use the output for debugging." The second is covered below.
All of these settings are available in the free sandbox, which is the place to configure them before an interview. The sandbox itself is described in how to practice in the CoderPad sandbox.
Where AI fits: AI Assist is not autocomplete
CoderPad has AI, but it is a panel, not a completion engine. The AI Assist documentation, updated July 2, 2026, describes a chat interface with a choice of "GPT, Claude, Gemini, Llama," enabled by default at the account level but under the interviewer's control: "Interviewers can enable or disable AI Assist for an individual pad from the Pad Settings."
It has three modes, Ask, Edit, and Plan, and Edit can "allow the AI assistant the ability to change the code (including the file structure)." It can be shared, where "You'll both be able to see the prompt history," or private to the interviewer. Either way, "All pad users' prompts and AI output will be saved for review in playback mode."
So the question "does CoderPad have Copilot-style completion" has a specific answer: no, not as documented. What it has is an AI you converse with in the open, and a record of the conversation. CoderPad Screen offers the same on project questions, with prompts saved into the report, per the Screen AI tools documentation. What an AI-permitted interview actually grades once the prompts are on the record is the subject of what AI-assisted coding interviews actually grade.
What this means for candidates
Check your language against the nine. If it is on the list, decide in the sandbox whether you want suggestions on or off, and set it; nobody else sees the choice. If it is not, practice typing without them. Learn the run shortcut and the selection-run trick. And treat AI Assist as a visible, recorded tool that the interviewer chose to give you, not a hidden accelerator: if the panel is there, use it in the open and be ready to explain what it produced. If it is not there, the rules are that it is not there. The wider format, including what the interviewer sees, is in the CoderPad interview format and preparation guide.
Share
Explore with AI
Continue exploring
Related guides
Assessment Guides · 4 min read
CoderPad Sandbox: How to Practice Before an Interview
The free CoderPad sandbox runs the same editor as a live pad, no login, 30-plus languages, tabs wiped after an hour idle. What it rehearses and what it cannot.
Assessment Guides · 4 min read
Does CoderPad Record Your Screen?
CoderPad records every keystroke in the pad, not your screen. What Interview playback and Screen code playback capture, and where video, audio, and webcam stop.
Assessment Guides · 4 min read
Does Mettl Detect Tab Switching? Browsing Tolerance Explained
Mercer Mettl counts every exit from the test window, warns each time, and can end the test at a limit the employer sets. Browsing tolerance and copy-paste rules.