Principal Backend Engineer (Go/PostgreSQL) - Remote

FunnelStory is hiring a Principal Backend Engineer to build reliable customer intelligence and AI workflows. Own unclear product problems and ship solutions customers can trust, using Go and PostgreSQL.

Company Details

FunnelStory brings customer data from multiple systems into a shared context graph, helping revenue teams and AI agents understand accounts and take permissioned actions. Its backend runs on Go, PostgreSQL, Docker, and AWS, with enterprise and on-premise deployments.

Website:

Requirements

Minimum 8 years of backend engineering experience at product-based organisations, including real startup experience.

Strong hands-on experience building production services in Go.

Ability to design PostgreSQL databases, debug queries, and resolve performance issues.

Experience shipping a customer-facing product that uses LLMs to make judgments, beyond a prototype or demo.

Experience owning a service or feature end to end, including reliability and production issues.

Ability to turn unclear customer problems into working solutions independently.

Regular use of AI tools to build products and write clean, maintainable code.

Experience working close to users and improving products through customer feedback.

A public GitHub profile, side project, or technical blog is a strong plus.

Candidate currently working at a product based organisation is a must.

Responsibilities

Build and improve customer-facing features in a multi-tenant Go and PostgreSQL backend.

Connect data sources such as CRMs, conversations, and support systems to produce reliable account intelligence.

Build AI workflows that analyse information, take permissioned actions, and maintain an auditable record.

Decide what an LLM should judge and what application code should calculate and store.

Make workflows safe to rerun and detect drops in output quality.

Keep features reliable and responsive across workspaces with 100 to 100,000 accounts.

Support production operations across AWS, Docker, enterprise, and on-premise deployments.

In the first 30 days, learn the system by shipping 2–3 fixes a week and 1–2 improvements to existing features.

Within 3–6 months, own a major new capability, from an unclear request to a feature customers use regularly. Potential areas include intelligence pipelines, CSM agents, renewal automation, and expansion signals.