Skip to content

Create an account

HekimBis home

Careers

Let's build software that eases physicians' daily work

We write HekimBis by watching how a clinic's day actually goes. We are looking for people in engineering, product, clinical knowledge and support, in a team where what is said and what is done are the same.

Two engineers work together in a technology park office; one of them is smiling.
Engineers and a clinical advisor sketch a workflow on a whiteboard.

How we work

Every capability we describe on the site and in sales works in the product; every sentence we write rests on the real behavior of the product.

We make product decisions with examples from the daily work of physicians and clinic teams. Clinical knowledge is part of the team.

Health data is sensitive personal data. Access, isolation and audit are considered first in design.

Which areas are we hiring in?

A team working across four areas builds the same product.

  • Engineering

    Turning work that runs from appointments to diagnostics and from finance to patient communication into software that works reliably.

  • Product

    Making product decisions that simplify clinical workflows and define scope and behavior clearly.

  • Clinical knowledge

    Bringing to the team how specialty-specific forms, devices and workflows are actually used.

  • Support

    Solving clinics' questions and carrying them back into the product as feedback.

Which problems does the team work on?

Specialty engine
Managing the forms, device surfaces and workflows of 34 specialties in a versioned and safe way.
Device bridge
Connecting devices on the clinic network without loss or duplication, even through outages.
National data submission
Sending the fields regulation requires with versioned mapping, receipts and reconciliation.
Access model
Authorization that applies plan, role, branch, care relationship and purpose checks together.
Patient communication
Message flows that follow consent, quiet hours and IYS rules and carry no health information.
Data migration
Moving data safely from earlier systems with a trial run and reconciliation.

What we look for before a feature counts as finished

  • Authorization tests

    Attempts to reach across organizations, branches and the wrong patient are tested and rejected.

  • Error and outage scenarios

    Internet outages, duplicate messages, unmatched records and interrupted updates are exercised.

  • Device compatibility evidence

    A device counts as integrated only with evidence by manufacturer, model, protocol and version.

  • Masking

    Patient and health data is masked in logs, monitoring and support tools.

  • Rollback and correction

    Releases have a rollback procedure, and clinical records have a reasoned correction chain.

  • Accurate description

    Every capability is described on the site with the real behavior of the product.

Open positions

If you would like to work in an area with no listing, write a short note about yourself and your interests. When a suitable position opens, your application is considered with your permission.

Send a general application

Four steps from application to offer

Your application is reviewed, an interview follows, a technical or clinical case study is requested depending on the role, and an offer comes at the end.

Team04End

Offer

The decision and offer are communicated.

  • The process is complete here.
4 / 6

All steps

  1. 01 Application (Candidate) The candidate applies to a posting or the general application form.
  2. 02 Interview (Team) An introduction and job interview with the team.
  3. 03 Case exercise (Team) A technical or clinical case is worked through together, depending on the role.
  4. 04 Offer (Team) The decision and offer are communicated.

Alternative path from 02 Interview; the process ends on this path.

  1. 02a No suitable position (Team) The application is kept in the general pool with the candidate's permission.

04 Offer

Frequently asked questions about careers

FAQ
Can I apply if no position is open?

Yes. You can send a general application, and it is considered with your permission when a suitable position opens.

How does the application process work?

Your application is reviewed, then an interview follows; a technical or clinical case study is requested depending on the role, and an offer comes at the end.

Is remote work possible?

The way of working is stated in the listing for each position.

How is my application data processed?

Your application data is processed only for recruitment; the details are in the KVKK privacy notice.

Which areas are you hiring in?

Engineering, product, clinical knowledge and support. Open positions are listed above, and a general application is always possible.

Can someone without a clinical background apply?

Yes. Clinical knowledge is part of the team; product decisions require learning clinical workflows, and we do that together.

How long is my application kept?

A general application is considered only with your permission; retention details are in the KVKK privacy notice.