DeshCyber Logo

Careers

Work where the record is the product.

A career at DeshCyber means building compliance evidence that is dated, versioned and reproducible — software and control research held to the same standard as an external assessment.

We hire people who write before they build, who name their assumptions, and who are comfortable being audited on their own output. Open roles are listed on the roles page; this page states what we are and what we look for.

Vision and mission

01

The two statements every role here is measured against.

Vision

A regulated organization should be able to prove its compliance position on any given day, without running a project to do it.

  • Evidence is produced as work happens, not reconstructed at quarter end.
  • One record answers the board, the regulator and the external assessor.
  • Anyone joining us inherits that standard from their first commit.

Mission

We build the platform and the control research that turn live system activity into verdicts an assessor can recompute independently.

  • Every rule is versioned and published before it grades anything.
  • Every artefact carries its inputs, its timestamp and its owner.
  • Every team is accountable to someone who did not build the thing.

What we look for

02

Six qualities we test for in every discipline, from platform engineering to assurance review.

Writes first

Can state a problem, the constraints and the chosen trade-off in a page that someone else can act on without a meeting.

Where it shows up

Design notes, rule specifications, engagement briefs.

Argues from evidence

Reaches for the artefact, the log line or the regulatory text rather than an opinion about what is probably true.

Where it shows up

Control research, incident review.

Precise about scope

Knows the difference between what a control claims, what it covers and what it leaves open — and says so plainly.

Where it shows up

Framework coverage, assessor conversations.

Engineering depth

Comfortable in TypeScript and data pipelines, and able to reason about correctness, determinism and failure modes.

Where it shows up

Platform, collectors, console.

Regulated-domain literacy

Can read SEC, DFARS, PCI or SWIFT source material and turn it into something testable, or is set on learning to.

Where it shows up

Rule research, assurance review.

Named ownership

Takes a surface end to end and stays accountable for it after it ships, including the parts that are unglamorous.

Where it shows up

Every function, from day one.

How we hire and how we work

03

The practical facts, stated before you apply.

Process
Written exercise, then two conversations

The exercise is scoped to a few hours and is close to real work; we pay for anything longer.

Working model
Dhaka-based with remote-friendly delivery

Overlap hours are agreed per team rather than imposed globally.

Working languages
English and Bangla

Written artefacts are produced in English; day-to-day work happens in both.

Progression
Reviewed twice a year against published expectations

Levels and their criteria are written down before anyone is measured against them.

Disciplines
Engineering, control research, assurance

Assurance never reports to the team whose output it reviews.

Applying
Open roles, or a written note

If nothing listed fits, send the problem you want to work on and why it matters.

Work on the record, not the paperwork.

Tell us what you have built and which mandate you know best; we reply within one business day.