Senior-Infrastrukturingenieur

Stellenbeschreibung:

  • Den Betrieb auf einem höheren Niveau sicherstellen. Sie machen unsere CI/CD‑Pipelines schneller und noch robuster, liefern zuverlässige Deployments aus und verwandeln jeden Vorfall in eine neue Lektion statt in eine Wiederholung.
  • Die Grundlage modernisieren. Buffer ist nicht neu, aber unsere Infrastruktur befindet sich in kontinuierlicher Verbesserung. Von der Bereitstellung von KEDA und Argo Rollouts bis zur Verbesserung unseres Signal‑zu‑Rausch‑Verhältnisses im Monitoring gibt es viel zu tun. Bei Modernisierung darf KI nicht unerwähnt bleiben: Wir nutzen sie bereits für Untersuchungen und Boilerplate und möchten sie noch tiefer in unseren Alltag integrieren.
  • Die Ingenieur:innen bei Buffer als Kund:innen behandeln. Sie entwickeln die Developer‑Tools weiter, die die innere Schleife beschleunigen, mit Dokumentation, die auch um 2 Uhr morgens oder beim Konsum durch einen Agenten noch Bestand hat.
  • Verantworten Sie die tägliche Zuverlässigkeit unserer Produktionsplattform. Halten Sie EKS, ArgoCD und die AWS‑Oberfläche unauffällig, stimmen Sie Autoscaling so ab, dass das System unter Last gut reagiert, und gehen Sie bei Incident‑Response so vor, dass uns jeder Vorfall etwas Neues lehrt, statt sich zu wiederholen. (Der On‑Call‑Dienst ist bei Buffer auf alle Ingenieur:innen verteilt, etwa eine einwöchige Schicht ungefähr einmal pro Quartal.)
  • Progressive Delivery zu etwas machen, dem das restliche Engineering vertraut. Implementieren Sie Argo Rollouts mit sauberen Rollback‑Pfaden, sodass die Zeit zwischen „dieses Deploy ist schlecht“ und „dieses Deploy wurde zurückgenommen“ in Sekunden bis Minuten gemessen wird.
  • Developer‑Tools als Produkte bauen, statt als lose Skripte. Entwickeln Sie unsere interne lokale Entwicklungsumgebung weiter, BIBEs (pro‑PR vollständige, isolierte Staging‑Build‑Umgebungen) und unsere CLI‑Tools, sodass die innere Schleife schnell, reibungslos und für AI/Agenten parallelisierbar ist. Messen Sie die Nutzung, sprechen Sie mit Ihren Nutzern und iterieren Sie.
  • Operativen Aufwand mit KI reduzieren. Automatisieren Sie risikoarme Workflows Ende‑zu‑Ende, damit das Team seine Zeit für die schwierigen Probleme verwendet, nicht für die sich wiederholenden. KI greift nicht direkt in die Infrastruktur ein; sie beschleunigt die Menschen, die daran arbeiten.
  • Den Stack aktuell halten. Treiben Sie Lifecycle‑Upgrades voran: Anwendungs‑Runtimes (Node.js, Python), Kubernetes, EKS, Helm‑Versionen und den Terraform‑verwalteten Infrastruktur‑Bereich. Verantworten Sie Sicherheitslücken auf Infra‑Seite.
  • Die Wirtschaftlichkeit unserer Plattform verbessern. Führen Sie Visibility‑Arbeit in Datadog, AWS‑Rightsizing und Log‑Filtern an, damit Observability und Cloud‑Ausgaben langsamer wachsen als das Unternehmen.
  • Mit EPD an der Plattform zusammenarbeiten, auf der sie bauen. Heben Sie mit dem Team die Dokumentationsstandards an, übernehmen Sie Ihren Anteil an der wöchentlichen Sicherheitsarbeit (Dependency‑ und Vulnerability‑Management ist jedermanns Aufgabe) und helfen Sie dem Infra‑Team, in Richtung geteilter Verantwortung und weniger Einzel‑Abhängigkeiten zu wachsen.

Anforderungen:

  • You've worked as an Infrastructure Engineer, SRE, "DevOps" engineer, or adjacent role for long enough to be considered senior.
  • You have hands-on experience operating production Kubernetes at scale on a managed offering (GKE, EKS, AKS), including authoring and maintaining Helm charts, and you're fluent with autoscaling primitives driving KEDA and the cluster auto scaler.
  • You have AWS depth across IAM, EC2, S3, SQS, ECR, and ALBs. You may have also used Cloudflare (WAF, Workers, etc.) and GCP (BigQuery).
  • You have strong Terraform skills. You default to modules for structure, and keep the code adaptable, readable, and self-contained. Bonus points if you contributed an OSS module.
  • You've operated production CI/CD with GitHub Actions (or equivalent) and GitOps via ArgoCD (or similar). You've authored ArgoCD pipelines and Helm configuration yourself, including canary or progressive delivery systems you'd trust to roll back safely.
  • You've built internal developer tools (CLIs, dev environments, per-PR environments) and you think about them as products with users, not scripts.
  • You have a track record of pragmatic build-vs-buy decisions on infrastructure tooling. You can defend a choice and revisit it when conditions change.
  • You've worked with DataDog, Sentry, or similar observability stacks, and you design logs and metrics with cost in mind. You know observability and cloud spend can grow faster than the company if no one is watching.
  • You're comfortable with the Cloudflare across Workers, Zero Trust, DNS, and the rest of their platform.
  • You read and modify TypeScript or Node services well enough to upgrade runtimes and unblock teams (legacy PHP and Python show up too).
  • You're fluent with modern AI tools. You use them to debug, document, and reduce toil, not just to generate code, and you bring those patterns into how infra runs.
  • You're proactive and you follow through. You spot what needs doing before you're asked, and you close the loop without being chased.
  • You turn ambiguity into proofs of concept. You take fuzzy asks, ship something rough teammates can react to, and iterate with them until it lands.
  • You thrive in remote, asynchronous environments. You're clear in your thinking, generous with context.
  • You don't wait for perfect information to start, and you don't wait for perfect to ship.
  • You see infra as a force multiplier for engineering, not a gatekeeper.
  • You care about Buffer's customers. When things are slow for them it's painful for you to see. When errors are flaky you find the root cause and try to eliminate the entire class of problem, because you see the system, not the bug.
  • You care about performance. If it's too slow to use, it shouldn't exist. You'd rather make it fast than work around it.
  • You're a generalist engineer with strong spikes: T-shaped folks with depth in infrastructure and the flexibility to pivot as priorities shift.
  • You create, not just consume. Open source contributions, a technical blog, conference talks, side projects, or active accounts on the platforms Buffer serves, your pick. We're a Team of Creators ourselves, and the closer infra is to the creator's experience, the better the platform becomes.
  • You think about infrastructure as a platform with users. APIs, SDKs, CLIs, MCP servers, or developer-facing tooling you've shipped where adoption, not just deployment, was the success metric. You've felt the difference between code that ships and code that gets used.
  • You play the long game. You'd rather invest in compounding fundamentals than chase the platform-of-the-month.
  • Bonus points if you're already a Buffer user or familiar with social media management tools.

Leistungen:

  • Offers Equity
Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...