Forward-Deployed Engineers are how Rocket gets into production. You take the platform to a hotel group and make it work in their environment: their PMS configuration, their data model, their sales process, their edge cases.
This is the highest-signal role in the company. You sit between engineering, product, and the customer — configuring integrations and mapping data one day, standing in a hotel’s sales office untangling a live workflow the next. If you’ve admired the FDE model at Palantir: that’s the job, applied to hospitality. You don’t need to be a software engineer — you need deep technical understanding, structured problem-solving, and the presence to own a deployment in front of a customer.
- Deployments, end-to-end. You own the technical success of each customer rollout — from initial system integration through go-live to steady production usage. You run multiple deployments in parallel, remote and on-site across the DACH/EU region, and later the US.
- Enterprise integrations. Configure and validate Rocket’s connections to PMS, CRM, and enterprise systems: API setup, webhooks, data synchronization, and customer-specific data mapping. Where no clean API exists, you coordinate with our engineering team on RPA and workaround solutions — you own the outcome, engineering owns the code.
- Production problem-solving. When something breaks at a customer, you’re the one who fixes it — debugging across our stack and theirs, communicating clearly with hotel operators and IT teams alike, and turning every incident into an engineering requirement so it doesn’t happen twice.
- Product feedback loop. You see how Rocket is actually used before anyone else does. You bring structured field insight back to Product and Engineering and directly shape the roadmap.
- 3 months: First deployment shipped to production independently; you know our integration stack cold.
- 12 months: You run several customer accounts end-to-end, your deployment playbook is the company standard, and customers ask for you by name.
