Adevinta

How I run my weekly server room check in 20 minutes, the exact checklist, the exact sequence, and why each step exists. Those 20 minutes have caught issues before they became incidents more times than I can count. Here is the exact sequence and, more importantly, why each step exists: 🔌 POWER (5 minutes) □ UPS front panel battery health indicator, any fault lights? Why: UPS batteries degrade silently. A fault light here means your next power event has no protection. □ PDU outlet load any circuits above 80% capacity? Why: 80% is the safe limit. Above it, you have no headroom for a planned addition to the maintenance load. □ Generator last test log (if applicable) Why: Generators that are not tested monthly may not start when needed. 🌡️ ENVIRONMENT (5 minutes) □ Ambient temperature reading target 18 to 27°C (ASHRAE A1 class) Why: Persistent high temperatures accelerate hardware failure. Small deviations compound over months. □ Walk the hot aisle for any localised hot spots? Why: Hotspots form before temperature sensors trigger alerts. A physical walk catches what sensors miss. □ CRAC/CRAH unit status no fault indicators, filters checked? Why: A clogged filter degrades cooling efficiency. It is also a fire risk. 🔧 HARDWARE (5 minutes) □ Visual inspection of all racks for any amber or red LED indicators? Why: Amber means degraded. Red means failed. Both need investigation before they become outages. □ Cable management for any recently changed cables that are not secured? Why: An unsecured cable can be caught, pull a connection, and cause an intermittent fault that takes hours to trace. □ Any hardware recently installed not yet in the asset register? Why: Undocumented hardware is a security risk and a maintenance liability. 📡 NETWORK (5 minutes) □ Core switch uplink interfaces all green? Why: A degraded uplink often operates at reduced speed before it fails. Catching it early means a planned fix. □ Are any interface error counters incrementing? Why: Error counters indicate physical-layer issues, such as a bad cable, a bad SFP, or a duplex mismatch, before they cause user-visible problems. □ Patch panel any cable labelling issues from recent changes? Why: Documentation degrades with every change that is not documented in real time. 20 minutes. Every week. Without fail. #ServerRoom #DataCenter #DCEngineer #ITOps #ServerRoomMaintenance #UPS #Infrastructure #Berlin #DACH #TechTips #SysAdmin #DCOps What's on your server room checklist that I haven't included? 👇

During my current job search, I had the pleasure of interviewing with a company that truly stood out, not just because of the role itself, but because of how the process was handled. First, the speed. After applying, I was contacted quickly. No weeks of silence. Just a clear, timely response. Simple, yet rare. But what really impressed me was what came before the first interview: they shared their full interview process ahead of time. A genuinely well-structured, user-friendly overview that included: ✅ Time dedicated to each step ✅ Stakeholders involved at each stage ✅ Expected waiting time between steps (YES PLEASE!) I have never, in all my years of interviewing, encountered such clear and organised communication around a hiring process. And if you know me, you know I am a total geek for structure, organisation, and clear communication. But beyond my personal appreciation for a good process, this kind of transparency does something much more meaningful: it kills the anxiety. Because that anxiety is real. Anyone who has been through a job search knows it intimately. It lives in the silence. It sounds like: — Will they contact me at all? — Will they let me know if the answer is no, or do I just... never hear back? — It's been a week. Should I follow up? Is it too soon? Too late? — How long do I keep this opening on my radar before I move on? When no timeline is given, candidates are left in a mental limbo that drains energy, attention, and confidence. Sharing the process in advance doesn't just feel professional, it's a genuine act of respect toward the person on the other side. Which brings me to a question I keep coming back to: how urgent is an opening, really? Companies speak of roles as business-critical, urgent, a priority. Yet in many cases, the application window stays open for weeks, sometimes months, before candidates receive any reply. The urgency is communicated internally, but the candidate? They wait. And wait. And wonder. I'm not a recruiting expert, and I know hiring pipelines are complex. But if a role is truly urgent, shouldn't the time-to-reply reflect that? Weeks of silence after an application isn't just frustrating, it sends a signal about how a company values people's time, even before day one. One company recently showed me a very different way. And it left a mark. 🙌 #JobSearch #CandidateExperience #Hiring #Recruiting #OrganisationMatters #Transparency

I'm very excited about attending this and seeing Elizabeth (Liz) Kalnin in action (again) 😍! Sign up while seats are still available!

🙋♀️RECRUITER QUESTION!🙋♀️ How does one go about securing a REAL/legitimate recruiter who is not after my money, is helpful, and doesn't 👻 me? Does it depend on sector, geography, or company specific? So far I've worked with 2, one of whom was tied to a specific company and helpful for a bit, and another who swore he'd help me no matter what, but neither were ever heard from again! I'd love to know how it works, even if I'm the only one who doesn't know! #recruiter #opentowork #HigherEd #ChangeManagement #Healthcare #Tech #HowDoesItWork

I’m happy to share that I’ve completed the Product Management program at Hero Camp. My goal wasn't to learn the 'what' of PM—having been in the trenches for years—but to master the 'how' of the future. Specifically, I focused on integrating Generative AI into the product lifecycle to accelerate discovery and sharpen decision-making. It’s been an incredible experience refining my frameworks and ensuring my approach to building products remains at the cutting edge.