Tenexti is an emerging software development company based in Lviv. We specialize in creating innovative solutions, delivering high-quality results, and helping our clients turn their ideas into reality. With a passion for technology and a commitment to excellence, we strive to build lasting partnerships and drive meaningful impact through our work.
We are looking for a Team Lead to join our team. This is the most important hire we will make this year.
🧑💻 What we expect from the ideal candidate:
You have real Java behind you, and you are comfortable in a large old codebase. We need someone who can open code written by people who are long gone, work out why it is the way it is, and change it without breaking it.
You have genuinely led people, not held the title. You have been responsible for the output of a team, and for what happened when that output was wrong. You lead by example — the standard you hold other people to is the one you visibly work to yourself.
You manage risk by instinct. Feature flags, gradual rollout, rollbacks you have actually tested, thinking about blast radius before you merge, knowing which doors only open one way. Our production system is business-critical and a bad night is not an incident, it is a business event.
You listen first. Working with a customer starts with hearing the real problem rather than the solution someone arrived with. Almost every expensive mistake in this kind of work could have been prevented by one more question at the beginning.
You can say no, and you can say it with a reason. Not everything worth asking for is worth building. You can explain cost, complexity and ROI plainly, hold the position when it is pushed, and change it the moment the argument against you turns out to be better than yours.
You do the scoping with the engineers, and you close the loop afterwards. You assess what has to be done together with the people who will do it, and then you assess what was actually done. Both halves. The second one is the half most people skip.
You own things and stand behind them. When something goes wrong, you are accountable for it, and you do not spend the meeting looking for whose fault it was. This is the quality we check hardest.
You think about the end user and about money. You understand ROI. You understand how the thing you are building helps the business earn, and you can argue about what to build next in those terms rather than only in technical ones.
Your English is strong, spoken and written. You will spend a meaningful part of every week live on calls in English — being interrupted, having the subject changed mid-sentence, and having to be clear anyway — and writing clearly afterwards. This is a hard requirement, not a box to tick.
You are open-minded and eager to learn. You are interested in modern tools, patterns and engineering approaches — AI-assisted development in particular — and you are excited to apply them in a real production system rather than in a side project.
💡 What you will do:
Be the technical counterpart to the CEO of the customer’s company. He is American, sharp, direct, not technical, and there is something on fire most days. He will bring you problems, ideas and complaints — three at a time, half-formed, usually at speed. You have to want that conversation, not merely tolerate it.
Turn loud, half-formed business problems into deliverables. There is no business analyst here and requirements do not arrive pre-chewed. You ask the questions, define the outcome, write down what we are explicitly not doing, and cut a first milestone small enough that being wrong about it costs two weeks instead of two quarters.
Then actually deliver them. Milestones, sequencing, and saying early and plainly when something will not land — while there is still time to do something about it.
Lead six engineers and set the engineering standard. You decide who works on what, how work is sliced, and what “good enough” means here. A part-time DevOps enginee
