Senior Full Stack Engineer — Cloud Infrastructure & IoT

This role is suitable for a Senior Full Stack Engineer with strong professional experience in Node.js, TypeScript, React, AWS, PostgreSQL, and automated testing.

The candidate should be skilled in REST APIs, event-driven systems, serverless architecture, infrastructure as code, CI/CD, distributed systems, and cloud troubleshooting, with knowledge of AWS IoT Core and connected devices preferred.

They should be familiar with designing backend services and web applications, managing cloud infrastructure, supporting OTA updates, optimizing databases, building end-to-end tests, improving deployments, and making technical decisions independently and collaboratively.

How would you design a Node.js and TypeScript backend service for managing connected devices?

I would separate device management, command processing, and reporting into well-defined services with typed contracts and clear error handling. I would use asynchronous workflows where appropriate, add authentication and authorization, and include structured logging, metrics, health checks, and automated tests.

How would you use AWS IoT Core, Lambda, and SQS to process device events?

AWS IoT Core could receive MQTT messages and route them to Lambda or SQS based on the event type. SQS would provide buffering, retries, and dead-letter handling, while idempotent consumers would prevent duplicate messages from causing inconsistent device state.

What considerations are important when designing an over-the-air update system?

The system should support signed artifacts, device authentication, version compatibility, staged rollouts, progress tracking, retries, and rollback. Updates should be delivered through a reliable workflow, with device health reported before and after installation to detect failed deployments.

How would you choose between AWS Lambda and ECS for a backend workload?

Lambda is well suited for event-driven, stateless, and intermittently used workloads with variable traffic. ECS is preferable when the service requires long-running processes, predictable resource allocation, custom runtimes, persistent connections, or more control over execution and scaling.

How would you optimize a slow PostgreSQL query used by an API?

I would inspect the query plan with EXPLAIN ANALYZE, check for unnecessary joins or data retrieval, and verify that indexes support the filtering, joining, and ordering patterns. I would also consider pagination, query restructuring, updated statistics, connection pooling, and whether the schema matches the access pattern.

How would you design a reliable asynchronous workflow using SQS?

I would make message handlers idempotent, configure visibility timeouts and bounded retries, and use a dead-letter queue for messages that repeatedly fail. I would also monitor queue depth, processing latency, and failure rates, while including correlation IDs for tracing messages across services.

How would you structure a React and TypeScript application that consumes backend APIs?

I would organize the application around feature boundaries, shared typed API clients, reusable components, and explicit loading, error, and empty states. Server state should be handled consistently, while validation, authentication behavior, accessibility, and predictable testing should be built into the design.

How would you test an end-to-end device management workflow with Playwright and Cucumber?

I would express business behavior as Cucumber scenarios and implement stable Playwright steps that interact with the application through user-visible behavior. Tests should use controlled fixtures or test environments, avoid brittle selectors, clean up created resources, and publish actionable reports in CI.

How would you define infrastructure and deployment workflows using AWS CDK or Terraform?

I would represent infrastructure as version-controlled, reusable modules with environment-specific configuration and least-privilege IAM policies. CI/CD should validate plans or synthesized templates, run tests, apply changes through controlled environments, and support rollback and auditability.

How would you troubleshoot a production issue spanning a React application, API, database, and AWS infrastructure?

I would first establish the affected scope and timeline using logs, metrics, traces, deployment history, and correlation IDs. I would isolate the failing layer, mitigate customer impact, verify the fix safely, and document the root cause and preventive actions after recovery.

Owl Labs is a collaborative technology company building smart connected products that make hybrid work and learning feel more natural. As a Senior Full Stack Engineer, you’ll develop Node.js and TypeScript backend services, React applications, AWS cloud infrastructure, IoT and OTA capabilities, PostgreSQL data solutions, automated tests, and CI/CD workflows. This is a flexible remote opportunity with a Boston-based hybrid team, offering a salary of $160,000–$180,000 USD plus equity, generous benefits, unlimited PTO, parental leave, and a work-from-home stipend. Apply to shape reliable software behind award-winning Meeting Owl products while solving meaningful full-stack and cloud infrastructure challenges.