Original listing text, shown exactly as published by the company.
Your day-to-day responsibilities
- Platform foundations for compute and deployment. Infrastructure that supports long-running data processing workloads and can be reproduced consistently across cloud and on-prem environments. You will define how these environments are structured, provisioned, and maintained.
- Deployment and environment model. Systems where environments are treated as replaceable and reproducible rather than manually maintained. Clear separation between platform capabilities and application code, with well-defined interfaces.
- Infrastructure automation. Infrastructure-as-code and deployment pipelines that work across environments. Tooling that abstracts away differences between cloud and on-prem deployments, allowing the same system to run in both.
- On-premise-first architecture with cloud as a development tool. We use cloud environments for development speed and iteration, but the platform must be designed so that customer deployments on-premise are first-class. This constraint should shape infrastructure decisions from the beginning.
- Execution model for workloads. How long-running, batch, and asynchronous workloads are defined, triggered, and observed. You will help establish patterns for how processing pipelines are expressed and executed, without locking into a single implementation approach.
- Security and access control. Identity and access models that scale across multiple environments, with secure-by-default infrastructure that does not become a bottleneck for engineers.
- What comes next. As the platform evolves, you will help define future capabilities such as hybrid deployments, GPU workloads, and scaling patterns for data-intensive processing.
What we’re looking forMust haves
- Experience building infrastructure or platform systems that other engineers depend on. You have built and evolved infrastructure that serves as a foundation for teams, not just operated or maintained existing systems.
- Experience designing for multiple environments. You have worked on systems that must run across different environments (e.g. cloud and on-prem), and understand the implications this has on architecture and tooling choices.
- Strong infrastructure and deployment fundamentals. You understand how to design, provision, and operate compute, networking, and storage in a way that is reproducible and maintainable.
- Strong AWS experience in production environments. You are highly proficient in AWS and have used it extensively, but you design systems with portability in mind and avoid unnecessary reliance on cloud-specific managed services.
- Infrastructure automation and tooling. You have built infrastructure-as-code and deployment automation, and understand how to make environments reproducible, predictable, and easy to evolve.
- Ability to make and own architectural decisions under ambiguity. You are comfortable working without predefined patterns, can prioritise effectively, and can justify tradeoffs in system design.
- Strong coding ability. You regularly write production-quality code (e.g. Python or similar) for tooling, automation, and system integration, and are comfortable working across infrastructure and application boundaries.
- Security and access control fundamentals. You understand identity, access control, and security boundaries, and can design systems that are secure by default.
- High ownership and autonomy. You proactively identify problems, define solutions, and drive work forward without waiting for detailed direction.
- Comfortable using AI tools in daily engineering work. You use AI-assisted tools (e.g. Cursor, Copilot, Claude, ChatGPT) as part of your workflow to accelerate development, exploration, and iteration.
Nice to haves
- Experience with on-premise or air-gapped deployments. Experience delivering software to environments outside of cloud providers, where infrastructure constraints are different and less controlled.
- Experience with data-intensive or batch processing systems. Familiarity with designing and operating systems that process large datasets or long-running workloads.
- Experience in early-stage or rapidly evolving engineering environments. You have worked in environments where systems and processes were not yet fully defined, and helped shape them.
- Experience building internal platforms or developer tooling. You have created systems, tools, or abstractions that improved how other engineers build and deploy software.
- Familiarity with containerised workloads or orchestration systems. Experience with container-based systems where appropriate, without being tied to a specific tool or platform.
Application Process• TA Partner Screen Call
- Hiring Manager Interview
- Technical Interview
- Values & Fit Interview
- SVP of Engineering Interview
Working at ICEYEAt ICEYE, you’ll join a diverse and highly engaged team united by the ambition to make the impossible possible. As a global scale-up, we combine speed and ambition with the opportunity to take real ownership from day one. Your growth, wellbeing, and success are a priority, with continuous professional development, training opportunities, and a culture where collaboration is how we win.
How We Work (Our Values)Make the impossible possible: We set ambitious goals and stay calm under pressure. We bring grit, optimism, and ownership when things get hard, and we keep moving until we find a way.
- Be curious: Go deep, ask questions, listen carefully, and think critically. Understand the why behind decisions.
- See the big picture: Stay close to what’s happening across the company so you can make better decisions. Consider how your work affects others.
- Drive effective teamwork: Create psychological safety, invite different perspectives, and build inclusive teams. There are no bad questions.
- Act as one team: We win together. We match tasks to the right owner and stay agile as priorities shift.
- Have fun: What we do matters and it should be enjoyable. Celebrate progress, take pride in results, and share the wins.