🎁 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 →
Tekion runs dealership operations in the cloud, which means customer, financial and vehicle data across thousands of retail sites, and this role protects it. It is a hands on mid level security engineering seat rather than a policy job. You implement and maintain security tooling, monitoring and access controls, run vulnerability management from scanning through analysis to remediation coordination, take part in incident detection, response and root cause analysis, and perform security assessments of applications, systems and cloud environments. Threat modelling and risk assessment for new projects are in scope, as is keeping the company aligned to SOC 2, ISO 27001 and NIST. The posting says the role works on moderately complex projects with minimal supervision, which is a fair description of what a second level security engineer is usually asked to do without being told. Who it is for: Tekion asks for a Bachelor's degree in Computer Science, Cybersecurity, Engineering or a related field (equivalent experience considered) and 4 to 6 years of experience in security engineering, IT security or related roles. Required knowledge: strong understanding of network, application and cloud security principles. Experience with security tools including SIEM, IDS and IPS, vulnerability scanners and endpoint protection. Knowledge of cloud platforms (AWS, GCP, Azure) and their security services. Familiarity with compliance and security frameworks (NIST, ISO 27001, SOC 2, CIS). Scripting or automation experience in Python, Bash or equivalent is preferred. Strong analytical and problem solving skills and good written and verbal communication. Industry certifications such as CISSP, GSEC or CEH are preferred, not required. Day to day: implement, configure and maintain security tools, monitoring systems and access controls. Support vulnerability management including scanning, analysis and remediation coordination. Participate in incident detection, response and root cause analysis. Work with engineering and IT to embed security practice into development and infrastructure. Help maintain compliance with SOC 2, ISO 27001 and NIST. Perform security assessments and testing of applications, systems and cloud environments. Contribute to threat modelling and risk assessments. Maintain security documentation, runbooks and knowledge bases. Provide guidance and mentorship to junior engineers. Location: Bangalore HQ. Honest fit guidance: this is a broad generalist security seat, not a specialist one. You touch tooling, compliance, incident response and assessment rather than going deep on any single one, which suits someone who wants range at the 4 to 6 year mark and suits a specialist less well. The certifications are preferred rather than required, so do not self reject over them. .
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.