DarDev hires engineers who can ship and explain what broke—not people who collect badges from passive courses. Our primary pipeline runs through DarDevLab hands-on labs and capstone projects in git; we weigh portfolio evidence and mentor-reviewed work over certificate walls. Roles are remote-friendly across Tunisia from our Tunis headquarters, with async overlap for EU client work on DarDev Services engagements.
We operate under Deployed Realities: Hesabi, DarDevLab, and our platform stack are software we run in production. Hiring matches that bar. If you cannot walk us through a deploy you fixed without slides, we will not pretend a PDF diploma closes the gap.
What roles we staff
Most hiring is for cloud-native delivery: platform engineers, backend developers, and DevOps practitioners who work on Kubernetes, GitLab CI, observability, and the SaaS products we operate. DarDev Services client work pulls the same skill set—identity patterns, pipeline hardening, runbooks—not a separate “consulting lite” track with lower technical expectations.
- Product engineering on Hesabi, DarDevLab, and internal platform services
- Platform and delivery for DarDev Services MENA engagements
- Mentor reviewers and lab authors for DarDevLab cohorts (often senior engineers already on staff)
- Occasional specialized roles (security review, technical writing) posted when a project needs them
The DarDevLab pipeline
DarDevLab is not only a product for students—it is our most reliable hiring funnel for junior and mid-level engineers in Tunisia. Candidates who complete Container Foundations through the Platform Capstone leave a git trail we can inspect before any interview slot opens. Tracks, rubrics, and grading criteria are public in dardevlab-certification-tracks; the pedagogical shift from video-first to lab-first is documented in hands-on-labs-vs-video.
Pipeline stages for Lab graduates we consider for staffing:
- Capstone sign-off
Mentor approves reproducibility, security basics, observability hook, and runbook—same rubric employers see on partner briefs.
- Shortlist review
Engineering lead reads capstone repo, MR history, and oral-defense notes. Top cohort performers enter internal talent pool—not automatic offers.
- Paid trial or internship
One sprint on internal tooling or a scoped Services task under senior review. We watch how you handle ambiguous tickets and async feedback.
- Staff or contract offer
Full-time for product roles when roadmap capacity exists; contract-to-hire common on client-heavy quarters.
You do not need DarDevLab credentials to apply—see portfolio path below—but Lab graduates skip the generic “take-home that mirrors our stack” because their capstone already is one.
Portfolio over certificates
We respect CKA, AWS, and university diplomas as signals of discipline. They are not substitutes for deploy evidence. Screeners look for:
- Public or shareable repos with README another engineer can follow without a call
- Commit history showing you fixed failures—not one pristine squash
- CI configuration that blocks bad merges, even on a small side project
- A runbook section: deploy, rollback, one failure mode you actually hit
Interviews emphasize explanation over trivia: screen-share a broken pipeline or pod you repaired, or defend a security tradeoff in your Compose file—not memorized cheat sheets.
How to apply without Lab credentials
Send a short note via the news.dardev.net contact form or careers inquiry on dardev.net with three links: best repo, LinkedIn or CV, and optional writing sample (blog post, ADR, or lab write-up). PDF-only resumes without git links rarely advance— not snobbery, but we cannot evaluate deploy skill from formatting.
Experienced hires discuss architecture plus a scoped challenge aligned to gitlab-ci-kubernetes-pipeline patterns. Seniors with verifiable production history may skip implementation but still share a postmortem from a real incident.
Remote work from Tunisia
DarDev is headquartered in Tunis and hires remote-first within Tunisia. You need reliable internet, a machine that runs kind or Docker, and overlap with team hours for standups and client calls—typically morning to mid-afternoon Tunis time for Services work with EU buyers. Occasional travel to Tunis office or client site happens on DarDev Services projects; product engineering stays remote unless you prefer coworking days.
What we value in every hire
Deployed Realities culture shows up in hiring: label beta honestly, write runbooks before claiming production, treat user corrections as bugs. See deployed-realities-explained for the customer-facing version—you should agree before joining.
When no role is posted, submit a portfolio anyway—we tag strong capstones in CRM for future quarters. Silence means no fit now, not a broken process.
Do I need a DarDevLab certificate to work at DarDev?
No. The Lab pipeline is the fastest path for juniors because your capstone is our work sample. Experienced engineers apply with production repos and incident stories; external certifications are optional context.
Are DarDev engineering roles fully remote?
Remote within Tunisia is our default for product teams. DarDev Services may require occasional client or Tunis office days. We do not hire employees fully outside Tunisia today.
How long does hiring take?
Lab graduate shortlists run after cohort sign-off—often two to four weeks to trial assignment. Open applications vary with capacity; expect async steps over several weeks, not same-day offers.
Does EscaHire replace applying to DarDev directly?
No. EscaHire is waitlist-only recruitment software for partner employers. Internal DarDev careers use the contact paths above. Waitlist signup does not auto-enroll you as a DarDev employee candidate.
What should students do before graduation?
Start with Container Foundations labs, publish work in git early, and treat capstone runbooks as interview material. Faculty aligning curricula should read dardevlab-certification-tracks and reach out via dardev.net for guest review sessions.
