🎁 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 →
Who Are We Raptee.HV is a full- stack electric motorcycle startup with a very strong technical moat, founded in 2019 by four engineers from Chennai (Ex Tesla, Wipro), working on bringing a no-compromise upgrade motorcycle to an otherwise scooter- only EV market. Raptee is incubated at CIIC & ARAI. Role Overview We are looking for a hands-on DevOps Intern to join our infrastructure and platform engineering team. You will be building and standardizing the CI/CD backbone that powers everything from firmware builds and VCU software to cloud backend services and mobile apps. This is not a shadow-and-observe role you will own concrete pipelines, standardize environments, and ship tooling that every engineer at Raptee depends on. You should be comfortable with Linux internals, have a bias for automation, and care about the quality gates that keep codebases clean at scale. What Youll Do Static Analysis Pipeline: Design and integrate a multi-project static analysis pipeline covering Flutter (App and VCU) and Golang codebases. This includes configuring linters, enforcing complexity thresholds, setting coverage gates, and wiring analysis stages into existing CI workflows so failures block bad code from merging. Docker Standardization: Audit, design, and roll out standardized Docker environments across the organization covering development, build, and test contexts. Containers must behave consistently across developer machines, CI agents, and deployment targets. Write and maintain Dockerfiles and Compose configurations that eliminate "works on my machine" permanently. Jenkins Pipeline Engineering: Improve existing Jenkins pipelines currently handling firmware and embedded builds. Extend coverage to additional projects, reduce build times, improve failure visibility, and implement best practices around stage isolation, artifact management, and post-build reporting. Process & Tooling Documentation: Produce and maintain runbooks, onboarding guides, and infrastructure playbooks. Documentation here is a first-class engineering artifact it must be accurate, minimal, and structured so that a new engineer can be productive from day one without hand-holding. Who Can Apply Graduated or pursuing B.E./B.Tech in Computer Science, Computer Science (Hons.), or Information Technology (IT/CS). Linux Proficiency: You must be deeply comfortable in a Linux terminal. Shell scripting (Bash) or Python automation for system tasks is expected you should be able to write a script to automate a repetitive workflow without being asked how. Containerization: Hands-on experience with Docker is required. You should understand layered image builds, bind mounts vs volumes, network modes, and multi-stage builds. Experience writing production-grade Dockerfiles not just tutorial-level docker run usage. CI/CD Fundamentals: Solid understanding of continuous integration and delivery concepts. You should be able to read and reason about an existing pipeline, identify bottlenecks or gaps, and propose concrete improvements. Exposure to Jenkins, GitHub Actions, or any equivalent platform is expected. Code Quality Tooling: Familiarity with static analysis, linting, and test coverage tooling in at least one compiled or strongly-typed language. Understanding why these gates exist not just how to configure them matters here. Systems Thinking: Interest in how software systems are built, deployed, and operated at the infrastructure layer. You should be curious about what happens below the application code build systems, process isolation, resource constraints, and failure modes. Tooling Fundamentals: Proficiency with Git, Linux CLI, and debugging in a headless or remote environment. Comfort working with config files, environment variables, and build manifests without a GUI. Good To Haves Hands-on experience with Jenkins shared libraries, declarative pipelines, or multi-branch pipeline setups. Exposure to Flutter/Dart or Go codebases even reading and navigating them without writing production code. Familiarity with AWS services relevant to CI/CD or infrastructure (ECR, ECS, S3, IAM, CloudWatch). Interest in automotive software, embedded Linux (AGL), or firmware build tooling. A prior internship where you shipped something to production not just ran commands in a sandbox. Whats In It For You Opportunity to work in a fast-paced and dynamic environment. Opportunities for professional advancement as the company undergoes expansion. A culture that fosters collaboration and creativity within the team. Collaborate closely with seasoned experts in the field. Gaining an entry point into the field of automobile development. .
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.