Senior AI Native Software Engineer

We are looking for a high-output, AI-native Senior Software Engineer who can take direction, execute quickly, think beyond the obvious solution, and consistently deliver production-quality software., It means that when a legitimate production emergency occurs, the response is:

“Let’s get this fixed.”

-not:

“It’s Saturday. I’ll look at it Monday.”

We expect reasonable judgment.

A minor issue can wait.

A customer-impacting production incident may not.

We want engineers who understand that distinction and are willing to step up when the business and our customers genuinely need them.

Follow Direction. Execute. Deliver.

This role requires someone who is comfortable operating within a Product-led development environment.

You will receive priorities and direction from Product and Leadership.

You are expected to:

Listen * Understand * Think * Build * Test * Ship * Improve * Move to the next priority.

We want your technical judgment.

We want your ideas.

We want you to challenge assumptions.

We want you to identify problems we haven’t seen.

But we also need someone who understands that execution matters.

This is not a role for someone who wants to spend weeks debating the perfect solution to a problem that could have been solved yesterday.

Your ResponsibilitiesBuild

• Implement product requirements
• Build production-quality features
• Develop APIs and backend services
• Build frontend functionality
• Work with databases and data models
• Integrate third-party services
• Work across the technology stack when necessary

Think

• Identify opportunities to improve features
• Suggest better technical approaches
• Identify edge cases
• Identify potential customer-impacting problems
• Look beyond the immediate ticket
• Recommend improvements to product workflows
• Think about scalability and maintainability

Debug

• Investigate bugs independently
• Read logs and error messages
• Reproduce problems
• Identify root causes
• Implement fixes
• Verify fixes before shipping
• Respond with urgency when production is impacted

Ship

• Write production-ready code
• Create appropriate tests
• Submit changes through Git
• Participate in code review
• Deploy through established processes
• Monitor production behavior
• Quickly address regressions

Improve

• Identify repetitive work that can be automated
• Improve development workflows
• Build reusable components
• Reduce unnecessary technical debt
• Use AI to increase development velocity
• Continuously improve your own engineering process, You are the person who:
• Gets excited when handed a difficult problem
• Wants to make things better than they found them
• Doesn’t need someone standing over your shoulder
• Can take a requirement and run with it
• Uses AI constantly to increase your output
• Can code without AI when necessary
• Notices things other people miss
• Suggests improvements without being asked
• Takes pride in the quality of your work
• Doesn’t stop at “technically it works”
• Understands that “done” and “done well” are different things
• Can accept direction without needing to control the direction
• Moves quickly when something important breaks
• Understands the importance of customers being able to use the product
• Wants to be known as the person who gets things done

You Probably Aren’t a Fit If…

This position probably isn’t for you if you:

• Are primarily looking for a leadership position
• Want to own the engineering roadmap
• Expect to manage other engineers
• Need constant direction
• Do the minimum required and stop
• Routinely look for the path of least resistance
• Remove functionality primarily to reduce development effort
• Resist requirements because they require more work
• Cannot code effectively without an AI assistant
• Treat an LLM as a replacement for engineering knowledge
• Refuse to work outside your preferred technology
• Spend excessive time over-engineering simple problems
• Need someone else to troubleshoot every issue
• Resist established product direction
• Measure productivity by hours instead of results
• Are unwilling to respond with urgency to legitimate production emergencies
• Prefer discussing work more than actually completing it, Can you take direction and turn it into working software?

Initiative

Are you actively finding ways to make the product and implementation better?

Quality

Do you care about building something excellent rather than simply checking a box?

Urgency

When something genuinely important breaks, do you respond appropriately and help drive it to resolution?

• Writing code without an LLM
• Debugging without an LLM
• Reading and understanding existing code
• Searching documentation
• Reasoning through problems independently
• Writing SQL and queries manually
• Understanding APIs and system architecture
• Fixing bugs without AI assistance
• Completing a feature when your AI tools are unavailable, * Senior-level software engineering experience
• Strong software engineering fundamentals
• Production software development experience
• Strong backend development experience
• API development and integration experience
• Database knowledge
• Git/GitHub experience
• Cloud development experience
• Strong debugging ability
• Ability to understand an unfamiliar codebase
• Ability to work independently
• Ability to follow established technical and product direction
• Strong communication
• Strong attention to detail
• Demonstrated ability to consistently deliver

We Particularly Value

• High personal standards
• Strong work ethic
• Curiosity
• Initiative
• Speed
• Product awareness
• Problem-solving ability
• Ownership
• Pragmatism
• Ability to work without constant supervision
• Willingness to learn
• Ability to remain calm during production issues
• A genuine desire to build great software, If you’re an exceptionally capable senior engineer who wants to use AI to become dramatically more productive, contribute ideas, follow direction, build great software, and consistently deliver-we want to hear from you.

We want an engineer who can use an LLM to accomplish in 30 minutes what might traditionally take several hours, but who can also sit down and write the code themselves when necessary.

If your AI tool stops working, you should still be able to ship the feature.

We Hire for Ambition, Not Minimum Effort

This is one of the most important things to understand about this position.

We are not looking for someone who does the bare minimum.

We are not looking for someone who constantly searches for:

• The easiest implementation
• The shortest path to “done”
• Ways to remove requirements
• Ways to reduce the amount of work
• Reasons something doesn’t need to be built
• Opportunities to turn a complete feature into a smaller feature simply because it’s easier

We want someone who looks at a product and thinks:

“How do we make this excellent?”

You should naturally generate ideas.

If you see a feature in a prototype and think there is a better user experience, better architecture, better performance, better workflow, or better way to solve the customer’s problem:

Speak up.

Bring the idea.

Explain why you think it’s better.

Challenge assumptions when you have a legitimate reason.

Help make the product stronger.

But there is an important distinction:

We want initiative-not insubordination.

You are expected to contribute ideas and challenge things intelligently.

Once Product and Leadership make a decision, however, you are expected to execute that direction.

We don’t need someone constantly trying to redefine the assignment.

We need someone who can say:

“Here’s a better way to do this. Here’s why. If you agree, I’ll build it.”

And once the direction is established:

“Got it. I’ll build it.”Don’t Reduce the Product Just to Reduce the Work

One of the behaviors we specifically want to avoid is taking functionality out of a prototype or requirement simply because it creates more work.

If a prototype contains functionality for a reason, your first instinct should not be:

“What can I remove?”

Your first instinct should be:

“How do I build this correctly?”

If something genuinely doesn’t make technical or product sense, tell us.

If something can be simplified without hurting the product, recommend it.

But we are not interested in engineers whose primary contribution is finding ways to do less.

We want engineers who make the product better-not engineers who make the assignment smaller.High Output Doesn’t Mean Cutting Corners

High output means high effectiveness.

It does not mean rushing bad code into production.

We expect you to:

• Move quickly
• Think before building
• Use AI intelligently
• Reuse good architecture
• Avoid unnecessary complexity
• Write maintainable code
• Test your work
• Consider edge cases
• Fix problems properly
• Ship

The goal isn’t:

“How fast can I get this off my plate?”

The goal is:

“How quickly can I deliver something that is actually good?”

Work-Life Balance - With a Sense of Urgency

We believe strongly in work-life balance.

We do not expect employees to routinely work nights and weekends.

We believe people should have time away from work, recharge, spend time with family, and live their lives.

But software doesn’t always respect the calendar.

If a serious production issue occurs on a Saturday, Sunday, holiday, or outside normal business hours, we expect the engineer to understand the difference between, * 401(k)

• Dental insurance
• Health insurance
• Health savings account
• Paid time off
• Vision insurance