How to apply for Senior Engineer - Platform & Data Infrastructure

About Ampd

Ampd Energy builds battery energy storage systems (BESS) to replace diesel generators on construction sites. Its products combine connected hardware with software and AI to cut emissions, noise, and operational complexity. The company is scaling its fleet from about 400 to 1,000 devices, so the platform team faces real growth pressure.

About the role

This role sits in the Software Solutions team behind Enernet, the cloud platform for fleet monitoring, alarms, scheduling, reporting, and a technician mobile app. You own the engineering that keeps the platform fast and reliable as device count and telemetry volume grow. The work centers on cutting infrastructure cost, reducing latency, stabilizing the data pipeline, and closing performance gaps.

A typical day

A typical day might involve profiling pipeline latency, reviewing cloud cost dashboards, and making changes to ingestion or storage to handle more device traffic. You would also coordinate with the team on Enernet features and the technician mobile app, since platform performance affects both. Expect to spend time on incident response when telemetry stops flowing or alarms are delayed.

Who Ampd is looking for

• Has hands-on experience scaling a data or IoT platform through a period of rapid device or traffic growth, ideally from hundreds to thousands of connected units.
• Can design and tune data pipelines that ingest continuous telemetry from many subsystems without drops, lag, or runaway cloud costs.
• Is comfortable owning infrastructure end to end: monitoring, alerting, cost analysis, latency profiling, and pipeline reliability.
• Has worked on a cloud platform that serves both web dashboards and a mobile app used in the field, and can reason about backend performance for both.

Tips for this application

• Quantify scale in your resume: number of devices, messages per second, data volume per day, latency targets, and cloud cost reductions you delivered.
• Name the specific stack you used for telemetry ingestion and storage (e.g., Kafka, MQTT, TimescaleDB, InfluxDB, ClickHouse, or similar) and explain why you chose it.
• Show a concrete example of stabilizing a data pipeline under load, including what broke, what you changed, and the measured result.
• Mention any experience with battery, energy, or industrial IoT systems, since Ampd's devices stream telemetry from a dozen subsystems.
• Keep the application focused on platform and data infrastructure work, not general full-stack or frontend projects.

What to cover in your cover letter

Explain why the 400-to-1,000 device scale-up is the kind of problem you have solved before. Describe a specific pipeline or infrastructure change you made and its measured impact on latency, reliability, or cost. Show that you understand telemetry from hardware subsystems and the constraints that come with it. State clearly that you want to work on Enernet and the platform behind a physical fleet, not just abstract cloud services.

Research before applying

• Read Ampd Energy's product pages on the BESS units and what telemetry each unit likely produces.
• Look up Enernet and any public material on its features, such as fleet monitoring, alarms, scheduling, and reporting.
• Check Ampd's news or announcements for details on the fleet growth from 400 to 1,000 devices and where the units are deployed.
• Find out what cloud provider and data stack Ampd uses, or prepare to ask that question in the first interview.

Likely interview topics

Based on the job description, expect questions about:

• How would you architect telemetry ingestion for 1,000 devices each streaming data from about a dozen subsystems?
• Walk through a time you reduced cloud infrastructure cost on a data platform. What did you measure, and what was the result?
• How do you detect and fix latency or data loss in a pipeline that feeds both a web dashboard and a mobile app?
• Describe your approach to monitoring and alerting for a fleet platform where device downtime has real operational consequences.
• How would you plan the platform's capacity and architecture for growth beyond 1,000 devices?

Common mistakes to avoid

• Submitting a generic platform engineering resume with no numbers on scale, latency, or cost.
• Focusing on frontend or product features instead of the data pipeline, infrastructure cost, and reliability work this role owns.
• Claiming IoT or telemetry experience without being able to explain ingestion patterns, message volumes, or failure modes.