Alex intake flow

Turn recruiter conversations into a deployable hiring brief

This is the core product motion: the recruiter tells Alex what they need, Alex keeps clarifying, Apex structures the hiring logic, and the system outputs a JD that can feed the whole recruitment engine.

Alex mode
Live
Auto-post control
Optional
GoHire API
Later integration
Recruiter pressure snapshot
Role target
Senior Data Platform Engineer
Tokyo Hybrid, platform ownership from day one
Urgency
30-day hire window
Interview slots should start immediately after JD approval
Must-have pattern
Deep cloud data infrastructure experience, bilingual communication, and calm cross-functional leadership under ambiguity.
Required stack: AWS, Kafka, Airflow, Snowflake
Stage 01

Alex starts with role intent, pressure, and success definition.

The intake should feel like a premium recruiter consultation. Alex collects business context before turning anything into a JD.

Progress: 1/4
Recruiter brief form
Lead source: No recruiter lead captured yet.
Alex live chat
Chat with Alex about this role
Ready
Alex

I’m Alex. Tell me the role, the hiring pressure, and what a great hire needs to achieve in the first 90 days, and I’ll tighten the brief with you.

Alex next actions
  • What outcome should this hire own in the first 90 days?
  • Which requirements are truly non-negotiable versus preferred?
  • What would make you reject an otherwise strong candidate?
Structured requirement cards
Automation choices
How should Apex proceed after JD approval?
Generated JD draft

Review before Apex posts the role

Tokyo / Hybrid
Draft under recruiter review
State: Draft
Recruiter activity timeline
Intake created
Just now

Alex opened the hiring brief and started clarifying role requirements.