Start with the institution's priorities
Ask what the role is expected to improve and which offices will be involved. Listen for shared processes, handoffs, and places where staff or students face avoidable friction.
Present a focused starting point rather than a long list of promised projects. Discuss what could be practical in the near term and what would require more people, time, or investigation.
Talk about change with care
Moving work into Slate can change responsibilities. Explain how you would involve staff, learn the current process, and define ownership before proposing a replacement.
Connect suggestions to student experience and staff needs. Avoid treating automation as the goal in itself or implying that existing staff are the problem.
Explore useful project questions
For student affairs, ask about onboarding checklists, visibility into completion, and follow-up for outstanding tasks. For operations, ask about application review, document processing, and communication workflows.
For finance, ask how payments, reconciliation, auditing, and reporting work today. Verify supported integrations, costs, and controls before promising savings or a particular implementation.
For financial aid, ask about approved data feeds, award communications, and checklist needs. Confirm privacy requirements, appropriate data handling, and access controls with the responsible teams.
For registrars and academic departments, ask about transfer evaluation, course articulation, portfolio review, and faculty participation. Verify what is supported in the institution's current configuration before proposing a solution.
Show technical judgment
Discuss how queries, conditional logic, content blocks, and appropriate personalization might support a defined workflow. Tie technical choices to a specific need rather than a feature list.
Explain how you would test permissions and keep access limited to what each role needs. Do not assume that all data belongs in Slate simply because it can be imported.
Close with a realistic approach
Describe how you would learn the current process, select a manageable pilot, test it with users, and agree on the next step. Make uncertainty visible and explain what you would verify before committing.