🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
About Ampd Energy Ampd Energy is transforming how cities build - cleaner, smarter, and more sustainably. We are trailblazers in making the construction industry emission-free. Our products are advanced, compact, and connected battery energy storage system (BESS) designed to replace the dirty, noisy, and hazardous diesel generators that power construction sites around the world. By combining connected hardware with advanced software and AI, we reduce emissions, noise, and operational complexity. We envision an emission-free future across all industries. Our mission is to develop robust, versatile, and easy-to-use products that deliver clean energy - empowering businesses and people to achieve more. We're seeking individuals who bring entrepreneurial drive, adaptability, and enthusiasm, and who thrive in an environment of continuous learning and evolution. Role Overview Join our Software Solutions team building Enernet, the cloud platform behind our fleet, device monitoring, alarms, scheduling, reporting, and the mobile app our technicians use on site. Our fleet is growing from roughly 400 to 1,000 devices, every unit streaming continuous telemetry across a dozen subsystems, and the platform needs architectural headroom well beyond that. This role owns the engineering that keeps the platform fast and reliable as that load grows, driving down infrastructure cost, cutting latency, stabilising the data pipeline, and closing the performance gaps that would otherwise surface at scale. That foundation of a higher-value product work on our roadmap can only be built on a pipeline that is stable, so getting this right is super critical. It is a hands-on role. What you'll do Data Pipeline Ownership: Own the flow from AWS IoT Core, Kafka into TimescaleDB, and legacy GCP Pub/Sub in place. You are accountable for throughput, correctness, latency, and cost across that path. Provide vision on improving the pipeline stability, scalability. API & BFF: Evolve the GraphQL contract that serves our web and mobile clients. Design secure, low-latency APIs (GraphQL and REST), and keep the BFF layer clean as the schema and product grow. Cost & Performance: Drive down infrastructure and observability cost per device, cut latency, and remove the throughput bottlenecks that would otherwise surface as the fleet grows, keeping monitoring spend proportionate to what it monitors. Scale & Reliability: Kafka partitioning and consumer groups, batched writes, backpressure, and hot-path isolation so one misbehaving device cannot degrade the fleet. Observability: Use our Grafana stack to identify and track slow queries, monitor the pipeline, and maintain alerts that fire before degradation becomes an incident. Safe Change: Evolve a live system safely staged, reversible changes with parallel runs, shadow validation, and rollback, so improvements ship without disruption. Full-Stack Collaboration: Review the frontend and mobile work, understand the GraphQL contract, and trace a bug from a Vue chart to a Timescale query to a Kafka consumer. Responsibilities Pipeline Stability at Scale: Stabilising and cost-optimising the telemetry path so it holds latency and throughput targets as the fleet grows, with observability to prove it. API evolution: Extending the GraphQL contract to support new product features without regressing latency or breaking clients. Production Health: Acting as a senior voice in incident response and reducing the support load that currently leaks into sprint time. Cross-Functional Delivery: Working with firmware, service, and commercial colleagues to turn raw telemetry into reliable, actionable tooling. Experience required Backend & Streaming: 510 years building and operating production backend systems, including meaningful time on high-throughput streaming or time-series data. Data at Scale: Deep, practical Kafka partitioning, consumer groups, rebalancing, ordering and idempotency, schema evolution plus strong SQL and time-series database skills (TimescaleDB, ClickHouse, InfluxDB or equivalent). BFF & API design: Designing secure, low-latency APIs (GraphQL and REST) that serve web and mobile clients. Live Migration: Has migrated a live system without downtime: parallel writes, shadow validation, staged cutover, rollback. Stack & Cloud: TypeScript / Node.js fluency (our services are largely NestJS) and AWS in production ECS, IoT Core, networking, working Terraform / IaC. Go: Our services are moving to Go for latency-sensitive paths; we expect you to be productive in it quickly. Prior Go experience is a plus, not a requirement, the pipeline judgement matters more than the language. Documentation: Write clear technical documentation to assist development and communication .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.