Pipeline Customization

The Customize panel is Ovii’s job-level operating layer. It does not create the role itself; it tells the system how that role will be evaluated after the job is live. In the current product, that layer is split into three controls: interview feedback, candidate status pipeline, and resume match scoring.

That separation is intentional. These three controls solve different governance problems. Feedback forms standardize interviewer evidence. Pipeline stages define how the team moves candidates through the process. Resume match scoring defines what the system should value when it ranks applicants against this specific job.

Treat this area as a calibration surface rather than an optional polish step. The better it is configured before activity starts, the cleaner the hiring process becomes later.

Note

Interview feedback form customization and status-pipeline customization are feature-controlled paths in the backend. If a save action is blocked or unavailable, review your company feature access before troubleshooting the job itself.

The defaults exist for a reason. Ovii starts each job from a reusable baseline so recruiters do not have to rebuild structure from scratch every time. In enterprise hiring, that is usually the right default because it keeps teams aligned and preserves consistency across similar roles.

Customize only when the role genuinely needs a different evaluation model. If every recruiter edits every job, the process becomes difficult to compare, hard to audit, and expensive to maintain. If nobody customizes when they should, the workflow stays neat but the role may be evaluated against the wrong criteria.

A practical rule is this: keep the default if the job follows the company’s standard hiring path; customize if the role needs materially different evidence, stage flow, or candidate-ranking logic.

The feedback-form editor exists to make interviewer evidence more role-specific. Ovii begins with a default form built from industry-standard criteria, which is a sensible baseline for common roles. The problem is that a default form cannot fully capture what makes one hiring process different from another.

For a deeply technical role, the team may need separate sections for algorithmic depth, system-design tradeoffs, domain judgment, or stakeholder communication. For a sales or operations role, those sections may be the wrong lens entirely. Customizing the feedback form lets the recruiter define what good evidence should look like before interviewers start scoring candidates.

This matters more than teams usually admit. A hiring process becomes inconsistent when interviewers are forced to improvise their own criteria. A strong custom form gives the panel a shared language for evaluation and makes debriefs easier because everyone is rating against the same frame.

Note

The feedback template is resolved with job-level priority first, then category-level fallback. In practice, that means a custom form overrides the default only for this job, while unchanged jobs can continue to use the shared company or category baseline.

Note

Once actual interview feedback has been submitted for the job, template edits can be locked. That guardrail exists so the team does not change the scoring rubric after candidate evaluations have already started.

The status pipeline is the operational map of the job. It controls how candidates move through the workflow and which stage names the team sees in candidate management, reporting, downstream actions, and interview coordination.

This is why stage labels are not cosmetic. A poor pipeline creates handoff confusion, bad reporting, and weak automation logic. A good one mirrors the real decision points of the hiring process without adding unnecessary ceremony.

Ovii seeds each job from the company’s default pipeline so recruiters can start from a stable structure. From there, you can rename stages, reorder them, activate or deactivate them, and add new ones where the workflow truly needs additional checkpoints.

Note

The frontend warns more aggressively once candidates are already active in the workflow. At that point Ovii allows safer changes, such as adding new stages, while preventing destructive edits like deleting or deactivating stages that already affect live movement.

Note

The backend also resets the approval state when the pipeline is replaced and then re-confirms it on save. This is important because other job-level features read the current approved pipeline, not an outdated draft.

Note

Assessment invitations and panel-assignment flows depend on the pipeline being confirmed. In practical terms, pipeline setup should be treated as a prerequisite for the later interview workflow, not as an afterthought.

Resume Match Score exists to make resume ranking job-specific. Without it, every job would inherit the same weighting logic even when the role clearly values different signals. That is a poor fit for enterprise hiring because a senior niche role, an early-career volume role, and a domain-heavy leadership role should not all be scored the same way.

Ovii solves that by exposing the scoring weights directly. The recruiter can decide how much the system should care about experience match, skill match, education match, certifications, domain relevance, and notice-period alignment for this one job.

The key idea is simple: weighting is how you tell the system what good fit means. If the role is skill-heavy, push more weight into skills. If domain familiarity is crucial, move weight into domain relevance. If immediate availability matters, allocate meaningful weight to notice period. That is how the ranking engine becomes operationally useful instead of merely mathematical.

Note

The current defaults are 45% for experience match, 40% for skill match, and 15% for education match, with the optional criteria starting at 0. That is a good general baseline, but it should not be treated as universally correct for every job.

Note

Scoring customization is saved at the job level. Changing these weights affects how this job evaluates candidates; it does not rewrite the scoring logic for every other role in the company.

The best way to use job customization is to treat it like configuration management. Make the decisions early, document the rationale in the hiring team, and avoid unnecessary midstream edits once real candidate activity begins.

In enterprise environments, the goal is not just to make one job look neat. The goal is to make interviewer evidence, candidate progression, and resume ranking defensible across recruiters, hiring managers, and approvers. That only happens when the configuration is stable enough to trust.