ZipRecruiter

Log In

1

Software Engineer Startup Jobs in Oklahoma (NOW HIRING)

Gitwit

Staff Software Engineer

Tulsa, OK

Helping shape ventures, not just software. Contributing to the decisions that determine whether ... That might mean you were an early engineer at a startup. It might mean you built a new product or ...

Gitwit

Staff Software Engineer

Tulsa, OK · On-site

Helping shape ventures, not just software. Contributing to the decisions that determine whether ... That might mean you were an early engineer at a startup. It might mean you built a new product or ...

next page

Showing results 1-20

All JobsSoftware Engineer Startup JobsSoftware Engineer Startup Jobs in Oklahoma

Software Engineer Startup information

See Oklahoma salary details

$58.6K

$136.2K

$189.7K

How much do software engineer startup jobs pay per year?

As of Aug 17, 2026, the average yearly pay for software engineer startup in Oklahoma is $136,214.00, according to ZipRecruiter salary data. Most workers in this role earn between $110,800.00 and $159,700.00 per year, depending on experience, location, and employer.

What is a software engineer startup?

A Software Engineer Startup job involves developing, testing, and maintaining software in a fast-paced, early-stage company. Engineers in startups often wear multiple hats, working on both backend and frontend development, infrastructure, and sometimes even product decisions. The role requires adaptability, problem-solving skills, and the ability to work with limited resources. Unlike larger companies, startup engineers may need to prototype quickly, iterate based on user feedback, and contribute to the overall growth strategy. This position is ideal for those who enjoy dynamic environments and taking ownership of projects.

What are the key skills and qualifications needed to thrive in the software engineer startup position, and why are they important?

To thrive as a Software Engineer in a startup environment, you need solid programming skills, a problem-solving mindset, and a degree in computer science or related experience. Familiarity with agile methodologies, cloud platforms, version control (like Git), and rapid prototyping tools is highly valued, and startup engineers may also benefit from exposure to full-stack development. Adaptability, effective communication, and the ability to work independently in uncertain environments are standout soft skills. These competencies enable engineers to rapidly iterate on products, effectively collaborate across small teams, and contribute to the dynamic demands of a growing company.

What can I expect from the daily work environment as a software engineer at a startup?

Working as a Software Engineer at a startup typically means you'll be part of a small, agile team where roles and responsibilities can shift quickly based on company needs. You'll often participate in daily stand-ups, collaborate closely with founders or product leads, and have the opportunity to contribute ideas beyond your core coding tasks. The pace is usually fast, and you'll likely wear multiple hats, working on everything from prototyping new features to troubleshooting production issues. This hands-on, collaborative atmosphere provides excellent opportunities for skill growth, creative problem-solving, and making a visible impact on the company's direction.

What are the most commonly searched types of Software Engineer Startup jobs in Oklahoma?

The most popular types of Software Engineer Startup jobs in Oklahoma are:

What are popular job titles related to Software Engineer Startup jobs in Oklahoma?

For Software Engineer Startup jobs in Oklahoma, the most frequently searched job titles are:

What job categories do people searching Software Engineer Startup jobs in Oklahoma look for?

The top searched job categories for Software Engineer Startup jobs in Oklahoma are:

What cities in Oklahoma are hiring for Software Engineer Startup jobs?

Cities in Oklahoma with the most Software Engineer Startup job openings:

Software Engineer Startup jobs near you
Infographic showing various Software Engineer Startup job openings in Oklahoma as of July 2026, with employment types broken down into 78% Full Time, 11% Part Time, and 11% Contract. Highlights an 100% In-person job distribution, with an average salary of $136,214 per year, or $65.5 per hour.

Staff Software Engineer

Gitwit

Tulsa, OK

Full-time

Medical, Dental, Vision, Life, Retirement, PTO

Re-posted 22 days ago

Job description

Zero-to-One Builder for an AI-First Venture Studio
Great zero-to-one builders are becoming more careful about where to spend their next years.
AI is opening a rare company-creation window, with unusual room for new ventures to emerge fast. But that does not make great opportunities easier to find. And it definitely does not make great products easier to build.
Once you've done real zero-to-one work, you know the risk is not just failure. It is spending your next years on something that was never real enough to deserve them.
Gitwit was built to find problems worth solving.

We are an AI-first venture studio built to win this moment through systematic exploration, ruthless validation, and fast cross-functional building. We do not ask you to make one blind bet on one company, one founder, or one codebase. We sweep broadly, test rigorously, and build the ventures that earn the right to exist.
This role is for the kind of engineer who already knows the difference: someone who cares as much about what should be built as how to build it, and who wants the real version of ownership. Real product authorship, real technical direction, real proximity to users and venture decisions, and repeated chances to shape what gets built and how it gets to traction.

And of course, real upside when the winners emerge.
What the Right Seat Actually Looks Like
This is not a role for someone who wants a clean lane, a polished backlog, and a roadmap handed down from somewhere else.

It is for an engineer who wants to be close to the questions that matter earliest: What is the real problem? What is the sharpest way to solve it? What should be built now? What should wait? What should be killed before more time gets wasted?

At Gitwit, engineers like this do not sit downstream from product decisions. They help shape them. You will work shoulder to shoulder with designers, product strategists, researchers, and venture leaders to turn raw opportunity into real products people want.

You will drive technical direction, but also influence the bigger decisions that determine whether something becomes a feature, a product, or a company. You will think about user experience, business model, technical tradeoffs, speed, quality, and what the market is actually telling us.

And because this is a venture studio, you will not spend your best years trapped inside one stale system or one narrow bet. You will get repeated chances to build from zero, learn fast, and apply that learning again.

That is the seat.
Why This Is a Rare Zero-to-One Seat
Most early-stage engineering roles ask you to make one concentrated bet: one company, one market, one founder, one codebase, one trajectory. Sometimes that works. Sometimes it means spending your next years inside something that was never strong enough underneath.

Gitwit is structured differently.

Here, you get the intensity and zero-to-one challenge of early-stage building without tying all of your learning, upside, and career energy to a single fragile bet.
This is not just a chance to join a company. It is a chance to build inside a company-creation system.
In this role, you will help turn raw opportunities into real products at the heart of new venture creation. You will be involved early, when the questions are still open, the signal is still forming, and the right move is not always obvious.
That means your work will include:
  • Shaping products from the beginning. Helping define what should be built, what should wait, and what should be cut before time gets wasted.
  • Building from zero and shipping fast. Taking ideas from early concept to prototype to real product in users' hands, often in days, not months.
  • Seeing your work in the wild immediately. You won't work on tiny pieces of a giant system that may never reach production. What you build here ships, gets used, and teaches us something right away.
  • Making foundational technical decisions. Choosing the right tools, architecture, and tradeoffs for the stage, instead of inheriting someone else's stack by default.
  • Working close to the truth. Learning directly from users, pressure-testing assumptions, and adjusting quickly when the signal changes.
  • Building across the full product reality. Thinking not just about whether something works technically, but whether it is useful, usable, differentiated, and economically sound.
  • Operating at a pace that keeps things fun. Small teams, minimal process, and the expectation that meaningful progress happens daily. If you love moving quickly, you'll thrive here. If you prefer long cycles and layers of review, this will feel uncomfortable.
  • Helping shape ventures, not just software. Contributing to the decisions that determine whether something becomes a feature, a product, or a company.
We are not looking for someone who has only worked around zero-to-one environments. We are looking for someone who has actually done the work.
That might mean you were an early engineer at a startup. It might mean you built a new product or system from scratch inside a larger company. It might mean you created something on your own and carried it far enough to learn what real users, real constraints, and real tradeoffs actually feel like.

What matters most is not where it happened. What matters is that you have felt the difference between building from zero and executing inside something already defined, and you know you want more of the former.

The strongest candidates for this role tend to have several of these traits:
  • They have real zero-to-one evidence. They have built something from scratch far enough to make meaningful product, technical, and speed-versus-quality tradeoffs in the real world.
  • They think like a product builder, not just an implementer. They care about what should be built, what users actually need, what should be simplified, and what is not worth building.
  • They move well in ambiguity. They do not need every variable resolved before they can make progress. They know how to create clarity while building.
  • They have strong technical judgment. They can make sound architectural and tooling decisions for the stage, without over-engineering or blindly defaulting to whatever is newest.
  • They are voracious learners with sharp judgment about emerging technology. They stay close to the frontier (new AI capabilities, tools, interfaces, and product patterns), not to chase novelty, but to understand what creates real leverage. They know how to evaluate new technology quickly, apply it selectively, and use it where it makes the product sharper, the workflow stronger, or the venture more advantaged.
  • They have taste. They care whether something is sharp, usable, coherent, and worth a user's time, not just whether it technically functions.
  • They can work as part of a real venture team. They communicate clearly, collaborate well, and can think across product, user, business, and technical realities without losing rigor.
  • They want the real version of ownership. Not just more work or more surface area, but more authorship over what gets built and how it earns traction.
You do not need to match some narrow founder-engineer stereotype to be right for this role.
But you should be the kind of engineer who has already shown the instincts and wants a seat that actually lets them use them.
This role comes with the things strong engineers should expect: competitive salary, strong benefits, and meaningful equity in every venture the studio builds, but the real offer is bigger than a comp package alone.

You get a rare zero-to-one seat in an AI-first venture studio built to launch multiple companies, not just maintain one. You get the intensity and authorship of early-stage building, with the structural advantages of a studio: stronger validation, shared resources, repeated shots on goal, and the chance to help build multiple high-impact ventures over time.
Practically, that includes:
  • Competitive salary
  • Meaningful equity in every venture the studio builds
  • 8 weeks of PTO
  • Excellent health, vision, and dental insurance, with 99% of employee premiums paid
  • 401(k) with 4% match
  • Life insurance
  • Paid parental leave
  • Cell phone reimbursement
  • Monthly parking stipend
  • Weekly team lunches
  • Dog-friendly office
  • High-trust, high-autonomy culture
  • The chance to work on multiple high-impact ventures each year
  • Your own private office, and collaborative workspaces in one of the coolest office buildings in Tulsa

The package matters. But for the right person, the bigger offer is where you get to place your next years.
Location and Work Style
This is a full-time, in-person role built around real collaboration (with room for real life).
This role is based in Tulsa. We're open to exceptional candidates who would relocate for the right opportunity, but this is not a remote role. We want engineers who want to build closely with the team in the room, in the work, and in the real decisions that shape what gets built.

That being said, we are very flexible with real life. Some days you might need to work from home, for when the plumber shows up, step out for a kids' appointment, or just for a day of heads-down building. What we can't flex on is the overall proximity and regular in-person presence that keeps the studio engine running fast.
How to Apply
No cover letter. No generic note.

This is the Gitwit Builder's Application. We think it does a much better job of highlighting your unique capabilities and qualities than a resume.

Don't spend time on polish. Raw, conversational, deeper narrative will give us a better signal of how great you are than a fancy deck. Notes, word doc, markdown file, notion, video - whatever works for you.

Click "Apply Now" to dive in.

Apply