Build systems that do real work.
Cognizec designs and builds AI systems that operate inside businesses: agents, workflows, applications, and the data and control layers around them. We are a small team, working remotely. No roles are open right now, but a CV is still welcome: send one below and it goes straight to the hiring team.
No open roles right now.
We are not hiring for a specific position at the moment. If you would like to be considered when one opens, send your CV with the form below.
Send your CVThe model is not the system, and neither is the office.
The problem picks the stack.
We select models, tools and infrastructure around the work, not the other way around.
Running is not finished.
A system that acts on a business needs logs, traces and metrics from the first day, or nobody can say what happened.
Autonomy needs boundaries.
Permissions, policies and human approval are part of the architecture, not something bolted on afterwards.
Remote, start to finish.
The team works remotely, and interviews are held online by video call.
Four kinds of work, one system.
Everything we build is a connected system, so most of the work sits across these lines rather than inside one of them.
Agent and workflow engineering
Orchestration, tool use, retries, evaluation, and the traces that show what an agent did and why.
Software engineering
Web applications, internal tools and the services that connect AI to the systems a business already runs.
Data and knowledge systems
Extraction, enrichment, pipelines, retrieval and document intelligence over real, messy sources.
Integrations
CRMs, databases and APIs, with the identity, permission and logging that make an integration safe to run unattended.
Engineers who would rather have a trace than a hunch.
You have shipped something that runs.
A system in production you can describe end to end, including what went wrong and how you found out.
You read the logs.
You would rather have a trace than a hunch, and you build so there is a trace to read.
You can explain your work to a non-engineer.
Most of the people we build for own a process, not a codebase.
You are comfortable owning a boundary.
Permissions, approvals and failure paths are your work, not someone else's problem.
Send your CV.
One form, sent straight to the hiring team with your CV. Nothing goes anywhere else.
If the form will not send, write to instead.