Skip to content
Tekansa
Careers

Small senior team, systems that run for years.

We are about thirty engineers, designers and architects building software for hospitals, lenders and booking platforms. The work is deeper than it is varied, the standards are not negotiable, and the person who writes the code is the person in the room with the client.

8
Disciplines we hire
4
Interview steps
~2wk
Decision time
0
Algorithm puzzles
What it is like

Six things that are true here, including the inconvenient ones.

01

You own the work

Engineers here talk to the client, understand why the system exists and carry a feature from conversation through to production. Nobody is handed a ticket cut from a document they never saw.

02

Senior people stay on the project

We do not staff a pitch with principals and deliver with juniors. The team you meet in week one is the team in month six, which is also why we turn work down when we have no one free.

03

The engineering standards are real

Tests, review, documentation and architecture are part of the estimate. You will not be asked to skip them to hit a date, because we price the date with them included.

04

Depth over variety

We go deep in healthcare, fintech, travel and education. You learn a domain properly rather than starting again every quarter, and that domain knowledge is what makes the work interesting after year one.

05

You are on our payroll

No subcontracting and no bench. That constrains how fast we grow, and it is the reason the standard holds.

06

Systems that outlast you

Much of what we build runs for years, in hospitals and lenders and booking platforms. It is a particular kind of satisfaction, and a particular kind of responsibility.

Hiring

Four steps, about two weeks.

You will know where you stand at every stage, and you will get a reason with the decision. We have been on the other side of processes that do neither.

  1. 01

    Introductory call

    30 min

    Thirty minutes with someone who does the work, not a recruiter reading a script. What you have built, what you want next, what we are actually doing.

  2. 02

    Technical conversation

    60–90 min

    We talk through a real problem from our own work, with you reasoning out loud. No whiteboard algorithms, no take-home that eats your weekend.

  3. 03

    Working session

    2 hrs

    A paired session on something close to the job: reading unfamiliar code, extending it, deciding what to leave alone. Paid if it runs long.

  4. 04

    Team and offer

    1 week

    Meet the people you would sit with, ask them anything, then a decision inside a week with the reasoning shared either way.

Disciplines

The kinds of people we hire.

We are not advertising specific vacancies today. These are the disciplines we recruit into, and we keep good applications on file for when a programme opens.

Where you would sit
  • Columbus
    6100 Channingway Blvd
  • Dakar
    Sacré cœur 1, Suite 8410
  • Noida
    Noida One, Tower-C, Unit 1017, 10th Floor, Sector 62

Engineering is based in Noida and runs hybrid. Remote is possible for some senior roles, and we will be clear about which before you invest time.

Write to us
Frequently asked

What candidates ask us.

01Are you hiring right now?

We hire continuously rather than in bursts, and we open roles when a client programme is confirmed. Rather than list vacancies that may close before you read them, we would prefer you write to us with what you do. If something fits, you will hear back within a week; if nothing does, we will say so instead of leaving it open.

02Is the work remote, hybrid or in-office?

Our base is Noida and most engineering runs hybrid, because pairing and whiteboarding are a real part of how we work. Fully remote happens for specific roles and senior hires. Tell us what you need and we will be straight about whether the role supports it rather than discovering a mismatch at offer stage.

03Do you take graduates and career changers?

Yes, though fewer than experienced hires, because we are honest that a small senior team has limited mentoring capacity at any moment. When we do, we take it seriously: a named mentor, real work from the first month and no fetching coffee. If capacity is full we will tell you rather than stringing you along.

04What is the interview actually testing?

How you think when you do not know the answer. We use a problem from our own backlog, and we care more about the questions you ask and the trade-offs you name than about reaching the solution we had in mind. There are no algorithm puzzles, because nothing here resembles one.

05How should I apply when nothing is advertised?

Email hello@tekansa.com with what you have built and what you want to do next. A link to something real, in a repository or in production, tells us more than a formatted CV. Say which of our domains interests you and why, because that is usually the part that decides fit.