Career Opportunities
We're hiring! If you're passionate about hardware, and you're done and get things smart - let us know at jobs@upverter.com. For everyone else... I guess there are always photo sharing sites.
Cache Invalidation
This job isn't easy. You'll need every skill you have, plus more. We work reasonable hours, except when we don't want to, and then we work unreasonable hours. Our engineers release more code in an afternoon than full-time Googlers release in a whole quarter, and sure, their code works and ours doesn't, but we have PRIDE, dammit, PRIDE, and we'll fix the bugs tomorrow before anybody notices.
Here are some skills you should have:
- Experience coding with Python, Protocol buffers, ZMQ, Canvas, Google Closure compiler, Node.js
- Experience with version control systems like git
- Solid understanding of Unix / Linux or Mac OS
- Willingness to write tests
- Willingness to beat others into writing tests
- Great ability in written and spoken English
- Limitless self-motivation and creativity
Bonus points for:
- Javascript experience outside of jQuery or Prototype
- Experience with non-relational databases, tornado, Flask, and nginx
- Contributions to open-source projects
- Links to things you've built
- Ball hockey player (especially goalies)
Electric Unicorn
Seeking Frank E. Engineer. We're not sure that is your name, but we do know that you are an electrical engineer. You are extroverted. You are obviously very rare. And you, Frank, are special. You can probably explain what a power supply is. Maybe you've even designed one? You enjoy helping people, and you want to see hardware return to its former glory. Maybe you even want to grow a beard someday? But not yet. Oh no, first you have a world in need of change.
Here are some skills you should have:
- Experience designing electronics from concept through manufacturing
- Understanding of the basic circuit building blocks
- Experience with the tools of hardware engineering (scopes, soldering irons, programmers, etc)
- Experience with the software of hardware engineering (Eagle, OrCAD, DxDesigner, etc.)
- Experience with version control systems like git
- Solid understanding of Unix / Linux or Mac OS
- Great ability in written and spoken English
- Limitless self-motivation and creativity
Bonus points for:
- Coding experience (shell scripting, Python, Javascript, HTML, etc.)
- Understanding of rapid development techniques (agile, scrum, etc.)
- Contributions to open-source projects
- Links to things you've built
Decision Making Unit
When was the last time you ran a next-level biological experiment? Lunch? Yeah, us too. Are you ready to move out of the minors and into the big leagues? Good. Because we love growth. And if you know how to make things fester and rot (in a good way), we'd love to see you at work.
Here are some skills you should have:
- Ability to measure and respond to metrics
- Deep understanding of social networks and how to win
- Willingness to write tests
- Great ability in written and spoken English
- Limitless self-motivation and creativity
Bonus points for:
- Programming experience
- Content creation - anything from blogging to video
- Having King Kong super-sized social graphs
- PR, social media or press experience
Human-Based Coffee Retrieval Device
Oh hey there, engineering student in need of an internship. What's that? You're sick of working at Google and not actually really kinda-sorta doing anything? Yeah, we've been there too. Rather than tell you why to apply, we find it's better to tell you why NOT to apply.
So, here are some reason NOT to apply to our co-op jobs:
- You don't get excited about hard problems
- You can't write code in an interview
- You don't know what flextime means
- You can't talk about anything you've created
- You like to wear suits to interviews/work
- You think C is your favourite language but can't explain garbage collection
- You've never written a test suite
- You've never shipped code
- You're not creative
- You've never written a script to solve a problem
- You don't miss your computer when you're away from it
- You haven't pulled all nighters debugging something
- You like Windows
- You expect to have work-life balance
- You've never forked an open-source project
- You've never submitted a patch
- You like predictable schedules and routine tasks
- You've never compiled an operating system
- You don't know what prototypical inheritance is
- You've never ruined a sysadmin's day
- You've never shrugged and said, "Let's see what happens!"
- You don't play as hard as you work