What’s a Good Interview Plan for Hiring a Full Stack Developer?

Hey everyone! I'm in a bit of a situation and could really use your insight. It's been over four years since I've been on the candidate side, and I've never actually led an interview. As the only developer at my small company, I need to hire someone soon because I'll be going on pregnancy leave. I want to make sure the interview process is respectful of everyone's time and focuses on real work, rather than just leetcode challenges or live coding sessions.

Here's my current plan:
1. Start with a quick 30-45 minute chat to gauge mutual fit and high-level experience.
2. Have a time-boxed, roughly 60-minute practical assignment to complete at home. This would involve creating a small schema and one resolver, with a focus on types, readability, error handling, basic access checks, and sensible use of SQL/Prisma. The candidate would then submit a small pull request with brief notes.

For an example task, I was thinking about having them implement server-side cursor pagination and debounced search for a user list using Next.js, GraphQL, and Prisma.

I have a few questions:
- Does this two-step flow seem reasonable for a one-person team?
- For the 60-minute task, would you prefer a take-home assignment or a paired live session? I lean more towards take-home because it mimics real work better.
- Are there any great one-hour tasks that fit well with Next.js, GraphQL, Prisma, and MySQL?
- How do you fairly manage time-boxing (maybe a 48-hour window to pick a 60-minute slot and accepting partial submissions)?
- Are there any red flags or must-have elements I might be missing?

Just to clarify, this isn't a job post—I'm genuinely looking for advice on the interview process so that I don't waste anyone's time, especially mine. Thanks!