HRDev-Sleek Technologies

Nothing is scheduled. The standby list is open.

We are not running a vacancy right now, and we would rather say so than keep a permanent listing up to collect applications. What we can do is show you how we actually work, so you can decide whether it is worth your time to put your name down.

Judge us on the work

Every line below is verbatim from the codebase behind this site. It is our own work, so it needs nobody's permission to publish. Client systems are not shown here and never will be.

scripts/build-brand-assets.mjs

JavaScript

/** Un-mattes ink-over-white into straight RGBA. */
function unmat(data, width, height, channels) {
  const out = Buffer.alloc(width * height * 4);
  for (let p = 0, q = 0; p < data.length; p += channels, q += 4) {
    const r = data[p], g = data[p + 1], b = data[p + 2];
    const a = 255 - Math.min(r, g, b);
    if (a <= ALPHA_FLOOR) continue; // clear; buffer is already zeroed
    const k = 255 - a;
    const f = 255 / a;
    out[q]     = Math.max(0, Math.min(255, Math.round((r - k) * f)));
    out[q + 1] = Math.max(0, Math.min(255, Math.round((g - k) * f)));
    out[q + 2] = Math.max(0, Math.min(255, Math.round((b - k) * f)));
    out[q + 3] = a;
  }

Scroll the block sideways to read the full line

What a reviewer looks for

The source art is ink printed on solid white, so every pixel is P = a·C + (1−a)·255. Both brand inks bottom out at red 0, which is what makes the darkest channel a faithful coverage read.

What matters is that the code says so. A routine that only works because of a property of its input has to name that property, or the next person changes the artwork and quietly breaks the edges. That is the standard here.

components/brand/BrandLockup.tsx

TypeScript

/**
 * The two theme variants are swapped in CSS rather than by reading the
 * active theme in JS: the provider pins data-theme to an explicit
 * light/dark on the server, so a `dark:` variant resolves on first paint
 * with no hydration gap and no flash of the wrong ink.
 */

<Image {...shared} alt="" src={`/brand/${slug}.png`}
       className={cn("block dark:hidden", className)} />
<Image {...shared} alt="" src={`/brand/${slug}-dark.png`}
       className={cn("hidden dark:block", className)} />

Scroll the block sideways to read the full line

What a reviewer looks for

Two images, one hidden per theme, swapped in CSS instead of by reading the active theme in JavaScript.

The comment names the failure it avoids rather than claiming the approach is better: no hydration gap, no flash of the wrong ink on first paint. We ask people to write down the bug they prevented, because that is the part a reviewer cannot reconstruct later.

Specimen 03 — production client system

Client systems are not ours to publish. We would not publish yours to win a hire either.

Why this slot stays empty

If you interview here, you will be asked to reason about code in front of us rather than to hand over anything you built under someone else's agreement.

What we are usually short of

No promises attached to any of these, because none of them is a funded seat today. It is simply where the work tends to arrive faster than we can absorb it.

Backend and integration
Systems that have to talk to something older than they are.
Mobile
Android first, on devices that are not flagships.
Infrastructure and on-call
The maintenance side, which is most of what we sell.
Design engineering
People who can hold both the interface and the code for it.

Putting your name down

Send something you built and two or three sentences on a decision inside it you would defend. Not a cover letter. If we have nothing, we will say we have nothing.

Based: Central Business District, FCT-Abuja 900108, Nigeria
Send to: careers@dev-sleektech.com

The standby list is the only thing open. It is read by a person, not a filter.

Join the standby list