Full-Stack Engineer
Location : Hyderabad (On-site)
Company : ADOSX Tech
Experience : 4–7 Years
Employment Type : Full-Time (with the risk appetite for working in a startup)
Own : End-to-end delivery of product features and the user-facing app, from
the Django API to the Next.js screens people actually use
About ADOSX
The future of automotive retail will not be software-enabled—it will be intelligence-driven and increasingly autonomous.
ADOSX is building a world-class AI-native operating system for automotive retail in India, combining agentic workflows, unified data platforms, and real-time intelligence into a single platform that helps auto-retail operate smarter, faster, and more profitably.
We're currently a four-member founding team—working directly with customers and building from idea to MVP. Backed by strategic investors from the automotive dealership ecosystem, our ambition is to redefine auto-tech space in the next five years.
This is not a 9-to-5 job. This is a builder's journey.
Joining ADOSX is closer to building a company than joining one. You'll work directly with founders, own products end-to-end, and experience both the 0→1 and 1→100 journeys while helping shape technology, culture, and customer outcomes.
We believe in high ownership, customer obsession, curiosity, bias for action, and having the courage to challenge assumptions. We value builders over titles and outcomes over hierarchy.
The truth is that early-stage startups are hard. There will be ambiguity, rapid change, and uncomfortable challenges. But there will also be extraordinary learning, genuine ownership, and the opportunity to create something that outlasts us.
Many people learn more in two years at a company like ADOSX than in ten years elsewhere.
If you want to help redefine how an entire industry operates, we'd love to build ADOSX together.
The Role
As the first full-time engineer at ADOSX, you will build the foundations that
future teams inherit. You are the engineer who turns the architecture into the
product people touch. You work across the whole stack, Django and DRF on the back and Next.js and React on the front, and you own the features end to end. Where the architect owns the dangerous core, you own the breadth: shipping the features and screens that make the product usable day to day, and building the integrations that feed them. You build agentically. AI coding agents are part of your daily toolkit and a big reason you ship fast.
You'll spend time inside dealerships, work closely with customers, and build systems grounded in operational reality—not assumptions.
What you'll own
Features end-to-end : You take a feature from data model to API to UI without
hand-offs: the Django models, the DRF endpoints, and the Next.js
screens, each built cleanly within the architect's boundaries.
The in-house integrations : Build and maintain the integrations to the external systems.
These are built in-house rather than bought, so you own the
protocol quirks, the version drift, and the reliability.
The user-facing app : The Next.js and React front end: the dashboard shell, data
tables, the AI chat surface, and the mobile-first screens for users
who are often on a phone in the field.
Messaging and scheduled flows : The customer-messaging integration (inbound webhooks,
queued outbound) and the scheduled jobs behind reminders,
follow-ups, and daily insight delivery.
Quality on your surface area: Tests, sensible error handling, and never breaking tenant
isolation or the audit trail, including when reviewing AI code.
What we're looking for
Solid full-stack delivery : Django and DRF plus React and Next.js, comfortable owning a
feature from database to UI on your own.
Agentic development as a habit: You use AI coding agents fluently to move faster, and you
review their output as carefully as a teammate's. You have caught
the subtle bugs they introduce.
Integration grit : You have wired up a fiddly third-party system and made it
reliable, and you do not flinch at messy upstream formats.
PostgreSQL fluency : You write the tenant filter every time and understand why.
Pragmatic and shippy : You prefer a working, tested feature today over a
perfect one next month, and you can estimate honestly.
A collaborator. You will pair with and unblock the juniors, and review their work.
Nice to have
- Celery or async experience, and front-end depth such as styled-components or a CSP-aware setup.
- Prior work integrating accounting, messaging, or other enterprise platforms.
- First six months, what good looks like
- The core transactional flow of the product works end to end in the user-facing app.
- The key in-house integrations are live and reliable on the pilot.
- The user-facing screens reuse a consistent component language and hold up on a mid-range phone.
You'll Thrive Here If
- You love ambiguity more than certainty.
- You prefer ownership over instructions.
- You think in systems, not tickets.
- You enjoy getting your hands dirty with customers.
- You learn by building rather than waiting.
- You use AI as leverage, not as a substitute for judgment.
- You want both the 0→1 and 1→100 journeys.
The Hard Truth
Early-stage startups are hard.
There will be ambiguity, changing priorities, and periods of intense execution because building from zero demands it.
But you'll own products end-to-end, work directly with founders and customers, and likely learn more in two years than many engineers do in ten.
If building the intelligence layer for Indian automotive retail excites you more than maintaining systems someone else designed, we'd love to build ADOSX together.
