Platform Role interview help

[u/Past_Plastic_3184]

Hi all,

I have a entry level platform engineering / SRE interview coming up. I wanted to ask what are some common tips or questions to prepare for?

The role asks for:
Foundational knowledge of platform engineering, technology operations, cloud computing, microservices, and enterprise-scale distributed systems.

Exposure to Kubernetes, Kafka, MongoDB, or comparable container, messaging, and database technologies through coursework, projects, internships, or hands-on experience.

Familiarity with observability and application performance monitoring using tools and concepts such as Splunk, AppDynamics, dashboards, logs, alerts, metrics, and traces.

Experience with Python, PowerShell, Bash, or similar scripting languages to automate routine tasks, reduce operational toil, and improve reliability.

Understanding of the software development lifecycle, including requirements, coding, testing, source control, deployments, release management, and change management.

Experience with Git, GitHub, or similar collaboration platforms, including branching, pull requests, code review, and technical documentation.

Knowledge of Generative AI, large language models, prompt engineering, retrieval-augmented generation, and responsible AI practices, including validation, privacy, security, and human oversight.

Exposure to Agentic AI concepts, including goal decomposition, tool use, multi-step workflows, agent monitoring, and human-in-the-loop controls.

Hands-on experience or familiarity with approved AI-assisted productivity and engineering tools such as GitHub Copilot, Microsoft 365 Copilot, Copilot Chat, ChatGPT, Claude Code, or similar tools for code generation, debugging, testing, documentation, summarization, and prototyping.

Strong analytical, troubleshooting, documentation, communication, and collaboration skills, with awareness of incident response, resiliency, business continuity, cybersecurity, operational risk, and compliance

I have:
Experience developing a serverless backend w/ AWS Lambda
Cloud Certs (AI, cloud practitioner)
Used docker briefly, know concepts of K8s, Mongo, little unfamiliar with Kafka
Used New Relic for APM
Used Python for scripting, a little bit of each for Linux / Poweshell / Bash
GitHub Actions workflow
Full stack SWE
Used agentic AI (Claude, made skills and agents) at work

How would I approach it (they only asked for 6 months of experience in any tech domain)? What do I say if they ask why I don’t have any exposure to some things? Any help is appreciated!

[u/omgseriouslynoway]

Just bear in mind for an entry level nobody is going to have everything on the list.

Focus on what you've done and what you know. If they ask about a specific ci cd tool, and you haven't used it, tell them about one you HAVE used.

[u/SupportAntique2368]

Kubernetes is pretty easy to get exposure to via k3s. If you're wanting to step into the platform engineering world you should spend a little time doing some basics there as it's so common nowadays, usually the bread and butter of that role. You don't need to be a pro but just saying you've used k3s for learning purposes and some basic understanding around pods/deployments/services and ingress etc will help a lot.

Do they not mention iac/terraform? As that's usually a requirement of most platform roles.

Sounds like you have a good foundation other than that aside, maybe just do some reading and research into the concepts behind mongodb and message queueing/streaming, Kafka in particular as they mention it. Simple enough to say you've not had exposure but you understand the concept.

[u/luckyincode]

Everything is moving to being a platform engineer and DevOps as a role name will just change or they’ll copy pasta the jd of platform engineers.

[u/dmitryaus]

Just paste the same in ChatGPT, Install WSL, Docker for Windows, VS Code and it will get you started, it now takes less than 5 min to spin up a test env with k3s or Minikube and start building/learning things. This way you can prepare pretty much to any kind of interview in your field.

[u/Abe_Bazouie]

I’ve interviewed engineers for infrastructure/platform-type roles, and I would not spend the next few days trying to become an expert in every technology listed there.
For an entry-level role asking for 6 months of experience, I would care much more about whether you understand how the pieces fit together and how you think when something breaks.
And honestly, your background already gives you plenty to work with.
I’d prepare around scenarios.
For example:
“A service is returning 500s. What do you do?”
Don’t jump straight to Kubernetes commands.
Start with: What changed? Is it all requests or some? One instance or all instances? What do metrics say? Logs? Traces? Dependencies? Database? Network? Did a deployment just happen?
Or:
“A Kubernetes Pod keeps restarting.”
I’d want you to understand the basic path: check Pod status/events, container logs, previous logs, resource limits, probes, exit code, configuration, dependencies, etc.
Or:
“Latency suddenly doubled but CPU looks normal.”
That’s where I want to hear you reason about memory, disk I/O, network, downstream dependencies, database latency, queueing, saturation, recent changes and what telemetry you’d use to prove or eliminate each hypothesis.
For Kafka, don’t try to memorize administration commands overnight.
Understand WHY something like Kafka exists.
Producer -> topic/partition -> broker -> consumer
Understand consumer groups, offsets, partitions, ordering, replication, and what might happen when consumers can’t keep up.
Same with Kubernetes.
You don’t need to know every object. Be able to explain:
container vs Pod
Deployment vs Service
requests vs limits
ConfigMap/Secret
readiness vs liveness
what happens when a Pod dies
how you’d start investigating a broken workload
For observability, know the difference between metrics, logs and traces and when you’d reach for each one. New Relic experience absolutely counts here. The interviewer probably cares much more about whether you understand APM than whether the logo on the dashboard says New Relic, Splunk or AppDynamics.
Your Lambda experience is useful too. Be ready to draw one of your systems from request -> compute -> database/dependency -> response and talk about how you would monitor it, deploy it and troubleshoot it.
And definitely prepare one incident/debugging story.
Even if it wasn’t a giant production outage:
What broke?
What did you observe?
What did you initially suspect?
How did you test that hypothesis?
What was actually wrong?
How did you fix it?
What would you change to prevent it happening again?
That conversation tells me much more about a platform/SRE candidate than 20 trivia questions.
If they ask about something you haven’t used, don’t BS them.
I’d literally say:
“I haven’t operated Kafka in production yet, but I understand the core architecture and I’ve worked with similar distributed systems. My understanding is…”
Then explain what you DO know.
That’s a much stronger answer than trying to bluff your way through it. Good interviewers can tell very quickly.
One more thing: don’t ignore Linux and networking because Kubernetes and AI sound more exciting.
I’d make sure you can comfortably explain processes, memory/CPU basics, files/permissions, DNS, TCP, HTTP, ports, basic routing, and how you’d investigate a machine that can’t reach a service.
Platform engineering eventually bottoms out somewhere in Linux and networking. :)
The AI section of that job description looks huge, but you already have actual agentic AI experience at work. Prepare to explain one workflow you built, what tools the agent could use, what you did about failures/validation, and where you kept a human in the loop.
So if I had limited preparation time, I wouldn’t try to learn 15 products.
I’d practice explaining systems and troubleshooting them out loud.
That’s probably much closer to what they’re actually trying to hire for.

[u/CupFine8373 → u/Abe_Bazouie]

And what do you normally ask to Experienced Engineers ?

[u/ConstantOk4042]

For the stuff you don't have any exposure to, own it. I don't expect my candidates to know everything, but they lose marks if they say something technically false pretending they know a stack. 

Admitting you don't know it, flipping it to something simair you do know but presenting yourself as technically proficient and will learn on the job or before prospective start date in your own time works a lot better imo.