Tracxn Program Manager

Case Study
Design careers page form

1
(1/8) Problem Statement (by Tracxn)
WTR is a product company building HR management systems for
Media & Telecommunications industries.
The Product team at WTR corporation is planning to revamp the
careers page on the WTR website.
The plan is to allow applicants to sign up on the WTR's website with
their details and then allow them to apply for the jobs they are
interested in.

The user flow to reach the careers application page is given alongside:

Assumptions:
We will only allow 'Email ID' based logins. So:
Do not consider phone number based logins or ‘'Social logins' using
Google+, Facebook etc

You have to cover the following:

1.Wireframes, messaging & product specifications for:
a - the 'signup form'
b - the post submission 'success message' for the form
2.'Email format and content' used for verifying email address
● Cover all input fields necessary, all checks and validations for
the input fields defined.+
It is recommended that you follow the provided format for solving the case study. However, feel free to use a different 2
format if you want to.
(2/8) Setting Context
Context (what are we trying to do and why)

3
For sample context - please see slide 11
(3/8) User Stories
User Stories (define typical interactions that will later be solved in the requirement)

4
For sample user stories - please see slide 12
(4/8) Wireframes showing user flows (insert wireframe images - make multiple slides if required)

5
For sample wireframes for user flows - please see slide 13
(5/8) Wireframe details (Provide annotated wireframes and specs for engineering team - add more slides if needed)
Annotated wireframe (insert images of annotated wireframes) Specs for Engineer (use the annotations to describe the
functionality)

6
For a sample annotated wireframe - please see here
(6/8) Any Callouts (i.e. Assumptions made, Edge cases not handled)
●

7
(7/8) Please answer the following questions briefly:
Why are you looking for a job change? How does this role at Tracxn fit in?

8
(8/8) Please answer the following questions briefly:
What do you think are the pros and cons of joining a startup?

9
Appendix

10
A. Sample for Setting Context
Context (what are we trying to do and why)
● Users have requested for a “snooze” functionality in their inboxes
● User research has indicated that this is similar to “snoozing an alarm clock” - i.e. “Do not tell me about this
email till such and such time”
● The feature we plan to implement will be available at an “email level” as well as on multiple emails at once
(similar to the existing delete functionality)

11
B. Sample User Stories
User Stories (define typical interactions that will later be solved in the requirement)
● John is a busy executive at Abc Inc.
○ John receives a lot of emails every hour
○ He checks his emails once every 2 hrs
○ He reads the subject, and who sent the email, and then decides whether he wants to opens and read
the body of the email
○ Sometimes he can decide from the subject itself that he wants to:
■ Delete the email
■ Archive it
■ Or mark to read for later (i.e. snooze it)
○ At other times, he has to open the email to make the above decision
○ Also, he doesn’t want the “mark to read later” functionality to be very complicated - otherwise it will
add to his already busy schedule - it should be a simple 1-2 click operation, as far as possible

12
C. Sample for - Wireframes showing user flows (insert wireframe images - make multiple slides if required)

1. Existing screen for

1 starting reference - User has
opened an email

2 2. A new “snooze” icon is

introduced

3 3. User clicks on icon - a

menu opens with multiple
options

13
D. Sample for - Wireframe details (Provide annotated wireframes and specs for engineering team…)
Annotated wireframe (insert images of annotated wireframes) Specs for Engineer (use the annotations to describe the
functionality)
On “clicking” on the “Snooze icon” a dropdown menu opens with multiple options. See
annotated image for reference.
1. Title of the dropdown menu
“Snooze until…”

2. Default options
Each option has a “human readable” text and the exact
date-time value mentioned.
The text is left-aligned, and the date-time value is right-aligned.
The default options are:
a. Later today:
i. Before 12PM, it is 6PM the same day
ii. Between 12PM and 6PM, it is 10PM the same day
iii. After 6PM, this option does not show up
b. Tomorrow:
i. Always 8AM the next day
c. Later this week:
i. On Saturday to Thursday - show Friday 8AM
ii. On Fridays, do not show this option
d. This weekend:
i. On Monday to Friday - show Sun 8AM
ii. On Saturday & Sunday, show next week’s Sunday 8AM.
Option text changes to “Next weekend”
Note: The sample wireframes are provided as a guideline for e. Next week:
the case study you are supposed to solve. You are expected i. On all days, always Monday 8AM the next week
to annotate the wireframes and explain the complete user
journey. Please do not provide more than 2 wireframes per 3. Custom option
slide. Clicking on this will open a standard “Date-Time” selector (see next page)

14