https://github.com/cubonetwork/fullstack-challenge

Challenge to work as software engineer at Cubo
https://github.com/cubonetwork/fullstack-challenge

Last synced: about 2 months ago
JSON representation

Challenge to work as software engineer at Cubo

• Host: GitHub
• URL: https://github.com/cubonetwork/fullstack-challenge
• Owner: cubonetwork
• License: mit
• Created: 2017-06-05T22:01:11.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2023-03-02T20:59:32.000Z (almost 2 years ago)
• Last Synced: 2023-11-07T18:15:38.609Z (about 1 year ago)
• Homepage: https://cubo.network/
• Size: 1.87 MB
• Stars: 170
• Watchers: 16
• Forks: 54
• Open Issues: 1
• Metadata Files:
  • Readme: readme.md
  • License: LICENSE

Awesome Lists containing this project

README

        


  



# { "developer": "fullstack" }

The objective of this challenge is to evaluate your domain in fullstack development: its organization, style and good practices with code, APIs creation, frameworks knowledge and technologies.

## Rules

1. Your code should be made available in a public or private repository, on your personal github or bitbucket;

2. Send the link to [email protected];

3. We use Angular and Node.js with Serverless, but you can feel free to choose other technologies;

## Challenge

### Front-end

The following layout should be developed

![layout](layout-onepage.png)

[You can download the PSD here](layout-onepage.psd)

- You can use the libs and frameworks that make you more comfortable;

- All fields are required in the form;

- We'll be happy if you develop tests for it;

### Back-end

The layout has a form, a table with percentage information of participation and a pizza graph that represents this distribution.

- You need to create APIs that sends and receives these informations;

- We'll be happy if you develop tests for it;

- In case of inconsistency, return the error in a structured JSON with HTTP 400 code;

#### Plus

Feel free to make improviments like new funcionalities, visual optimizations, API security, etc. 😉

## Questions?

Send your questions directly to [email protected] or opening a issue.