At Cohort Go, we’re solving a broad range of problems across the international education sector. At our core, we’re automating the manual and inefficient, improving productivity, reducing costs and increasing choice. To do this, we’re building our own modern web-based platform while integrating with banks, insurers and telco’s, just to name a few.
This video shows more about what we do at Cohort Go: https://vimeo.com/240610198
The engineering team is a core component of our organisation as everything we do is powered by our technology. Our team is in a growth phase and we're looking for developers who thrive in a rapid-paced environment with a passion for problem-solving.
Key to a healthy engineering team is experienced talent who knows how to guide the product forward. You enjoy taking a problem right from the whisper of an idea through to the detailed implementation. You understand that you’ll need to open important discussions throughout the organisation to get the right information. But you also know that sometimes you just need to take a punt, build a prototype, and get the feedback from the real world.
Technology and Tools
At Cohort Go we focus on automation, simplicity, and fast product turnaround and we pick our technology stack and tools to match.
Our applications all use:
- Ruby on Rails
- Heroku on AWS
Experience with these specific technologies would be great but is not expected. We figure that passionate engineers with similar skills will pick up new tech without much trouble.
As we onboard more customers and explore more product areas, the team is only going to get more interesting.
A day in your life at Cohort Go
You start the day getting in sync with the team during our 5-minute standup. Next, you move on to working on the next ticket that you’ve picked from this sprint’s backlog; time to improve the way that our matching engine detects relevant payments for transactions that we’ve received into our bank account.
By lunchtime, things are looking good, so you open a pull request. After CI gives the code a thorough battering and gives you a green light, you put the code out for review and engage in a discussion on the PR around the best way to structure the tests to cleanly validate and explain the functionality. After another push or two, you’ve agreed on a solution and your reviewer has approved and merged.
Twenty minutes later, the change is live in production, and it’s time to select your next win…