Four roles, always worth a conversation
Location: 4F, Jincheng Department Store, Huixian, Xinxiang, Henan, China
We do not hire by headcount targets. What a project needs is people who can carry a stretch of the chain on their own: ask a client what they actually need, get a model to the agreed quality line, deploy a system into somebody else's machine room, and then keep reading the data after go-live.
Each role below lists what we expect you to bring and what we are willing to teach. Do not screen yourself out using the second list.
Algorithms and data
Model selection and fine-tuning, RAG retrieval chains, data cleaning and labelling standards, evaluation and failure analysis. You are accountable for a pass rate on an evaluation set, not for a working demo.
Back-end and integration
Business systems and admin consoles, integration with what the client already runs, permission and data-model design, containerised deployment and monitoring — including wiring model services into real processes.
Front-end and mini-programs
Admin and user-facing interfaces, mini-programs and mobile, dashboard visualisation. Interfaces here serve operating speed; we are not building things that only look good in a screenshot.
Implementation and operations
On-site installation, client training, knowledge-base upkeep, usage data, incident handling and alerting, plus the publishing and monitoring rhythm behind GEO work.
From résumé to offer
Four steps, at most two of them face to face
Show what you have made
résumé or artefactsNo cover letter needed. Send one thing we can open: a repository, something you deployed, technical notes you wrote, even a set of materials you organised. Education and years of experience are welcome in the message, but they are not the first filter.
You prepare: a short introduction plus one thing that can be looked at
One conversation
about an hourWe talk about one specific thing you did: how you judged it, where it went wrong, what you would do differently. We also open up a real project we are on, so you can ask anything — including pay and working rhythm.
Decided here: which of the four roles the direction lands in
A small task
take it home, no time limitA slice cut from a real project: propose a chunking plan for a batch of documents, wire one page to an API, or write an incident review. The point is how you think and how you hand something over — the task content and your conclusions are not used for commercial delivery.
We look at: whether the trade-offs are explainable, whether the output is directly usable
Role and terms
in personWe go through the task together, then settle the specifics: which project, who you work with, terms and probation. We will not ask you to come in and work before this step.
Output: a verbal conclusion plus something in writing
How it is here
Said up front, so nobody is disappointed after joining
Builders decide
Solutions are written by the people who will maintain them, not by people who never touch the code.
- Scoping, design and delivery usually the same people
- No reporting material produced for its own sake
- Technical trade-offs are argued out with reasons
You touch real things
Client sites, live data, production equipment — not practice projects.
- You see how a requirement changes three times
- Model quality has an evaluation set; good or bad is a number
- Systems run in someone else's machine room, so incidents are real
What we will not promise
Better to read it here than to be disappointed later.
- No guarantee of no overtime: releases have crunch
- No guarantee of fully remote work: roles are based in Huixian, exceptions discussed
- This page states no salary range or headcount — terms are set in the conversation and the contract
How to apply
Say which role you want, and attach something we can open