Skip to content

Instantly share code, notes, and snippets.

@gwright
Last active September 22, 2020 20:53
Show Gist options
  • Save gwright/d4a73db35147e5de5553fea7fe03ab11 to your computer and use it in GitHub Desktop.
Save gwright/d4a73db35147e5de5553fea7fe03ab11 to your computer and use it in GitHub Desktop.

Full Stack Developers

We appreciate your interest in joining SeeClickFix's development team.

As an exercise to base our conversation moving forward, please complete and submit the following small app. Our tech stack is Rails and Ember, but you may implement this using any Ruby or Javscript framework (Rails, Sinatra, Node, etc.), as a Javascript single page app (Ember, Angular, React, ...), or some combination.

We are interested in your Ruby and/or Javascript skills, but if you think some other language or framework is a better demonstration of your skills, talk to us about your choices before investing your time on this excercise.

Description

The SeeClickFix engineering team would like to keep track of various events happening in its repos. The team has asked you to create an app which shows selected events types from the Github events api https://api.github.com/repos/:owner/:repo/events.

The application should allow the user to specify an owner, a repo, and an event type and then display matching events from the Github events API.

For each matching event, show the event type, actor information, and timestamp of the event. You may choose to show additional information specific to each event type to provide more details.

(1) The team is much more concerned about having a functional app than "look and feel" concerns, feel free to prioritize accordingly.

(2) For the purpose of this excercise you can assume that the repo access is public and you don't have to worry about authentication.

Please set aside two or three uninterrupted hours to focus on building the app, but do not spend too much more time than that. We're most interested in where you are going, not necessarily having a "finished" app.

Within the limited time, please give us a sense of how you organize code, use the language, understand the frameworks, design tests, and utilize git commits. We would like to see a commit history that shows how you would present code for review, so feel free to amend/rebase to curate the commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment