Skip to content
CAREERS / 01
Careers

Watch us build.

Then build with us.

Product engineering in the open.

Open roles
08
Tracks
Engineering · Business and operations
Office
DHA Raya, Lahore
CAREERS / 02
What to expect

Build what comes next.

Not the offer letter version. This is the engineering track, and it is the same shape for everyone on it.

Three colleagues sitting together on a sofa around one open laptop, one of them pointing at the screen.
Review · in the room
  1. DAY 01

    Access granted.

    Laptop ready. Repos unlocked. Team connected.

  2. DAY 03

    Understand the machine.

    Learn the architecture. Understand the product. Ask impossible questions.

  3. DAY 07

    First ship.

    Your first contribution reaches production.

  4. DAY 14

    You are building.

    No more onboarding. You are part of the system.

CAREERS / 03
How we work

Less theatre. More terminal windows.

The parts nobody puts in the advert.

  • 01

    Close to the people paying for it

    Your day overlaps the client's, which is why you get to argue with the person paying for the work instead of emailing them and waiting a day for the answer.

  • 02

    Nobody here codes alone

    Every pull request is read by an engineer who tells you why, and seniority buys no exemption from it. It is the closest thing to a guarantee that you leave better than you arrived.

  • 03

    Having an opinion is the job

    Architecture gets argued while it is still cheap to be wrong about. We would rather hear it loudly in your second week than quietly in your sixth month.

  • 04

    You own it in front of the client

    No account manager stands between your work and the people it is for. You explain your own decisions, which is the part that makes them yours.

  • 05

    Nothing important happens in private

    Sprints, reviews and deploys are open by default, and a postmortem blames the system rather than whoever shipped it. Harder to hide in, and much easier to learn in.

Think hard. Build fast. Leave it better than we found it.

CAREERS / 04
Open positions

What's open.

Every listing carries the date it went up and expires on a date we committed to.

Engineering

  • What you would own

    • Design and run ingestion and transformation pipelines in Python and Airflow.
    • Own schema and data-quality validation at the boundary, before bad rows travel.
    • Take a warehouse model from discovery through to something a client bills from.
    • Review other engineers' pipeline code, and have yours reviewed.

    What we are looking for

    • Several years building production data pipelines, not just notebooks.
    • Strong SQL and Python, and real Postgres experience.
    • Orchestration in Airflow or an equivalent, deployed rather than demoed.
    • You can explain why a pipeline broke, not only that it did.

    Nice to have

    • dbt, Snowflake, or AWS Glue.
    • Experience with billing or reconciliation data, where being wrong is expensive.
  • What you would own

    • Build retrieval and forecasting features that run against a real warehouse.
    • Set up evaluation before shipping, so a regression is caught rather than reported.
    • Serve models behind FastAPI and keep latency and cost inside a budget.
    • Work directly with the engineers building the product around your model.

    What we are looking for

    • Production ML or applied AI experience, end to end rather than research only.
    • Strong Python, and comfort with the serving side as well as the training side.
    • Retrieval-augmented generation built and evaluated properly, not just prototyped.
    • Judgement about when a model is the wrong answer to a problem.

    Nice to have

    • Vector search at scale.
    • Anomaly detection or time-series forecasting on operational data.
  • What you would own

    • Work on a real product with real requirements, not a throwaway exercise.
    • Open pull requests that a senior engineer reads and comments on properly.
    • Leave with work you can show and talk through in an interview.

    What we are looking for

    • Something you have built and can explain the decisions behind.
    • You want to be told why your code should change, not just that it should.
    • Comfortable in at least one language well enough to be useful in week one.

    Nice to have

    • A repository, a side project, or anything with your commits on it.
  • What you would own

    • Build and run transformations against real, messy operational data.
    • See what schema and null validation catch before bad rows travel.
    • Get your SQL and your Python reviewed line by line.

    What we are looking for

    • Solid SQL, and Python you can write without a tutorial open.
    • Curiosity about where data comes from and how it goes wrong.
    • You would rather understand a pipeline than copy one.

    Nice to have

    • Any exposure to Airflow, dbt or a warehouse.

Business and operations

Different work, same review culture.
  • What you would own

    • Run technical recruitment end to end, from sourcing to offer.
    • Own HR operations: onboarding, records, and day-to-day people questions.
    • Work with engineering leads to turn a vague need into a real role.

    What we are looking for

    • Strong experience in technical recruitment.
    • HR operations experience, not recruitment alone.
    • Enough technical literacy to tell a good engineering CV from a padded one.
  • What you would own

    • Run HR operations for US employees and consultants: onboarding, orientation, documentation.
    • Coordinate with US clients, vendors and internal teams.
    • Manage employment documents, HR records, payroll coordination and timesheets.
    • Support recruiting: screening, scheduling, and candidate communication.
    • Keep onboarding and documentation compliant with US HR standards.

    What we are looking for

    • Two or more years in US HR, staffing or recruitment.
    • Excellent English and confident client handling.
    • Familiarity with US onboarding, background checks and forms such as I-9 and W-4.
    • Experience with an HR system, ATS or CRM.

    Nice to have

    • Supporting an IT staffing or consulting company.
    • Comfortable running operations independently from Pakistan.
  • What you would own

    • Plan and run digital campaigns end to end.
    • Own social media management and the content that feeds it.
    • Turn engineering work into something a non-engineer wants to read.

    What we are looking for

    • One to two years in digital marketing or social media management.
    • Campaign planning and content creation you can point at.
    • Strong written communication.
  • What you would own

    • Work on live social and content, not filing.
    • Get your work reviewed by someone who explains the edit.
    • Leave with campaigns you can show and talk through.

    What we are looking for

    • Genuine interest in social media, content and digital marketing.
    • You write clearly, and you want to be told how to write better.
CAREERS / 05
How we hire

The whole process, written down.

Every stage, and what each one is actually for.

01

You send the form

Links and a few sentences. No account to create.

What it is for

To find out what you have built, in your words.

02

A person reads it

For engineering roles that is an engineer, and it could be the one reviewing your pull requests later.

What it is for

To judge the work rather than the formatting of the document describing it.

03

A conversation about something you made

You pick the thing. We ask why it is built that way, what you would change, and what went wrong.

What it is for

To hear you think, which a quiz cannot show and a whiteboard actively hides.

04

A working session on a real problem

One of ours, roughly as it arrived. Asking questions is part of what we are watching for.

What it is for

To find out what working together feels like, both directions.

05

A decision, either way

You hear back with a reason. A no comes with the reason too.

What it is for

To close the loop we opened.

CAREERS / 06
The practical part

Where, when, and what it means.

The section candidates scroll to find, so it is not buried.

Office
DHA Raya, LahoreOn-site roles are on-site. We are not quietly hybrid.
Applications
contact@devvaults.comThe form below reaches the same inbox.
CAREERS / 07
Application

Your résumé says what you know. Show us what you did with it.

Side projects. Abandoned GitHub repos. Hackathon disasters. Something you built at 3AM because you couldn't stop thinking about it. Curiosity beats credentials.

GitHub, a portfolio, a live thing, a repository you are proud of. One per line.

Optional. A URL, not a file.

Pick one thing and tell us why it is built the way it is.

After you send it

  1. You send the form
  2. A person reads it
  3. A conversation about something you made
  4. A working session on a real problem
  5. A decision, either way

Read the whole process

Rather just email us?contact@devvaults.com

We read portfolios before cover letters.