3-month internship
The role:
You will work together with Greg, our CEO and Product Development Team to ensure an effective product development process. You will be responsible for supporting and administering developers’ and product development meetings, preparing outputs and visualizing the given data. You will manage requests for product changes and track the progress of current tasks and features. There will be a lot of cross-functional work to make sure all the updates drift smoothly between our Dev and Sales teams. You will act as a link connecting the engineering and the business worlds.
You:
* want to learn how different teams work together to develop a great worldwide known product,
* have experience with issue tracking systems (e.g. Trac, Jira, Bugzilla, FogBugz),
* feel comfortable working with Google Docs,
* have impeccable English skills,
* like a geeky culture and are able to communicate with both geeks and non-geeks, * thrive in a start-up environment,
* have an interest in building products.,
Benefits:
* relocation assistance,
* books and mentors to help you grow,
* fun and challenging working environment.
Warsaw and our office
Warsaw University’s Institute of Informatics (MIMUW) is a top-notch CS faculty worldwide. It hosted ACM-ICPC 2012 and is alma mater to world champions in programming and a third of our team. The city of Warsaw is a booming cosmopolitan wannabe with a cool startup scene. We work hard, get challenged every day and learn a great deal. We go out to cool places, eat well and have lots of fun together. We often have guests and people in co-working, so there are extra brains and inspiration to grab. One floor below our office, a yoga school emanates peace and energy. The latter is harvested by mysterious installations at Warsaw Hackerspace, which occupies a dungeon in the basement.
Convince us with:
* a 1-page CV
* a completed task in Google Spreadsheet (this will be your cover letter): given list of: ticket id, developer, start date, end date; find out:
-
for each developer, the average time developer spent between starting and finishing working on a ticket (excluding Sautrdays and Sundays),
-
the average number of man-days spent on a ticket (assuming developers were not working on Saturdays and Sundays),
-
on which day of week (Monday, Tuesday, ….) developers finish working on tickets most frequently?
The needed data and instructions can be found here
Apply here: https://codility.com/jobs/?gh_jid=18393