Sr. Platform Engineer

Senior Platform Engineer Full-stack build and containerized deployment of enterprise workflow platforms EXPERIENCE 5–8 years EMPLOYMENT Full-time LOCATION [City], India · [Onsite / Hybrid / Remote] TEAM Cross-functional POD REPORTS TO [Engineering Manager / Delivery Lead] TECH STACK Flexible — see skills below About Codvo Codvo.ai is a technology and product-engineering partner that designs, builds and supports enterprise digital platforms. Through our Product Oriented Delivery (POD) model, we bring strategy, design and product engineering together in small, self-contained agile teams that own outcomes end to end. About the Role We're looking for a Senior Platform Engineer who can take a workflow-heavy enterprise platform from data model to production. You'll be the core builder in a small POD, owning the application end to end — data model, APIs, workflow logic and responsive UI — and packaging it as a containerized runtime deployed to the client's own cloud. Our delivery cycles are short and fixed-scope, so we value engineers who make sound design calls quickly and ship working software every week. Your First Engagement An enterprise fault-ticketing, field-service and Repair & Return (RMA) platform for a networking and communications equipment services company. It covers the full lifecycle of a customer-reported fault: customer and project onboarding (Supply, AMC and Warranty projects), fault logging with unique docket IDs, SLA-driven triage and engineer assignment, site-visit and remote-support reporting, fault analysis with automatic RMA generation, and repair coordination with OEMs and local vendors through to dispatch and closure. Delivery runs as a roughly 5-week build, 2-week UAT and 1-week hypercare, followed by ongoing maintenance and support. Key Responsibilities Architecture & data model • Design a single, normalized data model connecting customers, projects, sites, equipment, tickets and RMA records, with full traceability from a fault docket through repair and closure. • Make pragmatic stack and architecture decisions for a fixed-scope, fixed-timeline build, and document them clearly for the team and for handover. Workflows & business logic • Build the ticket lifecycle as explicit, configurable state machines (fault, engineer and repair & return statuses), including assign / reject / reassign loops and branching repair paths — working unit, repairable via OEM or local vendor, and non-repairable replacement. • Implement unique docket and RMA number generation, SLA and response-time calculations (business hours vs. 24x7, holiday calendars), and warranty/AMC validity checks against master data. • Implement role-based access control and user provisioning for customer, admin, field-engineer and repair-manager roles, including password policy. Web application • Build a responsive, mobile-friendly web app that field engineers can use on site: list and detail views, dynamic forms with per-type mandatory/optional validation, and auto-population of equipment, sub-system and serial data from master records. • Deliver bulk CSV import with template download, row-level validation, duplicate detection (within the file and against existing records) and partial import of valid rows. • Handle document, image and video uploads with previews, type and size limits, and secure storage. Reporting & notifications • Build operational reporting — cycle-time reports, status-distribution dashboards, filters by project, type, engineer and date — with CSV/PDF export and printable field reports. • Wire event-driven email (SMTP) and in-app notifications for key status transitions. Deployment & operations • Package the application as hardened container images and deploy them to a client-provided cloud (AWS, Azure or GCP), delivering runtime artifacts rather than source code. • Set up CI/CD, environment configuration and secrets management, database migrations, logging and monitoring, and run production cutover. • Turn around UAT defects quickly, support hypercare, and handle incident diagnosis, security patches and compatibility updates during the maintenance period. Delivery & collaboration • Work with the Product Owner to break scope into stories, estimate honestly, flag risks early, and separate defects from change requests. • Review code, set engineering standards for the POD and mentor other engineers. • Run knowledge-transfer sessions and produce concise technical and admin documentation. Must-Have Skills & Experience • 5–8 years building and shipping production web applications, with at least 2 years owning features end to end (UI, API, database and deployment). • Strong in a modern front-end framework — React preferred; Angular or Vue acceptable — with TypeScript and responsive design. • Strong in at least one backend stack — Node.js/TypeScript, Python, Java/Spring Boot or .NET — and in REST API design. • Solid relational database skills (PostgreSQL, MySQL or SQL Server): schema design, indexing, migrations and reporting queries. • Proven experience building workflow- or state-driven business applications such as ticketing, case management, service management or order/returns processing. • Hands-on with authentication and role-based authorization, file storage, email integration, and server-side PDF/CSV generation. • Practical Docker and CI/CD experience (GitHub Actions, GitLab CI, Azure DevOps or Jenkins), with deployments to at least one major cloud. • Writes automated unit and integration tests and cares about code quality. • Clear communicator, comfortable working directly with client stakeholders. Good to Have • Experience with field service management, ITSM/helpdesk, RMA/reverse logistics, or warranty/AMC tracking. • Kubernetes or managed container services (ECS, AKS, Cloud Run, App Service) and infrastructure as code (Terraform, Bicep). • Delivering into customer-owned environments with restricted access and security reviews. • Background jobs and queues; time-zone and business-calendar calculations. • Hands-on with AI-assisted development tools (e.g., Claude Code, GitHub Copilot, Cursor) to speed up delivery. • Familiarity with OWASP practices and container image scanning. What Success Looks Like • A working vertical slice (onboarding → fault logging → engineer assignment) within the first two weeks of the build. • All modules feature-complete and running in a staging environment inside the build window. • UAT closes with only minor defects, and production go-live and cutover happen on schedule. • The platform runs stably through hypercare, and support can be