Program Manager, Partner Integrations at #1 Loyalty Tech Startup

Compensation: ₱300k – ₱660k • No equity

Program Manager, Partner Integrations (Contract)

About the role

Laasie is a B2B hospitality loyalty and guest engagement platform. Our products sit in the booking and stay experience for hotels, so our PMS, CRS, and booking-engine integrations are the critical path for every customer we serve.

We're launching more of those integrations than ever, and the work has outgrown how we manage it. Partner documentation routinely describes behavior the platform doesn't actually exhibit, and we find the gaps in production during customer beta — which stretches projects out and pulls in engineering, support, and the customer. Meanwhile every new property needs an integration stood up and verified, work that currently lands on whoever is free.

This role owns both: the partner programs that bring a new integration into existence, and the operational setup of every integration that follows, for current accounts and new business. Engineering owns architecture and implementation — you own the program, and you gather your own evidence in Postman and CloudWatch before escalating anything. Partner and customer interaction is almost entirely over email, so your writing is the work.

What you'll own

Partner management

• Own the relationship with PMS, CRM, CRS, and booking-engine partners through onboarding, certification, sandbox and credential provisioning, and launch.
• Hold partners to their documentation. When behavior diverges from the spec, document it with a reproducible request and log evidence, get it to the right person, and drive it to a written answer with a date on it.
• Maintain an escalation map per partner, and track release calendars, deprecations, and breaking changes before they reach our customers.

Integration setup operations

• Own setup for every new integration instance — each new property, management group, or customer, on both new and established connections. Point of contact for integration changes as well.
• Run it end to end: kickoff with the customer's technical contacts, access requests, configuration and field mapping, connectivity and test transactions, sign-off, and go-live scheduling.
• Support new business as the integration expert: assess a prospect's PMS environment, confirm what it takes to connect it, and give realistic effort and timeline estimates.
• Drive down the per-property cost of setup through intake forms, configuration templates, and prerequisite checklists.

Integration documentation

• Own internal documentation: setup runbooks, configuration and field-mapping references, known partner quirks and workarounds, and a current inventory of which properties run on which connection and version.
• Own customer- and partner-facing documentation: integration overviews, prerequisites, supported capabilities by PMS, and setup instructions a hotel's IT contact can follow.
• Keep both current at each launch, partner release, and configuration change — so the documentation reflects how the integration actually behaves, and customer success can handle routine cases without escalating.

QA and validation

• Maintain a Postman collection per integration, and exercise each partner's sandbox against their documentation to find where reality diverges.
• Search and analyze AWS CloudWatch logs to validate behavior and triage issues: trace a transaction end to end, isolate failed requests, separate partner-side failures from ours, and quantify intermittent errors.
• Save reusable Logs Insights queries per integration and run them at every go-live, and re-run both against release candidates and partner-side changes so regressions are caught by us, not by a hotel.

Program management

• Keep one current, honest view of every integration in flight and every property in setup — scope, phase, blockers, owners, realistic dates.
• Enforce phase gates, so nothing reaches customer beta until the partner's actual behavior has been independently validated.
• Publish a weekly status leadership can act on, and be the escalation path when a beta or go-live goes sideways.

What you bring

• Exceptional written & verbal English. You can write a defect report a vendor's engineering team acts on, an escalation that creates urgency without burning the relationship, and setup instructions a non-expert can follow. Finalists complete a short written exercise from a real partner API doc and log excerpt.
• 6+ years in technical program management, integrations, implementations, or partner delivery — ideally B2B SaaS where third-party APIs are the critical path, running several concurrent implementations at once.
• Postman proficiency (required): collections, OAuth 2.0 and token refresh, environments and variables, chained requests, basic test assertions. Demonstrated in the interview against a live API.
• AWS CloudWatch log analysis (required): log groups and streams, filtering by time range and correlation ID, and Logs Insights queries. Equivalent Datadog or Splunk experience is fine if you'll come up to speed quickly.
• Proven ownership of vendor relationships, including escalations with a partner whose incentives don't match yours.
• Fluency with REST/JSON APIs, webhooks, OAuth 2.0, SFTP and file-based transfers, and sandbox vs. production environments.
• Ownership of integration or API documentation that internal teams and customers relied on — and that you kept current.
• Self-direction in an asynchronous environment: you work without being checked on, and surface problems early.

Nice to have

• Hospitality technology — Opera/OHIP, protel, Mews, Cloudbeds, Stayntouch, Agilysys, Infor, Aven SynXis — and multi-property rollouts.
• Postman scripting beyond the basics (pre-request scripts, Newman/CI) or comparable regression automation.
• Broader AWS familiarity, or comfort querying a database to narrow down a failure.

Engagement details

• 40 hrs/week spread across all five business days, with a one-business-day response standard on partner and customer email.
• Six-month initial term, open to converting to full-time if the fit is right. You'll work directly with the CTO, with access to engineering, customer success, and partnerships.