Staff Product Engineer

The basics

• Your title will be Staff Product Engineer

• This role pays above market rate with significant equity.

• Matt, Cofounder and CTO, is the hiring manager

• We work Mon-Thu in our office in Chancery Lane, London, Fri from anywhere



What are we building?

Walk around the average office and you’ll see people’s days taken up by emails, Slack and meetings instead of real work.

People in client facing roles - think estate agents, insurance brokers, recruiters - feel this pain most acutely. Instead of meeting clients, they spend hours doing admin. Following up. Scheduling meetings, then taking notes on them. Answering questions they’ve been asked a thousand times. Sorting through the mess that is their inbox.

We’ve built an AI executive assistant that looks at all your emails, messages and meetings, and uses that knowledge to answer your email, schedule meetings, take next steps from meetings and organise your inbox.



How has it been going?

Since launching in April 2024, we've gone from $0 to $16m in ARR and raised a Series B from top investors.



What do we value?

Autonomy, agency, and ownership.

Each of our Product Engineers owns one of Fyxer AI’s products.

They own both the product strategy (we have no product managers and have no plans for that to change) and the execution of that strategy.

They choose when to bring in qualitative data (customer interviews, surveys etc) and quantitative, supported by our data engineering department.

We’re very intentional about adding new people. We think a small team of exceptional people working hard at a problem they care about will always beat a larger, less focused team. That does mean you’ll need to bring an intensity to this role that might not be asked at other companies. But it also means you will be fast tracked into more senior roles and responsibilities far earlier.

What will I do?

In short, own one of Fyxer AI’s most important products:

• Decide on metrics for your product, and gain an intuitive understanding of its value by using it yourself and speaking to customers.

• Use quantitative data, customer insight, and product sense to build a strategy for your product area, and prioritise initiatives within that strategy

• Execute your strategy by coding up your ideas

• Manage and improve reliability in your product area, by monitoring logs, analysing support tickets and fixing bugs



A key area for responsibility will be mentoring and developing other product engineers, setting the product direction for a large area of the business, and setting the direction for the tooling the team uses internally to be productive.

What does our ideal hire look like?

• You’ve worked at an early stage tech company as a staff or lead engineer (<100 people), or been a founder

• You have an expert level understanding of Typescript and serverless architecture. If you don’t have these, you shouldn’t apply.

• You want to get involved in product work, rather than just being handed tickets. You’ll be expected to come up with features autonomously, by reading customer feedback and analysing usage data

• You can function as a fullstack engineer, working on client and server side code, and answering data questions using SQL

• High interest in AI and the problem we’re using it to solve

• Urgency and intensity in your work

Our tech stack

Broadly, we use a fairly typical serverless Typescript stack. It’s not a requirement to have worked with every tool in this stack, but the more the better!

• Typescript for all production code

• Firestore as our production database

• Firebase Auth as our auth system

• Backend deployed on Firebase Functions, and making use of PubSub and Cloud Storage

• React frontend, using ShadCN for components, TailwindCSS for styling, React Query for state management

• Posthog for frontend analytics (events, sessions, feature flags, experiments)

• BigQuery as our data warehouse, with Metabase for data visualization. Production data and Posthog events both stream into it so data is in one place.

• Sentry and Google Cloud Logging for monitoring

• Github Actions for CI/CD

The application process

1. Submit your CV (no need for a cover letter)

2. An initial call with someone from the Fyxer AI team to review your experience and motivation for joining (30 mins)

3. Product case study, remote (45 minutes)

4. Live coding, remote (60 minutes)

5. Meet team in office (60 minutes)