Tunnll

Smart transportation systems

Introductory task - Graphical UI/UX Designer

Introductory task - Graphical UI/UX Designer


Part One of the Introductory task.

A set of screens for a simple Android application.

Task description

Create a set of screens (or one screen if applicable) for placing an order (“new ride”) with an imaginary general purpose “MySmartaxi” taxi/ridesharing app. The screen(s) should support the use-case described below.

Prerequisites: The “MySmartaxi” app is installed on the user’s smartphone. The user has created an account in the app.

Use-case:

1
2
3
4
5
6
7
8
1. A user opens the "MySmartaxi" app on his/her smartphone.
2. The app shows the “New ride” screen to the user.
3. (optional) The app identifies the current user's location as his/her desired origin.
4. The user can specify his/her desired origin/destination:
• by typing in a [POI name](https://en.wikipedia.org/wiki/Point_of_interest).
• by typing in an address.
• by choosing from the recent origins/destinations.
• by choosing from favorite origins/destinations.

Requirements

  • The main requirement of this task is to design a non-interactive high-fidelity digital prototype for a mobile app user interface (Android OS - native application) for the provided main use-case.
  • The interface should comply with the Android Design Principles.
  • The interface should be implemented as a Material Design interface.
  • The interface language should be English.
  • Please, avoid using Lorem ipsum for any text in the design.

Deliverables

To show off the results of implementing this introductory task, please do the following:

  • Save the images of the interface along with any complementary materials (sketches, diagrams, etc.) to the cloud file storage.

Part Two of the Introductory task.

In case you are invited to complete Part Two of the Introductory task at our office, you will receive a detailed specification for the task on-site. As a clue, the task will be about job stories and task flow diagrams. The estimated time of completion of Part Two is 2-3 hours (on-site).

How this introductory task is organized

Introductory task structure

The introductory task consists of two parts:

  1. Part One. A simple task that can be completed remotely.
  2. Part Two. A more advanced task that you will be asked to complete in one of our offices.

If you complete the Part One successfully (deliverable quality and respect to deadlines), we will be glad to invite you to visit one of our offices and to complete Part Two on-site. In case of successfull completion of the Part Two, we will be glad to have an interview with you.

Deadlines and reporting

While completing Part One of the introductory task you are expected to meet the deadlines and to report your progress:

  • While implementing the introductory task you should send a simple 1-sentence daily report by email to introductory.tasks@tunnll.com: “Yesterday I implemented X and today I am working on Y.”.
  • Any applications with missed daily email reports will not be processed.
  • You have 3 business days to complete Part One of the introductory task after you send your first email report.

General rules

  1. The working and communication language of this introductory task is English (including the interview), if not specified otherwise.

  2. The internship process is very well documented. Please, make sure that you have read this document thoroughly (including all the links, footnotes and references) before sending any questions to introductory.tasks@tunnll.com.

  3. When we talk about deadlines, a “week” means a calendar week, i.e. 7 calendar days.

  4. Each task employs a set of custom-tailored reading sources that will help you to complete the task. If a reading source (article, book, link, blog post, etc.) contains some practical exercises, all of them should be completed and saved to your personal Dropbox folder (or Github account) before completing the actual task.

  5. Please, create an empty folder with any cloud storage (Google Drive, Dropbox, etc.) and an empty GitHub repository (for software engineers only).

  6. You should save all deliverables (files, documents, images, etc.) to your cloud file storage folder (or to Github in case of code).

  7. If you think you need help, do as follows:

  • Carefully re-read the task description, make sure you have understood the task correctly.
  • If the previous step does not help, copy the text you are not sure about (Error text for software engineers, definitions for all the others) and try to perform a problem research with Google/DuckDuckGo.
  • If the previous step does not help, create a detailed question in regards to your problem and post it on a respective site of the StackExchange network (some useful sites are Software Engineering, Graphic Design, UX, Startups (business-related), English Language and Usage and Writers among others). Your question should contain links to resources that you have found during your problem research.
  • If the previous step does not help, send your question to introductory.tasks@tunnll.com including the word “Question” in the subject. Your email should include a link to your question on the StackExchange network. Ambiguous questions like “It does not work” or “I do not know how to do that” will remain unanswered.

How to actually apply for this position

In order to apply for a position, please do the following:

  • Complete Part One of the introductory task.
  • Send an email to careers@tunnll.com:
    • Subject: Applying for (Position title) - (Your full name)
    • Body:
      • Full name.
      • Position title.
      • A link to access the cloud file storage folder (or Github repository for software engineers) that contains the deliverables for Part One of the completed introductory task.
      • How did you find about this position? Please, explain in 2-3 sentences.
      • Why do you want to work with us? Please, explain in 3-4 sentences.
    • Please, attach your CV in the PDF format.
We reserve the right to not respond to any applications that we receive.
ATTENTION! We do not accept applications for this position without a duly implemented introductory task. Please, do not waste anyone’s time by simply sending your CV to one of our emails - it will not be processed.