Full Stack Developer (Saas Platform)

Company Description

NeuraSpeech is a fast-growing Canadian MedTech startup dedicated to revolutionizing modern healthcare for Speech-Language Pathologists (SLPs) and Audiologists. Our flagship AI-powered SaaS platform provides a comprehensive suite of professional tools, including Complete Practice Management.

Role Description

As an Individual Contributor Full Stack Developer, you will be a core member of the engineering team, responsible for the end-to-end development of features across our platform. You will design, build, and deploy highly scalable, secure, and performant microservices and front-end components. This role requires deep commitment to robust architecture, code quality, and the ability to operate autonomously in a fast-paced environment.

Qualifications

• Experience : 3+ years of professional experience as a Full Stack Developer or Software Engineer.
• Core Tech Stack : Deep expertise in React.Js (functional components, hooks) and Node.Js for building scalable front-end and back-end APIs.
• Cloud Expertise : AWS knowledge is a must. Proven experience designing and deploying services using Serverless applications (specifically AWS Lambda, API Gateway, S3, DynamoDB / Aurora Serverless).
• DevOps & Tools : Experience with Distributed Version Control Systems (ideally Git), including branching, merging, and pull request workflows. Familiarity with Docker and basic container management.
• Database : Practical experience with both relational (e.G., PostgreSQL) and NoSQL (e.G., DynamoDB) database systems.
• Mindset : Demonstrated ability to thrive as a motivated and self-directed Individual Contributor.
• Bonus Asset : Previous experience working at a startup or within the MedTech / Health-Tech industry.

What you'll do

Challenge : Complete the Serverless Predicament (Your Move)

You are alone, happily coding a new, complex feature when a critical AWS Lambda function fails and takes down the entire API for 10 minutes. The on-call rotation is unreachable, and the clock is ticking on a major product demo. You manage to push a hotfix, but as the logs clear and the service stabilizes, your CTO walks up, sees the issue was a single line of bad code, and says, clearly frustrated :

we need monolithic control, not these small, unpredictable black boxes constantly generating cold starts."

You feel the pressure, the frustration, and the core architectural disagreement clash.

How do you respond, and how does the rest of the 30-minute outage play out?

Complete the story and share your solution with us! (Yes, you can use AI to write this, but we'll discuss your answer, and we'll know if you don't truly believe what you wrote)