Engineer ROI · Sep 7th 2018
Engineer ROI needs a mid to senior level full stack engineer to join its team. Are you the developer that we're looking for?
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.
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. See the "Your Income" section for more details.
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."
Lastly, we do 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 are not 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.
What problems will you solve?
Anything and everything related to MVC frameworks. Identify business problems, abstract them into models and serve the content through a browser.
Django 2.0 and related apps:
Django REST Framework
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.
You must be a Django all-star. Django is our MVC of choice and the technology that all developers in the organization share in common.
Nice to haves
You make money in the exact same way that the company does: billing for time. Paying a salary puts competing incentives between the developer and the company. Instead, we put your incentives directly in line with the company. So long as you work within our 25-35 hours per week guidelines, your income is directly tied to how much you work.