Find Jobs
Find Jobs Near You – Available Work in Your Location
Full Stack Engineer
Career Insights for Full Stack Developer
See where this job fits in the broader career landscape. Knowing your career path helps you see what's possible from here.
Scorecard
Based on California data
Review key factors to help you decide if this role fits your goals. How is this calculated?
What they do
A Full Stack Developer writes code to support all aspects of a web-application, including the front-end which implements the visual elements and the back end which provides the business logic in the application. Needs to be skilled in front-end language such as javascript, back end languages such as Python, Ruby or PHP and database languages such as SQL. Analyzes customer or user needs, designs programs, writes code, tests design, and documents programs. May assist with upgrades or maintenance.
$153,348 / year median in California
+5% projected growth
Job Description
Full Stack Engineer at Okara Full Stack Engineer at Okara in Union City, California Posted in about 13 hours ago.
Type:
full-time Okara is an AI CMO that runs a team of specialized agents across every organic and social channel that matters for growth - SEO, GEO, an AI writer, Reddit, Hacker News, X, and more on the way. Each of those agents is a real, shipped product used daily, by us and by customers, and we need engineers who can own a piece of that and move fast. You'll work directly with the growth team who actually use these agents every day, which means an unusually fast feedback loop: you ship something, someone on the growth team uses it that afternoon, and you hear immediately if it's wrong. Our tech stack is NextJs, React, Vercel, AWS, etc. Build and ship features across our agents - SEO, GEO, AI writer, Reddit, X - end to end, not just the easy parts. Own at least one agent within your first month: not just tickets assigned to you, an actual area where you're the go-to person. Work directly with the people using what you build, and fix what's actually broken, not just what's in the backlog. You can explain what you built and why, clearly enough that someone outside engineering understands the tradeoff you made. To succeed here, you need to have built and shipped something real, start to finish, that actual users touched, a previous founding engineer role in a growing startup would be great. To apply, send us a link to something you built and shipped that you're proud of, and one sentence on what you'd do differently if you rebuilt it today.