Team Mission

Omnichannel Integrations Team connects Text to the messaging platforms customers actually use to talk to businesses — Messenger, WhatsApp, Instagram, Telegram, Twilio, and more.

We build native, first-class integrations inside Text: consistent conversation history, reliable message delivery, correct attachment handling, and predictable behavior across channels — even when each platform has its own quirks.

We’re at an inflection point: we’re moving from externally-built connectors to building and owning key channels in-house, which means you’ll help set foundations and standards — not just maintain what exists.

About the Role

We’re looking for a Senior Backend Engineer to design, build, and scale the backend foundations for Omnichannel integrations at Text. In practice, you’ll build systems that translate third-party messaging platforms into a consistent internal model, keep data flowing reliably into the Inbox, and stay correct under real-world constraints.

This is reliability-heavy integration work, not “API wiring.” External APIs evolve, webhooks can be flaky, and constraints like rate limits, ordering, retries, idempotency, and media limits are part of the job — and customers notice immediately when conversation history breaks

High ownership: you’ll be joining early on the backend side of the team, with strong influence on architecture, patterns, and scaling strategy.

What you’ll do

• Build backend services for Omnichannel integrations and scale coverage across channels.
• Design ingestion and sync flows that are resilient by default ( deduplication, retries, idempotency, ordering guarantees).
• Translate third-party concepts into Text’s internal domain model ( messages, threads, participants, attachments, metadata).
• Handle channel-specific constraints without breaking user experience ( media size limits, API versioning, delivery semantics).
• Improve operational reliability with strong observability ( metrics, logs, tracing, alerting) and debuggable failure modes.
• Collaborate closely with teams across Text to keep data flows consistent and trustworthy.
• Shape architecture decisions: what becomes a reusable platform layer vs. channel-specific logic.

Who you are

• Ownership mindset: you treat the systems you own as products — and care about production outcomes.
• Systems thinking: you reason in failure modes, trade-offs, and long-term maintainability.
• Integration pragmatism: you can navigate messy external APIs and still build clean abstractions.
• Reliability-first: you design for partial failure (timeouts, duplicates, out-of-order events) and predictable behavior.
• Clear communication: you keep alignment and visibility as part of execution.

You may be a great fit if you have

• 6+ years of backend engineering experience in product-focused environments.
• Strong production experience with Go (Golang).
• Solid distributed systems fundamentals ( consistency trade-offs, retries/idempotency, backpressure, event-driven patterns).
• Experience integrating with third-party platforms and operating services in production.
• Comfort with SQL (PostgreSQL) plus stores like Redis.
• Experience with Pub/Sub or Kafka and async/event-driven architectures.
• Familiarity with cloud infrastructure ( GCP preferred) and modern delivery/ops practices ( CI/CD + observability).

Nice to have

• Experience with messaging/social channels ( Meta APIs, WhatsApp Business, Instagram, Telegram) or providers like Twilio.
• Experience in integration-heavy products where external change is frequent ( versioning, deprecations, migrations).
• Experience designing media/attachment handling at scale (limits, retention/lifecycle, storage costs, delivery reliability).
• Exposure to enterprise SaaS constraints (security/compliance mindset).

Why you’ll love working with us

• Inflection-point ownership: you’ll shape foundations, patterns, and standards for Omnichannel.
• High-impact channels: work on integrations customers care about most — high usage and business impact.
• Real engineering challenges: reliability and correctness under external constraints.
• Strong platform foundations: security/compliance/reliability baseline exists, so you can focus on evolution.
• Cross-product impact: your work powers Inbox experience and downstream features relying on trustworthy conversation data.

⚡️ If you enjoy integration-heavy backend work, distributed-systems challenges, and building systems customers rely on daily – we’d love to meet you.