Full Stack Engineer

3h ago

Company not listed

RemoteFull-time70,000 to 85,000 EUR yearly gross, depending on profile

Job Overview

A new opening is available for a Senior Full Stack Engineer in Either in Paris (Grands Boulevards, 75002) or full remote on Paris timezone. Work is on-site, and the arrangement is listed as full-time. The compensation mentioned in the listing is 70,000 to 85,000 EUR yearly gross, depending on profile. Skills mentioned in the listing include TypeScript, React.js, Node.js, Express.js, PostgreSQL, Artificial Intelligence and AI tools. The experience level listed is 5+ years. For general context: React is a popular library for building interactive user interfaces. Node.js lets developers run JavaScript on the server. Read the details below carefully and use the application link on this page if the role matches your profile.

★ TypeScript: Adds types to JavaScript so mistakes are caught earlier; day to day it means defining interfaces and typing function inputs and outputs.
★ React.js: Building user interfaces from reusable components and managing the data that changes on screen.
★ Node.js: Running JavaScript on the server to build APIs, handle requests and talk to databases.
★ Express.js: A minimal Node.js framework used to define routes and middleware for web servers and APIs.
★ PostgreSQL: A relational database where data lives in related tables; the work usually involves writing SQL and designing schemas.
★ SQL databases: Working with tables, relationships and queries to store and retrieve structured data.
★ GraphQL: Querying exactly the data a client needs through a single endpoint instead of many fixed ones.
★ Git and GitHub: Tracking changes, working on branches, opening pull requests and resolving conflicts so a team can share code safely.

★ TypeScript: interfaces versus type aliases, generics basics, typing API responses
★ React.js: components, props and state, useState and useEffect, lists, forms and conditional rendering
★ Node.js: npm and modules, building a simple REST API, asynchronous file and network operations
★ Express.js: routing and middleware, error handling, request validation
★ PostgreSQL: joins, indexes, transactions and constraints
★ SQL databases: SELECT, JOIN and GROUP BY, primary and foreign keys, normalisation basics
★ GraphQL: queries, mutations and schemas, resolvers, how it compares with REST
★ Git and GitHub: branching and merging, pull requests and code review, resolving merge conflicts

This role may be suitable for candidates who bring substantial experience and are comfortable owning technical decisions and supporting other team members. Those who are comfortable with TypeScript, React.js, Node.js, Express.js, PostgreSQL, Artificial Intelligence and AI tools and enjoy building practical projects may find the requirements a good match. Because the work is on-site in 75002) or full remote on Paris timezone, applicants who live in or can commute to the area may find it more practical. This is editorial guidance only, and the employer makes the final decision on suitability.

Applicants may want to highlight relevant experience with TypeScript, React.js, Node.js and Express.js in their CV. Because version control is mentioned, a GitHub profile with a few well-described repositories can make your skills easier to verify. If you have used AI tools or built small projects with language models, briefly describe what you built and how you checked the results. A short, role-specific summary at the top of your CV usually reads better than a generic profile. These are general tips, not requirements stated by the employer.

These suggested questions can help you prepare for an interview by focusing on the skills, responsibilities, and technical areas relevant to this role. They are for preparation only and are not confirmed employer questions.
Q: How do interfaces and type aliases differ, and when would you choose one over the other?
Q: How do state and props differ in React, and how do you decide where state should live?
Q: How would you structure a Node.js project so that routes, business logic, and data access stay separate?
Q: What is middleware in Express, and how would you use it for authentication or error handling?
Q: What is a transaction, and why do ACID properties matter?
Q: What is the difference between INNER JOIN and LEFT JOIN, and when would you use each?
Q: What benefits does TypeScript give over plain JavaScript on a team project, and what trade-offs have you noticed?
Q: How does useEffect work with its dependency array, and what mistakes do people commonly make with it?
Q: This role is based on-site in 75002) or full remote on Paris timezone. How do you collaborate with teammates in an office setting, and what does your availability look like?
Q: Tell us about a technical decision you owned and how you handled the trade-offs.
Q: How do you review code and support less experienced teammates?

applicants to apply for a job: