Supported question types, full-screen and region screenshots, and a practical Screenshot Ask workflow
Online Assessments and Screenshot Ask
When a prompt, code sample, or diagram is on screen, open Screenshot Ask and capture the current content. It works for online assessments as well as coding and system-design questions that appear during an interview.
Three steps
Choose the role and coding language → capture the prompt and constraints together → review the answer and follow up when needed.
Partial or full-screen capture?
Partial capture (preferred)
Use it when the question is concentrated in one area. Select only the prompt, options, code, or error so the image stays clear and the answer stays focused.
Full-screen capture
Use it when the information is spread across the display, when the prompt and code must stay together, or when you are not sure which area matters. Make sure the important text is readable and not covered by another window.
A simple rule
Use Partial when you can capture the complete question; use Full Screen when the context is spread out. In either mode, keep the prompt, options, constraints, input/output, and existing code together. If the text is too small or incomplete, recapture it instead of adding more follow-up questions.
Match the answer to the task
After one Screenshot Ask answer, press Cmd/Ctrl + D to cycle through General, I/O Format Check, Bug Diagnosis, Low Pass-Rate Review, and Multiple Solutions. Submit the current screenshot again after switching when you need a debugging, complexity, or alternative-solution view.
Supported question types
| Type | Typical use | What you get |
|---|---|---|
| Live coding | Algorithm and coding prompts, or a coding task during an interview | Approach, code, complexity, and edge cases |
| Technical assessment | Mixed multiple-choice, fill-in, written, and programming questions | Answer with explanation and key evidence |
| General assessment | Aptitude, verbal reasoning, and visual reasoning | Analysis, answer, and the reasoning behind it |
| System design and diagrams | Architecture, flow, and design prompts | Structure, trade-offs, and a response outline |
For complex images or small text, add a focused region screenshot and check that the prompt is complete before submitting.
Quick start
Choose the role and language
In Screenshot Ask, select the role and coding language for this round so examples match your context.
Choose a screenshot style
Use a full-screen screenshot when the prompt is short and centered. Use a region screenshot when the page is dense, long, or you want to emphasize one area.
Review and follow up
Review the solution, answer, or explanation. If code fails, the language needs to change, or you want a shorter interview-ready version, follow up or capture the latest state again.
Screenshot tips
Include the whole prompt
Keep the question, options, constraints, and input/output requirements in the same capture whenever possible.
Capture code in context
Include the function signature, examples, constraints, and existing code—not just the middle lines.
Include the error details
For debugging, capture the code, error message, and test case together so the cause is easier to locate.
Clear when the question changes
Remove the previous screenshot before moving to a new question so old content does not affect the answer.
Context boundary
Screenshot Ask analyzes the current image only. It does not automatically read Interview Materials, knowledge-base notes, or the voice transcript. Use Voice Ask or text questions when your personal background matters; open the stealth notes preview separately when you need a quick reference.
Coding during a live interview
If the interviewer gives you a coding prompt during a voice interview, switch to Screenshot Ask, submit the prompt, and review the approach. Return to Voice Ask when the coding task is over. See Shortcuts for the common switch and submit actions.
Continue with a spoken follow-up after the screenshot
This is a common mixed workflow:
- Press
Cmd/Ctrl + 2for Screenshot Ask, capture the full prompt withCmd/Ctrl + H, then submit withCmd/Ctrl + Enter. - Review the approach, complexity, and code. If you need a debugging or alternative-solution view, press
Cmd/Ctrl + Dand submit the current prompt again. - When the interviewer asks a spoken follow-up such as “Why this approach?” or “Can you optimize the complexity?”, press
Cmd/Ctrl + 1to return to Voice Ask. Submit withCmd/Ctrl + Enterafter the question finishes, or use Auto mode. - Voice Ask uses the live transcript and confirmed Interview Materials; the screenshot is not injected automatically. If the follow-up still depends on the prompt, switch back and capture the current prompt again.
Continue
AI Reading Assistant
Send to your preferred AI
Smart Summary
Deep Analysis
Key Topics
Insights