🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Job description About The Team The Platform Security team at Tide plays a crucial role in safeguarding our cloud environments and protecting our Members, partners, employees, and intellectual property. As a Platform Security Engineer within this team, you'll work closely with the Platform Team, Risk Team, and the broader Tide Engineering teams. Your role will involve enhancing the visibility of our cloud resources and ensuring the secure configuration of our infrastructure. At Tide, you'll find your work particularly fulfilling due to our company culture and the exceptional people you'll collaborate with. About The Role As a senior platform security engineer you will Designing next generation cloud infrastructure to ensure it is kept up do date without reliance manual processes like patchingDefining and embedding security best practice and standards into our cloud engineering teamsBuilding guardrails and defining policy around IAM to ensure least privilege is enactedIdentifying ways to make sure new security misconfigurations are not created via IaCHardening our existing cloud infrastructureReviewing cloud integrations between Tide and any third parties and be a point of contact for any cloud security incidentsWhat We Are Looking For You have good infrastructure security experience and passionate about tackling risks from misconfigurationsYou have deep expertise in at least one public cloud, preferably AWS or GCP.You are familiar with docker and containerised applications.You have a good understanding of Kubernetes and how to secure workloads running in a Kubernetes cluster.You are familiar with the cloud-native approach to implementing workloads in a Kubernetes cluster.You are comfortable with writing CI/CD pipelines using GitHub Actions or any other CI/CD tools such as Jenkins, GitLab Actions, CircleCI etc.You are able to review and write Terraform and are able to propose improvements to external providersYou write reliable software in Python or GoYou have operations experience in running and maintaining software, operating a large cloud deployment, or creating and triaging alerts around the health and security of your systemsYou work well with other people, see the value of a team, and partner effectively with all stakeholdersYou thrive by identifying high leverage work and doing it without explicit directionYou aim to always be learning new things and share this passion with those around youWhat You'll Get In Return Competitive salarySelf & Family Health InsuranceTerm & Life InsuranceOPD BenefitsMental wellbeing through PlummLearning & Development BudgetWFH Setup allowance15 days of Privilege leaves12 days of Casual leaves12 days of Sick leaves3 paid days off for volunteering or L&D activitiesStock Options .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.