Full-Stack Product Engineer (Part Time)

Build the product end to end, from the first customer workflow a user sees to the data, integrations, and reliability underneath it. This is a high-ownership fractional engineering opportunity for someone who wants product influence as well as technical ownership.

You will not inherit a finished roadmap and a narrow service boundary. You will help decide what should exist, ship it, watch how people use it, and improve the system with the founders and product team.

About Tegy
Tegy is building the strategy team ambitious companies wish they had. It turns messy business context into defensible decisions, models, memos, decks, and action plans with senior-grade rigor on demand.

We are early enough that the engineers who join now will shape the product architecture, the user experience, the development culture, and the standard for what a trustworthy AI-native strategy product should feel like.

Why join now
• Own customer-visible product outcomes instead of maintaining an isolated layer.
• Work directly with founders, strategists, and early users on high-value problems.
• Influence architecture and engineering standards before they harden.
• Ship quickly with modern AI tools and a small decision-making surface.
• Build a product where quality of reasoning and quality of experience both matter.

What you will own

1. End-to-end product workflows. Build coherent experiences across interface, application logic, APIs, data, and deployment.
2. Fast, durable shipping. Turn product intent into small releases that create user signal without accumulating avoidable fragility.
3. Product quality. Improve performance, instrumentation, error handling, security, and the details that make the product feel credible in consequential work.
4. Data and integrations. Design the structures and connections that let Tegy use customer context, produce useful artifacts, and fit into real operating workflows.
5. Engineering foundations. Establish practical standards for architecture, testing, reviews, observability, documentation, and developer velocity.

What success looks like

First 30 days: Understand the current product and customer journey, ship a useful improvement, map the highest-leverage technical risks, and establish a working rhythm with product and AI engineering.

By 60 days: Own and deliver a meaningful vertical slice from user experience through production, with instrumentation that shows whether it worked.

By 90 days: Lead a product stream with limited supervision, improve reliability and release quality, and leave the system easier to extend than you found it.

Who will thrive
• You have personally shipped customer-facing web products across more than one layer of the stack.
• You make pragmatic architecture decisions and can improve an inherited system while continuing to deliver.
• You care about user workflows and business outcomes, not just technical elegance.
• You are comfortable with ambiguity, direct feedback, and owning the result after code reaches production.
• You use AI development tools thoughtfully while maintaining judgment, review discipline, and accountability for the output.

Experience with modern typed web applications, APIs, relational data, cloud deployment, testing, and product analytics is useful. Exact frameworks matter less than proof that you can learn quickly and own a complete product surface.

Engagement and compensation
Start with a paid four-to-six-week build sprint or a fractional contract of roughly 15 to 25 hours per week. The sprint range is US$3,000 to US$7,500. Ongoing work typically falls in the US$30 to US$60 per hour range, depending on scope, availability, location, and demonstrated capability.

The equity range is 0.0% to 3.0%, with the specific grant shaped by ownership, sustained contribution, commitment, and demonstrated impact.

This role is open worldwide. You should be able to maintain reliable scheduled overlap with US Eastern time for product decisions and collaboration.

How to apply
No long cover letter is needed. Send:
• One or two products or meaningful features you personally shipped, including the outcome, your contribution, and one tradeoff you made.
• A short response: when you inherit an early product with user demand, technical debt, and an ambitious roadmap, how do you decide what to stabilize and what to ship next?
• Your location or time zone, availability, preferred engagement model, and compensation expectations.

Candidates who advance will discuss real Tegy product problems; any substantial build exercise will be paid.

Exceptional people rarely arrive on a hiring calendar. We meet strong candidates year-round and move quickly when there is a compelling fit.