Engineering network
Work on software that has to operate in the real world.
Codemind assembles teams around product and agent-system responsibilities. We are interested in engineers and specialists who value clear boundaries, evidence and direct communication.
Current status
No specific vacancy is advertised here today.
We removed the previous generic job listings because a public role should have a verified owner, scope, location, status and application route.
Codemind is building relationships with specialists in the UK and Sri Lanka for future product and engineering work. An expression of interest is not an offer of employment or a promise of available work.
Introduce your experienceShare a concise professional introduction and links to work you are allowed to disclose. Do not email identity documents, financial information or other sensitive personal data.
Useful disciplines
Teams are shaped by the responsibility.
The mix changes between application development, product improvement, integration and agent-system work.
Full-stack engineering
Product work across interface, application state and APIs.
AI engineering
Context, retrieval, model integration, tools and evaluation.
Backend engineering
Domain services, data, integration, identity and reliability.
Frontend engineering
Accessible product interfaces and complex workflow interaction.
DevOps and platform
Deployment, observability, security boundaries and operations.
Quality engineering
Risk-based automation, integration, accessibility and release evidence.
Product
Problem framing, workflow design, prioritisation and outcome measurement.
UI/UX
Research and interaction design where the product requires it.
Working principles
Quality without theatre.
The strongest signal is the ability to make a useful decision visible, explain the trade-off and leave a system easier to operate.
- Write and speak clearly with business and technical colleagues.
- Prefer explicit contracts, state and tests over hidden assumptions.
- Use normal software when it is the dependable answer.
- Understand failure, recovery and operational ownership.
- Treat privacy, accessibility and security as product work.
- Do not invent evidence to make a case study or CV sound stronger.