Arc.dev interview process: vetting and preparation

Preparing for Arc.dev can feel confusing when platform vetting and employer interviews appear in the same hiring journey. This outline separates those checkpoints and shows what to confirm about the format, your preparation, and the next decision.

For the vetted developer route, prepare around the following areas. Use your application instructions to establish their order and whether any evaluations are combined.

• Application and profile review: Be ready to explain your listed stack, relevant experience, individual contributions, availability, and the work you want.
• Communication evaluation: Rehearse explaining a project, answering follow-up questions, and describing how you communicate a blocker or hand off work remotely.
• Technical evaluation: Check whether your invitation specifies a coding assessment, a live technical conversation, or both. Prepare to implement, test, and explain work in the required environment.
• Matching and employer selection: A hiring company can evaluate its own requirements through further interviews. Its hiring decision remains separate from Arc.dev’s platform evaluation.

Before starting an assessment, confirm the time limit, permitted language, editor, submission requirements, allowed references, and any screen-sharing or recording requirements. A previous candidate’s account does not establish the instructions for your application.

For help organizing the experience you will discuss, visit the resume builder.

Start with the skills claimed on your profile and the format specified in your invitation. The exercises below are original preparation prompts; they are not verified Arc.dev interview questions.

• Implementation: Build a small feature in your main stack. For a frontend profile, try a paginated list with loading, empty, and failed-request states. For a backend profile, try an endpoint with validation and persistence.
• Debugging: Reproduce a failure with a small input, explain its cause, and add a test that would catch it again. Practice distinguishing the observed symptom from the underlying error.
• Testing: Check normal behavior, empty inputs, invalid inputs, and relevant boundary cases. Explain what your tests establish and what remains untested.
• Technical judgment: Discuss an alternative implementation and its costs. If performance matters, identify the bottleneck before proposing an optimization.

In a hypothetical practice session, a backend engineer applying through Arc.dev builds an inventory update endpoint. The engineer explains how concurrent requests could oversell an item, then describes how the implementation and tests address that risk. The rehearsal connects working code with a decision the engineer can defend aloud.

During practice, clarify requirements before coding and narrate decisions at useful checkpoints. If you get stuck, explain what you know, the smallest experiment you would try, and how its result would guide your next step.

Prepare a project explanation that covers the problem, your responsibility, a decision you made, and an outcome you can substantiate. Distinguish your contribution from the team’s work, and use measurements only when you have evidence for them.

Rehearse follow-ups that test depth: Why did you choose that approach? What failed? Which alternative did you reject? What would you change with another month? These are practice prompts for discussing your experience, not a claimed Arc.dev interview script.

For remote collaboration, prepare a concrete example of a blocked task. Explain what information was missing, what you documented, whom you contacted, and how you communicated progress while waiting. A specific account makes your working habits easier to assess than a general claim that you communicate well.

Once an employer interview is scheduled, review that company’s job description separately. Connect your examples to its stack, expected ownership, product problems, and collaboration schedule. Confirm whether its selection process includes coding, system design, behavioral discussion, or a take-home assignment.

To rehearse explaining your work before the conversation, start with the mock interview page.

The assessment organizer’s instructions determine whether AI assistance is permitted. This guide does not establish Arc.dev’s current AI policy. Check the rules for the platform evaluation and each employer round, and ask about AI suggestions, transcription, and external references if the instructions are unclear.

SubcueAI offers live assistance through two surfaces. Its native macOS/Windows desktop app captures system audio and your mic, uses a floating local overlay, and works with desktop meeting clients. Its Chrome/Edge browser extension provides live assistance in a Side Panel for browser-tab calls, capturing meeting-tab audio only, never your mic, so it does not transcribe the candidate. The Firefox build supports mock practice only.

Neither surface adds a meeting bot to the call or injects a content script into the meeting page. Those properties do not establish permission or guarantee invisibility. A shared or recorded screen can expose visible assistance; screen sharing, recording, proctored assessments, and company-managed devices are outside the scope of assurances about hidden use.

Before considering permitted live assistance, read the detectability and privacy guides for its visibility limits.