Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe proposal for Data engineer onsite challenge #39

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

HzJavier
Copy link
Contributor

@HzJavier HzJavier commented Jul 27, 2016

This is a proposal for the Data engineer onsite challenge. In the design was involved @go-diego-go, @vidalon, @jivux and me.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.

**Hard**
- What are the main influences on job satisfaction?
- Where should I create my new iOS team based on my current perks and needs?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are the current perks and needs I would ask. Or is the intention for the candidate to ask this question?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We would be providing that list of perks and needs

@julianlimon
Copy link
Contributor

I wonder if we could ask additional questions about creating a data model (maybe as a bonus). Something like "what additional information would you capture to correlate this with employee performance or company value". This is of course a silly example but the point is to get them to think about data capture and data models.

**Hard**
- What are the main influences on job satisfaction?
- Where should I create my new iOS team based on my current perks and needs?
- Given a set of users and a set of companies, find the correct match for each user, based on its characteristics and the ones of the company.
Copy link

@oryws oryws Jul 27, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will the company characteristics be provided by us?

@bobmazanec
Copy link
Contributor

Great concept and choice of datasets!

I expect tool/database choice will be very important — Numbers and my MacBook are really struggling! :-)

Good 'detail' questions & comments so far; no matter how many we think & talk through in advance, I look forward to seeing how it "evolves" based on actual experience with candidate(s)!

@bobmazanec
Copy link
Contributor

  • For discoverability, etc., please link to this directory and/or file in 'ancestor' READMEs

Sorry, something went wrong.

@bobmazanec
Copy link
Contributor

How well did this work for the on-site?

  • is it worth keeping (perhaps with tweaks/changes)?
  • give up on it and try something else?

@vidalon
Copy link
Contributor

vidalon commented Aug 2, 2016

I think that it went pretty well. The only thing I would add is to let candidates know that they will need to have a database installed and a development environment to manipulate data so that they can go farther in the exercise.

The candidate that did this and to whom we extended an offer said that he had been in several interview processes and that ours was the best!! 😉 😉

@HzJavier
Copy link
Contributor Author

HzJavier commented Aug 2, 2016

Sorry guys, I've been busy lately. I will improve based on your suggestions. But yeah, the candidate really liked the challenged and felt engaged with it.

My only comment would be that the easy questions seemed to be very easy. Maybe we should start from the medium ones, since the candidate quickly went to get those easy wins, and did, but that took him some time that could have invested in the medium or hard ones, and show more of his expertise.

@go-diego-go
Copy link

I totally agree with @HzJavier
Even though he really liked the challenge I think his time could be better spent on more interesting questions like the ones on the medium and hard categories

@zxul767
Copy link
Contributor

zxul767 commented Nov 6, 2016

@orojuan @AnaCostillaG @magania Now that the data team is taking over this process, we should review this document and revamp it with what we've discussed internally. We can open a new branch to document what we discussed last week so it's also visible to everyone else in case they want to provide feedback and contribute in any way.

Copy link
Contributor

@bobmazanec bobmazanec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For discoverability, etc., please link to this directory and/or file in 'ancestor' READMEs

@bobmazanec
Copy link
Contributor

@zxul767 Worth closing this PR pending the review suggested above (#39 (comment))?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants