This page is a role-selection tool, not another biography. Start with the work the property needs done, then use the closest role page to judge the fit.
Different properties use different titles. The important distinction is whether the need is shift control, broad operations leadership, systems/reporting improvement, or a time-bounded improvement engagement.
A shift-management vacancy is not the same problem as a reporting-improvement mandate. A broad operations role is not the same as a three-month workflow engagement. Combining them into one vague title makes evaluation harder.
Use the role cards below to choose the closest operating mandate first. Then inspect only the evidence that belongs to that mandate.
Role clarity first. Evidence second. Hiring decision after both.
Choose by responsibility and expected output rather than by the exact title used at another property.
The most direct fit when a casino needs experienced live-floor control, high-limit judgment, rosters, staff discipline, disputes, SOPs, and useful shift reporting.
Useful where the casino needs someone who can read the floor quickly, understand table games, slots, cage pressure, handovers, staffing issues and daily manager priorities.
Useful where the CMS has data but the GM still waits for clean reports. This role fits casinos that need stronger use of exports, dashboards, KPI review, SOP discipline and safe AI-assisted reporting.
Useful when the casino has pressure now: weak reports, system rollout, department cleanup, SOP gaps, management change or a need to stabilize one part of the operation quickly.
Department breadth matters most for the broader operations and systems/reporting roles. A shift role should remain much more focused on the live operating period.
Table spread, game performance, fills and credits, ratings, disputes, dealer errors, supervisor notes and daily table results.
Shift handovers, variances, approvals, document quality, exception notes, reconciliation pressure and manager follow-up.
Machine performance, hand pays, jackpots, floor notes, technical follow-up, daily summaries and performance movement.
Incident notes, dispute reviews, game protection comments, camera-review summaries and careful wording around sensitive observations.
Host follow-up briefs, visit summaries, comp review support, player-service notes and manager-approved communication support.
Procedures, checklists, staff training notes, audit preparation and the daily discipline needed before AI can safely support the operation.
A useful role definition includes its boundaries. The options on this site are operational roles and controlled improvement work, not pure software development or automated management authority.
If the property needs one of the excluded mandates, the fit should be rejected rather than stretched.
Once a role shape looks plausible, use one actual operating problem to test whether my approach matches the property’s expectations. That is more useful than discussing AI or job titles in the abstract.
The next step is evidence and chronology specific to the role you selected. The first-90-days plan matters after those two checks pass.
Each page answers one different hiring question. Follow only the steps you need.
Dates, casinos, countries, titles, departments, responsibilities, and downloadable CV evidence without repeating the sales argument.
Tell me the department, the report, the system issue or the workflow that needs attention. From there, we can see if the role fit is serious.