Senior Software Engineer - Evinova

WHY JOIN US? Evinova is a health-tech business focused on accelerating better health outcomes by advancing digital transformation across the life sciences sector. By combining science-based expertise, evidence-led rigor, and deep human insight, we design digital solutions that enable healthcare to work better for everyone. Operating at the intersection of healthcare, technology, data, and analytics, we are helping unlock the full potential of digital health, transforming how clinical research is conducted, how care is delivered, and how patients experience healthcare. Our solutions are built to scale, driving efficiency, improving decision-making, and ultimately delivering better outcomes for patients worldwide. At Evinova, we are driven by a shared purpose to transform health through data and digital innovation. Our teams collaborate across disciplines to solve complex challenges, continuously learning and evolving in a fast-paced, high-impact environment. We also recognize the importance of flexibility and balance. Our ways of working support both individual needs and team collaboration. To foster connection and collaboration, employees are expected to work from the office three days per week , creating opportunities for in-person teamwork, innovation, and meaningful connection. About the Organization We are looking for a software engineer who builds things that last and ships things that work — someone who holds both as a standard, not a trade-off. This is a hands-on engineering role. You will write code every day, own features from design through deployment, and be a meaningful contributor to a product used by clinical teams at scale. The work sits at the intersection of complex domain logic (clinical study design) and a fast-moving technology landscape, including AI. Neither of those things should intimidate you. The engineers who thrive here are the ones who treat a working system as something to understand before they change it, who can move fast without leaving a mess, and who know the difference between a decision that should be revisited and one that should be made carefully the first time. What the Work Looks Like You will be part of the product engineering team building Study Design er — a product that helps clinical teams design, plan, optimize and execute trials more effectively. The team ships continuously and owns its deployments. That means you are responsible for your code in production, not just in a pull request. Day to day you will: Develop and ship features across the full stack — frontend, backend, infrastructure Collaborate directly with product, design, and domain experts to turn requirements into good software Participate in code review as someone who gives and receives meaningful feedback Contribute to how the team works: surfacing problems early, improving processes, raising the quality bar Essential Skills and Experience Bachelor's degree in Computer Science, Engineering, or a related field 5&#43; years of hands-on software development experience, with a track record of shipping production systems History of working across the stack, not deep in one layer Comfortable in fast-moving environments where the requirements and the technology are both evolving What We're Looking For You build things end-to-end. You are comfortable across the stack and don't draw hard lines at the edge of your comfort zone. You understand how your code lands in production — what the deployment looks like, how it behaves under load, how it fails, and how you'd know. Infrastructure is not someone else's problem. You have judg e ment about quality. You write code that the next engineer can read, extend, and safely change. You know when &#34;good enough&#34; is genuinely good enough and when cutting corners creates debt you'll be paying back for months. You test your own work meaningfully, not just to hit coverage numbers. You use AI fluently, not blindly. AI tooling is a standard part of how you work. You use it to move faster — on coding, on learning unfamiliar patterns, on working through problems. But you evaluate the output rather than accepting it. You understand that generating code and understanding code are different things, and you don't confuse them. You bring judgment to what the model produces; the model accelerates that judg e ment, it doesn't replace it. You are curious about the domain. Clinical trial design is a specialized space. You don't need to know it coming in, but you need to be genuinely interested in learning it — because the best solutions come from understanding the problem, not just the ticket. You raise the room. At this level, your impact extends beyond your own output. You give clear, useful feedback in code review. You share context instead of hoarding it. You flag problems before they become incidents. You make the people around you better at what they do. Technical Skills This is a representative view of our stack. We don't expect full coverage — but given the scope of the role, you should be able to pick up unfamiliar parts quickly and deliberately. Frontend: React, TypeScript, Vite, Tailwind, shadcn / ui Backend: Node.js, Python, FastAPI <