Full Stack Engineer

Ecoplant (acquired by Ingersoll-Rand) makes the world a cleaner place.

Utilizing cutting-edge AI, we optimize Factories' electricity usage to decrease CO2 emissions.

Among our customers are industry giants such as Nestlé, Quaker, and Osem.

The Application squad owns the customer-facing half of EcoPlant: the NestJS real-time data layer that turns a fleet-wide stream of sensor readings (about 1,300 messages a second) into live dashboards, the EcoPlant web client, and the value, savings and reporting services behind them. You will own code from the message broker down to the chart a customer opens, measure it in production, and fix what the numbers show.

We are looking for a highly passionate, skilled, and experienced Full Stack Engineer to join our growing team.

Qualifications:

· Bachelor's degree in Computer Science or a related field.

· A minimum of 3 years of experience as a Backend or Full-stack developer – Must

· Proficiency in TypeScript on Node.js and React or Angular – Must. Familiarity with Nest.js.

· Working knowledge of a message broker in production (Pulsar, Kafka or similar): subscriptions, acknowledgement semantics, backlog and consumer lag, key-based partitioning – Must

· Proficiency with cloud technologies and services such as AWS (preferred), GCP, or Azure: SQS, CloudWatch, IAM roles, EKS – Must

· Kubernetes basics you can reason about from a manifest: probes, requests and limits, rolling updates, why a pod stays Pending.

· Node.js performance skills: the event loop and what blocks it, child processes or worker threads, memory behaviour, and measuring a change before claiming it helps.

· Hands-on experience with Redis and relational databases (Postgres); time-series stores such as InfluxDB are an advantage.

· Observability as a daily tool: Grafana (Loki, Prometheus), Coralogix or an equivalent, and reading Kubernetes events.

· Testing discipline: unit tests with Jest or Vitest, integration tests against real datastores, and load or end-to-end tests you design yourself when none exist.

· Clear written communication: merge-request descriptions that state what changed and what was measured, root-cause analyses, and honest reporting when a result is inconclusive.

· Advantage: Nx monorepos, GitLab CI with per-branch review apps, industrial IoT or energy domain exposure, Java familiarity, MobX, and SSE or WebSocket streaming in the browser.

Responsibilities:

· Own the real-time data path end to end: Pulsar consumption, per-asset routing, SQS publishing and SSE fan-out, including its throughput, lag and memory in production.

· Find bottlenecks with evidence, not intuition: broker admin stats, micro-benchmarks, Loki and Prometheus queries, CloudWatch queue metrics. Change the design when the numbers say so.

· Ship features across the stack: React and Angular screens for stations, trends and investigation, backed by NestJS endpoints and the value, savings and reporting services.

· Keep shared libraries safe for the other apps that import them: opt-in flags, additive APIs, backward-compatible defaults, and a build and test pass across every consumer before merge.

· Prove changes at scale before promotion: deploy to a per-branch review app, seed it with production-shaped data, run load and end-to-end tests against staging, and report measured before/after numbers in the merge request.

· Debug production incidents across services and clusters (EKS, GKE, Pulsar, Redis, SQS), write the root-cause analysis, and turn recurring classes of bugs into integration tests.

· Work with DevOps on Kubernetes manifests and capacity, and with the platform teams that own ingestion, alerts and the rule engine.

· Review code with the same standard you hold your own to: correctness first, then removed behaviour, cross-file effects, reuse and simplicity.

Why Ecoplant

· Ecoplant is during rapid growth, aiming to double our R&D center this year

· Hybrid environment with a healthy work-life balance

· A friendly and inclusive workplace culture that fosters collaboration and innovation

· Engineering practices with real teeth: a review app per merge request, code review in passes, and no production rollout without measured results from a lower environment

Join us in transforming the way we power production for a brighter future.