As a software engineer at Floorganise, you are proactively involved in the development of our Shipyard-MES web tool Floor2Plan. Translating customer-specific requests and roadmap items into our architecture and engineering new concepts and methods.
The challenge for our development teams in both NL and Spain is continuously aimed at translating shipyard complexity into simplicity in use and sleek design and UX? Are you a .NET engineer with good ideas, clear insights and a curiosity to keep developing?
Then please apply with Floorganise and join our international team!
Join us in Las Palmas de Gran Canaria as:
.Net software engineer
The sea plays an enormous role in the major challenges of our time; wind energy at sea, deep sea mining, maritime safety or reducing our carbon foot print.
The maritime industry provides answers and solutions for these challenges. But who develops affordability and efficient cross supply chain cooperation to deliver on time? Floorganise is full on engaged to impact this future. Join us in this quest with your programming skills in either Zwolle (NL) or our new office in Las Palmas de Gran Canaria (ES).
Floorganise. Triggering smart Shipbuilding
About the role
.NET Software engineer
Come on board with Floorganise
But why?
Because with Floorganise you are joining a winning team that changes the future of shipbuilding. You will be part of an international team of developers based in the Netherlands and Spain that works for shipyards in three continents, where your personal contribution is valued and seen. Every developer is basically full stack but there is ample opportunity to develop your own preferences and expertise.
PS: Did you know that the average age at Floorganise is 33 years old?
What makes up for my working day?
You are in the lead
Product development at Floorganise has different starting points. Good ideas from across the team, a product owners roadmap and requests from our customers. Depending on priority and planning, you pick up a topic. It's up to you determine the sequence, technical setup and setup of your code.
Obviously you are not working solo as cooperation and communication is an important part of being efficient but the essence is that you are in charge of your own work.
Am I working solely?
Not at all.
Collaboration and cooperation is instrumental at Floorganise. We work from a scrum methodology and therefore there's a day start, retrospective and all those other ingredients that belong to an agile approach. You are not working solo but there is however a lot of opportunity to use your own input, ideas and solutions.
Because we are a compact and young company you are being heard. Your contribution is visible and greatly valued. We are ambitious all together so if you want to learn or need something to do your job better (training, hardware, latest IT tools) then that is all sorted quickly.
More about our stack
A Q&A
1. Which stack and tooling techniques are used ?
1.C# 2.MS SQL 3.ASP.ET 4.NET Core 5.SharePoint 6.Azure 7.AngularReact 8.jQuery 9.Jira 10.Teamcity 11.Visual Studio 12.Visual Studio Code 13.BitBucket
_____
2. How is this stack applied?
We use C# in the backend. We use Angular for the frontend. Both the back and frontend are built with different design patterns, where we consider which patterns are best suited for the solution.
3. What should someone do and what will the tasks be?
- Participate in the development team.
- Further development of existing modules.
- Develop new modules.
_____
4. What is the biggest challenge for a developer in his work?
Complex relationship between functionality, performance and speed of realizing new features. Being able to make a difference within the application. Everywhere in the application there are features that make the difference for our end users. By the way, this is a very nice and grateful group that consists of shipbuilding developers, welders and ironworkers, for example. This group has often had to deal with disappointment when it comes to automation. We care about this by wanting to make a difference for them with our team.
_____
5. What does your software development lifecycle look like? How long does it take on average for a new feature to be put into production?
4 quarterly releases, a feature/module is often developed within a quarterly release. Small features sometimes go to our customers' live production environment within a week.
_____
6. How do you bring new releases to your end users, is that fully automated?
Via TeamCity we can release to customer environments at any time. Dev/test is usually released automatically, staging/production manually.
_____
7. Which development methodology do you use?
Scrum / Kanban / Test-driven.
_____
8. What role does quality play within your team and how does this show?
We define in advance the objectives that we want to achieve with a feature. If necessary, a screen study is done to ensure that the UX is as good as possible. Through code review, unit test, the application is kept at a high level in the team during development. In this phase, the quality is not only about as few bugs as possible, but also the right choices performance wise (application performance). The unit test is performed automatically at check-in. With each quarterly release, an extensive test is performed that runs through the entire application to address any regression not recognized by the unit tests. Tickets are registered in Jira. We have the Jira service desk module for customers. Code base on bitbucket, build server / deployment via teamcity to azure.
_____
9. How is the collaboration with the product owner? And is there a clear plan of what needs to be made and when? And with what frequency do changes generally take place?
Every month we look ahead at which features/modules will be developed in the near future. This is with a horizon of two quarters ahead. The dynamics of our customers mean that the quarter ahead is often well established, but the following quarter is no longer fixed.
10. What does your IT infrastructure look like?
- Local development laptops, Visual studio as IDE.
- Office 365 / Sharepoint as workplace automation
- Bitbucket as codebase, teamcity as build server/deployment to Azure
_____
11. What is (approximately) the division between bug fixing, new construction/new features, and elimination of technical debt?
- Bug fix 20%
- New construction/new features 50%
- Eliminate technical debt? 30%
In summary
About you:
- You are ambitious and want to develop your knowledge and skills
- You have a EU passport (from a NATO country)
- You are proficient in English
- You communicate clearly
- You like to work independently in a solid team
- You posses a bachelor or master level university degree or equivalent
- Experience with C#, ASP.NET, .Net.Core, MVC, HTML, CSS and Angular
Our offer:
- An inspiring job full of challenges and development potential
- Working with colleagues from the Floorganise Las Palmas Office in conjunction with our Dutch team
- Challenging assignments for shipyards across three continents
- Experienced and expert colleagues in a personal, stable and trusted team
- A pleasant workplace, working with the latest tools
- You can work part-time with us and you will receive a competitive salary
- There is a lot of support for personal development.
Interested?
Apply here!
We would like to get to know you and see if there is a match. Of course we are also curious about your work and would therefore like to see something of your code. For example, something you have made that you are proud of. We find that much more telling than just your CV.
Call Ronald on +31613324100 or email ronald@floorganise.com. He is available all day and evening.