QA engineer

Job Summary


Responsibilities

• A day in the life of a developer here:
  • Start of day: A short stand-up focused on blockers and priorities, not a long status meeting.
  • Deep work: Blocks on actual product tasks: API, UI, refactors, debugging, tests.
  • Getting unstuck: Ask early. Nobody is measured on suffering quietly through an edge case.
  • Reviews: Feedback on the code, not the person: naming, trade-offs, and why one approach won.
• A calm environment: Predictable hours and no theatre around estimates. Transparent discussions about roadmap, client expectations and how each project impacts the business. A single office in Ahmedabad: no distributed-team coordination tax.

Hiring process

• Send your profile: A CV or LinkedIn, your GitHub or a project you are proud of, and two lines on the work you want to do. We read every one.
• Day 0: A short intro call: Twenty minutes with the person you would work with: what we build, what you have built, whether the role fits. No test yet.
• Within 24 days: A practical conversation: An hour on code you have written, or a small task on the stack you would use here. We talk through trade-offs; nobody writes on a whiteboard.
• Week 1: Meet the founder, then the offer: A conversation with Abid about the company and where it is going, then a written offer with the salary, the start date and who you report to.
• Week 2

The tech stack you would work in


Backend

• Laravel and PHP 8, or Node.js with NestJS
• PostgreSQL and MySQL, with Redis for queues and cache
• REST and GraphQL APIs, documented and versioned

Frontend and mobile

• React and Next.js with TypeScript and Tailwind CSS
• Flutter for iOS and Android from one codebase
• Accessibility and performance budgets on every screen

Delivery

• GitHub, pull requests reviewed before merge
• CI/CD with automated tests, staged releases on AWS
• AI tooling for the application base; engineers write the product

What we look for in a developer, whatever the stack

• Fundamentals : You understand why the code works, not just that it does: data structures, HTTP, the database, the browser.
• Ownership : You take a feature from the conversation with the client to the release note, and you say when something is going wrong.
• Clear communication : You can explain a trade-off to a founder in plain words, in writing, and you ask early rather than guess quietly.
• Curiosity with judgement : You try new tools and you know when not to. A calm reaction to a bug in production counts for more than a long list of frameworks.

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.