SleekSky
Website:
sleeksky.com
Job details:
About SleekSky
SleekSky builds and runs software for clients who want to scale their technology without heavy overhead — dedicated teams, a startup-inspired culture, and a bias for agility, ownership, and continuous improvement. We combine professional depth with real room to learn, decide, and build things that last.
The Role
Most jobs at this level hand you a ticket queue. This one hands you a problem and expects you to carry it the whole way.
You'll work across a live US healthcare platform that our dedicated team builds and operates — the schema underneath it, the services and background jobs in the middle, and the screens people actually use on top. A real piece of work here looks like this: members aren't finding out their kit shipped. That's a migration, an API, a queue worker, a third-party integration, the admin screen that configures it, the translations, the tests — and the follow-up when it misbehaves in production three weeks later.
The job is wide on purpose. The engineers who do well here find that appealing rather than exhausting.
Two openings. Backend-leaning full-stack, 1–4 years.
What you'll own
- Services and jobs. Node.js and Express on PostgreSQL through an ORM, with Redis-backed queues and workers behind anything asynchronous — scheduled reminders, retries, bulk imports, report generation.
- Interfaces. React front-ends: internal admin tooling, operational dashboards for non-technical staff, and patient-facing flows where the person on the other end may be stressed and on a slow phone.
- Integrations with the outside world. Telephony and messaging, transactional email, fax and physical mail, identity and single sign-on, payments, and clinical data exchange. Real systems, with real failure modes, that you don't control.
- The data model. You'll write migrations against a live database holding real patient records. There is no "just drop the table and reseed."
- What happens after you ship. Logs, alerting, and the evening message that says something looks wrong. You are the first responder for the code you wrote.
What makes the problem interesting
- A platform of a dozen-plus applications, several white-labelled — every customer's configuration is different, and all of them are live.
- Regulated health data, which changes how you write, log and test code, and what you're allowed to put anywhere near a test.
- Asynchronous behaviour everywhere: background jobs, scheduled reminders, email, SMS, and automated voice flows, where the thing you care about happens minutes later in a system you don't control.
- Localisation across several languages, retrofitted into code that already shipped.
- Real patients on the other end. We ship continuously, so your work reaches them in days.
What you'll bring
- One to four years of writing code other people depend on. Professional experience counts. So does substantial personal work that strangers actually use — we have hired on the strength of the second.
- Real fluency in JavaScript or TypeScript, server and browser. Not equal depth in both, but no fear of either.
- Working knowledge of a relational database. You can write a join, you know what an index is for, and you've been burned at least once by an ORM quietly doing something expensive.
- Enough Git to live on a shared branch without dreading a merge.
- Clear written English. A large part of this job is explaining a technical decision to someone who is not an engineer, in writing, without them having to ask twice.
On stack matching: we don't require experience with our exact stack and we don't weight it heavily. Several of our strongest engineers arrived using a different database, a different ORM, and no queue or telephony experience at all, and were productive within weeks. What we can't teach quickly is the habit of finishing things.
Who this isn't for
- You want a narrow, well-defined lane — front-end only, or feature work where someone else absorbs the consequences.
- You need fully specified requirements before you start. Our stories are deliberately thin; working out what is actually being asked is half the role.
- Nothing you've started outside work has ever held your attention past the first weekend.
Click on Apply to know more.