Let me be straight about where I am. I joined Netradyne in July 2024 as an Associate Software Engineer and was promoted to Software Engineer within six months. Netradyne builds fleet safety systems — telemetry streaming off vehicles on the road, turning into alerts a fleet manager acts on. When an alert is wrong, someone stops trusting the product.
My work there is backend quality and automation, not feature development. I write the API test suites for the Speeding V2 microservices, debug the Alert Geofence module end to end through REST endpoints, database queries and event flows, and I built the automation that replaced our manual API regression pass. It's a job spent reading other people's services closely enough to find what they got wrong.
I want the other chair. Not because testing is beneath me — because two years of it taught me what careless design actually costs, and I'd rather be the one making those calls than the one filing them. So I've built three backends on my own time, each one aimed at a failure mode I've watched cause real damage: a charge that fires twice, an event that never leaves the service, inventory sold to two people at once.
I also don't think the automation background is a detour. Most production bugs aren't in the logic somebody wrote — they're in the seams between services, where a retry wasn't planned for or two writes were supposed to be one. Finding those for a living is decent preparation for building things that don't have them.
What I'm after is an SDE-1 backend role on a team that owns services in production, anywhere in India or fully remote. I'd be joining as someone early in backend work with real depth in a narrow slice of it, and I'd want reviewers who care about correctness enough to tell me when I'm wrong.
I'd rather a system refuse a request honestly than accept it and be wrong about it later.