Fullstack Engineer

Full Stack Engineer

Location: Hybrid, Bangalore
Employment Type: Full-Time Opportunity

Role Overview

We are looking for experienced Full Stack Developers to build production-grade web applications and APIs. You will own features end to end from database schema through backend services to the user interface. This is a hands-on build role for engineers who are comfortable working through ambiguity, shaping the design as much as writing the code, and operating as an owner rather than a ticket-taker.

Must-Have Skills

Frontend

• Strong JavaScript fundamentals (ES6+, async/await, closures)
• React experience preferred (hooks, state management, component architecture)

Backend

• Proficient in Python, writing production-grade code
• Hands-on experience with FastAPI or Flask for building REST APIs

Database

• Experience with relational databases (PostgreSQL, MySQL, SQL Server, or equivalent)
• Good understanding of schema design, joins, indexing, and query optimization

Architecture & Problem Solving

• Ability to think through system design and build scalable solutions
• Strong analytical mindset to break down complex or ambiguous problems

Good-to-Have Skills

• Experience with Claude Code or other AI-assisted development tools extra points for this
• Desktop app based on Electron framework extra points for this
• Agentic Frameworks (ADK, Langraph)
• API documentation (Swagger / OpenAPI)
• Git and version control best practices
• Basic DevOps awareness (Docker, CI/CD)
• Testing experience, both unit and integration

Behavioral Expectations (Non-Negotiable)

Proactive communication

Shares updates without being asked and flags blockers early

Asks the right questions

Clarifies requirements upfront before jumping into implementation

No working in silos

Collaborates openly, seeks feedback, and loops in stakeholders regularly

Ownership mindset

Treats the project as their own rather than just completing tickets

Transparency

Speaks up when something is unclear instead of making assumptions

What Success Looks Like

• Features shipped end to end schema, API, and UI with minimal hand-holding
• Requirements clarified early, so rework is rare
• Blockers surfaced the day they appear, not at the end of the sprint
• Code that others can read, test, and extend