About The Position

Fetch is seeking a Backend Engineer II to join its Data Platform team as the company enters its AI-first era. The role helps architect and evolve systems that power how Fetch's data products are built, delivered, and accessed, including data pipelines, governed data access, delivery infrastructure, and partner-facing integrations. The engineer operates at the problem level, identifying ambiguous, high-impact issues and driving technical solutions. The role calls for strong technical ownership, proactive attention to quality and reliability, and leadership through influence across engineering and cross-functional stakeholders. Fetch Platform Engineering focuses on the foundations other teams rely on, including core systems, architecture, automation, and developer workflows. The environment involves complex and ambiguous problems, data-informed judgment, practical trade-offs, and close collaboration across product and engineering. Platform engineers build durable platforms, improve developer experience at scale, and enable teams to deliver confidently.

Requirements

  • At least 2 years of professional software engineering experience, with increasing technical scope and ownership.
  • Strong platform or backend engineering background and experience building reliable, scalable systems.
  • Ability to independently identify and scope ambiguous technical problems, then define and execute work to solve them.
  • Experience owning systems or components used by multiple teams or consumers, with attention to reliability and predictable operation.
  • Track record of improving code quality, system health, or engineering practices within a team, often through self-initiated work.
  • Experience contributing to or leading cross-team technical initiatives, including migrations or phased rollouts.
  • Solid understanding of data infrastructure fundamentals, including pipelines, governed data access, and delivery at scale.
  • Strong code review judgment and understanding of rollout safety, monitoring, and operational risk.
  • Mentorship experience with peer or junior engineers.
  • Fluency in modern software ecosystems such as Kubernetes, event streaming, CI/CD, observability tooling, and AI-assisted development workflows.
  • Ability to clearly communicate technical trade-offs and build stakeholder alignment without relying on formal authority.
  • Comfort operating in ambiguous, evolving environments with a focus on measurable outcomes.

Nice To Haves

  • Experience with data delivery, connectors, clean rooms, DSP integrations, or similar partner-facing data infrastructure.
  • Familiarity with data governance and compliance-aware system design.
  • Experience modernizing legacy systems or migrating to newer architectures.
  • Exposure to AdTech, MarTech, or data-monetization ecosystems.
  • Track record of improving reliability, latency, or developer velocity on a data- or integration-heavy platform.
  • Experience giving upward feedback or informally mentoring across levels, even without formal management experience.

Responsibilities

  • Proactively identify and solve ambiguous, complex problems within the team's problem space, and define projects that address systemic issues.
  • Set and raise the team's technical quality bar; initiate refactoring and system-health work; improve reliability and efficiency through code review, thoughtful rollouts, and proactive stability improvements.
  • Define and drive solutions for high-ambiguity issues spanning multiple projects or systems, and lead major initiatives or migrations across teams or functions, ensuring smooth complex or phased rollouts.
  • Identify tools, processes, or platform capabilities that improve team velocity and reduce operational overhead.
  • Help define the team's technical direction and goals, balance project impact, product quality, and engineering efficiency, guide decisions through well-reasoned trade-offs, and communicate technical strategy to technical and non-technical stakeholders.
  • Collaborate with Product, TPM, and partner engineering teams; clarify trade-offs and decision ownership when views diverge, and work toward resolution before disagreements become blockers.
  • Coach peers and junior engineers, invest in their growth, provide constructive upward feedback to managers, and model accountability, transparency, and sound engineering judgment.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service