Job search
Private Mock Interview Practice: Compare Aliases, Recordings, and Sharing Controls
Separate what a partner can see from what a service records, retains or shares, then practice with material you are permitted to disclose.
Private mock interview practice starts with a precise question: private from whom, and which information? An alias can hide your name from a partner while the service still holds account details, audio, transcripts or feedback. A one-to-one session can also create a replay or shareable file. Choose the practice format by who can see your identity, which artifacts it creates and where those artifacts can go.
This guide compares public descriptions from interviewing.io, Aced and PMExercises, checked October 20, 2026. We read current policies and opened public privacy FAQs; we did not enter a private session, change account settings or test deletion. The worked examples are fictional. If you are preparing for a specific position, browse recent roles on LandOffer.ai and build a practice brief from public requirements rather than confidential employer material.

Separate partner identity, stored content and downstream sharing
A display name controls one surface: how another participant sees you. It does not remove identifying facts you say, a recognizable voice, a camera background or a name visible in a shared editor. A neutral alias can reduce an obvious identity link. Before using it, check whether the same distinctive handle already points to your public coding profile.
Recording is another question. Audio, video, chat, code, transcript and feedback are different artifacts. A service can avoid video while retaining text. An AI-feedback opt-out may describe one processing feature without establishing that every other copy disappears. Ask which artifact a control affects before treating it as a general privacy switch.
Sharing introduces a third boundary. A session may be visible only to participants while a replay link can be forwarded, a transcript downloaded or a coach's notes stored elsewhere. We did not verify a public-link default, expiration setting or export-revocation control for the services below. Those are specific unknowns to resolve when they matter to your choice.
These distinctions also change the value of feedback. A reusable written correction may be enough to improve an answer without keeping the entire conversation. If you need a recording to examine pacing, decide what it adds and where it will live. Keep a recording when it serves that review task; useful feedback does not always require the whole conversation.
What current public service descriptions establish
Interviewing.io's FAQ describes voice without video and says the interviewer does not have access to your information. Its privacy policy, effective April 25, 2024, separately says account registration uses information such as name and email. It warns that interview disclosures are not confidential and cannot be guaranteed against participant sharing. Anonymous presentation therefore does not establish confidentiality of what you say.
Its terms, carrying a November 2, 2018 effective date, describe rights to use interview content for service delivery, improvement and research. That is not evidence that every interview is public, nor does it establish a particular recording-deletion deadline. We did not test replay visibility, unmasking, downloads or erasure.
Aced's practice FAQ says partners receive a public display name, which users can change on the account page. It offers audio-only participation and optional contact exchange. We opened these public answers in a signed-out browser; we did not verify the account controls themselves. An audio-only call removes camera exposure but leaves spoken identifiers and voice recognizable.
The same FAQ describes automatic transcripts and AI feedback, with access described as an early feature for paid members, plus an account-setting opt-out from AI feedback. It does not establish what happens to existing transcripts after opting out. Avoid converting that documented feature choice into a claim of no recording, no processing or immediate deletion.
Aced's privacy policy, updated October 1, 2026, describes service providers, purpose-based retention and requests to review, update or delete personal information. It also explains that some information may be retained after account termination for specified purposes. A deletion-request route is a control to investigate, not a verified promise that every interview artifact disappears immediately.
PMExercises' mock guide suggests that peers discuss whether to record. Its terms, labeled January 18, 2021, contain broader recording and reuse language for mock interviews or training, alongside rights over contributed content. Clarify how that applies to the particular session before assuming a peer's verbal agreement settles platform reuse. We did not establish a verified alias or per-artifact sharing control there.
Worked comparison: choose for a specific privacy requirement
Consider a fictional engineer, Jules, who wants feedback on explaining a coding solution. Jules can use a public toy problem, does not need video feedback and wants to keep their current employer and personal contact details away from the practice partner. Jules would prefer written feedback to a reusable recording.
| Option | Documented control relevant to Jules | Remaining boundary | Decision for this brief |
|---|---|---|---|
| Interviewing.io | Anonymous audio format; no video described | Platform account data and nonconfidential interview disclosures remain | A reasonable candidate for the identity requirement; confirm replay handling before booking |
| Aced peers | Changeable public display name, audio-only option and optional information exchange | AI/transcript choice and existing-artifact retention require separate confirmation | Also a candidate if Jules accepts peer feedback and verifies relevant settings |
| PMExercises peers | Guide allows discussion of recording | Broader terms and unverified identity/sharing controls do not establish Jules' desired boundary | Do not choose it on a privacy assumption; clarify controls first |
For Jules, the completed decision is to shortlist interviewing.io and Aced for the partner-identity requirement and defer booking until replay or transcript handling is resolved. Jules can practice a toy coding problem with low identifying context, but the public evidence does not establish a no-retention service among these options.
If Jules requires a guarantee that no recording or transcript is created, none receives a pass from this review. That narrower requirement needs a direct, session-specific answer. A paid coach could still use an external meeting recorder or a note-taking tool; payment alone does not establish a different confidentiality arrangement.
The comparison is deliberately bounded. It does not rank security architectures, test voice recognition or claim one provider's personnel are more trustworthy. It resolves which documented presentation controls fit one practice need and identifies the unresolved artifact requirement. A different need, such as camera-presence feedback, would change the shortlist.
Worked sanitization: preserve the engineering decision
An alias cannot protect a story that identifies its source. Here is an entirely fictional draft Jules might bring to practice:
At Cedar Harbor Systems, I handled the May 14 incident for client Blue Orchard. Our billing-worker.cedar.internal job retried the same request after a timeout. The incident ticket was CHS-4817, and I worked with Priya in the three-person settlement team to stop duplicate processing. I separated an uncertain request outcome from a confirmed failure, checked retry safety and recommended pausing automatic retries until we reconciled affected requests.
All names, hostnames, dates and identifiers above are invented. They illustrate the shape of disclosure, not actual confidential information. The useful interview skill is explaining how someone recognized a retry risk and chose a safer recovery path. Naming the client or ticket adds little to that assessment.
A reduced practice version is:
I investigated duplicate processing in a batch workflow after a timeout. I separated an uncertain request outcome from a confirmed failure, checked whether retries were safe, and recommended pausing automatic retries until the team could reconcile affected requests. I would like feedback on whether that explanation makes the decision and its trade-off clear.
| Original detail | Practice treatment | Why it changes the exposure |
|---|---|---|
| Employer and client names | Removed | Eliminates direct organizational identifiers |
| Exact date and ticket number | Removed | Reduces easy links to a particular incident |
| Internal hostname | Replaced by functional description | Retains the system's role without its address |
| Named teammate and tiny team | Removed | Avoids identifying colleagues through context |
| Timeout, uncertain outcome and retry decision | Retained | Preserves the reasoning being evaluated |
The output now asks for one observable judgment: can the listener explain the difference between an uncertain outcome and a confirmed failure after hearing Jules' answer? It retains the decision without preserving the original trail of identifiers. This is manual editorial minimization, not an automated anonymization test or proof that the story cannot be recognized.
Remaining leakage is concrete. A colleague could recognize an unusual incident sequence. Jules' voice, vocabulary or a public account handle could reveal identity. A screen share might expose a signed-in avatar, browser tab, file path or comment author even when the spoken story is reduced. The service can also associate the session with its account information.

For a real experience, generalize only in ways that remain truthful and permitted to discuss. Do not replace removed facts with invented accomplishments or present this fictional version as your work. If the incident itself is restricted, use a clearly labeled hypothetical problem instead. Our guide to software-engineer resume bullets applies the same distinction between specific reasoning and unsupported claims about experience.
Review the actual session surface before you start
Check the visible display name, camera state and shared workspace before introducing your example. For a scheduled call, also review the meeting invitation and any recording notice. A platform's general description may not answer what happens in a particular coach's external meeting tool.
Ask a narrow question when the documentation leaves a gap: “Will this session create audio, video, a transcript or AI notes; who can access each; and can I get feedback without those artifacts?” Follow with the retention or deletion question for the artifact you actually care about. An answer about camera recording does not settle transcript retention.
For sharing, distinguish a private account view from an externally accessible link. If you choose to export feedback, inspect what the file includes before sending it elsewhere. A transcript can preserve names spoken casually at the start, and a screenshot can include account identity outside the answer itself. A sanitized excerpt you control may serve a specific feedback need better than the whole replay.
These are actions for your own future session, not account changes performed for this article. We did not create an export, inspect a private replay or verify that revoking a link removes a recipient's downloaded copy. The recipient's separate copy is a different boundary from access to the original service.
Keep useful feedback while limiting unnecessary copies
Ask for feedback that can stand alone: the point where your explanation became unclear, the assumption you failed to state and one corrected approach. That lets you carry the learning into another attempt without distributing the full interview. If you retain a recording, use it for a defined review task and make a deliberate decision about keeping it afterward.
Opting out of AI feedback, cancelling a subscription and requesting deletion are different operations. Confirm what each does in the relevant service. Do not infer that a billing change removes content or that an email opt-out changes interview processing. The public sources reviewed here do not establish those equivalences.
The practical choice is the service whose documented controls fit your actual practice material and feedback need. Anonymous audio can fit low-identity coding rehearsal; camera feedback requires accepting visual exposure; a sensitive work story may be unsuitable for either. An alias does not change permission to disclose confidential information.
LandOffer publishes this guide and offers separate job-search tools. Start with one public role requirement from recent jobs on LandOffer.ai, turn it into a toy exercise or permitted work example, and request one specific correction. Ask the partner to evaluate that correction using only the permitted material. The job listing supplies a preparation target, not permission to share private work or an assurance about interview questions.
Sources and Further Reading
- Interviewing.io FAQ — anonymous audio presentation.
- Interviewing.io privacy policy — account information and interview-disclosure limits.
- Interviewing.io terms — interview-content purposes.
- Aced practice FAQ — display name, audio-only option, transcripts and AI-feedback opt-out.
- Aced privacy policy — processing, retention and data requests.
- PMExercises mock-interview guide — discussion of recording.
- PMExercises terms — recording and contributed-content provisions.
Public sources checked October 20, 2026. Documented controls and untested account behavior are kept separate; the examples are fictional.


