Software Application Developer

This position is a strong match for a mid-to-senior full-stack engineer in Canada who enjoys building secure, scalable SaaS platforms—someone comfortable owning both backend microservices (TypeScript/Node.js, SQL/Postgres, Redis/OpenSearch, AWS) and modern frontend architecture (React micro-frontends with SingleSPA, Webpack, Storybook), and who wants hands-on impact in a compliance/anti-fraud product where performance, multi-tenancy, CI/CD, and OWASP-grade security practices are core to the day-to-day work.

1. Why are you interested in joining Case IQ / Lextegrity as a Software Application Developer?
   I like the combination of compliance, anti-fraud, and large-scale data processing. It’s motivating to build software that helps real companies detect and prevent corruption and economic crime instead of just moving pixels. Your stack (TypeScript/Node.js, React micro-frontends, AWS, PostgreSQL, Redis, OpenSearch) is exactly where I already have strong experience and where I want to grow further.

2. What is your experience with TypeScript and Node.js for backend development?
   For the last several years I’ve been building backend services primarily with TypeScript and Node.js (Express/Nest/Fastify). I’ve designed and implemented REST and GraphQL APIs, background workers, and integration services. I focus on clean layering (routing, validation, business logic, data access), strong typing, good error handling, and observability, with a lot of emphasis on maintainability and testability.

3. How comfortable are you with React and micro-frontend architectures like SingleSPA or similar?
   I’ve built several production React + TypeScript applications using shared design systems and Storybook. On one project I helped split a monolithic SPA into domain-based micro-frontends: set up module boundaries, shared libraries, routing, and communication between apps using SingleSPA / Module Federation patterns, while keeping UX consistent and performance acceptable.

4. Describe your experience with relational databases and search/caching technologies such as PostgreSQL, Redis, and OpenSearch/Elasticsearch.
   I’ve used PostgreSQL as the primary OLTP database: schema design, indexing, complex queries, migrations, and performance tuning. Redis I’ve used for caching, rate limiting, queues, and short-lived tokens. With Elasticsearch/OpenSearch I’ve implemented full-text search, filtering, aggregations, and log analytics, tuning mappings and queries to match specific use cases and performance targets.

5. What is your experience working with AWS and cloud-native applications?
   I’ve built and deployed services on AWS using Lambda, ECS/Fargate, S3, API Gateway, CloudFront, RDS, and CloudWatch. I’m used to infrastructure-as-code and CI/CD pipelines for building, testing, containerizing, and deploying services into multiple environments, with environment-specific configuration and automated rollbacks where possible.

6. How do you think about security and OWASP best practices in your day-to-day development?
   I start with strict input validation, least-privilege access, and secure handling of credentials and tokens. On the backend that means parameterized queries, robust authz/authn, and consistent logging/auditing. On the frontend I focus on preventing XSS/CSRF, using safe APIs, and proper security headers. I also pay attention to dependency management, secure defaults, and reviewing designs for data exposure and multi-tenant isolation.

7. What experience do you have with SaaS, multi-tenancy, and event-driven architectures?
   I’ve worked on multi-tenant SaaS where we used either separate schemas per tenant or shared schemas with tenant scoping in the DAL, plus strict access controls and tenant-aware caching. In event-driven systems I’ve published and consumed domain events via queues/streams to decouple services, drive async workflows, and integrate external systems without tightly coupling core services.

8. How do you ensure code quality, scalability, and reliability (testing, code review, CI/CD)?
   I rely on TypeScript’s type safety, ESLint/Prettier, and layered architectures to keep code clean. I write unit tests (Jest/Vitest), integration tests for APIs, and add E2E tests where it makes sense. Code reviews are standard in my workflow, focusing on correctness, clarity, and architecture. In CI/CD we run linters, tests, builds, and sometimes smoke tests before promoting artifacts to staging and production.

9. Describe how you work in an agile, cross-functional team with designers, QA, and product managers.
   I participate in sprint planning, stand-ups, refinements, and retros. I help break down requirements into clear technical tasks, estimate work, and surface risks early. I collaborate closely with design and QA, give feedback on UX feasibility and edge cases, and keep communication transparent so everyone has the same understanding of scope and priorities.

10. Why do you think you’re a strong fit for this specific role and team at Case IQ?
    My experience lines up with your stack and responsibilities: TypeScript/Node.js APIs, React micro-frontends, AWS, PostgreSQL, Redis, and search technologies, all in a multi-tenant SaaS context. I enjoy owning features end-to-end, care a lot about security and performance, and I’m comfortable working remotely in a collaborative, agile team. On top of that, I’m genuinely interested in the compliance and fraud-prevention domain, which makes this role a very natural fit.

This role is ideal for a mid-to-senior full-stack engineer based in Canada who loves building secure, scalable SaaS platforms end to end—owning backend microservices in TypeScript/Node.js with SQL/Postgres, Redis/OpenSearch, and AWS, as well as driving modern frontend architecture with React micro-frontends using SingleSPA, Webpack, and Storybook—and who wants tangible impact on a compliance/anti-fraud product where multi-tenancy, high performance, CI/CD, and OWASP-level security practices are part of the everyday engineering discipline.