Software Developer Engineer - Front end

CapitalNow (Finxer Technologies Private Limited)

Location: Hyderabad, on-site

Experience: 3–6 years

Context

This is a lean, high-ownership team rebuilding after recent attrition. There is no bench, no hand-holding, and no waiting for a senior developer to unblock you. If you need a mature process and a large team around you to be productive, this isn't the role.

What You'll Own

• Website revamp (Next.js) end-to-end — architecture decisions, not just implementation
• Customer-facing loan application funnels — KYC forms, eligibility flows, disbursal tracking — where a broken component directly costs the business money and users' trust
• Performance: Core Web Vitals, bundle size, SSR/SSG strategy — not optional, actively measured
• Direct API integration with the Node.js backend, including payment gateway UI (Razorpay/PayU/Cashfree) and BBPS flows
• Production ownership — you ship it, you monitor it, you fix it if it breaks

Non-Negotiable Technical Bar

• React + Next.js: must be able to explain SSR vs SSG vs ISR trade-offs and justify a choice for a real page, not recite definitions
• TypeScript: strict mode, not "I've used it a bit" — must be comfortable typing complex forms and API responses
• Performance: must be able to walk through how they'd debug a slow page, not just name Lighthouse
• State management: real reasoning on when to use Context vs a library (Zustand/Redux) vs server state (React Query) — not dogma
• Git: comfortable with rebase, resolving real conflicts, PR discipline — on a small team, sloppy commits create real friction
• Must be able to read and reason about backend API contracts, not just consume whatever's handed over
• Can't explain a technical decision from a past project without falling back to "that's what the senior dev told me to do"
• No evidence of ownership — only ever worked on assigned tickets in a large team, never owned a feature start to finish
• Can't discuss what happens when things go wrong in production (no incident or debugging story)
• Portfolio/GitHub is templated tutorials only, no real shipped work
• Vague on fintech-adjacent concerns (data handling, sensitive form fields, PII on the client) — this is a lending product, not a portfolio site

Good to Have

• Fintech/lending/BFSI exposure
• PWA or mobile-first experience
• Has worked in a startup that went through a rough patch (resilience signal)