grayfox
Joined 12 years ago
Karma
384
Submissions
89
Member since
Oct 25
Recent submissions
Comment · 10 years ago
Comment · 10 years ago
Neat stuff.
Hopefully they can get neat API integrations going to tie into all the machine learning being applied to shop/chat interfaces.
Comment · 10 years ago
Our Support Engineers and Technical Content Creators do real intensive technical work.
The role is not important at Compose. The system is built to best groom out 'core competencies'. A Support Engineer is a strong Ops/Systems Administrator with great communication and customer skills. A Technical Content Creator is a strong developer with excellent written communication skill.
Our Analytics is maintained, built, and improved by a 'Content Creator'. Our hiring, too, is ran by a 'Content Creator'. Similar folk contribute across the app, and apply skills in various areas.
It is a mature way to work. To get the best people, you need to offer competitive wages.
Comment · 10 years ago
Oof, bummer. Your experience is slower than average. We ran into a grading crunch when we launched our Enterprise product. When you submit your work to us, your submission is anonymous. Three engineers grade each submission.
Platform Engineers will experience the greatest wait periods. The other roles tend to be quicker.
Expected time-frame:
* Proceed from application to work sample: 24 hours.
* Complete work sample: Up to the candidate. We build them to take 2-6 hours.
* Grade work sample: 1-4 weeks.
* Schedule work day: 1 week.
* Receive decision: 2-5 days.
Thanks for taking our time to try the process out, it is appreciated. The method is constantly under improvement.
Comment · 10 years ago
EQ has proven to be of vital importance in growing healthy teams. There was that Google study: http://www.inc.com/robin-camarote/google-study-reveals-emoti...
The work-day would be where we assess EQ. It is difficult to stay objective and consistent when assessing soft-skills. It provides the risk that biases and could-be-wrong impressions dictate your hiring decisions.
Two things, in my eyes, have helped us find bright and 'good' people:
First, by using consistent criteria that are as specific (binary) as possible, we have been able to find people who are not just talented, but conscientious contributors.
Secondly, the way we write/pitch/communicate during the process sets the tone for both the people we want and the environment we want to create. If you go through an uncomfortable, even aggressive, hiring process, what would you expect from the environment and the people within that environment? We try for good-ness from word one.
Comment · 10 years ago
Ah! Out of space in the main post. We are only able to hire those that can legally work within Canada, the US, or the UK.
Once hired, fully remote from anywhere.
Comment · 10 years ago
Compose | Remote (Canada, US, UK)
What: Databases-as-a-service. We offer production grade, auto-scaling, automatically backed-up, add-on compatible MongoDB, PostgreSQL, Redis, and more.
$: All roles start at 100k and scale up based on experience. MacBook Pro, pension match, health.
Hiring Process: Blind hiring! First, a light application. Second, all candidates who complete the application receive a work-sample resembling the work one would do in the role. No deadline. Final step is a paid work day ($500).
Compose has grown into a vibrant group where folks can feel comfortable being themselves, living a balanced life. We welcome you to enjoy comfort when taking risks, collaborate with spirited peers, and to unleash your creative and talented personality.
* Work from anywhere!
* Many neat conundrums to solve.
* Self-managing, distributed decision making. Choose your projects. We're deadline averse and quality focused.
* Hardly any meetings.
* Ruby/Go.
* Fizz: https://www.compose.io/articles/the-tool-we-built-to-help-us...
Roles:
* Platform Engineer / Application Developer
* Support Engineer
* Technical Content Creator ('Developer Advocacy' type of role)
To begin: https://compose.interviewed.com
Comment · 10 years ago
That image from Julia Claven is excellent.
That is brutal, for conjecture.
A fledgling open-source DB winding up on an as-a-service provider can provide mutual benefit; the database gets users running their product on a stable, consistent platform and the provider can profit from the margins on the value-added deployments they provision.
Hardly 'a vulture feasting on the carcass of its own mother'...