Founding Engineer

MeetDoris Ltd.; Greater London; On-site; GBP 70,000 - 100,000; Full time

Benefits offered by this job

Equity in the company

Job summary

MeetDoris Ltd. in London is seeking an engineer to own the surface end-to-end, from the underlying ontology to what a customer sees. You will work on a system that connects calls, emails, documents and CRM into a single, typed deal record.

You will implement extraction, a flow engine, an agent that answers pipeline questions and a notetaker that links calls to the right deal, in a small, customer-focused team.

Qualifications

• Several years building software that other people depend on.
• Fluent in Python or TypeScript, and able to pick up the other language.
• Comfortable in a relational database and able to justify schema choices.
• Have cared for something in production, including deployment and post-incident steps.
• Prefer asking customers over guessing.

Responsibilities

• Own the end-to-end surface, from ontology to what a customer sees.
• Handle extraction that turns conversations into commitments and stakeholders.
• Develop a flow engine for typed graphs of blocks on finish or schedule.
• Build an agent that answers pipeline questions and shows executed queries.
• Create a notetaker that maps calls to the correct deal in Zoom/Meet/Teams.

Skills

Python or TypeScript

Relational databases

Production deployments

Customer-focused

Job description

You would be among the first engineers here, which means you get to own a surface end to end, from the ontology underneath it all the way to what a customer sees.

What you would work on

The ontology is the layer underneath everything we ship. Calls, email, documents and CRM fields resolve onto one typed record per deal today, and that list will grow. This layer should reach wherever a company keeps a model of its own business: a warehouse, a ticketing system, a billing platform, a product analytics tool. Every agent, flow and screen reads from it.

What is live today, and where the next few years of work sit:

• Extraction that turns a conversation into commitments, objections, stakeholders and competitors, each carrying the passage it came from
• A flow engine that runs typed graphs of blocks when a call finishes processing, or on a schedule
• An agent that answers questions about a pipeline and shows the queries it ran to get there
• A notetaker that joins on Zoom, Google Meet and Microsoft Teams and resolves every call onto the deal it belongs to

Experience we are looking for

• Several years building software that other people depend on, in whatever stack you learned it in
• Fluent in Python or TypeScript. We use both, and we care more that you can pick up the other one than that you already have
• At home in a relational database, and able to say why one schema is better than another
• You have looked after something in production, and stayed for the deploy, the incident and whatever came next
• You would rather ask a customer than guess

Useful, and not required: LLM-backed systems, event-driven or asynchronous processing, or any exposure to CRM and go-to-market data.

You do not need to have worked in sales software. You do need to find it interesting that a deal can stall for a reason nobody wrote down.

What you get

Equity in the company, so what you help build here is partly yours. A surface of the product to own, rather than a queue of tickets to work through. And on a team this size, when you find something wrong you can fix it that week, without asking anyone.