Theme

Category: ROCKEN Documentation

  • Story 3.5.2. RJ. Help center. Hero and search results

    Content

    General info

    The Hero section of the Help Center serves as the introductory area for users, guiding them to find the answers they are looking for. This section will include a prominent title, an explanatory text, and a search input field. The explanation text will instruct users on how to use the Help Center and encourage them to reach out if they cannot find the information they need.

    The goal is to provide a welcoming, easy-to-use entry point for visitors, helping them navigate the resources effectively. The search input field will allow users to quickly locate relevant articles, ensuring a smooth and user-friendly experience.

    User story

    As a Help Center visitor

    I want to see a clear introduction and have a search input field available

    So that I can easily understand the Help Center’s purpose and find information quickly.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=54236-36303&t=Tb42tMQaRDggm2rb-4

     

    #

    Acceptance Criteria

     

    01

    Scenario: Display Hero Section in Help Center
    Given the user navigates to the Help Center main page
    When the page loads
    Then the Hero section should be displayed at the top of the page, containing a title, explanatory text, and a search input field.

     

    image-20241006-155349.png

    02

    Scenario: Show Explanation Text
    Given the user is viewing the Hero section
    When the text is displayed
    Then the text should read: “If you haven’t found the answer to your questions on this page, if something is unclear, please contact our Help Center. Here you can find answers to almost all questions.”

     

    03

    Scenario: Search Input Behavior
    Given the user is viewing the Hero section
    When they start typing in the search input field
    Then the system should display a list of dynamically matching articles as the user types.

    04

    Scenario: Search Functionality
    Given the user has entered a keyword in the search input
    When they press Enter or click the Search button
    Then the system should navigate to a search results page, displaying articles that match the entered keyword.

     

    image-20241006-160342.png

    image-20241006-160412.png

    05

    Scenario: No Search results
    Given the user has entered a keyword in the search input
    When they press Enter or click the Search button
    Then the system didn’t find matched information and shows contact us content

    image-20241006-160535.png

    image-20241006-160635.png

  • Story 3.3.3. RJ. Application. Title

    Content

    General info

    This story involves displaying the appropriate title on the application pages based on whether the user is applying to a specific job vacancy or submitting a general application. If a specific vacancy is selected, the title and details should match the job position. If the user is applying from the main page, a default "Upload resume" title should be shown, indicating a general application process.

    User story

    As a candidate applying to a vacancy,
    I want to see the correct header labels and vacancy title on the application page,
    So that I know which position I’m applying for or if I’m submitting a general application.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=53430-5788&t=T1cu0YDDVtmi76or-4

     

    #

    Acceptance Criteria

     

    01

    Scenario: Display correct title for vacancy-specific application
    Given: the user has navigated to the application page for a specific vacancy
    When: the page loads
    Then: title should display the job title

     

     

    02

    Scenario: Display general application header and title
    Given: the user has navigated to the application page from the main page without selecting a specific vacancy
    When: the page loads
    Then: title should display "Upload resume" instead of a vacancy title.

     

     

  • Story 3.3.2. RJ. Application. Sub-title info line

    Content

    General info

    This story involves displaying the appropriate labels on the application pages based on whether the user is applying to a specific job vacancy or submitting a general application.

    User story

    As a candidate applying to a vacancy,
    I want to see the correct labels on the application page,
    So that I know which position I’m applying for or if I’m submitting a general application.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=53430-5788&t=T1cu0YDDVtmi76or-4

     

    #

    Acceptance Criteria

     

    01

    Scenario: Display correct labels for vacancy-specific application
    Given: the user has navigated to the application page for a specific vacancy
    When: the page loads
    Then: the sub title should show the "Official Partner" label, location, workload, and copy link for recomendation

     

    image-20241006-130514.png

     

  • Story 2.2.5.1. RT. Jobs page. Prefilter for Recomended Tab

    Content

    Content | General info | User story | Visual design: | Acceptance criteria

    General info

    Feature in the recommended tab to display applied pre-filters for job matches. The applied filters should be highlighted to indicate the logic used for matching. This feature will ensure that users have clarity on which pre-filters are active without being overwhelmed by a long list of all possible filters. Only the pre-filtered items should be displayed, enhancing the user experience and enabling more focused decision-making.

    User story

    As a RT user,
    I want to see the applied pre-filters highlighted in the Recommended tab,
    So that I can understand which logic is being used to filter the job matches.

    Visual design:

    –

     

     

    Acceptance criteria

     

    01

    Scenario: Viewing pre-filters in the Recommended tab
    Given the user is in the recommended tab
    When the recommended tab displays candidate job matches by categories and industries
    Then the active pre-filters are highlighted in the filter panel.

    02

    Scenario: Displaying only pre-filtered items
    Given the recommended tab is open
    When pre-filters are applied
    Then only the pre-filtered items (jobs) should be shown in the list, not the entire set of possible filters.

    03

    Scenario: Clarity of applied filters
    Given there are multiple pre-filters active
    When the user checks the filters in the recommended tab
    Then the pre-filter logic is clearly highlighted to show what conditions are used for matching.

  • Story 1.6.2.3. CRM. Process. Implementation of Detailed Rejection Reasons with Additional Textboxes (Manual Rejected by Company)

    Content

    [ Content ] [ General info ] [ User story ] [ Visual design ] [ Acceptance criteria ]

    General info

    The CRM will include a new feature allowing users to select detailed rejection reasons when changing a candidate’s status to "Company rejected." This will ensure clearer communication of rejection reasons to candidates. A modal window will present users with a dropdown list of predefined rejection reasons, which, upon selection, will display corresponding pre-written texts. This functionality will enhance the user experience and streamline the rejection process.

    Rejection Reason

    Pre-written Texts (English)

    Pre-written Texts (Deutsch)

    Work Experience / Career

    Your work experience does not meet our partner’s requirements.
    Our partner is currently seeking candidates with a different career background.
    Your previous career path does not align with our partner’s requirements for this position.

    Deine Berufserfahrung entspricht leider nicht den Anforderungen unseres Partners.
    Derzeit sucht unser Partner nach Kandidaten mit einem anderen beruflichen Hintergrund.
    Dein bisheriger beruflicher Werdegang stimmt nicht mit den Anforderungen unseres Partners überein.

    Education / Certification

    Your education does not meet our partner’s requirements for this position.
    Our partner requires specific certifications that you unfortunately do not possess.
    The education required for this position is missing from your profile according to our partner’s requirements.

    Deine Ausbildung entspricht nicht den Anforderungen unseres Partners für diese Position.
    Unser Partner benötigt spezifische Zertifizierungen, die Du leider nicht besitzt.
    Die für diese Position erforderliche Ausbildung fehlt in Deinem Profil gemäss den Anforderungen unseres Partners.

    Industry / Product Knowledge

    Your industry knowledge does not meet our partner’s expectations.
    Our partner is looking for someone with specific product knowledge that you lack.
    Your experience in the industry is not sufficient for our partner’s position.

    Deine Branchenkenntnisse entsprechen nicht den Erwartungen unseres Partners.
    Unser Partner sucht jemanden mit spezifischen Produktkenntnissen, die Dir fehlen.
    Deine Erfahrung in der Branche ist nicht ausreichend für die Position unseres Partners.

    Salary

    Your salary expectations are beyond our partner’s budget.
    Unfortunately, our partner cannot meet your desired salary.
    Your salary request exceeds the budget allocated for this position by our partner.

    Deine Gehaltsvorstellungen liegen über dem Budget unseres Partners.
    Leider kann unser Partner Dein gewünschtes Gehalt nicht erfüllen.
    Dein Gehaltswunsch übersteigt das für diese Position festgelegte Budget unseres Partners.

    References

    The provided references do not meet our partner’s expectations.
    Your references were not sufficient to meet our partner’s requirements.
    Our partner needs more comprehensive references for this position.

    Die bereitgestellten Arbeitszeugnisse entsprechen nicht den Erwartungen unseres Partners.
    Deine Arbeitsnachweise waren nicht ausreichend, um die Anforderungen unseres Partners zu erfüllen.
    Unser Partner benötigt umfassendere Referenzen für diese Position.

    Skills

    Your skills do not match our partner’s job requirements.
    Our partner is looking for specific skills that are missing from your profile.
    Your current skills do not meet our partner’s requirements for this position.

    Deine Hard-Skills entsprechen nicht den Anforderungen unseres Partners für diese Stelle.
    Unser Partner sucht spezifische Fähigkeiten, die in Deinem Profil fehlen.
    Deine aktuellen Fähigkeiten entsprechen nicht den Anforderungen unseres Partners für diese Position.

    Overqualification

    You are overqualified for our partner’s position.
    Our partner is looking for a candidate with less experience for this role.
    Your qualifications exceed the requirements for our partner’s position.

    Du bist für diese Position unseres Partners überqualifiziert.
    Unser Partner befürchtet, dass du in dieser Position unterfordert wärst.
    Deine Qualifikationen übertreffen die Anforderungen dieser Position unseres Partners.

    Underqualification

    You are underqualified for our partner’s position.
    Your qualifications are not sufficient for this role according to our partner’s requirements.
    Our partner needs someone with more experience and qualifications.

    Du bist für diese Position unseres Partners nicht genügend qualifiziert.
    Deine Qualifikationen sind nicht ausreichend für diese Rolle gemäss den Anforderungen unseres Partners.
    Unser Partner benötigt jemanden mit mehr Erfahrung und Qualifikationen.

    Other

    (Textbox for additional comments)

    (Textbox für zusätzliche Kommentare)

    User story

    As a CRM user,
    I want to select detailed rejection reasons and see corresponding pre-written texts when a candidate is manually rejected,
    So that I can provide clear and consistent feedback to candidates.

    Visual design

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=51321-21680&node-type=frame&t=6giRil3QJgJs9VpE-0

    Acceptance criteria

    01

    Scenario: Opening the rejection modal
    Given the CRM user is changing status
    When the user opens the modal window
    AND the status of a candidate is changed to "Company rejected"
    Then the user sees a rejection reasons dropdown and a submit button.

    02

    Scenario: Selecting a rejection reason
    Given the user has opened the rejection modal
    When the user selects a reason from the rejection reasons dropdown
    Then the corresponding pre-written texts for that reason are displayed below the dropdown.

    03

    Scenario: Viewing pre-written texts
    Given the user selects a rejection reason from the dropdown
    When the reason is selected
    Then the user sees the three pre-written texts related to that reason and the selected text is shown in a textbox.

    04

    Scenario: Submitting rejection reasons
    Given the user has selected a rejection reason and the corresponding pre-written text
    When the user clicks the submit button
    Then the selected reason and text are saved and the candidate’s status is updated to "Company rejected."

  • Story 1.6.5.2. CRM. Process by Download – Vacancy Type Change Warning

    Content

    [ Content ] [ General info ] [ User story ] [ Visual design ] [ Acceptance criteria ]

    General info

    The CRM system needs to ensure that the vacancy types align with the process requirements of the associated companies. When a vacancy is marked as "by download," it alters the usual candidate process workflow. This user story addresses the need for warning messages to inform CRM users about potential discrepancies when changing vacancy types. If a company is set to receive shared profiles by download and the user attempts to change a vacancy to the email type, the user should receive a warning. Conversely, if the company type changes from email to download, all associated vacancies should also be automatically updated to reflect this new requirement. This ensures that users are always aware of the process type required by the company, thus minimizing errors and maintaining the integrity of the workflow.

    User story

    As a CRM user,
    I want to receive warnings when changing the type of a vacancy,
    So that I can ensure that the vacancy type aligns with the company’s process requirements.


    RT-2409
    –
    Получение подробных данных проблемы…
    СТАТУС

    Visual design

    –

    Acceptance criteria

    01

    Scenario: Changing vacancy type from download to email
    Given a vacancy and company have type "by download"
    When the user attempts to change the vacancy type to "email"
    Then the user receives a warning: "The assigned company requires Application by download. Make sure this is verified for this vacancy."

    02

    Scenario: Changing company type from email to download
    Given the company type is "email"
    When the user updates company type to “download“
    Then all associated vacancies should automatically change to "by download" type.

    03

    Scenario: Creating a new vacancy for a download type company
    Given a company requires "Application by download"
    When the user attempts to create a new vacancy and selects the "email" type
    Then the user receives a warning: "The assigned company requires Application by download. Make sure this is verified for this vacancy."

  • Epic 1.0.6. Search

    General info

    The main goal of this epic is to enhance the search functionality within the CRM system by integrating Elastic Search. This implementation will improve the efficiency and speed of filtering results for users when searching for candidates, job listings, or companies. By utilizing Elastic Search, the system will be able to handle complex queries, support a wide range of filter combinations, and return accurate results in a timely manner. This epic includes setting up Elastic Search, configuring it to work with various filters, and ensuring that the search speed and accuracy meet the expected performance benchmarks.

     

    Epic ticket:

    User stories

    Visual design

     

     

  • Story 1.0.6.1. Elastic search for filters

    General info

    The objective of this story is to implement Elastic Search for managing filters on different search pages within the CRM system. Elastic Search will be utilized to enhance the speed and accuracy of search queries, especially when using multiple criteria. The system should support complex filtering, including keyword searches and range-based filters, ensuring that CRM users can quickly find relevant information.

    User story

    As a CRM user
    I want to use multiple filters on search pages
    So that I can efficiently find relevant candidates, jobs, or companies based on specific criteria.

    Visual design:

     –

     

     

    Acceptance criteria

     

    01

    Scenario: Filter with Elastic Search
    Given Elastic Search is set up and configured
    When a user enters filter criteria and initiates a search
    Then the system should return results that accurately match the applied filters and display them in the search results.

     

    02

    Scenario: Search using multiple filters
    Given the user selects more than one filter (e.g., location and job title)
    When the search query is executed
    Then the system should only display results that meet all the selected criteria and hide any results that do not match the combined filters.

     

    03

    Scenario: Keyword search functionality
    Given the user enters a specific keyword in the search bar
    When the search is performed
    Then the system should return results that include or match the entered keyword in any relevant fields and display them in order of relevance

     

    04

    Scenario: Filter validation
    Given the user applies a combination of filters (e.g., location, job title, and skill)
    When the search is executed
    Then the system should ensure that the entered criteria are valid for the search type (e.g., no conflicting filters) and show an appropriate message if there are no results that match the current combination of filters.

  • List for Roken.jobs

    1. Mobile Layout:

      1. Header and footer. DONE

      2. Side or top menu. DONE

      3. Reduce the logo to a symbol. DONE

      4. Consider whether anything should be displayed in the header. DONE

    2. Work on the dark theme (in our new approach with black shades and accent colors, this was not accounted for). We need to check and ensure it looks good in both light and dark themes. DONE

    3. The publication section is almost ready; if any issues remain, they can be refined. Finalize the mobile versions of the filters. DONE

    4. Job Application Flow:

      1. Improve the mobile and iPad versions. DONE

      2. Add an option to apply without a specific job listing. DONE

    5. Homepage:

      1. Refine the dark theme. DONE

      2. Mobile and iPad versions. DONE

    6. General Tasks:

      1. Add animations where needed. DONE

      2. Implement micro-animations or element interactions (element states, page loading states: spinners or skeleton screens). IN PROGRESS

  • Story 3.6.7. RJ. About us. Our clients’ feedback

    Content

    General info

    The "Our Clients’ Feedback" section on the "About Us" page displays testimonials from clients who have had positive experiences with Rocken®. This section features a card-slider format that allows users to scroll through various feedback entries. Each testimonial includes the client’s name, title, and feedback about working with Rocken®. The section highlights Rocken’s ability to deliver innovative and efficient solutions that meet client needs, emphasizing its value as a trusted partner.

    This section reinforces Rocken’s credibility and builds trust by showcasing real experiences from satisfied clients.

    User story

    As a visitor to the "About Us" page
    I want to read feedback from Rocken’s clients
    So that I can understand how Rocken has successfully helped other companies and decide if Rocken is the right partner for me.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=54477-24170&t=oU8DZGxl3KlCWYRG-4

     

    #

    Acceptance Criteria

     

    01

    Scenario: Display of Clients’ Feedback Section
    Given the user navigates to the "About Us" page
    When the page loads
    Then the "Our Clients’ Feedback" section should be displayed with at least 4 client feedback cards, as shown in the provided mockup.

     

     

    02

    Scenario: Card Navigation
    Given the user is viewing the "Our Clients’ Feedback" section
    When the user clicks the left or right arrow
    Then the system should navigate to the previous or next feedback card.

     

     

    03

    Scenario: Feedback Display
    Given the user is viewing the "Our Clients’ Feedback" section
    When the card is displayed
    Then the feedback text should be shown along with the client’s name and title, as shown in the mockup (e.g., P. Dubois, Leiter IT Service und Support).

     

     

    04

    Scenario: Testimonials Scroll Behavior
    Given the user is viewing the "Our Clients’ Feedback" section
    When the page is loaded
    Then the cards should be displayed in a horizontally scrollable format that allows users to browse through the feedback without reloading the page.

     

    05

    Scenario: Fewer than 4 Feedback Entries
    Given there are fewer than 4 feedback entries
    When the section is displayed
    Then the feedback cards should be aligned to the left of the section for better visual presentation.

    06

    Scenario: Consistent Card Height for Feedback Text
    Given the user is viewing the "Our Clients’ Feedback" section
    When the feedback text in each card has different lengths
    Then all cards should maintain the same height, and if the text exceeds a certain limit, it should be truncated with three dots (…).