Sr. Full Stack Developer (JavaScript + TypeScript)
Software Development · Vadodara · 4 - 8 yrs
Read the posting on KekaCareers
Open roles, and what to do when there are none
Everything open is listed below, read from our own record of the board rather than retyped by hand. When the list is empty it says so plainly rather than filling the space. An empty list here is worth an explanation rather than an apology. That explanation is the next thing below.
Live from the board
What is open right now
One list, three honest states. When roles are posted they appear here with the same title, team and location the board carries. Each one links to its own page on Keka. When none are posted the count is zero and it says zero. When the record cannot be read, it says that instead of guessing.
Each posting below carries the title, the team and the location exactly as the board states them, and opens onto its own page on Keka. The description, the requirements and the application itself all live there. Nothing about a role is summarised or interpreted on the way here, because a rewritten job description is a second version of the truth that starts drifting the day it is written.
Open roles
Why that list is usually short
How long people stay is the one employer figure Atyantik offers for publication, and it is the context this list is missing without it.
Ask how long people stay and the answer, given by the founders rather than pulled from a report, is around five to six years on average. The longest-serving person here is at ten. Both of those are worth reading carefully: five to six is an average across everyone, not a promise about any one person and not a minimum anybody signs up to, and ten years describes one individual rather than a common outcome.
Nobody has audited those figures and no independent population sits behind them. They are what Atyantik says about itself, which is the honest weight to give them. They are stated here anyway, because how long people stay is the single most useful thing to know when reading a short list of openings, and it is the one employer figure offered here for publication.
What an empty board is not, is a statement about anything other than the board. The only thing that can be read off it with confidence is what it says: on the day you looked, nothing was posted. Everything past that is inference, and none is offered here. If you want to know what the work is actually like before deciding whether to keep watching, the four pages below are the honest answer and they carry facts rather than encouragement.
What the arrangement actually is
Three things in the order somebody meets them. Each one names something that can be asked about before an offer is signed.
A named tech lead from the first week, and an expectation that you teach yourself.
Every new joiner is assigned a tech lead. That is a standing practice rather than a favour arranged for some people. The second half matters as much and is easier to leave out. The environment expects you to learn on your own. The lead is there to point and to review, not to walk you through it.
Ask how the lead is assigned and what that person actually does in the first weeks after somebody joins. It is a standing practice rather than a case-by-case arrangement, so there is something concrete to describe.
Moving up is decided on knowledge and contribution, not on years served.
There are KPIs, and they are the mechanism. Advancement is based on knowledge and contribution rather than on the number of years somebody has been here. What the rubric contains is published nowhere. Treat that as the stated basis for moving up rather than as a document you can go and read.
Ask what advancement is based on, and listen for whether the answer is a duration. That single distinction is the whole of what is being claimed here, and it is a short question.
Open-source work is encouraged, and that includes your own projects.
Contributing to open source is encouraged here, and so is maintaining projects that are yours rather than the company’s. The second half is the rarer one and it is meant literally: work with your name on it, kept by you.
Ask what happens to a project you already maintain. Maintaining your own is encouraged here, and asking early costs nothing and settles it either way.
Whether this suits you
Where this fits
You want your code read by a senior software engineer before it ships, on every change. You would rather that be a rule than a courtesy.
You want a named person to point you and to review your work, and you are content to do the actual learning yourself.
You expect to be somewhere for years rather than months, and a team whose average stay is measured in years is what you are looking for.
You maintain something of your own outside work and you want that to stay yours.
Where it does not
You want a remote-first job. People here do work from home, and that is not the offer being made.
You want a promotion timetable you can count in years, with each step arriving on a schedule.
You need to know what happens between sending something and hearing back before you spend an evening on it.
Which of these is yours
Four pages sit under this one, and the internship programme has a page of its own. The split below is by where somebody actually is, not by what each page is called. The page names do not help until you already know which one you want.
Still deciding whether to apply
- Why join AtyantikThe case for the work, and what the years look like from inside it.
- Life at AtyantikThe working day in two timezones, what happens to code you write, and the building it happens in.
- The Atyantik teamThe people you would work beside, by name and photograph, and how long they tend to stay.
Decided, and want to know how it runs
- The hiring processWhat happens after something is sent, stage by stage.
- How to applyWhere an application goes, who reads it, and what is never done with it.
Still a student
- The internship programmeSix months every year, December to May, for final-year students. The form tells you if you are eligible as you fill it in.
Questions about the list itself
How often does something get posted?
No frequency is published and none should be read off this list. Atyantik says this about itself rather than measuring it from records. People stay around five to six years on average, and the longest-serving person is at ten. That is an average across everyone rather than a promise about any one person, and it is the context worth having when the list is short.
It says nothing is open. Is the list broken?
It is not, and the two cases are deliberately printed differently. A zero means the record was read and there is genuinely nothing posted. If the record cannot be read at all, this section says so and sends you to the board. Printing a zero we cannot stand behind would be the worse failure of the two.
Can I be told when something opens?
Not through this listing. There is no application form anywhere on atyantik.com, and no openings alert to sign up for. The Keka board is the thing to watch, and it is one link from the top of this section. The newsletter in the site footer is a different thing and carries company writing, not job postings.
If this list and the board disagree, which is right?
The board, every time. What is shown here is read from our own stored copy of it, so there is a window in which the two can differ. The board is where a role is actually posted and where an application actually goes, which makes it the authority and this a convenience.
The board is where a role is actually posted
It is worth checking directly rather than taking this list's word for it, and it is where an application to a listed role goes.