APPLICATIONS & DATA ENGINEER

APPLICATIONS & DATA ENGINEER

Hyderabad - WFO - Hybrid

Full Time

Australia Shift: 7-4 PM IST or 8-5 PM IST

8+ years experience.

KEY RESPONSIBILITIES

• Build and maintain internal web applications: reporting dashboards, and multi-user applications that store what people enter. That includes finishing the half-built ones, and moving working tools off personal machines and accounts onto client-managed hosting with the persistence, authentication and error handling they never had.

• Integrate REST APIs across point-of-sale, rostering, reservations, events, mobile ordering, accounting and workspace platforms, replacing manual exports with live feeds.

• Design and own the PostgreSQL data layer, including migration of historical data out of spreadsheets and platforms being replaced, and reconciliation across systems that disagree.

• Build scheduled pipelines that extract, reconcile, publish and alert, plus the daily and weekly reporting that runs on them. Run it in production: own the schedules, respond when something breaks, decide what happens when a source is late, missing or wrong, and follow up the discrepancies that do not resolve themselves.

• Build forecasting and inventory models: one framework configured per venue, validated out-of sample, with a manager reviewing and signing off the output. Managers often know something the model cannot, so an override is captured with its reason rather than treated as an error.

• Build Model Context Protocol (MCP) servers over vendor APIs where the platform ships no connector of its own, so an AI assistant can be pointed at a system like the point-of-sale directly, under the permissions of the person asking.

• Make the reporting interpret as well as present: what changed, why, and what to do about it. That means thresholds, analysis and, where it fits, a large language model whose output is checked before anyone relies on it.

HOW WE WORK

• One build per problem. Where several venues need the same thing, they get one application configured differently for each.

• Everything goes into client’s GitHub from the first commit and deploys through CI. Credentials never live in a repository. A project is finished when someone else can pick it up and change it, which makes documentation part of the work.

• The engineer is accountable for every line, including what AI wrote. What goes into production is what they have read, understood and can explain.

• Nothing goes live without a second set of eyes on the numbers: the department that asked for it checks the output, and the person who owns the number signs it off.