Metatech Work History Capture (WHC)

[gauravpandeydigilantern]

Work History Capture (WHC), 1. Configuration and Data:

• Data Storage: The WHC needs to store information about domains (e.g., Software Engineering, Systems Engineering), competency groups, competencies, activities, and guidance/help information. This data can be stored in CSV files or a database.
• Configuration: The WHC should have a way to manage configuration settings, including field definitions, word limits for text fields, and other parameters. This can also be stored in CSV files or a database.
• Offline Capabilities: Candidates should be able to save their work in progress to their local computers and resume editing later.
• Email Submission: Candidates should be able to submit their completed work history via email.

2. Data Input:

• General Information: The WHC needs to collect general information about the candidate, including their name, email address, executive summary, degrees, and certifications.
• Position Information: For each position held, the WHC needs to collect information like the company name, position title, start and end dates, duration, and a description of the position.
• Work History Information: For each position, the WHC needs to collect information about the domain, competency group, competency, activity, percentage of time spent on the activity, and a description of the work performed.

3. Functionality:

• Picklists: The WHC should provide picklists to help candidates select information from pre-defined options, such as domains, competency groups, and competencies.
• Validation: The WHC should enforce data validation rules to ensure the data entered is accurate and consistent (e.g., ensuring that dates are in the correct format, preventing overlap in position dates, enforcing word limits for text fields).
• Add/Delete Entries: Candidates should be able to add and delete individual work history entries as needed.
• Performance Progress Indicator: The WHC should display the percentage of the position's period of performance that has been filled with work history entries.

Overall, the client seeks a web-based application that simplifies and improves the process of capturing candidate work history. This application will be user-friendly, efficient, and secure, making it easier to manage and analyze candidate data.

[gauravpandeydigilantern]

I. User Interface and Features:

A. Candidate Registration and Profile:

1. Sign Up/Login: Secure registration and login system for candidates.
2. Profile Creation: Allow candidates to create and maintain their profile, including:
   • Personal Information: Name, Email, Phone Number, Address
   • Executive Summary: Brief summary of their professional experience (word limit enforced).
   • Education: Degree, Year, Institution (with picklists for degree types and institutions).
   • Certifications: Title, Year, Provider, Certification Number (with picklists).
3. Profile Editing: Enable candidates to edit their profile information.
4. Password Management: Secure password management features (forgot password, password reset).

B. Work History Input:

1. Position Entry:
   • Company Name: Free text entry (with word limit).
   • Position Title: Free text entry (with word limit).
   • Start Date/End Date: Date pickers with validation to prevent overlapping periods.
   • Duration Calculation: Automatic calculation of position duration in months.
   • Position Description: Free text area with word limit (75 words).
2. Work History Details:
   • Domain Selection: Picklist of available domains (e.g., Software Engineering, Systems Engineering).
   • Competency Group Selection: Picklist of available competency groups, dynamically updating based on the selected domain.
   • Competency Selection: Picklist of available competencies, dynamically updating based on the selected competency group.
   • Activity Selection: Picklist of available activities related to the selected competency.
   • % of Position: Input field for the percentage of the position's period of performance dedicated to the selected activity. Validation to ensure the total percentage across all activities doesn't exceed 100%.
   • Performance Description: Free text area with word limit (75 words) to describe the candidate's experience with the selected activity.
3. Adding/Deleting Entries: Allow candidates to add new work history entries or delete existing entries as needed.
4. Progress Indicator: Display a progress bar or percentage indicating the completion of the position's period of performance.
5. Guidance/Help: Provide clear and concise guidance/help information for each field, accessible through icons, tooltips, or a dedicated help section.
6. Save and Resume: Enable candidates to save their progress at any time and resume editing later.

C. Submission:

1. Review and Submit: Allow candidates to review their work history information before submitting it.
2. Confirmation: Provide a confirmation message upon successful submission.
3. Data Download: Optionally, allow candidates to download a copy of their submitted work history in a standard format (e.g., CSV, PDF).

II. Back-End Features and Management:

A. Data Storage and Management:

1. Database: Choose a suitable database to store all information (MySQL, PostgreSQL, MongoDB, etc.) and create a database schema to organize the data.
2. Data Validation: Implement backend data validation rules to ensure data integrity (e.g., enforce data types, check for null values, and handle date formats).
3. Data Security: Implement appropriate security measures to protect candidate data, including data encryption and access control.

B. System Administration:

1. Admin Portal: Create an admin portal for managing the WHC application:
   • User Management: Create and manage user accounts (candidates and administrators).
   • Data Management: View, edit, and delete user data.
   • Domain, Competency Group, Competency, Activity Management: Add, update, and delete domain, competency group, competency, and activity information.
   • Configuration Settings: Modify settings like word limits, field descriptions, picklist values, and other system settings.
   • Reporting: Generate reports and analytics on submitted work history data.
2. Logging: Implement logging mechanisms to track system activity, errors, and user interactions.

C. Integration and Deployment:

1. API Development: Consider developing an API to allow integration with other systems (e.g., applicant tracking systems, HR systems).
2. Deployment: Deploy the WHC application on a secure and reliable server environment.

III. Additional Features (Optional):

1. Search Functionality: Allow administrators to search and filter submitted work history data by various criteria (e.g., domain, competency, candidate name, position).
2. User Roles: Introduce different user roles (e.g., candidate, admin) with specific permissions.
3. Feedback System: Allow candidates to provide feedback on the WHC application.
4. Gamification: Consider adding gamification elements (e.g., badges, points) to motivate candidates to complete their work history.