Software Engineer

CodeSpeak Ltd; Greater London; Hybrid; GBP 65,000 - 90,000; Full time

Benefits offered by this job

Relocation to London

In-person work

Job summary

CodeSpeak Ltd. is looking for engineers who can help shape a new proto-language for prompts used by coding agents. You will work in person in London, delivering production software and actively improving AI-assisted workflows.

The team values strong CS fundamentals and a collaborative approach to tooling and software architecture. We hire quickly, with two technical interview stages and a final round. Relocation to London is available for the right candidates, and participation in a growing

Qualifications

• Solid CS/SE fundamentals
• Experience delivering production software
• Ability to work with AI-powered coding tools

Responsibilities

• Inject relevant requirements into the agent context when starting a new feature
• Evaluate and resolve conflicts before coding based on requirement-level diffs
• Support code review by tracing changes to original intent and constraints
• Communicate with the team about architecture implications and trade-offs

Skills

CS fundamentals

Software engineering

Job description

CodeSpeak is an Agentic Engineering Toolkit: a set of tools to make AI coding work well for production-grade software projects.

Coding agents are amazing for prototypes, one-offs, and hobby projects. Yet, for serious production, results are more mixed:

• the amount of slop in codebases is growing, and they become less and less maintainable (GitClear-26),
• people can’t keep up with reviews,
• and more and more areas in projects accumulate “comprehension debt” (nobody really understands how they work).

As a result, engineering leaders are seeing more incidents per PR (+23.5%, see Cortex-26). In other words, people ship slop, and it’s starting to bite them. “The Claude Code moment” happened in late 2025, so what we see today is not even the full extent of the consequences.

At CodeSpeak, we believe three simple things:

• AI coding tools can help people make quality production software;
• Nobody wants to ship slop, people just don’t have the right tools to remain on top of their codebases;
• While coding may be solved by models, Software Engineering is still a human job.

CodeSpeak’s Vision. The prompts we give to coding agents are a new proto-language that is emerging right now. And we want to make it into a good, usable production language. The valuable part is that these prompts contain the intent behind the code. The resulting code can be generated from it, therefore it must be a complete description of the system. Right now, this description is very messy, and we want to make it clean and useful.

The proto-language of prompts that’s emerging right now is at the “spaghetti prompts” stage:

• important decisions are largely buried in session logs that nobody reads (because they are often not very readable),
• exploration, ideation, and prototyping are mixed with careful construction of lasting architectures,
• there’s no modularity, abstraction, or static checks on prompts.

To fix this, we need to do the same things we did to fix spaghetti code: we need to organise the high-level intent from prompts into always-up-to-date, reusable logical modules that humans and agents can navigate. Like modules in a programming language, but on the next level. That’s Software Engineering for the age of AI, and CodeSpeak is building tools that make it possible.

CodeSpeak’s Current Approach. We believe that user intent is the real primary artifact, and code is just what's derived from it. Right now, we're building an engine that captures this intent from session transcripts, distills it into structured requirements, grounds them in the code, and enforces them as the codebase changes.

These requirements become the layer developers actually work through, across the entire development process. For example:

• When an agent starts a new feature, CodeSpeak injects the relevant requirements into its context, so it builds with the rest of the system in mind.
• When a new prompt in a chat contradicts older requirements, a code isn’t written until the conflict is resolved.
• Code review starts from the requirement-level diff: what intent changed, what constraints were added or removed, and whether the implementation still satisfies them.

See more in our blog, and this is only the beginning. Let’s talk about what will come next when we meet.

Team

CodeSpeak is founded by Andrey Breslav, creator of Kotlin – a language used by millions of developers every day. Around him is a team that has built the tools other engineers rely on, at Google, Databricks, Perplexity, JetBrains, Sourcegraph, and Elastic. When it comes to program analysis and developer tooling, these are some of the best people in the world.

We hire very fast, just two tech interview stages + final. We work in person and are ready to relocate you to London.

We'd love to see more women apply. If you're on the fence, please do apply, and if you know someone brilliant (whether they are actively looking or not) please share!

28% of computing graduates in the UK are women. It's a lot of talent we don't want to miss out on.

• Smart, curious, self-driven engineers with a passion for making programming better.
• Have a solid understanding of CS/SE fundamentals.
• Have experience delivering production software: 3+ years.
• Actively improve their workflows with AI-powered coding tools.
• If you have some recent interesting code to show us, it would be a plus.