Applications are handled securely through Lever.
At Provectus, you don’t prototype in a sandbox and hand a client a slide deck. You embed inside a bank, an insurer, or a health system, learn the work, and ship a Claude + AWS system into their real, regulated production. Then you watch the business number move. We’re an Anthropic and AWS Partner with 150+ certified architects. That means the newest models, real budgets, and problems that matter, without the layers, politics, and long wait for impact of a firm with a hundred thousand people. 350+ builders, 100+ customers in production, led by our founders since 2010, offices across North America, LATAM, and EMEA
Why Provectus?
Frontier access. Anthropic Preferred Partner: newest Claude models, real budgets, real problems.
Real tasks (not scope), real deployment. You go where the operating problem is and ship production code to real users, not slide decks that sit in a drive.
Embedded, not engaged. You are part of the customer’s team and inside their process, not a vendor running a project alongside it. Embedded is not staff augmentation.
Autonomous. You own the work from framing through to production, visible to clients and founders. You own the method; nobody hands you a ticket.
Your experience stays portable. Every engagement is a new problem, often in a new industry, so your skills compound instead of narrowing to one product. No legacy maintenance grind, not a single stack.
Craft & growth. Build beside senior FDEs on a Claude certified team, with a real platform (talks, OSS) to grow your name.
We give you a stage: Claude certification, conference talks, open source contributions, published work under your own name.
What you’ll do:
What we look for:
What We Offer:
We’re real:
How we hire:
- Recruitment interview
- A short practical task (about 2 hours) OR a live engineering session.
For the practical task, pick one of 2 or 3 use cases from our roster. They are synthetic problems, not a live client deliverable.
For the live session, we hand you a business function and the constraints. You have to understand the job and rebuild it, then say what you’d build and how you’d know it worked.
Use AI the way you normally would; we expect AI generated code. What we look at is how you used AI, the judgment behind your choices, and what you researched beyond what any LLM already knows. - A task discussion session after the practical task. A discussion about what you’d build and how you’d know it worked. No LLMs for this one.