Data Operations Analyst
Empresa confidencial
1. Role Overview
The Data Operations Analyst is the technical backbone of The Revstudio's delivery operation. This role exists at the intersection of data, systems, and automation — responsible for the accuracy and integrity of every report, export, and dataset that TRS uses internally or delivers to clients.
Beyond execution, the Data Operations Analyst is expected to grow into a builder: someone who identifies repetitive processes, proposes solutions, and implements them using Python, SQL, Google Sheets, or scripted automation. The goal is not just to get the work done — it is to build systems that make the work progressively faster, more reliable, and less dependent on manual effort.
2. Why This Role Exists
TRS operates across multiple client systems, OTA platforms, and internal tools simultaneously. The volume of data that moves through the operation — rate exports, performance reports, audit outputs, system records — requires a dedicated person who owns its accuracy and flow.
At the same time, TRS is a business that scales through systems, not headcount. The Data Operations Analyst is the person who builds those systems. Every automation, every script, every structured process that removes a manual step from the team's daily work is a direct contribution to TRS's capacity to grow.
3. Core Responsibilities
Reporting & Data Delivery
The analyst owns the complete reporting workflow — from data extraction to final delivery. This includes both internal performance tracking and client-facing outputs.
Download and process reports from client PMS, channel managers, and OTA platforms on scheduled and ad hoc cadences.
Consolidate, clean, and structure data across Google Sheets, Airtable, and export files for internal and client use.
Produce formatted PDF reports and structured data files that meet TRS quality standards before delivery.
Maintain reporting accuracy: every figure in a report is verified against its source before it ships.
Track reporting schedules and flag delays or data anomalies to the coordinator before they become client issues.
Automation & Technical Development
This is where the role grows beyond operations and into infrastructure. The analyst uses her technical skills to reduce the manual load across the team — building tools that work consistently without human intervention.
Write and maintain Python scripts for automated report generation, data downloads, and file processing.
Build and maintain SQL queries for data extraction and cross-system comparisons.
Develop Google Sheets automations and structured templates that the full team uses.
Build scripts and tools to support recurring processes such as OTA audits, rate monitoring, and availability checks.
Support internal web and HTML tooling when required for data presentation or process documentation.
Document every automation with clear instructions so any team member can run, troubleshoot, or update it.
Systems & Data Accuracy
The analyst is the steward of TRS's internal data infrastructure. Records are only useful when they are current and accurate — this role is accountable for maintaining both.
Keep Airtable and Notion databases up to date: client information, property records, rate logs, and operational trackers.
Perform data entry and system updates with zero-error accuracy. When an error occurs, it is caught, corrected, and the root cause is addressed.
Support the coordinator in maintaining system configuration and record integrity across all platforms the team uses.
Identify data inconsistencies across systems and resolve them proactively.
Distribution Support
When distribution task volume exceeds Jade's capacity, the analyst steps in to support execution. This is a secondary function — distribution is not this role's primary lane — but the ability to cover it accurately is part of the role's value.
Assist with rate changes, availability updates, and content edits in OTA extranets when workload requires it.
Handle data entry tasks that overlap between reporting and distribution systems.
Never take on distribution tasks that compromise the primary reporting and automation workload without explicit coordination with the coordinator.
Process Contribution
The analyst is not just a follower of processes — she is expected to improve them. As she gains autonomy and context, the standard rises: the expectation is that she identifies what is not working and brings a proposal, not just a problem.
Flag manual processes that could be automated or streamlined, with a suggested approach.
Document all recurring technical workflows with step-by-step instructions.
Participate in process reviews initiated by the coordinator and contribute observations from the operational level.
Take initiative on small-scale improvements without waiting to be assigned — then communicate what changed and why.
4. Growth Trajectory
Now — Month 6
Executing assigned tasks with full autonomy on repetitive workflows. Increasing independence on reporting and data delivery. Beginning to propose small automation improvements.
Months 6–12
Owns the full reporting cycle independently. Delivers at least two automation tools that reduce manual work for the team. Reports to coordinator directly with minimal founder involve.
5. What Good Looks Like
A strong Data Operations Analyst at TRS is the person who catches the error before anyone else sees it. Her reports are accurate on the first pass. Her scripts run without supervision. When something breaks, she diagnoses it quickly, fixes it, and tells the coordinator what happened and what she changed.
She does not wait for the coordinator to tell her that a process is inefficient. She notices it, thinks through a better approach, and brings a proposal. She documents what she builds so that her work survives beyond her own involvement in any given task.
Over time, she becomes the person who makes the whole team faster — not by doing more herself, but by building the tools and structures that reduce friction for everyone.
6. Skills & Experience
Required
Proficiency in Python for scripting and automation — able to write, debug, and maintain scripts independently.
Working knowledge of SQL for data extraction and querying.
Advanced Google Sheets skills: formulas, data validation, structured templates, and basic scripting.
High accuracy in data entry and data handling — precision is not optional in this role.
Able to manage multiple concurrent tasks and prioritize without losing output quality.
Clear written communication when documenting processes and flagging issues.
Valued but Not Required at Entry
Experience with HTML or web-based data presentation tools.
Familiarity with hospitality systems: PMS, channel managers, or OTA extranets.
Prior experience building automation in an operations or agency environment.
Exposure to Airtable, Notion, or ClickUp as operational databases.
7. What This Role Is Not
This is not a purely technical role. The analyst works directly within TRS's client delivery operation. Her outputs reach clients — which means accuracy, formatting, and timing are held to the same standard as any client-facing function.
This is not a role for someone who executes tasks in isolation without communicating. The analyst is expected to flag issues, propose improvements, and stay coordinated with the team — especially when working across multiple client workflows simultaneously.
This is not a static role. The expectation is continuous growth in autonomy, technical scope, and process ownership. Executing the same tasks the same way indefinitely is not the standard here.