blocshipCareers at Blocship
Build software that real people actually use.
We're a small senior studio building Flutter apps, full-stack products and AI integrations for clients with real users and real money moving through them. Every role here reports to the engineer who sets the architecture.
Why here
A small team is the whole point.
There's no bench, no resourcing spreadsheet, and nobody between you and the decision. That's the trade: more ownership, less cover.
Features, not tickets
You take a problem from scoping through to production, including the part where it breaks at 2am.
Claude every day
We ship in weeks what takes months elsewhere. Architecture and every critical path still get reviewed by a human.
Written and async
Decisions live in writing, not in someone's head or a meeting you missed. Fewer calls, clearer trails.
Production, not demos
Payments, fleets, health data, hardware. Things where being wrong costs somebody something.
Open roles
One role, open now.
Open the role to read the whole thing and apply without leaving the page. No account, no portal.
Upwork Bidder
First contact with every inbound client. You read job posts, work out which are real, and write back like someone who understood the problem. It's the first thing a client ever sees from us, and most studios get it wrong by sending everyone the same paragraph.
Worth being clear about
You are not a sales layer. Clients are promised they deal with Shahzad directly and they will. Your job is getting the right ones to him faster, never standing between them and the person building their software.
- Around 20–30 proposals a week — chosen carefully, not sprayed. We measure what gets read, not what gets sent.
- Working the feed for briefs that match what we genuinely ship, and skipping the rest however good the budget looks
- Writing proposals that name the client's problem in the first sentence — no templates, no capability lists
- Qualifying budget, scope and whether the thing is buildable, before the call rather than after
- A short written brief to Shahzad ahead of every call, so he walks in knowing the problem
- Tracking what won and what didn't, honestly
- English good enough to write in, not just to read
- Enough technical literacy to tell a Flutter job from a WordPress one
- Some track record on Upwork, or a very good argument for why you don't need one
- Evenings on-site genuinely suit you
- Hours6:00 PM – 2:00 AM, Monday to Friday
- Starts1 September
- WhereOnsite in Karachi
- This form — read by Shahzad, reply within a week
- A short written test, about 30 minutes, real job posts
- One conversation onsite, evening, so you see the room
How hiring works
Four steps. You'll know where you stand at each one.
A link and two short honest answers. That's the whole application — no cover letter, no portal account. Read by Shahzad, reply within a week.
About thirty minutes on real job posts, not a puzzle. It is the job, so you find out what the work feels like at the same time we do.
In the evening, so you see the room and the shift you'd actually be working before either of us commits.
Within a week of the conversation, with the reasoning. No silence, no stringing along.