Role: Senior Software Engineer/ Solutions Architect

Salary: Php 90K-140K+ /month

Shift:

• EST: 3:00 AM – 1:00 PM
• PH Time: 3:00 PM – 1:00 AM

Looking for Builders, Not Passengers

Most engineers are given maps.

We are looking for someone who creates the roadmap.

We are building an AI company at speed. The kind where the architecture decisions made in the next 12–18 months will define the company for the next decade.

This role is not for someone who wants a comfortable sprint cycle.

It’s for someone who wants to build systems that matter, someone who comfortable assembling parts of an airplane while the airplane is in the air.

We are looking for a Driven and Talented Software Engineer who can operate with the ownership, speed, and sound judgment of a leader.

Someone who doesn’t wait to be pointed at problems.

Someone who hunts them and solves them graciously.

The Work

You won’t be maintaining legacy systems.

You’ll be building the core systems the drive change and impact a significant number of extremely reputable and large businesses.

That means:

• Designing architecture that scales before the scale exists
• Turning ambiguous ideas into production systems quickly
• Shipping fast while protecting the parts that cannot break
• Making technical decisions with long half-lives

You will have real ownership of critical infrastructure, product, and platform decisions.

When something blocks progress, you remove the blocker.

No drama. Just velocity.

The Kind of Engineer Who Thrives Here

This role is intentionally polarizing.

You’ll probably thrive here if:

• You build things because you can’t help yourself
• You care deeply about craft, performance, and elegant systems
• You move faster than most teams while maintaining high standards
• You learn new domains faster than most people can Google them
• You default to ownership instead of permission

You likely have at least one project where:

• you built something that was technically extremely difficult from scratch
• people now depend on it
• and you did it mostly because you wanted to see if it was possible

You have very high standards.

For your code.

For your thinking.

And especially for yourself.

What This Is Not

This is not:

• a maintenance role
• a Jira-ticket factory
• a place to hide behind processes
• an environment tolerant of mediocre engineering

We are building with controlled velocity:

Fast without being sloppy.

Ambitious without being reckless.

The Upside

If you are the right person, this will be one of the most leveraged periods of your career.

You’ll get:

• Ownership over systems that matter
• A small team of other high-agency builders
• Real influence on product and architecture
• Equity that actually means something if we win
• A front-row seat to building an AI company’s new products from the ground up

The Filter

This role is not for everyone.

Most engineers prefer clear maps and tickets, predictable scope, and stable systems.

If reading this made you feel slightly uncomfortable and excited at the same time, you are probably the kind of builder we are looking for.

Most developer engineers won’t apply.

That’s the point – this is intentional.