Infrastructure Engineer
Posted 2 days ago
The role in short
Architect, provision, and operate Rowspace's AI data platform within customer-controlled cloud environments, managing the full deployment lifecycle and scaling agent workloads.
The Role
We're looking for an Infrastructure Engineer to own the customer deployment lifecycle for our enterprise-grade AI data platform. You'll architect, provision, upgrade, and operate Rowspace inside our customers' own cloud environments, where large volumes of sensitive financial data are handled under strict security and compliance requirements, including real-time correlation of public data with private, tenant-isolated customer data at scale.
What You'll Do
- Design and automate deployments in customer-controlled environments, including networking, Kubernetes, IAM, DNS, key management, and infrastructure-as-code.
- Own customer deployments end to end: from technical scoping and initial provisioning through upgrades, scaling, incident response, and ongoing reliability.
- Scale the compute and orchestration platform that powers agent workloads and high-volume data processing, ensuring jobs are scheduled efficiently and remain reliable, observable, and cost-effective under growing demand.
- Build the next generation of Rowspace’s deployment platform, adding secure, out-of-the-box deployment options across Databricks, Azure Marketplace, and other enterprise platforms.
- Work with customer platform, security, and DevOps teams to navigate their infrastructure constraints, change management processes, and security reviews.
- Partner with our founders, AI Research, and Product teams to translate prospect, customer, and product needs into infrastructure that can be deployed and operated reliably across diverse environments.
What You Have
- 4+ years of experience in infrastructure or platform engineering, including deploying and operating production systems in customer-controlled cloud environments.
- Deep experience with AWS, GCP, or Azure, plus Kubernetes, containers, and infrastructure-as-code.
- Strong distributed-systems fundamentals and experience scaling compute-intensive, asynchronous workloads.
- Strong operational instincts across observability, reliability, incident response, and cost-performance optimization.
- Ability to work directly with enterprise stakeholders, from platform engineers to CISOs, and turn ambiguous infrastructure conversations into actionable plans.
- Startup mentality with the ability to move fast while building robust, scalable systems.
Perks & Benefits
- Health & Wellness: Comprehensive medical, dental, and vision insurance
- Future Planning: 401(k) plan including employer match on contributions made while employed by Rowspace
- Food & Fuel: Monthly commuter stipend, plus free daily lunch and a fully stocked snack bar in the office
- Team Culture: Regular team offsites to bond and strategize away from the desk
Prep for this interview
3 questions likely to come up at Rowspace, each matched to a line in this posting.
- 1Cloud, deployment and security
They wrote: “Deep experience with AWS, GCP, or Azure, plus Kubernetes, containers, and infrastructure-as-code.”
How would you debug a deployment that works in staging but fails at the customer's site?
How to answer
Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.
- Compare versions, config and environment variables
- Check network rules, proxies and certificates (common in enterprise)
- Look at resource limits and permissions
- Add the missing check to your install steps afterwards
Tip: List the usual suspects and how you'd check each without full access.
- 2Discovery and scoping
They wrote: “Own customer deployments end to end: from technical scoping and initial provisioning through upgrades, scaling, incident response, and ongoing reliability.”
How do you decide what to build first when a customer wants ten things?
How to answer
Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.
- Score each request by business value and by effort, with the customer in the room
- Pick one item that proves value fast and unblocks later work
- Write down what's out of scope so it doesn't creep back in
- Revisit the list after the first release, with real usage data
Tip: Show a simple way to rank the list and name what you'd leave out on purpose.
- 3Ownership and working with customers
They wrote: “Ability to work directly with enterprise stakeholders, from platform engineers to CISOs, and turn ambiguous infrastructure conversations into actionable plans.”
Tell me about a project where the requirements kept changing. What did you do?
How to answer
Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.
- The project and why requirements kept moving
- What you did to pin them down (short demos, written decisions)
- The trade-offs you made to keep shipping
- The result, with a number if you have one
Tip: Show how you reduced the change, beyond how you coped with it.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.
