01./New requirements
Shape a new product
Some engagements begin with a new product: clarifying user workflows, making product constraints explicit, and turning an approved direction into software.
Careers
Craftnotion works across new products, existing systems, and continuing roadmaps. Role context depends on the responsibility and conditions of the verified opening.
Product work context
Understand the work
before evaluating a role.
A role can touch new products, existing systems, or a continuing roadmap, depending on the responsibility that is open.
02./Existing systems
Improve what already runs
Other work starts with an existing system. The responsibility may involve understanding current behavior, reducing risk, and shipping changes that fit the product already in use.
03./Continuing roadmaps
Extend a product over time
Continuing roadmaps connect design, engineering, review, release, and handoff work. The exact scope depends on the approved role and the product context it names.
Hiring information
What a verified role
will make explicit.
We publish role details when they are approved, including responsibility, working conditions, and the hiring steps candidates can expect.
01./Step
Role status
A published opening names the responsibility, current requisition status, and the conditions approved for that role.
02./Step
Role context
The role description should explain the product context, expected outcomes, collaboration points, and evidence relevant to the work.
03./Step
Conversation steps
Approved hiring steps are shared with the role. We do not promise a fixed stage count, response time, or unpaid production task.
04./Step
Candidate data
Application fields and handling terms should be clear before submission. See the Privacy Policy for how candidate information is handled.
When a verified role opens, its brief will describe the product context, responsibilities, and conditions. Nothing is collected before then.
