Original Product Artifact Working functional specification presented as a readable portfolio view

Product artifact · Functional specification

Functional Specification Documents (FSD) for Job Management Module (P001)

A readable web presentation of the working specification used to define job data, configurable hiring stages, shortlisting criteria, publishing states and implementation-level use cases for the Placement Management System.

System: Placement Management System
Module: Job Management Module (P001)
PRD reference: High-Level PRD for Placement Management System Ver 1.0
Document version: 1.0

Download source transcript

Configurable hiring stages

Each opportunity could carry its own hiring process.

Instead of one global pipeline, the specification made stage order, duration, dependencies, ownership and assessment tooling explicit at the job level.

Input	Definition	Field values	Input type	Notes / validation
Hiring Stage	The various stages involved in the hiring process for this job posting.	Initial Screening · Shortlisting by NavGurukul · Phone Screening · Technical Screening · Assessment Tests · Coding Challenge · Behavioural Interview · Technical Interview · Managerial Interview · Final Interview · Reference Check · HR Interview · Offer Negotiation · Job Offer · Onboarding	Dropdown	Allow custom input for “Other”. Allow users to reorder stages.
Hiring Stage Specs	Additional specifications or notes for each stage, including instructions, expected outcomes or links to assessment tools.	Free text	Text Area	Provide examples or template text and validate key details.
Stage Duration	The expected or allowed duration for completing the stage.	Numeric	Numeric	Ensure logical durations; support alerts or reminders where useful.
Stage Dependencies	Indicates whether the current stage depends on completion of previous or parallel stages.	Yes · No	Radio Buttons	If Yes, specify the dependent stage(s).
Responsible Role	The role or team responsible for executing or overseeing the stage.	Placement Team · PML · Hiring Org	Dropdown	Allow custom input for “Other”.
Assessment Tools	Tools or platforms used during the stage, such as coding platforms or personality tests.	Free text	Text Area	Shown when applicable, such as assessment tests or technical interviews.

Job shortlisting criteria

Learning evidence was translated into explicit shortlisting rules.

The specification connected providers, learning items, achievement thresholds and weightage so job-specific evidence could be configured instead of manually interpreted each time.

Input	Definition	Field values	Input type	Notes / validation
Learning Provider	The learning provider responsible for the modules, tasks or contests used for shortlisting.	Moodle · AtCoder · Speak & Improve · Write & Improve · Read Theory · CodeChef	Dropdown	Keep the provider list up to date.
Module / Task / Contest / Specs	The specific learning item considered for shortlisting.	Moodle modules · AtCoder Contest · Read Theory Task · W/I Grade · S/I Grade	Dropdown	Provide a comprehensive list and guidance or examples.
Achievement Criteria	The threshold that must be met for a candidate to be considered for shortlisting.	Module Passing · AtCoder score above threshold · Contest rank · Grade above threshold	Text Entry / Dropdown	Enforce consistent criteria descriptions and logical values.
Weightage	The importance given to the criterion in the overall shortlisting process.	0–100	Numeric	Validate that total weightage across criteria adds up to 100%.

Publishing states and outputs

The specification defined what the workflow produced, not only what users entered.

Job records carried their configuration and status forward into operational views and the student-facing job board.

Publishing states

DraftUpdate JSCPublishedExpiredClosed

Output 01

Job Posting Record containing job details, shortlisting criteria, hiring stages and publishing status.

Output 02

Job Board Display for published opportunities.

Implementation use cases

The workflow was carried into actor, trigger, precondition, success and exception logic.

These use cases show the transition from product requirement to executable behaviour for engineering and operations.

JP_UC001

Create a New Job Posting with publishing status as “Update JSC”

Primary actor: Placement Team
Stakeholders and interest: Placement Team needs to create job postings efficiently; Campus PMLs need to complete Job Shortlisting Criteria and publish the job.
Trigger: Need to add a new job opening to the system.
Preconditions: User is logged in with appropriate permissions. The system has current location and education-qualification reference data.
Postconditions: A new job posting is created and saved in Job Records with its publishing status.

Main success scenario

Navigate to the Post Job section.
Select Add Job Posting.
Fill the required shortlisting fields such as Learning Provider, Module / Task / Contest / Specs, Achievement Criteria and Weightage.
Submit the form.
The system validates required fields and date logic.
The system confirms creation and updates Job Records.

Extensions

If mandatory fields are missing or validation fails, the system prompts the user to correct the data before submission.

Special requirements

The flow should guide the user through each step and allow saving a draft when the posting cannot be completed in one session.

JP_UC002

Edit an existing “Update JSC” Job Posting and move it to “Published”

Primary actor: Campus PMLs
Stakeholders and interest: Campus PMLs need to complete Job Shortlisting Criteria and publish the job.
Trigger: Need to change a job from Update JSC to Published.
Preconditions: The job posting exists with status Update JSC.
Postconditions: The job posting is updated in Job Records and the publishing status is changed.

Main success scenario

Open Job Records and select the posting with Update JSC status.
Open Job Shortlisting Criteria.
Complete the required job and shortlisting information.
Review the job details and publishing status.
Submit the form.
The system confirms the update.

Extensions

If the job posting is incomplete, the system prompts the user to complete missing information before publishing.