Backend Engineer - Workflows at Text · Wrocław

Team Mission

The Workflows team is the foundation of Text's workplace and AI Agents skills automations.We build the execution layer behind Text's AI agents. When an agent runs a skill - whether a user built it in our visual builder or generated it by describing it in plain language - our platform is what executes it: scheduling it, scaling it, and keeping it reliable under real production load.

This is the infrastructure that lets agents act, not just respond. As Text's AI agent capabilities grow, so does what runs through us - more skills, more integrations, more throughput, higher stakes on reliability.

About the Role

We're looking for a Senior Backend Engineer who thrives on full ownership to join as the second backend engineer on the team. You'll work directly with Michał to double our backend capacity, unblock our frontend team, and help us ship the things we've been building toward for months.

This is not a role for someone who needs a well-worn path. The AI agent skill ecosystem is evolving fast - and so is our platform. Priorities shift, architectural decisions happen weekly, and the backend work is genuinely ahead of what we can currently staff. You'll be expected to pick up complex topics, drive them to production without hand-holding, and communicate proactively along the way. In return, you get real ownership, a tight-knit team, and the chance to work on infrastructure that sits at the center of where Text is going.

What you'll do

• Build, scale, and maintain Go-based backend services powering AI skill execution, workflow scheduling, and connector management.

• Contribute to key upcoming features: workflow sharing, credential sharing, new task types, and new third-party integrations.

• Work alongside the frontend team to design and implement APIs that unlock new product capabilities.

• Take part in the evolution of our unified skill builder - including the AI generator that lets users create agent skills from natural language descriptions.

• Help manage the DevOps side of our world: Kubernetes, Helm, GCP - we are self-sufficient by design.

• Participate in architectural decisions, including our longer-term ambition to migrate off our current (inherited) workflow execution engine.

• Use AI coding tools daily - we are an AI-first team and expect every engineer to actively burn tokens to ship faster.

Who you are

• Owner, not executor. You pick up a task and take it all the way to production. You define what "done" means, spot the risks early, and don't wait to be told what comes next.

• Communicator. You share what you're working on, flag blockers before they become fires, and keep the team oriented without needing to be asked. Small team, no hiding.

• System thinker. You understand distributed systems at a level that goes beyond syntax — async flows, message queues, backpressure, resilience patterns. These concepts are part of how you reason.

• Pragmatic builder. You know how to balance "do it right" with "do it now." You've maintained legacy systems and you know that reading a codebase you didn't write is a core skill, not a chore.

• AI-native. You use tools like Cursor, Claude Code, or similar daily and have built habits around them — not as experiments, but as how you work.

You're great if you have

• Strong, production-grade Go (Golang) experience — this is our primary language for all new backend work.

• Solid hands-on experience with asynchronous distributed systems: event-driven architectures, job queues, eventual consistency.

• Experience with message brokers such as RabbitMQ or Google Pub/Sub.

• Solid PostgreSQL skills — schema design, query optimization, understanding of what happens at scale.

• A track record of independently delivering backend features end-to-end.

Nice to Have:

• Experience with workflow or task execution engines (Conductor, Temporal, Airflow, or similar).

• Familiarity with Kubernetes, Helm, and Docker — we manage our own infra.

• GCP knowledge (we're fully on Google Cloud).

• Experience with Redis or Valkey for caching and distributed synchronization.

• Some exposure to Node.js (parts of our ecosystem still live there).