Come Build The Web With Us!
We are looking for a few good engineers to help build a better web, and to maybe crack open a few beers with us when we're done. Want to know more? Click a section!
Who you are
You may think we're hiring you for your skill-set, but we are actually hiring you for that big sexy brain. Cloudspace engineers are never done learning, and as one of them, you won't either. Our weekly training sessions will keep you sharp while our client demands will push you into new technologies. If you're eager to be taught, we are eager to teach.
Feel like you've got a really great handle on a specific technology? Great! Teach us all about it! Set up a training session with the managers and put your teachin' cap on. We want that knowledge in our brains and yours! Cloudspace's open office also adds to the knowledge sharing. It's not uncommon to hear someone shout from the corner "Hey, does anyone know of a good ordering gem that works with multiple scopes?", "Who is up for Taco Tuesdays?", or "Has anyone used update_all to cut down on the number of queries when updating many records with the same data?". Shout out the answer if you know it, perk your ears up if you don't.
An added bonus of our open office plan is the ability to blow off steam with your fellow engineers. What does that mean? Two words my friends, Nerf War. Does yelling "Batman could totally take Ironman in a fight!" while shooting neon green foam discs at your coworkers sound uninteresting to you? If so, this is probably not the office for a person of your discernible tastes.
What the job is
Our full-time engineers work directly with our clients in teams of two, building a variety of software for a wide range of startups and well established companies. Weekly conference calls and daily Skype conversations will keep you abreast of exactly what your client wants, while your partner will keep your code clean and your mind fresh. Strong communication skills are key to a successful relationship not only with your client, but with your team member. Full-time engineers primarily work in Ruby on Rails, but will dabble in Python, PHP, iOS and Android development.
Our part-time engineers mainly work with clients hosted on our custom content manager, Skywriter. You may be asked to add additional features to an already existing app, create demos for new technologies, or a variety of other software maintenance tasks. You will work closely with our Account Manager and the majority of the work will be completed in PHP.
Why you want to work here
Cloudspace is run by engineers, so you'll never be asked "Can you download the list of Facebook users?" -- we've all been there ourselves. As such, we have created a workspace optimized for engineers. Here are a few of our super sweet perks:
- Full-time engineers are given a quad-core MacBook Pro to work from (Actually, we work from virtual machines running Ubuntu to match the staging and production environments...but we run those virtual machines on MacBook Pros)
- Cubicle free environment! Great for Chatty Cathies
- Private offices! Great for Silent Sallies
- 18 vacation/sick days a year (earned on a month to month basis the first year)
- Stock options after 5 years
- Health, Vision and Dental coverage
- Breakfast every Friday morning
- Random lunches on us
- Whiskey Wednesdays
- Beer 'o' Clock on Fridays
- Quarterly Day Trips! Laser Tag, Bowling and Batman movies have dominated in the past. Care to suggest something new?
Ready to apply? Take our simple coding test, and send the completed code (and your resume) to us. If we like it, we'll invite you in for an interview to make sure we're a good fit for each other.
Languages Accepted: Ruby, Python and PHP
Parsing an Email
What do we mean by parse an email? Go to Gmail, open an incoming email, and do View Original. You should see a text file of a raw email. The goal here is to parse that and extract relevant fields.
This is actually a very difficult thing and a proper implementation could take months. However, it's possible to do the basics, without handling all of the intricacies, in maybe an hour.
- Take in an email and parse it into relevant fields. Figure out what those relevant fields are.
- Create a good foundation. Try to write extensible/maintainable code.
- When you're done, list out next steps you'd take in your implementation. Eg, 'I'd focus on handling different MIME types in the body', etc.
- Don't use a library like TMail that does parsing for you, but feel free to use any non- email-specific libraries you want to.
A few notes about your goals:
- The directions are purposefully vague. Make decisions on what you think is best for the goal you're trying to accomplish. Feel free to tell us why you made certain decisions in your summary.
- Use the RFC Email Specs as a starting point to help you parse the email.
- Google is your friend!