We are replacing legacy tools in a market that has been underserved by modern software for decades. Our product is live, customers use it daily, and the feedback loop between what they need and what we build is short. What we need is someone who improves the product, faster, and easier to sell.
You work directly with the CTO. The team is small, which means your decisions shape the product immediately. There is no layer between you and the impact your code has on customers.
Concretely, this means: You look at the codebase and the product with the eyes of someone who cares about clean architecture and maintainable code. When something is off, you see it and fix it, not because someone filed a ticket, but because you understand how the system should work. You take customer feedback, sometimes contradictory, and work with the CTO to turn it into a roadmap that makes sense. You figure out the right solution, not just the quick one. You lead by example. You over-communicate, you review pull requests thoroughly, you pair-program when it helps, and you keep the ticket system clean. Other developers look at how you work and raise their own standards. You have an eye for intuitive, modern design. We are replacing clunky legacy tools, and our UI needs to reflect that. The app has to feel modern, fast, and obvious to use.
You know you are doing this job well when the product becomes easier to sell, when customer complaints go down, and when deadlines set by the CTO are met consistently.
We expect you to make decisions on your own and not wait for someone to tell you what to do. When you need help, you ask for it. You care about the product because you want to understand what customers actually need. Setbacks happen, what matters is that you show up the next day with the same energy. And you share what you learn back to the team, because engineering at Elara is not a silo.