Purpose over vanity metrics
We publish honest readiness labels on products and experiments — internally and on the corporate site.
Culture
Engineering craft, honest innovation labels, and continuous learning — from Hyderabad and across India. Static culture content; no employee portal.
Culture pages describe intent and norms — not guaranteed benefits or policies. Formal HR policies require leadership and legal review before reliance.
Life
A small product company building trust-heavy experiences — devotional services, automation, and platforms that respect tradition.
We publish honest readiness labels on products and experiments — internally and on the corporate site.
Engineers and designers own features end-to-end with lightweight review, not heavy hierarchy.
Headquartered in Hyderabad with collaboration across India — product domains stay separate from marketing releases.
Spiritual and family contexts demand empathy, accuracy, and calm UX — not growth hacks.
Engineering
TypeScript-first stacks, config-driven content, and production discipline without resume-driven complexity.
Next.js, APIs, and integrations should be understandable by the next engineer — not clever for its own sake.
Marketing and trust pages stay fast and auditable; dynamic features earn their server cost.
Payments, WhatsApp, SMS, and AI slots are planned early — partners and products plug in without rewrites.
Evals, human-in-the-loop paths, and cost caps before customer-facing agent features.
Innovation
We experiment in the Innovation Lab — concepts and prototypes are labeled honestly, not sold as finished products.
Concept, Prototype, Planned, or Live — every R&D item carries a status badge.
Explorations have exit criteria: promote, pivot, or archive — no infinite science projects.
Guides and internal notes turn spikes into playbooks for the next engineer or client engagement.
Investors and partners see the same readiness language we use publicly — no slide-deck fiction.
Growth
Continuous improvement through docs, pairing, and external resources — budget and formal L&D policies subject to company stage.
We maintain public guides and resources — writing clarifies thinking for the whole team.
Pull requests and design critiques are teaching moments, not gatekeeping.
Relevant courses and events supported when aligned to roadmap — case-by-case approval.
Mobile, AI, DevOps, and product design exposure encouraged within project needs.
Ways of working
Distributed collaboration practices — not a fully remote-only company; hybrid norms evolve with team size.
Decisions and specs live in docs and tickets — meetings for alignment, not status theatre.
Core overlap hours for standups and pairing; flexibility outside that window where roles allow.
Optional in-office collaboration in Hyderabad for local teammates when projects benefit.
Staff admin and repos follow least-privilege access — no public login on the corporate site.
Hiring
We do not run an applicant portal on nexynthlabs.com. Listed roles appear on /careers; otherwise use the placeholder flow below.
Apply via mailto links per role or a general careers email — attachments and portfolios welcome.
Applicant tracking and structured pipelines are future infrastructure — not available today.
We add roles when product and client load justify another teammate — not continuous bulk hiring.
When openings exist, they are config entries in src/config/careers.ts — easy to update without code deploys beyond build.
Edit culture sections in src/config/careers.ts — config-driven, no CMS required.
See open roles or send a general application by email.