Geometry Expert
Medior .NET Developer · Salaried Employment
Location: RemoteAt Vlieg Engineering, we work on our platform called Rodly. Rodly automates the engineering and production of reinforcement for precast elements and has the ambition to globally revolutionize construction. We do this with algorithms rooted in linear algebra.
This position has been filled. However, we are always looking for talent and warmly welcome your application.
At a glance
Job requirements
What we expect from you
Minimum technical knowledge
| C# | Minimum 2 years of experience |
Other non-technical requirements
Rodly's architecture is very well constructed, but it can also be very overwhelming to work in when you're just starting out. A change in a specific domain often impacts the overall output of the complete algorithms.
In the initial phase, it is therefore necessary that you are able to absorb a vast amount of information, stay unoverwhelmed, and compartmentalize information effectively. We will help you with this!
Nice to haves
Knowledge of Linux, because we host all our applications on our own server and occasionally need to configure things here.
Knowledge of C++ and/or CUDA, because there are algorithms we would like to optimize in the future.
Why are we hiring someone?
The hardest phase is behind us: the phase where everything was conceived from scratch and the phase where we had to demonstrate our capabilities to the market. The team is growing, the customer base is growing, and there is simply a lot of work waiting for you.
Common reasons for rejection
Insufficient mathematical intuition. For example, you should be able to internally visualize cross products and dot products effortlessly.
Responsibilities
What you will be doing
Tasks
We essentially have two types of assignments: clear ones and ambiguous ones.
Clear assignment
A clear assignment could be: "There is an error message for this wall, solve it." You receive the context of the situation (often as input JSON), find out where the error occurs, and determine where you are in the process (since the Rodly algorithm consists of several concrete steps). You process this information and formulate a plan. Sometimes the current algorithm isn't intelligent enough for this new situation, in which case you get the freedom to rewrite a section completely from scratch. However, it also frequently happens that you need to add an interpretation of this new situation to the existing algorithm to achieve a good result.
Ambiguous assignment
An ambiguous assignment could be: "Integrate calculation software X with Rodly." It is then your responsibility to dive into the documentation and figure out what is and isn't possible. Once you've done this, you present a plan and consult with development partners about their requirements. You gather this information, create a plan, and subsequently build a proof of concept. If successful, you write your final implementation and ensure you add sufficient unit tests to secure all your logic.
Biggest challenge
Your biggest challenge is staying conscious of the decisions you make, because a change in your specific area always impacts the overall outcome. Sometimes a problem appears to occur at a relatively high level, but is actually the result of a bug in a lower-level algorithm. Developing this awareness takes time, but is crucial.
The Stack
What you will work with
Stack & tooling
How we apply the stack
We work in Azure DevOps and maintain multiple projects. Each project has its own scope (e.g., shared front-end code or mathematical algorithms). Every project has various repositories, keeping each repository highly specific. There are several 'parent' repositories, such as REST API projects, Windows Clients (WPF Blazor), and dashboards (Blazor). We only write code once. Everything is placed in the right location and reused.
Everything is C#. A small portion is written in .NET Framework for compatibility with legacy software, but the majority is written in modern .NET Core. We self-host all software on our own Linux server.
Development Lifecycle
How we work
- How long before a feature is live in production?
- The day you finish it
- How do you deploy releases to end users?
- With the click of a button!
- Development methodology
- Agile.
- Urgent production bugs
- Approximately bi-weekly.
- Role of quality
- We have an extensive set of unit tests and safeguard every new scenario we encounter. Our CI/CD pipeline catches everything. We also expect you to add unit tests whenever you discover a new scenario.
- Collaboration with the product owner
- Most things are discussed informally and verbally, often daily.
- DevOps tooling
- Everything is on DevOps: the board, repositories, PRs, and pipelines.
- Work distribution
- Bug fixes (15%), greenfield/new features (60%), tackling technical debt (25%).
Benefits & Terms
What we offer
- Remote work policy
- We don't have an office. Everyone works from home. We do try to see each other frequently—for example, grabbing a bite to eat and having a fun time together!
- Secondary benefits
- 8% holiday allowance, 160 vacation hours per year on top of standard public holidays, and a gross pension allowance of 7% of your gross monthly salary.
- Training & courses
- I believe you'll learn more within the team than from a course.
- Growth paths
- There is no predefined growth plan, but initiative and entrepreneurship are highly valued. When you put your best foot forward, we notice, and the sky is the limit.
About the Organization
Who we are
What we do
Vlieg Engineering focuses on developing advanced mathematical algorithms to automate engineering processes. Active in the construction sector, our Rodly platform generates reinforcement for precast elements. We approach this generically, treating every element (beams, walls, floors) uniformly.
The core formula is simple: geometry + specification = reinforcement. In practice, this is highly nuanced, so we rely heavily on mathematics to get it right!
The team
Currently, we are a team of four: myself as founder (I'm also a .NET developer, among other roles), one executive assistant, and two highly skilled .NET Developers!
Atmosphere
The atmosphere is optimistic. I'm a goofball and often busy behind the scenes. I frequently call the team at random moments to share exciting updates, and I often pitch spontaneous algorithm ideas on evenings or weekends when I'm too excited to wait until Monday morning. You're welcome to do the same, though it's never expected.
Social activities
I divide my time between the Netherlands and Sweden. When traveling across the Netherlands, chances are high I'll be passing near your location. Whenever possible, I like to drop by and treat to lunch.
Why developers stay?
Freedom and trust. This includes both the flexibility to manage your own schedule and the intellectual freedom to design and write the algorithms you deem best.
Long-term vision
Before the end of the year, I want to have three top developers on the team while I shift focus toward business growth alongside my executive assistant. This year, we are building the core team that you can be a part of.
Next year, we plan to scale exponentially, establishing Rodly as the national standard for data-driven engineering and precast element production. From there, we target Europe and then global expansion.
Our ambitions are high. As a key member of this core team, the knowledge you gain will position you to step into higher leadership roles as the company grows.
About the Team
Your place on the team
Are your own ideas welcome?
100%. Frameworks exist, but once you understand the canvas, you are empowered to execute solutions your way. I believe people perform best when trusted and uninhibited by micromanagement. We encourage this daily.
Is innovation embraced?
100%. We aim for optimal performance. If existing algorithms hit a ceiling and new techniques you bring forward elevate our system, you will have full autonomy to implement them.
Staying up-to-date
You will be joining one of the most innovative engineering teams in the Netherlands—there's no better place to learn.
Experience level in the team
Two seniors and one medior developer.
Application
Ready for the next step?
Complete the intake form. It contains key questions we will review during your initial interview.
If aligned, you will receive a complex assessment to complete independently without AI tools to evaluate your mathematical intuition. You will have 2 hours for this assignment.
After submission, we will schedule a call (usually within a few days) to discuss technical details, your insights, and your code implementation (AI reliance will be obvious during technical discussion).
Following this discussion, we will promptly share our decision. If selected, we will configure your equipment so you can start. Within your first month, I'll visit to grab dinner locally to get acquainted. We continue meeting periodically in person (e.g., quarterly).
Vragen geïnspireerd door werkenmet.net