What actually goes into one job entry
Title. Company. Dates. Team size. Budget, if it's relevant. Three to five real achievements. The tools and technologies you used. Who you reported to, who reported to you. The scale of what you were responsible for. Individually, none of these fields is hard to fill in. Add them up across one role and you're looking at fifteen or twenty distinct pieces of information — and most CV tools ask for every one of them through a form, field by field, role by role.
The actual bottleneck isn't typing speed
The friction isn't that typing is slow. It's that structured forms ask you to retrieve and organize memories in an order that doesn't match how you actually remember them. You don't think "job title, then dates, then three bullet points." You think in stories — the project that went sideways, the launch that actually worked, the year you spent fixing something nobody else wanted to touch. A form fights that. A conversation doesn't.
What a voice interview does differently
Talk through a role the way you'd describe it to a colleague — fifteen to thirty minutes is typical for one substantial job. We transcribe it with Amazon Transcribe, then generate a structured, multi-paragraph summary with Bedrock that pulls out the actual data points: the achievements, the scale, the tools, the timeline. You read the result and correct anything it got wrong or missed. Nothing gets saved to your profile until you've reviewed it.
The output isn't just faster to produce. It tends to be more complete, because you're not trying to remember what belongs in which box. You're just telling the story, and the structure gets extracted from it afterward instead of imposed on you beforehand.
When forms still win
Not everything belongs in a voice interview. Personalia — your name, email, phone number, address — is faster to type than to say out loud and have transcribed. Skills and interests work well as a quick bulk-edit list, one per line, not a monologue. Voice earns its place specifically where the content is a story: a role, an achievement, the context behind a gap in your history. Use the right tool for what you're actually capturing.
Related guides
- The structured career profile — what the interview actually builds
- How AI agents are starting to manage your career — the same summarization pipeline, used a different way