Engineering roles. No sales roles.
We build security platforms that clients own outright — source code, infrastructure, and roadmap all transfer at handover. That only works if the people building them can scope a system, ship it, document it, and explain it. If that is the work you want, this is the page.
Open roles
Open application
We're not advertising a specific listing at the moment. Applications are still read — by an engineer, not an applicant tracking system.
Tell us which of the four disciplines below matches what you do, and what you have actually shipped. Skip the cover letter. A link to something you built is worth more than a page describing it.
What you'd work on
The work itself
Four disciplines, mapped to the four things WhyCrew builds. Most engineers here work across two of them rather than staying inside one.
Platform Engineering
Multi-tenant data lake architecture on Elasticsearch, OpenSearch, and Wazuh. Detection engines, ingestion pipelines, and zero-downtime migrations off Splunk, Sentinel, and QRadar.
Detection & SOAR
Detection content mapped to MITRE ATT&CK, SOAR playbook development, and alert triage automation built around how analysts actually work.
Applied AI
Private LLM agents — Llama 3, Mistral — deployed inside a client's perimeter. Fine-tuning, evaluation, and the human-review gates that keep high-severity cases with a person.
Compliance Engineering
Turning NIS2 and DORA obligations into running systems: incident reporting windows, ICT risk workflows, third-party risk, and audit evidence that survives supervisory review.
How we work
No pitch, no pipeline
The same things that make the client engagements work make the job work.
Remote-first, EU-anchored
Primary engineering hub in the EU with global delivery. Where a client's data residency requires in-region work, that is planned into the engagement rather than improvised.
Fixed scope, fixed timeline
Engagements are scoped and priced up front. That discipline runs inward too — projects have an end, and handover is the goal rather than a renewal.
You talk to clients
There is no sales layer between engineering and the people using what you build. Every inquiry reaches an engineer, which means engineers hear the requirements first-hand.
What we look for
- You have shipped something to production that other people depend on
- You can explain a technical trade-off to someone who is not an engineer
- You are comfortable writing the documentation and the runbook, not just the code
- You would rather hand a client something they own than something they rent
Apply
Send it to an engineer
This is the same form the rest of the site uses, pre-routed to the engineering team. Put your portfolio, repo, or writing in the message field.
Frequently asked questions
Before you apply
No. We don't have a sales team, so there is nothing to hire for. Every inquiry that reaches WhyCrew is answered by an engineer, and that is a deliberate choice rather than a staffing gap.
Delivery is remote-first, anchored on an EU engineering hub with global delivery for clients outside the EU. Some client engagements carry data-residency requirements that shape where specific work happens; that is scoped per engagement.
The form on this page reaches the same inbox as every other WhyCrew inquiry, and it is read by an engineer rather than screened by an applicant tracking system. General inquiries get a reply within one business day.
Yes — that is what this page is for when no listing is open. Tell us which of the four disciplines below matches what you do and what you have shipped, and it goes to the engineering team directly.