Process & Intake Analyst

We are looking for a Process & Intake Analyst to join our newly formed Operations team in Cyprus. Operations exist to make our fast-growing company easier to work in: clear routes for asking for things, clear owners for the things that matter, and rules people can actually find.

Job Responsibilities

• Design and run the request front door. Map how cross-functional requests arrive today, define request types and intake forms, set triage and routing rules, and launch the route in phases, starting with the highest-volume request types.
• Make response times measurable. Define service levels with the teams that receive requests, instrument the route so that volumes, waiting time and resolution time can be reported, and use the data to fix the bottlenecks it reveals.
• Build and maintain the policy and process repository. Inventory existing policies and process documents, consolidate duplicates, retire stale content and bring each item into a consistent structure with an owner, a version, an approval status and a review date.
• Run the review cycle. Make sure reviews happen on time, chase overdue items, and report on the health of the repository, so that it stays current rather than decaying after launch.
• Create and maintain the ownership register. Record named owners for cross-functional processes, systems and vendor relationships, resolve gaps and overlaps with the departments involved, and escalate where no owner can be agreed.
• Map and improve processes. Document current-state workflows, identify duplicated steps, manual handoffs and unnecessary approvals, and propose and implement simpler routes with the people who run them.
• Configure and automate. Set up workflows, forms, templates, dashboards and simple automations in the company's existing tools, and prototype small helpers with scripting or AI assistants where they remove manual work.
• Make the systems easy to use. Write clear guidance, run short onboarding sessions for teams adopting the front door or repository, and collect and act on feedback.
• Keep the systems portable. Collaboration tooling is changing over the next year, so design structures and content that can move between platforms without being rebuilt.
• Report to the Head of Operations on adoption, service levels, repository health and the process issues the data surfaces.