Side job for software engineers
Do you want to engineer software as a side job alongside your university studies? We have space for talent in our nest! Start your side job with Easy LMS!
What are you going to do?
You will participate as a regular team member
A side job means that you are available to join one of our problem-solving teams for twelve hours a week. A problem-solving team is a mix of back-end software engineers, front-end designers, and implementation consultants. They work closely together to build valuable features for our clients. You will participate as a regular team member. This means you will:
- Join feature planning meetings where you discuss how to solve problems from an end-user perspective.
- Write feature solution proposals for the product owner. We work in short cycles of two or four days.
- Implement the solution with modern techniques.
- Code review your team’s work and process their feedback on your work.
- Test whether the feature meets our quality standards before deploying with your team.
- Optimize our workflow, product architecture, and code quality.
Together we will make sure the side job fits your study schedule; we are flexible!
Mainly, you’ll be learning through doing since we believe your learning curve will be steeper than just watching from the sidelines! Making mistakes is okay, because this is when you learn the most.
Is a side job an option for me?
You are a match if you:
- Love software engineering.
- Are available for at least 12 hours a week.
- Want to work at an experienced, dynamic company.
- Want to get a feel for working in the real world at a software company.
- Want to join us on our mission to make effective learning available for as many employees around the world as possible.
We don’t require a special college degree or affinity with particular frameworks or software programs. The most important thing is that you already have some experience with developing software and are eager to learn. For example, you develop in your spare time, or for projects during your study. We expect you to have entry-level programming skills, so you can easily keep up.
We expect you to have entry-level programming skills
The day of a software engineer in a nutshell
Let's assume you will be working from home.
9:00 First, a cup of coffee and time to read up on the important communication from the last week. A lot happened! You also dive into the subtask you started last week.
9.15 You prepare for the stand-up with your problem-solving team.
9.30 Stand-up time on a video call! You tell the team about your progress and ask a senior software engineer to help with writing acceptance tests for your subtask.
10.00 You complete your subtask with the help of a senior colleague. Your subtask is part of the story to make the delete account feature fully self-service. You commit your work and request a code review.
11.00 It's time to pair program. You want to learn more about Node.js, so our senior developer decides to develop the next subtask of the story with you.
12.00 A colleague peer-reviewed the code of your first subtask. You walk through the comments together. Your colleague shows you a more sustainable way to solve the technical problem.
12.30 Lunchtime! You combine your lunch with watching a new episode of Stranger Things.
13.00 You start refactoring your code. You mastered a new approach, profit! You push your subtask to Git and all tests pass. Nice!
13.30 Time to do the manual QA for the story with your problem-solving team. You discover one bug and solve it together with your teammates!
14.30 The self-service story is done! Everything works as expected, so it's time to deploy. Within 10-15 minutes, all clients worldwide will be using the new feature!
15.00 Time to unwind! You go for a walk to the supermarket to pick up some vegetables for tonight's meal.
15.15 You jump on a video call with the team leader to discuss what your next story will be. Your study schedule is very unpredictable next week, so you decide to pick a story you can do independently.
15.45 You write a proposed solution and get approval from the product owner immediately! You can write the acceptance criteria in user story format and create subtasks.
16.30 Another developer asks you to review his code. It is always interesting to see how others solve things! You leave some remarks and questions to understand what the other software engineer tried to do.
17.30 You make notes so you can continue easily next week. You give your problem-solving team a final update about your story and next week's schedule. Bye, until next week!
What do we offer?
We learn from our mistakes and work in a way that prioritizes learning over results
- Focus on personal growth and development. We learn from our mistakes and work in a way that prioritizes learning over results.
- An open and diverse team of young and experienced colleagues.
- A calm company that cares about its employees, physically and mentally. For instance, we offer monthly chair massages, healthy lunches, and a very green office. On top of that: we don’t do overtime.
- An agile environment with a lot of freedom, responsibility, and flexibility to shape your working life to your personal life.
- We alternate normal working weeks with play weeks where we step away from our daily work and dedicate time to side projects and experimenting with (new) technical stuff.
- We provide you with all the hardware you need to do your job, such as a standing desk, multiple screens, monitor glasses, and so on.
- We celebrate success and alternate smart and focused work with relaxing moments, like barbecuing, and Friday afternoon drinks!
- An attractive salary and secondary benefits.
Are you keen to work with us? Please explain your motivation in an email and send it with your resume to email@example.com. Do you have questions about this side job? You can contact Caroline Heijkoop on +31 683712762.