Full-Stack Product Engineer

Fawna is hiring a Full-Stack Product Engineer to build the systems that turn raw customer conversations into clear, trustworthy product insight. This role spans product UI, backend services, integrations, data models, search, and AI-assisted workflows.

The ideal candidate enjoys working close to customers and product decisions. Rather than owning only one technical layer, this engineer will help shape complete workflows - from importing a support ticket to surfacing a recurring theme and presenting the evidence to a product manager.

About Fawna

Fawna connects customer feedback from support desks, CRMs, call tools, review platforms, and internal notes. It organizes this information into themes, summaries, trends, and evidence-backed insights that product, support, success, sales, and leadership teams can use together.

What this role will own

• Designing and shipping end-to-end product features across frontend and backend systems.

• Building integrations with support desks, CRMs, call platforms, review tools, and collaboration products.

• Creating durable data models for sources, conversations, themes, insights, workspaces, and permissions.

• Developing dashboards, review queues, search experiences, and evidence views.

• Improving ingestion pipelines, background jobs, observability, and failure recovery.

• Working with AI-assisted classification, summarization, retrieval, and evaluation workflows.

• Strengthening security, privacy, auditability, and account-level access controls.

Problems the team is solving

This engineer may work on challenges such as:

• Importing large volumes of feedback reliably from systems with different APIs and schemas.

• Grouping related conversations without losing important source context.

• Making search and filtering fast across many workspaces and data sources.

• Helping users understand why an AI-generated theme or summary exists.

• Designing permissions that remain understandable as teams and workspaces grow.

• Measuring quality so automated outputs improve without becoming opaque.

How product development works

Engineers work closely with product design, customer-facing teams, and early customers. Projects usually begin with a customer problem and a desired workflow rather than a fixed technical specification.

The strongest solutions at Fawna are technically sound, easy for customers to understand, and explicit about the evidence behind each insight.

What Fawna is looking for

• At least four years of experience building production web applications.

• Strong TypeScript and React skills.

• Experience designing backend APIs and working with relational databases.

• Comfort moving between product UI, server-side logic, and infrastructure concerns.

• Good judgment around data privacy, authentication, authorization, and secure defaults.

• Ability to simplify ambiguous requirements into practical technical plans.

• Clear written communication and comfort working in a small, high-ownership team.

Helpful experience

• SaaS integrations, webhooks, OAuth, queues, and background processing.

• Search infrastructure, embeddings, retrieval systems, or analytics pipelines.

• LLM-based product features, prompt evaluation, structured outputs, or model monitoring.

• Multi-tenant architecture and workspace permission systems.

• Observability, incident response, and performance optimization.

• Customer feedback, support, CRM, or product analytics products.

What success looks like

During the first three months, the engineer will learn the domain, ship a meaningful product improvement, and become comfortable with the core application architecture. Within six months, success means independently leading larger workflows, making sound technical decisions, and improving the team’s ability to ship reliable features.

What Fawna offers

• Competitive salary and meaningful equity.

• Remote-friendly work with optional collaboration in Berlin.

• High ownership over product and technical direction.

• Modern equipment and a dedicated learning budget.

• Flexible hours and a low-meeting operating style.

• Direct access to customer problems and product strategy.

• An opportunity to help define an emerging software category.

Interview process

• Introductory conversation about experience, interests, and working style.

• Technical and product discussion based on a realistic Fawna workflow.

• Practical exercise or review of a previous project, depending on experience.

• Final conversation with team members focused on collaboration and expectations.

The process is designed to evaluate product judgment, engineering fundamentals, communication, and the ability to make thoughtful tradeoffs - not puzzle-solving speed.