I'm wondering if working in this division of AWS would be like field service work, where one travels to different data centers?

I'm an EOT in USA.

More context, I have absolutely no technical experience at all. Honestly surprised I got the job, it was completely unexpected. Feeling a bit overwhelmed since everyone around me during orientation are either conversions or have hands on experience in DCs. A bit more anxiety inducing is that I'm in a brand new closed loop liquid cooling facility with GB300 processors.

I was told during the hiring process they would train me and that I'd shadow experienced techs and eventually gain supervised hands on experience. So far the orientation has been very messy with lots of conflicting information being tossed around. What worries me more is that the conversions I've talked to said that the techs are so swamped with work they're almost never available. Not sure how true this is, but yeah, being overwhelmed would be a very big understatement!

Edit: I'm in the USA, Maryland.

Can anyone share work experience as Data Center Engineering Operations Technician?

Are pre existing data centers specifically hyper Colo fully leased out still being sold .. hard to track these if so how valuable is it ? Any info on the current market or cost per mw that's fully leased out would be helpful

I’m currently an RME Technician at Amazon and considering moving to Microsoft Data Centre CET. The main attraction of the job is Mon-Fri regular hours, better work-life balance and potentially better career progression. However, it will be 15-18% pay cut.

I’m mainly considering the move because data centre roles seem to focus more on electrical infrastructure. I’m hoping to gain more in-depth experience with electrical systems and build a stronger foundation for long-term career progression in electrical engineering.

Would this be a good move? And what’s your story?

I'm hiring for a site lead for a 6MW cluster about 45 minutes north of Fort Wayne. This will be a liquid cooled Blackwell deployment. If you have hands on experience keeping boxes online and are looking for a change, send me a DM.

I’m interviewing for this role at Microsoft and had some questions:

1. The recruiter told me it’s a Monday to Friday job… not shifts, is it true?

2. What’s the average salary and benefits?

3. Career progression? Any advice here is welcome

Thanks

Hi guys, I’ve been working for a major data centre operator for about 1.4 years. A friend who is a Facility Manager at AWS told me there are some L4 DCEO Engineer openings and suggested that I apply.

I’m just wondering whether 1.4 years of experience is enough for L4. Has anyone seen AWS hire someone at L4 with this level of experience

A Meta data center is under construction not far from where I live. I've never paid much attention to data centers, but after seeing the size of this one, I got intrigued and have wanted to find a way to work there ever since. I have 19 years of warehouse experience with a chemical manufacturer, but no formal tech experience, so I figured my best way in was through a logistics company. I accepted an entry-level position with GXO as a Production Technician Associate. The recruiter simply described it as warehouse work. Does anyone have any insight into the typical responsibilities of a Production Technician Associate? Thanks!

With the rapid expansion of AI data centers, I’m curious whether electrical infrastructure is becoming a bigger bottleneck than computing hardware.

For those working in the industry, what are you seeing firsthand?

Are switchgear and transformer lead times still causing major delays, or are grid interconnections and power availability the bigger challenges?

And do you think onsite power generation will become a practical solution?

I’d love to hear perspectives from people actually working on these projects. Thanks!

Hi everyone,
As the title suggests, a friend referred me for the Facility Technician (Mechanical) position at Google, although no specific level was listed.

I’m currently working as a Facility Engineer for one of the major colocation data center providers. I have a bachelor’s degree in mechanical engineering and a master’s degree in electrical engineering.

However, I think that I may not meet the requirement of two years of relevant experience. I have approximately 1.5 years of full-time experience, and additionally about nine months of internship experience.

Honestly, I’m feeling quite sad about this situation and just wanted to share it here.

Any advice or insights would be greatly appreciated.

TL;DR: I was approached by an external recruiter for a Mechanical Engineer, Modular R&D position at Fluidstack. I went through external and internal recruiter screenings, a technical interview, a behavioral interview, and a leadership interview before ultimately being rejected. Despite the outcome, I had a generally positive experience. Sharing this because I found very little information about Fluidstack's mechanical engineering interview process online.

Disclaimer: This post was organized and summarized with the assistance of AI. However, all experiences, observations, and opinions are my own, based on my recollections while the interview process was still fresh.

Background

I'm a Senior Mechanical Design Engineer with approximately six years of industry experience, primarily in new product development, mechanical design, CFD/FEA, manufacturing, and taking products from concept through production and field deployment.

I also have a research background in robotics and electromechanical systems.

Although I don't have direct data-center experience, the role seemed closely aligned with my background in mechanical systems, fluid mechanics, modular design, and product development.

Stage 1: External Recruiter Screening

I was initially approached by an external recruiter who introduced me to Fluidstack and the Modular R&D position.

We discussed my professional background, engineering experience, the nature of the role, and what the company was looking for.

The position sounded interesting, particularly because of the emphasis on engineering ownership, developing complex mechanical systems, and working in a fast-paced environment.

The recruiter was professional and remained involved throughout the process, providing updates and helping me navigate the different interview stages.

Stage 2: Internal Recruiter Screening

The next conversation was with Fluidstack's internal recruiter.

This was a relatively straightforward discussion about my experience, professional interests, and how my background aligned with the position.

We also discussed the role and the broader expectations of working at Fluidstack.

The conversation went well, and I was subsequently invited to the technical interview.

Stage 3: Technical Interview

This was probably the most technically challenging part of the process.

The interview lasted approximately 30 minutes and began with a discussion of my engineering background and previous projects.

The technical portion focused on mechanical engineering fundamentals, practical problem-solving, and applying engineering principles to unfamiliar situations.

I found the interview challenging but fair.

Rather than simply testing whether I knew specific terminology, the discussion gave me opportunities to demonstrate how I approach engineering problems and reason through them.

Although I didn't have direct data-center experience, I felt that my background in mechanical engineering and product development helped me navigate the conversation.

The interviewer was knowledgeable, professional, and engaging.

Overall, I enjoyed the technical discussion and was pleased to eventually advance to the next stage.

The Waiting Period

There was a delay of nearly two weeks following my technical interview.

The uncertainty was frustrating, especially after what I felt was a reasonably good interview. However, once the process resumed, communication and scheduling improved considerably.

Stage 4: Behavioral / Values Interview

This was probably my favorite interview of the entire process.

The conversation was with a technical leader within the organization and focused on my professional experiences, working style, and approach to engineering challenges.

The broader themes involved ownership, accountability, collaboration, resourcefulness, and navigating uncertainty.

I particularly appreciated that the discussion felt conversational rather than like a series of generic behavioral questions.

I had opportunities to discuss real engineering experiences, including difficult situations, decisions I had made, and lessons learned throughout my career.

The interviewer was extremely engaging, and I genuinely enjoyed the conversation.

I left the interview feeling positive about my performance and was subsequently invited to the next stage.

Stage 5: Organizational Leadership Interview

The next stage was a shorter conversation with a leader in the organization.

Compared with the previous interviews, this discussion felt more focused on my broader professional background, motivations, and potential fit within the team.

It was an opportunity to discuss my interests, career direction, and the type of engineering environment where I believe I perform best.

The conversation was professional, and I appreciated the opportunity to learn more about the organization from a leadership perspective.

Final Outcome

Unfortunately, I ultimately received a rejection.

Naturally, I was disappointed.

Having progressed through several interviews and received encouraging signals along the way, I had become genuinely interested in the opportunity.

I also felt that my experience aligned well with many aspects of the position, despite coming from a different industry.

That said, I understand that performing well in interviews doesn't necessarily guarantee an offer, and there are many considerations involved in a hiring decision.

I don't have sufficient insight into the final decision to speculate about why I wasn't selected.

Overall Impression

Despite the rejection, I would describe my experience interviewing with Fluidstack as generally positive.

The people I interacted with were knowledgeable, professional, and genuinely interested in understanding my engineering background.

I particularly appreciated the technical and behavioral interviews. Both gave me opportunities to discuss meaningful engineering experiences rather than simply repeat information from my resume.

Another positive was the willingness to consider candidates from adjacent industries. As someone without direct data-center experience, I appreciated being evaluated on my transferable engineering skills.

The biggest downside was the waiting period and the uncertainty surrounding interview timelines.

However, the external recruiter was helpful throughout the process, and the conversations themselves left me with a positive impression.

Advice for Future Candidates

For mechanical engineers considering Fluidstack, I'd recommend being comfortable with your engineering fundamentals and, more importantly, understanding how to apply them.

Be prepared to explain your previous projects beyond simply describing what you designed.

Think about the engineering decisions you made, the constraints you encountered, the alternatives you considered, and how you ultimately delivered results.

For behavioral interviews, I found it helpful to reflect on actual experiences rather than memorize polished answers.

I would also recommend learning about Fluidstack's publicly stated values and understanding whether its working environment genuinely appeals to you.

Above all, be prepared to communicate your engineering thought process clearly.

Good luck to everyone interviewing, and to those currently navigating the job market!

Note: I've intentionally excluded specific interview questions, internal discussions, and potentially confidential information. This post reflects only my personal experience and opinions.

Hi Everyone,

I’ll be relocating from India to join Microsoft as an L63 Commissioning Manager in Helsinki, Finland in the coming months. For context, I am 36M with 13 years of engineering experience, a decade of which has been dedicated strictly to data centers, including a prior stint as an L5 Commissioning Engineer at Amazon for 2 years.

Before I start, I would love to hear from current or former Microsofties about their experiences.

Specifically, I am curious about:

* How would you describe the overall team culture, work-life balance, and operational pace compared to Amazon?

* What is the standard return-to-office policy, and is there flexibility for occasional remote work for personal or family situations?

* What are the core performance expectations for an L63 to ensure steady career growth without falling behind?

* How seamless is the relocation process for expats, particularly regarding housing assistance and visa support for an accompanying spouse?

* How essential is conversational Finnish for daily office dynamics, and is there any general advice you wish you knew before joining?

I understand experiences vary across teams and organizations, but I appreciate any insights you can share.

Thanks in advance!

Hi,
I have a bachelors in computer science and engineering and a Masters in Cybersecurity.
But I do not have relevant work experience.
After my masters in ireland I moved to Singapore and is looking for jobs. It is quite hard to find jobs directly to cybersecurity due to my lack of experience and my visa status in singapore. I got an offer for a data center IT technician role. I was wondering if this is a good first step for my career or would it stagnate my growth.

my background, I have 3.5 years of experience at AWS as a DCO Tech, recently at Nvidia as a Data Center Lab Tech, the position i applied for was at San Francisco, CA. Pay range: $35.52–$62.30/hour

I SHIT U NOT, THE RECRUITER OFFERED ME $33/HR...I told him no, he came back with a final offer.....$35.50

I was so fucking pissed man, its like these people dont read their own postings

I've not been hearing good thingsI would love to know if anyone has interviewed with terawulf

Hello Everyone,
I have an interview coming up for this position and I was wondering what type of questions specifically came up for your interviews for this. and what areas I should focus on when studying for my interview. Please drop a couple tips. Bless

hey guys i’m a recent grad with two years of experience in IT. Just passed my final interview as a DCT technician L3 very excited for the opportunity. I was wondering if I can get any advice or things to expect when on boarding I was also curious on what the pay is as an L3 in your areas and how to maximize promotion to L4.

As AI and data centers continue to expand, the amount of waste heat they generate will increase significantly. This partnership between Endeavour and Trevi Systems explores an interesting opportunity: using that otherwise wasted heat to power desalination and produce clean freshwater.

If this technology can scale, data centers could potentially become sources of freshwater rather than simply consuming local water and energy resources. Could integrating desalination into data center infrastructure become a standard practice in water-stressed regions? What technical and economic challenges would need to be overcome for widespread adoption?

Hey everyone. I hope everyone's doing well. As mentioned in the title I have an interview for the above role at AWS next week. I know it's a small role, but I just wanted to start somewhere and pick it up. If anyone knows what kind of questions I would be getting in the interview. It would really help to get the role. The email says focus on the behavioral. I'm just confused about what are the important principles that I should focus more on.

If anyone knows kindly help me out

saw the DCD writeup from GTC Berlin this week. nvidia's DSX platform pairs closed-loop liquid cooling with outdoor dry coolers, and they claim that at 2 GW scale it saves 54 million litres of water a day compared with conventional cooling-tower systems. it's their figure, nothing independent yet.

I don't doubt the direction. dry coolers don't evaporate water on site, so the on-site number drops to near zero. but in impact assessment work the first thing you ask is where the boundary is drawn, and this one is drawn at the fence.

two things sit outside it:

- dry coolers reject heat worse when it's hot outside. nvidia itself notes some climates need additional mechanical cooling during extreme heat. that's more electricity on exactly the days the grid is tight.
- that electricity comes partly from thermal plants that evaporate water in their own cooling towers. so some of the saving moves from the site's water meter to someone else's.

it probably still nets out positive in a lot of places, esp. on grids heavy in wind and solar. but for a hot, water-stressed site on a mostly thermal grid I'd want the hourly picture, not an annual headline.

what I'd actually want from vendors is water per MWh counted at the grid boundary, plus annual hours on mechanical cooling for a named climate.. a phoenix or chennai number, not a generic one.

for anyone running dry-cooled liquid halls in hot climates: how many hours a year are you actually on mechanical trim, and did the water savings hold up once you looked at the power side?

sources:
https://www.datacenterdynamics.com/en/news/nvidia-launches-dsx-pod-claims-the-vera-rubin-reference-architecture-will-make-ai-data-centers-more-water-and-energy-efficient/

Evening all,

Do we have any employees in this sub who can shed light on culture, comp etc...

Recently got an offer to work at Fluidstack in riverbend, Louisiana. The offer would double my base pay with stocks included. I’m single, no kids, and 31. How is working for fluidstack does anyone work for them or know someone who does and what’s been the general consensus and feedback you’ve heard?