About the role
We build production web platforms for clients who need software that works, scales and can be handed off cleanly. You'll work across the stack, from interface to API to data model, in small, senior-led teams.
This is a hands-on role. You'll ship every week, own quality, and help clients' teams level up in the process.
Your team
You'll be part of a senior engineering group that shares patterns across engagements, with weekly engineering reviews and knowledge sharing.
The impact you'll have
Shippable every week
Small, reviewed increments that reach users quickly.
Quality you can trust
Tests, observability and CI that make releases boring.
Clean hand-off
Documented, maintainable code that client teams are happy to own.
What you'll do
- Ship features end-to-end across frontend, APIs and data layers
- Own quality through tests, reviews and observability
- Break down ambiguous problems with product and design
- Raise engineering standards on every engagement
A typical week might include
- Standup with the product team
- Building a feature end-to-end
- Code review and pairing
- Improving test coverage and release tooling
Technical scope and expected depth
The areas this role may cover. The exact environment and priorities are agreed for each engagement.
Application and interaction design
Build responsive, accessible interfaces with explicit loading, empty, error, and recovery states. Connect interaction decisions to user research, domain rules, and measurable task completion.
Services and integration
Design APIs with clear contracts, authentication, authorization, pagination, validation, and failure semantics. Handle retries, idempotency, timeouts, and downstream dependencies deliberately.
Data and domain modeling
Choose data models and transactional boundaries around business invariants. Plan schema changes, migrations, query performance, retention, and compatibility with existing consumers.
Testing and release engineering
Use focused unit, integration, and end-to-end checks around meaningful failure modes. Build repeatable deployment, rollback, configuration, and environment practices.
Production operations
Add logs, metrics, traces, alerts, and runbooks that support diagnosis. Review availability, latency, accessibility, and security as ongoing product requirements.
Incremental modernization
Isolate legacy dependencies behind deliberate seams. Deliver changes in reviewable increments and document the decisions future engineers will need to maintain the system.
What you'll deliver
Production increments
Small, valuable releases that prove the product direction and keep learning close to real user behavior.
Technical foundation
Maintainable services, interfaces, data contracts, environments, and operational signals that support the product beyond launch.
Quality system
A practical standard for testing, review, security, performance, observability, and release confidence.
Team enablement
Pairing, documentation, decision records, and working agreements that improve the client team’s ability to ship.
What you bring
- 6+ years building production web applications
- Expert TypeScript, React and Node.js or similar
- Experience with relational databases and cloud deployment
- Pragmatic approach to testing and architecture
Practical capabilities we will discuss
- Engineering fundamentals
- Explain concurrency, state, error handling, interface contracts, data integrity, and deployment compatibility through systems you have built. Show where a simpler implementation was sufficient and where a stronger abstraction was necessary.
- Modern application stack
- Bring production experience in a modern frontend ecosystem and a server environment such as Node.js, Java, Python, or .NET. Describe how you selected libraries, managed dependencies, and kept the product maintainable.
- Security and accessibility
- Explain authorization boundaries, input validation, session handling, sensitive-data protection, and accessible interactions. Show how these requirements influenced the design rather than appearing only in a final review.
- Delivery evidence
- Discuss a feature or service you owned through release and operation, including testing, deployment, monitoring, feedback, and an issue that required you to revise the original approach.
Nice to have
- Next.js, GraphQL, event-driven systems
- Accessibility and performance expertise
- Open-source contributions
How success is assessed
Success criteria are agreed at the start of the engagement and reviewed as the work progresses. Typical signals include:
- Users can complete the intended workflow with less friction and clearer feedback.
- The team can release frequently enough to learn without trading away reliability.
- Defects, incidents, and operational surprises are found earlier and understood better.
- Technical decisions are documented at the level needed for future change.
- Client engineers gain confidence and ownership rather than becoming dependent on one expert.
Your first 90 days
First 30 days
- Get set up on an active product team
- Ship your first production change
- Learn the architecture and delivery workflow
By day 60
- Own a feature from design to release
- Improve a test or CI weak spot
- Review peers' pull requests
By day 90
- Lead a significant technical decision
- Mentor a junior or client engineer
- Contribute to our engineering standards
How we work with clients
- Prepare workshops with a clear decision, relevant evidence, and the people needed to act on the outcome.
- Document assumptions, alternatives, costs, dependencies, and risks so stakeholders can review your recommendation.
- Escalate delivery or quality concerns early with options and a recommended course of action.
- Protect confidential information and use approved collaboration and delivery environments.
- Transfer knowledge through pairing, practical documentation, and walkthroughs with the people taking ownership.
Tools you may use
- TypeScript
- React
- Next.js
- Node.js
- PostgreSQL
- GraphQL
- Docker
- Playwright
Interview process
- 01
Apply
Share your background. A human reads every application.
- 02
Intro call
30 minutes on your goals, experience and what you want next.
- 03
Technical conversation
A practical discussion with a practitioner — no trick puzzles.
- Technical conversation. Discuss a system you built and how you'd evolve it.
- Pairing session. Work through a realistic problem with an engineer. No whiteboard puzzles.
- 04
Team & terms
Meet the people you'd work with, then agree scope and terms in writing.
Location, engagement and compensation
This is an expression-of-interest profile for client work we are shaping. A confirmed vacancy, employment arrangement, travel requirements and compensation range have not yet been published. Before an approved role proceeds, we agree client context, availability, duration, compensation or rate and any benefits in writing.
Telugu Technologies is an equal opportunity employer. We consider all qualified applicants regardless of race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability or veteran status, and provide reasonable accommodations on request — email careers@telugutechnologies.com.