Applying to Atyantik

Applying happens on Keka

Every application reaches us through the Keka board. It is the only place a role is ever posted, and the only place one can be applied to. Some weeks that board is empty. It is empty today. What to do about that is the next section, and it is a real answer rather than a holding line.

Open the Keka board

Two ways in, and they are not the same

Is there something on the board you would want to do?

  • Apply to a posted role

    Take this when

    Something on the Keka board matches the work you want to be doing.

    What it costs you

    You set up a Keka account, upload your CV there, and answer whatever that posting asks. Your application is attached to a specific role from the first minute, which is the fastest version of this.

  • Write to us with no role attached

    Take this when

    The board is empty, or what is on it is not what you do.

    What it costs you

    You send a message and a CV through the contact form and it reaches hr@atyantik.com. It is read. It is not attached to a role, because there is not one. So nothing about it moves on a schedule. There is no position in a queue to check.

After you press send

  1. First

    The file is stored exactly as it arrived

    Before anything reads it, the whole submission is written down as one object, attachments included. Nothing is retyped and nothing is summarised into a field. If a question comes up later about what you actually sent, the original is what answers it.

  2. Then

    It is recognised as an application and routed

    Anything that looks like somebody applying for work is separated from client enquiries. It goes to hr@atyantik.com, with your attachments carried along. A message that mentions hiring in passing, sent by a company asking about a project, is not treated as an application. It does not reach that inbox.

  3. Then

    You get one acknowledgement

    One message, confirming it arrived and where it went. It carries the Keka link, so you can also apply there directly if a role is posted. That is the whole automated sequence. There is no second message and no third.

  4. After that

    A person reads it

    From that point every decision and every reply is a person at Atyantik. Nothing automated is deciding whether you go forward, and nothing automated is writing to you.

What to put in it, in the order it gets used

  1. 1

    Something you built, and what was hard about it

    Name one specific piece of work, and the part of it that did not go smoothly. Three sentences of that tell a senior software engineer more than a stack list does in a page. The problem you chose to describe is itself the signal.

  2. Why 2 waits for 1The message is read in full before anything else is opened. This is the only part guaranteed to be read.

  3. 2

    Where you want to go next

    What you want to be doing in two years decides whether a role fits. It predicts that better than what you have done already. Say it plainly, including if the answer is a direction rather than a title.

  4. Why 3 waits for 2It is the question a first conversation opens on, so answering it early skips a round.

  5. 3

    A CV, as a normal file

    A PDF or a document is fine and neither is preferred. It is stored as sent and opened by a person. Formatting for a parser is effort with nowhere to land. Write it for somebody who will read it.

  6. Why 4 waits for 3It is opened after the message, and it confirms what the message already said rather than replacing it.

  7. 4

    Links, if you have them and only if they help

    A repository, something running, a piece of writing. One that shows how you think beats five that show that you were present. Nothing here is required, and an application with none is not weaker for it.

This ordering is not a preference. It follows from the handling above: a person reads the message first, in full, and no software reads the file for terms.

The parts nobody advertises

  • Nothing scores you, ranks you, or sorts you against anybody else. There is no automated first cut to survive.
  • Your CV is kept as a file, not mined for keywords. Nothing reads it looking for terms to match. The words you chose reach the person in the order you wrote them.
  • One acknowledgement, and then nothing. There is no follow-up sequence, and nothing will invite you to complete a profile.
  • No automated status updates. If you hear from Atyantik after the acknowledgement, a person wrote it.
  • No promised reply date. We would rather print no number than print one that gets missed. Nothing on our side is set up to send you a deadline it has not agreed to.

What actually lands in the hiring inbox

This is the record a person opens. Six fields, your message underneath it in full, and your files.

The forwarded record

One message to hr@atyantik.com, per application

  • Who you are. Your name and the contact details you gave, exactly as you typed them.
  • What you are asking about. The role you mentioned, if you mentioned one, and a link to that posting when it matches something live on Keka.
  • What you wrote. Your message in full, unedited and unsummarised. Nothing paraphrases you to the person deciding.
  • What you attached. Your files, either attached to the same message or as links that expire.
  • When it arrived. The timestamp, so the sequence of a conversation is never in dispute.
  • What is missing on purpose. There is no score, no rating and no fit assessment anywhere in that record, because none is produced.

How the hiring conversation runs after that

Questions that come up before people send anything

Nothing is listed. Is it worth writing anyway?
Yes, with one caveat worth knowing first. A message sent when nothing is posted reaches hr@atyantik.com and gets read. Being read is the whole of what it gets. It is not attached to a role, because there is not one, so nothing about it moves on a schedule. If you would rather not send something into that, watch the Keka board instead. Both are reasonable and neither is the clever one.
What happens to my CV, and how long do you keep it?
It is stored as the file you sent, and it is not parsed for skills or keywords. The submission is kept for 90 days in immediate storage and then archived. Personal data in the archive is held for three years, under the same policy that covers every form on this site. If you want it deleted, ask. The stored submission, the record of it and the retained details are removed. The hiring team is told, so their own copy goes too. That applies whether or not anything came of the application.
Will I hear back?
You will get the acknowledgement automatically. After that, a person replies or nobody does. We are not going to print a date here that nothing on our side has committed to keeping. What we can tell you is that no automated step is deciding it. If you have not heard anything and want to know where things stand, reply to the acknowledgement. It reaches the same inbox a person is reading.
I applied on Keka and also emailed. Have I made a mess of it?
No. They arrive in different places and neither cancels the other. The Keka application is attached to the posting, so it is the one that matters for a listed role. The message is a second copy in a hiring inbox. Nothing counts it twice and nothing penalises you for it.

Where to go from here

If the board has what you want, go there now. Still working out whether this is a place you would want to spend years? The other careers pages each answer a different part of that.

Ready to apply

The route out, and the inbox for when the board is empty.

Still deciding

Three different questions, one page each.