Hey there!
We are seeking a cracked, hacker-minded engineer — one part builder, one part problem-finder — to join our Engineering team at Procedure. This isn't a "write code, push PR, move on" role. You'll be embedded with our clients, understanding their business before you write your first line of code.
We're an AI engineering company — seasoned builders shipping software products, with and without AI, since 2017. Our team is a mixed bag — of the smart and the hard workers, the organised and slightly chaotic, the early risers and the midnight-oil burners. We love debating over languages and frameworks, reading/sharing articles, podcasts, tech essays. If you love tea or coffee, Marvel or DC, Peterson or Zizek, or even something eclectic, you will feel right at home.
People who work with us fall in love with their craft. We have changed the definition of "work" for them.
Here are some of our beliefs about work
Work is only 1 part of your life. Weekends are sacred. Side gigs are welcome. We treat it as such.-
Remote by default. Commuting is a waste of time. Go crazy with the hours you save.
-
Done is better than perfect. We love clean code but shipped solutions more.
-
Curiosity has no leash here. Some of our best ideas came from people chasing a thread nobody asked them to pull.
Apart from work, we continually invest in growing you as a professional and a human.
Extensive Boot Camp — learn, regardless of your experience, about Data Structures and Algorithms, LLD, HLD, DevOps, frontend, backend and/or test engineering.-
Book Club — broaden your horizons by picking up a book every month and have fun doing so.
-
Internal Projects — where your craft, experimentation and learning precede deadlines. Also, try out new technologies and domains.
Growth requires mentorship
We believe choosing a mentor is more important than choosing a company. My co-founder, Braj, and I have over a decade of experience in our respective fields — I'll mentor you on engineering and code, Braj on product thinking and problem-solving. Ask our ex-employees how it shaped their careers.
What's it like here
There's no middle management between you and the founders. You'll talk to us, argue with us, and build alongside us.
But here's the part that makes this role different from a typical full stack gig: you won't just write code — you'll own outcomes. Think of yourself as a mini-CTO for the products you work on. You'll sit with clients, understand what keeps their users (or their business) up at night, and then go build the thing that fixes it. Some weeks you'll be deep in code. Other weeks you'll be scoping a project with a client, figuring out what to build before you open your editor. Your week-to-week will look different, and that's the point.
A quick clarification: this is not consulting. Consultants make recommendations and leave. You won't. You'll own the problem from discovery through to production — and you'll stick around until it actually works. When a client's metrics move, that's your scorecard.
We don't want engineers who wait for specs to arrive in a neat document. We want people who go find the problem, define it, and then solve it — end to end. That also means knowing what not to build. Half the job is prioritisation — figuring out which problems deserve your time this week and having the judgment to say "not now" to the rest.
This sounds good. But what exactly will you work on?
Since we are a service company, you will have the advantage of working on a wide gamut of problems — technology & real world-wise. You will be involved in all stages of a product lifecycle. You'll never have to wonder why you are working on something because you'll always know it.
The best way to describe this role: one client, many capabilities. You won't be siloed into "I only do React" or "I only do APIs." You'll stretch across whatever the problem demands — frontend, backend, data pipelines, AI integrations, infrastructure. The measure of success isn't lines of code; it's whether you moved a number the client cares about.
And it's not a one-way street. The patterns you discover on client projects, the shortcuts you build to save yourself time, the hard-won lessons from a tricky deployment — you'll bring all of that back. You'll improve our internal tools, sharpen our shared libraries, and make the next project better for the engineer who picks it up. What you learn in the field feeds back into how we work as a company.
Some of the sectors we are working on:
-
Healthtech
-
Edtech
-
Insurtech
-
Sportstech
-
Fintech
-
And much more!
Trust us; there's never a dull day at work.
Here's what we expect from you
-
You love building things and think of shipping as a craft. We wouldn't have it otherwise.
-
You have 2-5 years of software engineering experience — enough to have shipped real things, not just tutorials.
-
You're comfortable across multiple languages and frameworks. We care about your ability to pick up what's needed, not your favourite tech stack.
-
You understand that technology exists to serve a business. You can connect what you're building to why it matters for the client's revenue, retention, or operations.
-
You can walk into a room with a CTO and hold a technical conversation, then explain the same thing to a non-technical stakeholder without skipping a beat.
-
Ambiguity doesn't paralyse you. You're the kind of person who starts with what you know, figures out the rest along the way, and asks good questions when stuck.
-
You know how to prioritise ruthlessly. Not everything is urgent, and you have the judgment to tell the difference — and the spine to say "not now."
-
You have a hunger to learn more — and an instinct to share what you learn with others.
This role is NOT for you if
-
You want a well-defined box to operate in. We don't really have boxes here.
-
You can't start building until every last detail is specced out.
-
You need someone checking in on you daily to stay on track.
-
You want a role that's only about writing code and never about understanding the "why."
-
You'd rather hand off a recommendation than stick around and own the outcome.
-
You'd rather go deep in one area forever than stretch across many.
We appreciate honesty — both from us and from you. If the above list sounds like you, no hard feelings. But if reading it made you think, "that's definitely not me" — we should talk.
Recruitment Process
Please read this JD well. While we understand that it's difficult for one's experience to match 100% of the role requirements, we want you to know what you're getting into and apply only if you have a good chance of thriving here.
