Konijn Jobs

Open role

Solutions Engineer

AWAREWAYS B.V.

IND sponsorUtrechtDutch: required

About the role

Other vacancies Solutions Engineer Root causes, fixes & integrations Location Utrecht (hybrid working possible) Employment type Full-time (32–40 hours) Team Technical Support & Solutions Overview Why does the same login problem turn up at three different clients in a single month? And what would you have to change in the code so that nobody ever has to look at it again? At Awareways, you’ll be one of two Solutions Engineers. You work closely with our Support Engineer and with the engineers who build Wave. We’re filling the second Solutions Engineer position because more clients means more support cases, and we’d rather remove the cause than keep answering the same question. Your mission in one sentence: reduce the amount of support Wave needs. A year from now, fewer cases reach our second and third line. The problems you’ve tackled stay solved, and you can show which recurring issues have disappeared and how much time that has freed up. And Client Support and Implementation have an easier time: getting a client onboarded takes less hassle, and so does keeping them happy when something goes wrong. About Awareways Awareways helps organizations handle information more securely. We combine cybersecurity, psychology, learning and creative communication. Our product, Wave, brings training, communication, simulations and measurement together in one place, connecting what people know with how they practice and how they actually behave. We don’t build bespoke solutions for individual clients. We build one product that keeps improving and works for more and more clients as it does. Staying close to our clients is essential to that: what we learn from clients and users, we turn into improvements that benefit everyone. This role is part of our Product division, within the Technical Support & Solutions team. You’ll work in Solve, our third line of support, which tackles the technical problems behind recurring issues. The first line, Implementation and Client Support, helps clients directly. Your direct teammates are the other Solutions Engineer and the Support Engineer, who handles escalated cases as the second line. You report to the Head of Product. You work most closely with the Support Engineer, who brings you the patterns in incoming cases, and with the Head of Technology, who reviews your solution proposals and has the final say on architecture. What will you be doing? Nearly all of your work starts with a problem a client has run into. You’ll write code, but to solve problems, not to build new features from the roadmap. Tracing recurring problems to their root. When the Support Engineer or the first line sees the same issue coming back, you find out why. You reproduce it, dig through logs and data, and follow it through the code until you can explain what’s really going on. Building structural fixes yourself. You write the fix in PHP and Symfony, with tests, and submit it as a merge request. The engineers in Build review it and ship it in a release. Afterwards, you check that the cases have actually stopped. Turning bigger problems into roadmap proposals. Some problems need more than a fix. You write a proposal covering the cause, the impact, the options and an estimate. Once the Head of Technology has reviewed it, the Product Delivery Engineer weighs it against everything else on the roadmap. Making integrations more reliable. Many cases start where Wave connects to client systems, such as single sign-on (SSO) and learning platforms linked via LTI. You find out where these connections break and make them more robust, so the Support Engineer has fewer complex set-ups to rescue. Preventing escalations with knowledge and tooling. Not every case needs a change to Wave. Sometimes the first line just needs a clear explanation, or a small tool to check a client’s configuration. You write and build these, so cases get resolved sooner. Showing where support time goes. You track which issues recur most often and how much time they cost, so the Head of Product and the Product Delivery Engineer can see where structural work pays off. What won’t you be directly responsible for? (though your input is always welcome) Handling individual client cases and complex set-ups. That’s the first line and the Support Engineer. You step in when a case points to a deeper problem, or needs extra technical knowledge. Deciding which solutions get built, and when. That’s the Product Delivery Engineer, with the Head of Product setting the product vision. You make the case with your proposal and your numbers. Wave’s architecture and technical standards. The Head of Technology has the final say. You flag when a structural fix calls for a bigger change. Building roadmap features and running releases. That’s Build. Larger solutions are built there, with you as the person who knows the problem best. A day as a Solutions Engineer At stand-up, the Support Engineer brings up three tickets from three different clients this week: employees who log in via SSO are ending up with a second account in Wave. You pick it up, and within an hour you’ve reproduced it in the test environment. The client’s identity provider sometimes sends email addresses with capital letters, and Wave treats them as new users. The fix itself is small. The tricky part is the accounts that already exist twice, some with training results on both, in data that clients report on. You head over to the Head of Technology, and together you agree on a plan: fix the login today, then merge the duplicates with a migration you test on a copy of the data first. At 12:30 you have lunch with colleagues from across the company. In the afternoon you write the fix and its tests, and open a merge request. The Domain Expert Back-end reviews it and asks for one more test case. Then comes the less glamorous part: the migration script, line by line, with a check on every merged account. You also write a short note for Client Support, so they can explain to clients what happened. By the end of the day, the Support Engineer has updated all three tickets with the expected release date. You add the issue to your overview of recurring problems. SSO is now in the top three, so you start drafting a proposal: Wave needs a better way to match users coming in from client systems. That one’s for tomorrow. Who are we looking for? You’re a developer who gets more satisfaction from cracking a hard problem than from building something new. You don’t mind reading other people’s code, and you want to understand why something broke before you fix it. What you bring: Getting to the root cause. You don’t stop at the symptom. You form a hypothesis, test it against logs, data and code, and only consider a problem solved when you can explain why it happened. Fixing it once. You build solutions that work for every client, not just the one who reported the problem. And you check afterwards that the problem really is gone. Translating between clients and code. You can turn a vague report (“it doesn’t work for some people”) into a problem you can reproduce. And you can explain a technical cause to non-technical colleagues in a way they can pass on to a client. Your communication skills are well developed. Writing proposals that make decisions easy. When a problem needs more than a fix, you write a proposal that sets out the cause, the impact, the options and what each one costs. That lets the Product Delivery Engineer and the Head of Technology decide without a long meeting. Helpful, but critical. You ask questions to understand the need behind a request or ticket. You set priorities, and you’re not afraid to say “no” or “not yet” and explain why. Throughout, you focus on what adds value for the most clients. Organized and careful. You plan your own work and stay on top of things when several people need you at once, such as an urgent escalation in the middle of a structural fix. You care about quality and privacy: Wave handles personal data belonging to our clients’ employees. Strong command of English. You communicate clearly in English with your teammates, both in conversation and in writing. Dutch is a plus. Required At least two years of professional development experience, with code running in production. You’ll be writing fixes yourself from day one. Hands-on experience with PHP and Symfony, since Wave’s back end is built on them. Experience with SQL and with debugging in production using logs, data and queries, because finding causes is at the heart of this role. Strong command of English, since our development team works in English. Nice to have Experience with integrations such as SSO (SAML or OpenID Connect), LTI or REST APIs. If you understand the concepts, you’ll learn our integrations here. Dutch, since most of our first-line colleagues and clients are Dutch-speaking. A background in support, operations or consultancy, or experience with event sourcing and CQRS. You don’t need a computer science degree, or any background in cybersecurity or security awareness. Why this role at Awareways? Because we build one product rather than custom work, a problem you solve this week disappears for every organization that uses Wave, and for every colleague who would otherwise have had to answer it again and again. You sit between our clients and our code. You see what goes wrong in practice, you fix it yourself, and your proposals help shape what we build next. Few roles give you such a complete view of Wave: the code, the data, the integrations and the people who use it. What we offer Room to grow. A role with real responsibility in a mission-driven organization, and room to develop both professionally and personally. Personal development. We start with an external assessment and review your growth together at regular intervals. Workplace. A great office in Utrecht, with hybrid working and the option of focus days at home. Equipment. You’ll get a laptop and a phone. Most of us use a MacBook, but if you strongly prefer something else, that’s fine. Getting here. We cover your travel costs. If you’re coming from outside Utrecht, we can give you a Swapfiets for the ride from Utrecht Centraal to the office. Together at the office. We have lunch together every day, with ‘kroketten’ on Fridays, and we celebrate wins with drinks. Strategic off-site. Once a year we get away for a few days to work on the future of Awareways, with time for drinks and karaoke too. Salary. €3,800 to €4,800 gross per month (based on 40 hours), depending on your experience, skills and education. Hours. 32 to 40 hours per week. Time off. 25 days of paid holiday. For later. A solid pension plan, with the option to make extra contributions on favorable terms. Grow with us. After one year, you’re eligible for our Stock Appreciation Rights plan. Diversity matters to us, and we keep working to make Awareways a place where everyone feels at home. That’s why we welcome people of all backgrounds and experiences. Interested? We don’t ask for a cover letter. Instead, tell us in no more than 300 words about a problem that kept coming back and how you found the real cause. What was the symptom, what was the cause, and how did you make sure it didn’t return? In the second interview, we’ll work through a short case from Wave together. Send your CV and your answer to Mati Kochen (Head of Technology) at [email protected] , with the subject line “Vacancy Solutions Engineer”. We’ll be in touch, and we’d love to get to know you over a coffee. Apply to this job!

More open roles at AWAREWAYS B.V.