Senior Full Stack Javascript Engineer

This role is suitable for a Senior Full Stack JavaScript/TypeScript Engineer with 7+ years of experience who can independently architect, develop, test, and deploy end-to-end applications.

Required skills include strong React, Next.js, Node.js, TypeScript, PostgreSQL, MongoDB, Azure, Hono, and Jest experience, along with knowledge of security, scalability, reliability, and third-party integrations.

The candidate should be familiar with building product features across the frontend, backend, databases, and cloud infrastructure; collaborating asynchronously with cross-functional teams; monitoring production systems; and troubleshooting post-deployment issues in a small remote team.

How would you architect a full-stack feature using React, Next.js, TypeScript, Node.js, and PostgreSQL?

I would define clear boundaries between the Next.js UI, API layer, domain services, and persistence layer. I would use TypeScript contracts, validate inputs at the API boundary, design the PostgreSQL schema and queries, and add unit and integration tests before deploying the feature.

When would you use Next.js server-side rendering, static generation, or client-side rendering?

I would use server-side rendering for personalized or frequently changing pages, static generation for stable public content, and client-side rendering for highly interactive features. The choice should also consider SEO, time to first byte, caching, and the amount of data required in the browser.

How would you design a secure Node.js API with Hono?

I would organize routes by domain, apply middleware for authentication, authorization, logging, rate limiting, and error handling, and validate request bodies with a schema library. Secrets would be stored in Azure-managed configuration, while database queries would use parameterization to prevent injection attacks.

How would you model and optimize PostgreSQL data for a creator marketplace?

I would model core entities such as users, brands, campaigns, creators, content submissions, payments, and social accounts with normalized relationships and appropriate constraints. I would inspect query plans, add targeted indexes, paginate large result sets, and use transactions for operations that must remain consistent.

How would you decide whether data belongs in PostgreSQL or MongoDB?

I would use PostgreSQL for transactional, relational data such as campaigns, contracts, and payments, where constraints and joins are important. MongoDB can be useful for flexible, document-oriented data such as evolving social media payloads, provided access patterns and consistency requirements justify it.

How would you integrate a third-party social media or eCommerce API reliably?

I would isolate the integration behind an adapter, handle OAuth tokens securely, validate external responses, and implement timeouts, retries with exponential backoff, and rate-limit handling. Webhooks should be authenticated, idempotent, logged, and processed asynchronously when the operation may be slow.

What would your Jest integration testing strategy look like?

I would test API routes and service boundaries against a controlled test database or isolated test environment, covering authentication, validation, database behavior, error cases, and third-party failure scenarios. Tests should be deterministic, independent, and aligned with the product test plan rather than only testing implementation details.

How would you deploy and operate this application on Azure?

I would use separate environments with infrastructure and configuration managed consistently, automated CI/CD pipelines, secure secret storage, and controlled database migrations. Azure monitoring, centralized logs, metrics, alerts, and deployment health checks would support reliable releases and quick diagnosis of production issues.

How would you troubleshoot a performance regression in a live Next.js application?

I would first use logs, metrics, traces, browser performance data, and database query plans to identify whether the issue is in rendering, network calls, server execution, or persistence. I would reproduce the problem, measure a targeted fix, and deploy it incrementally with monitoring to confirm the improvement.

How would you design a scalable and secure payment workflow?

I would avoid storing sensitive payment data directly, use the payment provider’s tokenization and webhooks, and make payment operations idempotent. The workflow would persist explicit states, verify webhook signatures, authorize access by role, and use transactional updates so financial records cannot be duplicated or partially applied.

Stack Influence is a VC-funded, high-growth creator marketplace connecting eCommerce brands with everyday social media users. As a Senior Full Stack JavaScript Engineer, you’ll architect, build, test, and deploy end-to-end features, integrations, and infrastructure across React, Next.js, TypeScript, Node.js, PostgreSQL, Hono, Jest, and Azure, with additional MongoDB exposure. This is a fully remote role open worldwide, offering a flexible four-day work week and a salary of $125,000–$200,000 USD per year, plus potential equity. Join a small, senior team where your work will have immediate impact on a rapidly scaling product.