We're not hiring yet — but we'd still like to meet
Aplyqk is founder-run and intentionally small. The first few hires will set the team's culture for years; we'd rather start the conversation early than do a panicked hiring sprint when the time comes.
Where we are right now
Aplyqk is a working product in active development across India, the US, and Canada. The core daily-run pipeline ships matches, tailored cover letters, reply intelligence, and interview extraction. Billing is the next major chapter.
We're built on a deliberately small stack — Spring Boot 4 + Java 21 on the backend, FastAPI + Pydantic for the agent service, Next.js 16 on the frontend, Postgres for storage, Moonshot Kimi K2.6 for every LLM call. No microservice sprawl, no multi-cloud theatrics. The whole thing fits in one engineer's head.
Funding stage: bootstrapped, profitable-by-design (the cost target is roughly $0.30 per user per day, easily covered by the cheapest paid tier). When we hire, it'll be against revenue, not against an investor's roadmap.
How we work
The actual operating principles, not the press-release version.
Boring technology by default
We use Spring Boot, Postgres, Next.js, and one LLM provider. We don't add a tool to the stack until the absence of it is the bottleneck. Engineers here ship to production on day one.
AI as a sharp tool, not a magic show
Aplyqk uses AI in places where it earns its keep — match scoring, reply classification, drafting. We don't bolt LLMs onto every feature for marketing reasons. If a regex does the job, we use a regex.
Write to be understood
Code, prompts, customer emails, internal docs — all of it. We ship faster because anyone on the team can read anyone else's work without an explanation. Documentation isn't an afterthought.
Solo-builder energy, even after we're not solo
Tight feedback loops, low ceremony, real ownership. Whoever ships the feature watches its metrics, fields the support tickets, and decides what to fix next.
Roles we'll hire for
A concrete plan, not aspirational chart-padding. Each opens when the milestone next to it is reached.
Senior Full-Stack Engineer
When we hit ~500 paying usersEnd-to-end ownership across the Spring Boot backend, Next.js frontend, and the agent service. You'll touch every layer in your first month.
AI / ML Engineer
Same time as full-stackOwns prompt engineering, model evaluation, and the agent-swarm architecture. Comfortable shipping production prompts and measuring quality regressions.
Customer Success / Growth
Once revenue justifies itFirst non-engineering hire. Talks to users, runs onboarding, surfaces product feedback into the engineering backlog without being annoying about it.
Remote, with a bias toward India + US time zones
Our users are in India, the US, and Canada — having engineers whose working hours overlap meaningfully with at least one of those markets matters more than where you sleep. We don't do "remote, but actually be online for every San Francisco meeting" — that's just a worse version of in-office.