We're hiring. This is senior work: you own a whole project, ship it to production, and stay close to the founder you're building for. The roles open right now are below. If one sounds like you, introduce yourself. We read every note.
Senior Software Engineer
Production AI and SaaS work, full ownership of a project from scope to deploy. Senior only.
Business Development
Source and qualify founder engagements. Comfortable talking scope, timelines, and technical tradeoffs.
Who does well here, and what the work asks for.
Most job listings are wishlists. This is closer to an honest picture of the work. Every project is owned by one engineer, end to end, so the people who thrive here tend to share a few things. Read it as a window into the work, not a checklist to pass. If most of it already sounds like you, we'd love to hear from you.
You've shipped to real users recently
The work here is shipping, with your name on the deploy. People feel at home fast when they've put real software in front of real users in the last 18 months and remember what that takes.
You've spent years in production code
Roughly five years and up of building customer-facing systems that run under real load. The depth matters because you'll be the senior voice on the project: you've seen things break in production and you know how to keep them running.
You like owning a project end to end
Scope it, build it, deploy it, and debug the webhook at midnight when it breaks. You run the whole thing yourself, with the founder beside you and no layer in between. People who enjoy that ownership thrive here.
You write clearly
Founders read your Slack messages, your specs, and your Loom updates. Clear writing keeps a remote, async project moving and builds trust, so it's a real part of the job.
You have a sense for good scope
You can spot a brief that's heading somewhere bad, and you've been willing to say so, even to a paying client. We do the same with client work, so we trust the people here to make that call.
The day-to-day of working here.
Async-default
Loom > meetings. Daily written updates. One weekly working session per project. No standups.
Project-based pay
You bid the milestone, we agree, we ship. Above-market when the scope is right. No tracked hours.
Direct to founder
Same Slack channel as the client founder. No middle layer. Your judgement matters because they hear it.
One project at a time
You own one engagement. Specialists rotate in for ~1-week deep-dives, then back out.
Questions before applying.
Do you hire junior engineers?
＋
Not right now, and it's nothing against junior engineers. It's how the model is built: every project is owned solo, end to end, with no senior watching over the work. That setup asks for someone who can already run a project alone, and it wouldn't be a fair place to grow into the role. So for now, this is senior-only. Plenty of great engineers we'd love to work with simply aren't a fit for how this is built yet.
Why are you so selective about hiring?
＋
We turn down about half of the client work that comes in, and we look for engineers who are just as deliberate with their own time. Hiring a few people a year, all senior, is what keeps pay strong, autonomy real, and the work good for everyone already here.
Can I work remotely from outside Pakistan?
＋
Yes. Most roles are remote across PK, EU, and LATAM timezones. The one real constraint is overlap: engagements need about 3-4 hours a day shared with the client founder, which usually lands in US-East mornings.
What does pay look like?
＋
Above-market for the project-rate model. Senior full-stack work typically runs $80-140/hr depending on stack and project. We share the project margin with you openly, with no opaque markups.
How is the specialist network different from a full-time role?
＋
Specialists join a project for a 3-15 day deep-dive when their depth is exactly what's needed, things like RLS migrations, RAG eval, or payments compliance. They're paid per engagement rather than retained, and some have been in the rotation for years.
Will my code be public?
＋
Most client work stays private, so a lot of what you build won't be public. After launch we push for permission to show a case study, and we pay a small bonus when a client says yes.
Three things, in this order.
A working URL
GitHub, a portfolio, a Vercel link, or a Loom of you shipping something. Pick whichever shows your work best. You can skip the CV.
One paragraph
What you've shipped lately, why this model fits how you like to work, and what you'd rather not do. Five sentences is plenty.
A 30-minute chat
No live coding, no take-home. We talk through a project you've shipped and how you'd scope a hypothetical one. It's a conversation between peers, not an exam.
A role is open. We'd love to hear from you.
If one of the roles above fits how you like to work, send a working URL and a short note. We read every one, and we reply.
Core MVP shipped to production by week 4.
or send a 2-min Loom →or email hello@obsidiancode.io