Software Engineer

Nestium; Union, Northern (NJ, KY); On-site; USD 110,000 - 130,000; Full time

Job summary

You’ll collaborate closely with data, GIS and product teams to ensure reliable, scalable services with low latency and clear interfaces as we scale across markets. You value maintainable code and robust failure handling, and you will own production reliability end to end.

Qualifications

• 3+ years shipping production backend or full-stack software.
• Experience with Python and/or Node.js.
• Experience deploying to the cloud, preferably GCP.

Responsibilities

• Design, build and operate backend services and APIs in Python and Node.js.
• Run production workloads on GCP with CI/CD, logging, metrics and alerting.
• Own reliability for critical paths under real load.

Skills

Python

Node.js

GCP

Tools

Cloud Run

CI/CD

Cloud SQL

Job description

You'll own services end to end — design, implementation, deployment and on-call quality — for the product that turns location questions into reviewed intelligence. Stack is Python and Node.js on GCP. You work closely with data, GIS and product; you care about latency, correctness and systems that stay understandable as we scale across CEE markets.

What you'll do

• Design, build and operate backend services and APIs in Python and Node.js — report workflows, auth, delivery and platform integrations.
• Run production workloads on GCP (Cloud Run, Cloud Storage, Pub/Sub, Cloud SQL) with solid CI/CD, logging, metrics and alerting.
• Own reliability for paths that matter: ingestion handoffs, report generation, and client-facing delivery under real load.
• Partner with data and GIS engineers so spatial and market data moves cleanly through the product — clear contracts, no silent failures.
• Raise the bar on code review, testing and operational docs so the next engineer can take over without archaeology.

What we're looking for

• 3+ years shipping production backend or full-stack software (Python and/or Node.js).
• You've owned services in the cloud — preferably GCP — including deploy, debug and recover.
• You write clear interfaces, think in failure modes, and prefer boring, reliable systems over clever ones.
• You're comfortable collaborating with non-engineers (analysts, researchers, designers) and translating product needs into shipped work.