Find Jobs
Find Jobs Near You – Available Work in Your Location
Skip to job details
P
PixaSocial
Backend Engineer (Early-Stage / Founding Team)
Career Insights for Back End Developer / Engineer
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 New Mexico data
Review key factors to help you decide if this role fits your goals. How is this calculated?
What they do
A Back End Developer or Engineer is responsible for server-side web application logic and integration of the work front-end web developers do. Usually writes web services and APIs used by front-end developers and mobile application developers.
$113,789 / year median in New Mexico
+10% projected growth
Job Description
| | |
- | ## About PixaSocial Ai PixaSocial Ai (https://pixasocial.
Sign in at https:
//app.pixasocial.com. Legal entity andNew Mexico HQ:
PixasocialLLC, 1209
Mountain Road PL NE Ste N, Albuquerque, NM 87110, USA. This role is onsite/hybrid at that HQ.Careers listing:
https://pixasocial.com/careers (currently LinkedIn-only; apply for this role by email as below).- ## About the role Founding-team backend seat in Albuquerque.
The surface area is real:
auth and accounts, campaign and media APIs, psychographic services other engineers own in depth, inference job orchestration, publishing, billing-adjacent usage, persona export. We need someone who can pick a load-bearing piece, design it, ship it, and keep it up. This is mid-level with founding-team scope: you will work directly with founders and you will be in the product every week. Onsite/hybrid at PixasocialLLC, 1209
Mountain Road PL NE Ste N, Albuquerque, NM 87110. We are not listing other offices.- ## What you'll do
- Architect and implement backend systems that the app at https://app.
com actually runs on:
APIs, persistence, jobs, and the glue between generation, media, and publish.- Own slices of AI capability on the server side—job orchestration for image/video/voice, webhooks, status, retries—working with platform and psych-stack engineers rather than wrapping a model in a vacuum.
- Make data models that survive a real
SaaS:
workspaces, assets in Media Studio, campaigns, channel connections, usage.- Tighten the path from "generate" to "schedule/post" so failures are visible and recoverable.
- Raise the quality of boring things that early products skip: authz, auditability of publishes, migrations, backups of customer media metadata.
- Sit with founders on sequencing: what we build this month vs. what we must not pretend is done.
- Write the kind of docs and API notes a global remote engineer can use without pinging Albuquerque at 2 a.m. their time.
- Live in the product. Register, build a campaign, publish a test post, export a persona if you can. Your cover letter should name the first backend fix, not a generic "I love startups."
- ## What we're looking for
- Mid-level backend engineer who has taken services from sketch to production and on-call.
- You'll likely work with Python and/or TypeScript, HTTP APIs, queues, and Postgres. Comfort with files/object storage and third-party APIs (social, generation) matters more than a branded framework.
- You can design a schema and an API, then change them without breaking mobile/web clients.
- High agency. Founding-team energy means you will do unglamorous work (logs, migrations, a stuck publish job) without waiting for a PM ticket.
- Able to work onsite/hybrid in Albuquerque, NM. Do not apply as fully remote for this listing.
- ## Nice to have
- Prior early-stage or small-team backend where you were one of a few people on the server.
- Experience with media pipelines, webhooks, or social-platform APIs.
- Enough inference/job-queue literacy to debug a stuck generation without throwing it over the wall.
- Comfort pairing with GTM on what "usage" and "workspace" mean for brands vs. creators.
- ## How to apply (required for the next interview round) We only advance people who have used the product.