Senior AI-Native Full-Stack Engineer (Laravel / Vue / Inertia)

Company: Orpical Technology Solutions Inc.

Location: Remote, United States only (must be physically located in the US and authorized to work here)

Employment Type: Full-Time

Reports To: Director of Technology / CTO

Compensation: Competitive salary + equity participation in JV projects

 

Orpical Technology Solutions is a senior, AI-native software consultancy. We ship production work across fixed-fee engagements, ongoing client development, scoped SOWs, and select JV partnerships, and delivery discipline is what keeps us hired.

We're hiring a senior full-stack engineer who has moved past AI-assisted coding and into agentic delivery: someone who ships production software by orchestrating the system that writes it, not just by accepting autocomplete suggestions. Our work spans user-facing web products, headless systems, automation pipelines, and agent services; Laravel, Vue, and Inertia are our default stack for traditional apps, but not everything we ship has a UI.

This role is US-based only. You must be physically located in the United States and authorized to work here. Applications that don't meet this requirement will not be reviewed.

This role is NOT for you if

·         "AI-native" to you means tab-complete autocomplete and reviewing every suggestion by hand

·         You want a ticket-routing role with tightly scoped work, heavy process, and clean handoffs

·         You want to avoid post-deploy support, operational work, or owning production outcomes

What you'll own

·         Ship production features end-to-end: implementation → PR → deploy → support, with the delivery loop running through the harness you helped build

·         Work across a mix of spec-driven MVPs, legacy stabilization and refactoring, scoped SOW feature work, and internal fulfillment tooling

·         Build across a growing mix of shapes. Not everything ships with a UI. Headless systems, automation pipelines, and agent services are an expanding part of what we deliver, and you should be as at home there as you are in a traditional app

·         Deploy and operate across whatever the project requires. Our default pairing is Laravel Forge on DigitalOcean or AWS, while client environments often live on AWS, Azure, or other infrastructure entirely

·         Translate PRDs and acceptance criteria into execution plans, prompts, and guardrails, and validate AI output for correctness, security, and alignment before it touches main

·         Collaborate closely with a Senior Account Manager who owns client alignment, while you own technical execution and delivery outcomes

How AI fits into the work

AI isn't a productivity hack here. It's the delivery model. We want engineers who have moved beyond AI-assisted coding (a human reviewing every suggestion) into designing the loops, harnesses, and validation gates so that work moves reliably with judgment at the right checkpoints. In practice, that means:

·         You know the difference between piloting AI (babysitting each suggestion) and orchestrating it (designing the system that ships the feature)

·         You think as an orchestrator, not an operator. Context engineering, prompt shaping, and tool setup are table stakes for you, not the whole game. The job is getting real work through the loop

·         You front-load validation. Criteria and failure modes are defined before the agent runs, so the harness catches regressions without a human reviewing every step

·         You can point to concrete examples where you've used long-running loops, subagents, or harnessed workflows in real delivery work (not tutorials, the work you ship)

·         You step in decisively when automation stops helping or risks production stability

Tech environment

Our default stack

·         Application: Laravel, Vue.js, Inertia.js, Tailwind CSS

·         Runtime & data: MySQL, Redis, queues/Horizon, Linux/Nginx

·         Hosting & deployment: DigitalOcean, AWS, or Azure for hosting; Laravel Forge for server management and deploys

·         Delivery & collaboration: GitHub (PR-based workflows and CI/CD), Linear (work tracking), Slack (team and client communication)

We default to this stack because it's battle-tested, ships fast, and scales with how we work, but we're not religious about it. Project requirements, client environments, timelines, and financing structures can push the right answer elsewhere. In an AI-native delivery model, the stack is an input to the process, not a constraint on it.

On the AI side, we care less about which tools you've used and more about whether you're tracking the frontier: running current-generation models, experimenting with new harnesses and orchestration patterns as they land, and reading the repositories driving the state of the art. CLI or IDE, whatever you reach for. The question is whether what you learn is making it back into how we ship.

What we're looking for

Assumed baseline (we won't dwell on these): 5+ years shipping production software, strong Laravel and Vue.js, Git/GitHub PR fluency, comfort deploying and operating production systems, solid security-minded habits (OWASP basics, secrets, least privilege). If this is where your résumé ends, this isn't the role for you.

·         Your practice has moved past AI-assisted coding and into agentic delivery, with concrete examples you can walk through, not abstract claims

·         You live on the frontier. You track the repositories driving the state of the art, run current-generation models, and experiment with new harnesses and orchestration patterns as they emerge

·         You translate specs, PRDs, and client constraints into execution plans that run through a harnessed workflow, not just typing into a chat window

·         You own features end-to-end (implementation → PR → deploy → support) and you don't need tight guardrails to move

·         You know where AI lies to you, and you've built the discipline to catch it before it ships

·         You're as at home building headless systems, automation pipelines, and agent services as you are building traditional user-facing products

How you operate

·         Insatiable learner. You track docs, papers, and the top agentic development repositories, ask sharp follow-ups, and retain context across a lot of surface area

·         Ego-free collaborator. You discuss tradeoffs, admit gaps, and prioritize outcomes over being "right" (including when an agent's output is better than yours)

·         Get-it-done mindset. You move with incomplete info, communicate risks clearly, and ship quality work without needing a heavy process

·         Ownership mentality. When something breaks, whether in code you wrote or a loop you ran, you investigate, resolve, and follow through

·         Reliable under pressure. When a client's system is down, you respond with urgency without normalizing emergencies as the default

Why join Orpical

·         High ownership, low bureaucracy. Your decisions matter

·         Work across diverse real-world systems that most engineers don't see in one role

·         Operate in an AI-native culture that applies AI to production delivery, not experiments

·         Equity participation in JV projects alongside salary

·         Build alongside senior operators who value speed, judgment, and building products that drive real-world value

How we hire

We keep our process lean and transparent: application review → working conversation with engineering → drop-in hackathon → decision. We move quickly for strong candidates and we give direct feedback either way.

How to apply

Email your resume to kim@orpical.com, subject line "Senior AI-Native Engineer - [Your Name]".

In the body, include:

1. Confirmation that you are physically located in the United States and authorized to work here

2. One short paragraph describing a specific AI-native workflow you've built or used in production: what it does, what runs unattended, and where your judgment applies

3. A link to 1–3 shipped projects (LinkedIn, portfolio, or live URLs)

4. Optional Loom Link given in this Google Form of a 3–5 minute walkthrough of a PR you are proud of and how AI fits into the workflow.

Applications without these three items will not be reviewed