Senior Software Engineer / Technical Lead

Praxeon Health Technologies Inc

https://tryeyeq.com/

Full-time, permanent | Southwestern Ontario
Reports to the Executive Team

About the Company

We are a Canadian healthcare technology company preparing to bring a new cloud-based healthcare operating platform to market.

The platform combines clinical records, scheduling, billing, payments, patient communications, operational workflows, integrations, reporting and business intelligence into a single system.

The product has been developed alongside the healthcare organizations that will initially use it, giving our team direct access to real users, real workflows and a highly practical development environment. We are preparing for our initial production deployment, followed by a broader commercial rollout across Canada.

This is not an early-stage prototype. It is a large, working application with thousands of automated tests, CI/CD controls, authorization and security checks, Canadian-hosted personal health information, and integrations with healthcare services, payment systems, communications platforms and third-party vendors.

We are now looking for the person who will become the technical owner of the platform as it moves into production and scales nationally.

This Is Not a Traditional Software Development Role

We have built the platform differently.

The founders have used modern AI development tools, including Claude Code and Codex, extensively throughout the development process. We believe AI is fundamentally changing how software companies should be built and how much a small, highly capable technical team can accomplish.

We're not looking to immediately build a large engineering department.

We're looking for one exceptional senior technical person who can take ownership of a sophisticated production platform while using AI coding agents as a major part of their development capacity.

You need to be an excellent software engineer yourself. But your value isn't going to be measured by how many lines of code you personally write.

It will be measured by whether the platform is reliable, secure, maintainable, fast and continuously improving.

You'll use AI aggressively where it makes sense, while applying the engineering judgment required to know when its output is right, when it's wrong, and when a problem requires deeper investigation.

What You'll Own

You will become the technical owner of the platform. Responsibilities include:

- Production reliability: Own the health of the production environment, including monitoring, logs, performance, database health, backups, disaster recovery and uptime.

- Production incidents: When something goes wrong, lead the technical response to determine what happened, contain the problem and restore normal operations.

- AI-driven development: Use Claude Code, Codex and other appropriate development tools to build features, investigate problems, generate tests, refactor code and accelerate development.

- Code quality: Review and understand AI-generated changes before they reach production. Maintain the engineering standards and automated gates that protect the platform.

- Release management: Own staging and production deployments, CI/CD, rollback procedures, migrations, feature flags and release discipline.

- Architecture: Understand the entire application architecture and make sound decisions about how it evolves as the platform grows.

- Database: Own PostgreSQL architecture, migrations, performance and data integrity, including the safe handling of production data and personal health information.

- Integrations: Own and troubleshoot integrations with healthcare services, payment providers, communications platforms and other third-party systems.

- Security:



Work with external cybersecurity and privacy specialists to maintain appropriate technical controls around authentication, authorization, audit logging, secrets, PHI and other sensitive information.

- Observability: Build the monitoring and visibility necessary to identify problems before customers have to tell us something is wrong.

- Technical support escalation: Support and implementation teams will handle normal user questions. You will own difficult technical issues they cannot resolve.

- Technical documentation: Ensure architecture, integrations, deployments, incidents and important technical decisions are documented.

- Technical roadmap: Work directly with the founders and executive team to determine technical priorities and clearly communicate risk, complexity and trade-offs.

The existing platform already has CI gates covering type checking, linting, test suites, authorization and security, along with a staging-before-production deployment model. You'll inherit these controls and continue strengthening them. The responsibilities are consistent with the technical ownership described in the original draft.

The Technology You'll Inherit

You don't need to have worked with every component on Day 1, but you need enough experience to understand and ultimately take ownership of the architecture.

Application: JavaScript / ES Modules, Node.js 22, React 19 and TypeScript across newer shared and mobile packages.

Data: PostgreSQL, row-level tenant isolation, version-controlled SQL migrations, managed Canadian database infrastructure, automated backups and restore processes.

Infrastructure & Delivery: Containerized API hosting, AWS services in Canadian regions, CDN-delivered web application, object storage and SFTP, GitHub, GitHub Actions, Vitest, ESLint, automated CI quality gates, staging and production environments.

Integrations: REST APIs, SFTP, OAuth2, SOAP, webhooks, XML/CSV, healthcare services, payment systems and other third-party platforms.

Product surfaces: Staff-facing web application, patient-facing portal, mobile application and external integration platform.

This retains the actual technical stack from the existing posting while removing the industry-specific integrations that could identify the product.

Who We're Looking For

You are a senior engineer who has already been responsible for software that real businesses depended on every day.

You don't panic when production behaves differently from staging.

You can work through logs, database queries, network requests, infrastructure, third-party APIs and application code until you understand what's actually happening.

You should have:

8+ years of software engineering experience, including meaningful responsibility for production applications.

Deep experience with JavaScript and Node.js, with the ability to understand and improve a large existing codebase.

Robust PostgreSQL and relational database skills, including schema design, production migrations, query performance and data integrity.

Strong experience with APIs and third-party integrations, including dealing with situations where real-world implementations don't behave exactly as the documentation suggests.

Practical understanding of cloud infrastructure, CI/CD, monitoring, logging and production operations.

Strong understanding of authentication, authorization, security boundaries, secrets management and audit logging.





Experience diagnosing difficult production problems across multiple layers of a system.

Experience handling sensitive or regulated information is strongly preferred.

AI-Assisted Software Development

You should be exceptionally comfortable with AI-assisted software development.

We're looking for someone who sees Claude Code, Codex and future coding agents as leverage, not competition.

You should be comfortable giving an AI agent a complex engineering objective, evaluating its approach, inspecting the resulting changes, challenging its assumptions, running appropriate testing and determining whether the result is safe to deploy.

We don't care whether a human or an AI wrote a particular function.

We care whether the system works.

We're probably not the right environment for someone who believes every feature needs to be manually coded by an engineer.

We're also not looking for someone who blindly accepts AI-generated code because the tests passed.

We want someone between those extremes: someone capable of recognizing when AI can efficiently solve a problem and equally capable of recognizing when it is wrong.

That philosophy is already central to the original description of the role.

Your First 90 Days

Your first priority isn't building new features.

It's taking ownership of the platform.

During your first 30 days, you'll learn the architecture, codebase, database, infrastructure, integrations, deployment process and security model directly from the founders and existing technical advisors.

You'll establish and validate production monitoring and alerting, understand the existing CI/CD and release process, validate backup and recovery procedures, and become comfortable deploying and rolling back the application.

During Days 30–60, you'll participate directly in the initial production rollout. You'll work alongside our implementation and operations teams, investigate production issues and begin taking responsibility for fixes and releases.

During Days 60–90, the objective is straightforward:

The founders should no longer need to be the first call when the platform has a technical problem.

You should be capable of owning the technical operation of the platform.

Where the Role Can Go

This role has significant room to grow.

We don't have a predetermined engineering headcount.

If one exceptional engineer working with modern AI development tools can support the platform, we won't hire five engineers simply because that's what a traditional software company would do.

If growth, complexity or reliability demands additional people, you'll help determine when we need them, what expertise we need and who we hire.

As the company grows, this role could naturally develop into Director of Engineering, VP Technology or CTO-level responsibility, depending on the individual and the needs of the business.

Nice to Have

Experience with healthcare technology, privacy-regulated software, PHI, PHIPA/PIPEDA or other regulated environments would be valuable but isn't mandatory.

Experience with React at scale, multi-tenant SaaS architecture, Canadian data-residency requirements or healthcare integrations would also be useful.

What We Offer

This is an opportunity to take technical ownership of a platform after the hard work of getting from idea to working product has already happened, but before the company has built a traditional engineering organization around it.

You'll have direct access to the founders and executive team, significant influence over the technical direction of the company, freedom to use the best modern development tools available, and the opportunity to help build a technology company around a small number of exceptional people amplified by AI rather than a traditional large development organization.

📌 Senior Software Engineer / Technical Lead (London)
🏢 Praxeon Health Technologies
📍 London