Product Engineer | Design Engineering Knowledge
Neural Concept is hiring a Product Engineer | Design Engineering Knowledge in Cambridge, United Kingdom. Level rates it ; you can apply on Neural Concept.
Level's read on this job
- Level rates this role Works on AI ●●●○: the daily work is on AI products, without building the model.
- The posting allows some remote work.
- Tools and skills the posting cites include RAG and AI agents.
- Level lists 35 other open roles at Neural Concept.
- The role was posted within the past week.
AI in this role
Location: Cambridge (UK), hybrid with up to 2 remote days per week
Team: Product
Start date: ASAP
About Neural Concept
Neural Concept is the engineering intelligence platform used by leading manufacturers in automotive, aerospace, and energy. We combine geometric and physics AI with LLM-based agents so engineering teams can move from customer requirements to validated designs in a fraction of the usual time.
About the role
Design decisions depend on information that lives outside the CAD model: customer requirements, design rules, manufacturing and assembly constraints, and cost targets. This information is spread across specification documents, handbooks, ERP systems, requirements management tools, and system models. Engineers gather it by hand, often late in the process, and conflicts surface at design reviews or on the production line.
We call the capability that closes this gap Design Engineering Knowledge. It connects the design to the information ecosystem around it, so requirements, constraints, and trade-offs are available to engineers and AI agents while they work on the design itself.
As a Product Engineer, you will build this capability. Requirements are the first focus area: extracting them from customer specifications and requirements management systems, structuring them, and keeping them traceable. You will then extend the same foundation to design rule checks, Design for Manufacturing (DfM), Design for Assembly (DfA), and Design for Cost, and connect it to the enterprise systems where this knowledge already lives.
You will work with the Product Manager, solution engineers, and customer engineering teams, as the primary developer from the first customer conversation to the version running in production.
What you will do
Build the requirements foundation: ingest customer specifications and RFQ packages, extract requirements with LLM and agent-based pipelines, and keep each one traceable to its source document and page.
Extend this foundation to design rules, DfM, DfA, and Design for Cost, turning standards, handbooks, and company know-how into constraints that software and agents can use.
Bring requirements, constraints, and trade-offs into the design workflow, so engineers can check a design against them at any stage and see which ones apply to the part they are working on.
Build integrations with the systems around the design: requirements management systems, ERP (cost, materials, and supplier data), and system design and MBSE tools for architecture and system-level requirements.
Design the data model that links requirements, rules, and constraints to parts, design parameters, and simulation results.
Create evaluation sets and quality metrics with customers, so extraction and checking accuracy is measured and improves with every release.
Design human-in-the-loop review flows where engineers validate and edit AI output, with versioning and a full audit trail.
Spot recurring patterns across customers and turn them into reusable components of the Neural Concept platform.
Who you are
Must have
Experience building and shipping production Python software in fast-moving, cross-functional teams.
Hands-on experience with LLM applications in production: structured outputs, retrieval-augmented generation, agents, and evaluation.
Experience integrating with enterprise systems through APIs and data models, for example ERP, PLM, or requirements management tools.
Experience with document processing, such as PDF parsing, OCR, or information extraction.
Strong software practices: testing (pytest), CI, packaging, code review, and git.
A product mindset. You talk to users, understand the problem before writing code, and ship in small, measurable steps.
Clear, concise communication with both customer engineers and internal teams.
Based in Cambridge (UK) or willing to relocate.
Nice to have
Background in mechanical engineering or physics, with exposure to DfM, DfA, or design-to-cost practices.
Familiarity with requirements engineering and model-based systems engineering (MBSE, SysML).
Experience working with CAD data or geometry processing.
Experience with vision-language models, vector databases, or search ranking.
What you get
Ownership of a product capability that customers use in real engineering programs, with direct access to the engineers who use it.
A competitive salary and rewarding opportunities as we continue to scale.
A collaborative, multicultural team where your work is visible and recognized.
Colleagues who share knowledge freely and support each other.
A hybrid model and flexible hours. We focus on results and trust you to organize your time.
We're proud to be an equal opportunity employer, and we're committed to building a diverse and inclusive environment where you can thrive.
How we rate this
Product Engineer | Design Engineering Knowledge at Neural Concept rates 71 out of 100 for how much of the daily work is AI. That makes it Works on AI (AI Level 3 of 4). The level is about AI in the job, not seniority.
Works on AI. The daily work is on AI products, without building the model.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Questions you could be asked
- How would you design a retrieval step so the model answers from real data instead of guessing?
- How do you decide when an AI agent can act on its own versus asking for approval first?
- Describe a typical day in a role like this one: which parts run through AI directly?
- If you removed AI from this role, what would be left, and how do you decide what still needs a human?
Adapt your resume
- List these exact terms on your resume: RAG and AI agents. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
- Show where AI is part of your daily process, not a one-off project. This role expects it to be a running habit.
Want an expert to read your CV for this job?
Free. Send your CV and the role you want next. You get your review by email within 24 hours.
Get new remote software engineering jobs (Works on AI ●●●○ or higher) by email
One email a week with the new remote software engineering jobs (Works on AI ●●●○ or higher), each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free. One email a week. Unsubscribe in one click.
Similar roles
Software Engineering roles that work on AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step