Engineer ROI · Sep 7th 2018
Why you should work for Engineer ROI
Frequent Rotation Across Projects - If you find yourself thinking "I wish I could switch projects every 3-6 months" or "I enjoy learning new APIs", you're the right type of personality for our team.
The company specializes in custom software development. Essentially, we are a plug and play solution for mid-size businesses that require a talented team of developers. Any business in the world can benefit from software, which ensures your exposure to a wide range of industries and requirements as new projects come in. The common thread in all that variety is that our projects relate to MVC frameworks.
This is a full time position paid on an hourly basis ($30 per hour for 7+ years of experience, $25 per hour for less). Said in another way, you have more control over your income.
Earning money based on hourly pay means that you earn money in the exact same way that the company does: billing for time. Paying a salary would put competing incentives between the developer and the company. Instead, we tie your incentives directly in line with the company. So long as you work within our 25-35 hours per week guidelines, your income is 100% tied to how much you work.
Do you do an amazing job meeting customer expectations with a minimal number of bugs? That's called job security. Customers always have their favorite developers. Make a name for yourself with quality work.
Engineer ROI also believes that connecting income to time worked maximizes team quality. The kind of people that want to collect a salary and drag the team down are not attracted to the company. That means you will work with talented colleagues that are motivated to make you, the code and the entire team better.
Quality of Life - Your work week totals 25-35 hours with 30 being the ideal amount. You can work at any time of day so long as your work hours are consistent and evenly spaced across 4-6 days per week. One of our teammates works from 11 pm - 5 am in his local time zone because that's when he wants to work. The company cares more about you working when you're at your peak mental state rather than the time of day when you work.
Meetings are strictly limited to when they are necessary. Because your income is based on your time worked (which includes meetings), the company is incentivized to value and protect your work time.
An Engineer's Environment - Test driven development comes first. We do not build features until existing code passes all tests. You are assigned tasks with the repository, at which point you are expected to own the problem and fix it. Because we operate in a "no micromanaging" environment, we need a team player that sincerely cares about the impact his/her engineering decisions will have across the project.
Version control is paramount. Commits to a project are not meant to be a fancy save button. Commits tell the team, "I have tested this feature and it's production ready."
The team practices phased releases to minimize the risk of breaking production. Development turns into a commit, which is then passed to staging. Only if staging passes and operates normally do we merge a commit merge from staging to master and release it into production.
Nobody wants to get yanked out of bed to fix fires (we should not be like IT people on call!). Slow and steady keeps us looking sharp and polished to clients and keeps emergencies to a minimum. It's better for us and it's better for our customers' businesses.
Small Teams - The size of the company is 4 total. Your work is meaningful, appreciated and because of the small team size, you have the ability to significantly influence the architecture and frameworks used within a project.
Django 2.0 and related apps:
Django REST Framework
Laravel and PHP
You must have 2+ years of direct experience with Django. Django is our MVC of choice and the technology that all developers in the organization share in common. In order to be considered for our senior level pay rate of $30/hr, you need to make your case for why you deserve to be a senior level developer.
2+ years of experience using Git for version control.
Nice to haves
Day to Day
We intentionally avoid chatter apps like Slack or Skype. Most questions do not require an immediate reply, making threads within the repository's issue tracker our preferred method of communication. The biggest challenge for any developer is to minimize interruptions to help you spend most of your workday in the zone. Keeping chatter restricted to the issue tracking system keeps conversations organized and minimizes distractions. Genuine emergencies are handled over phone calls or What's App.
About 80%+ of your time is spent architecting or writing code. The remaining time is spent on team communication - reviewing proposed solutions from teammates, clarification on requirements, etc.
The types of projects and problems you encounter are everything related to MVC frameworks. Identify business problems, abstract them into models and serve the content through a browser.