Job Description: Use the responsibilities and qualifications from the JD you pasted as-is — it's already well structured for a posting. Only thing I'd tighten: the qualifications list "Bachelor's from a tier-I institution" as a hard requirement, which will auto-filter out strong non-traditional candidates (founders, dropouts with real production experience). Worth deciding now whether that's a true deal-breaker or should move to "good to have," since it changes who your AI even surfaces.
Candidate preferences
- Preferred gender: No preference — JD doesn't specify one, and setting one here isn't something I'd recommend defaulting to.
- Preferred notice period: Not stated in JD. Given the role's scope (early-stage, high-ownership), 30–45 days is a reasonable ceiling if you want to filter out very long notice periods — your call.
- Must currently be working in: JD doesn't require prior healthcare-industry experience, only healthcare-domain work once hired. I'd leave this unrestricted — LLM + Kubernetes + GCP talent at 3-5 YOE is already a narrow pool; requiring current healthcare-industry employment narrows it further for no stated reason.
- Other must-have criteria for AI (2 × 100 char):
- "Founding engineer or startup background preferred; comfortable with ambiguous, broad ownership"
- "Links to published research or open-source LLM/agent projects a strong plus"
Suggested priority ranking (adjust to how the AI actually weighs these on your platform):
- LLM/GenAI + Python/FastAPI (core technical bar)
- Kubernetes/GCP infra experience
- Experience range (3–5 yrs)
- Research publication ability / healthcare domain exposure
- Salary fit
