I recently graduated and have three different job offers that I'm trying to decide between, all of which are in the platform engineering space but vary a bit in focus. The pay is similar across all of them, but I'm unsure which would be the best fit for my career goals.
1. **Job 1**: As a Platform Engineer, I'd be working on creating tooling and SDKs to help developers provision their own infrastructure. This role also involves managing cloud infrastructure, allowing devs to easily set things up. There's a focus on building reusable modules for logging and monitoring, which sounds exciting, but I'm concerned about unclear expectations regarding my day-to-day tasks and the team dynamics.
2. **Job 2**: This position is with a technical consulting company that specializes in building multi-cloud Kubernetes platforms using open-source tools. They assured me there would be no non-technical work involved, which I like. This job also leans heavily on Terraform and other tools without much software development on my end.
3. **Job 3**: This role involves building an internal developer platform (IDP) for a company with around 2000 developers, starting from scratch. My concern here is whether this might distance me from my goal of focusing on infrastructure and tooling in the long run.
I'm leaning towards something like Job 1 for the future, but I'm worried about the lack of clarity about my specific tasks. Would Job 2 still allow me to pivot towards more development-focused work later on?
6 Answers
When deciding, consider the benefits like salary, vacation time, and how close the job is to your home. All three look impressive for a new grad, so focus on other factors that matter more than just the specifics of the jobs.
If you're aiming for a future in infrastructure software, Job 2 might be your best bet for building strong foundations while maintaining flexibility. Also, check out prepare.sh for tailored interview questions that could clarify your role better.
Software development is critical these days, and even platform engineers need to be comfortable with deploying software. Don't lose sight of that as you choose your path.
As a newcomer, finding a role with good mentorship is key. Look for jobs where you'll have the opportunity to learn from experienced colleagues who can guide you along the way.
From my experience, starting in consulting gives you a great advantage. You'll be exposed to various technologies and clients, helping you build a diverse skill set and expand your professional network. I got referrals that significantly helped my career progression after starting in consulting.
It really depends on your long-term goals. Jobs 1 and 3 seem like they offer more opportunities for development-related work, while Job 2 appears more focused on client-specific deliverables. Ask yourself what excites you more: building tools or constructing infrastructure for clients? It's vital to think 3-5 years ahead and consider which job aligns with your future aspirations.
That's a solid approach! I'm still figuring things out post-graduation, but I want to lean towards development tools. Do you think I can pivot towards that path even from Job 2?
That's a good point! But I'm also worried about the lack of software development in Job 2. If I want to write infrastructure tooling later, will not coding at Job 2 hinder that path?