r/dev

▲ 2 r/dev

Early-stage startup offering €50/hr deferred + equity — worth the risk?

Hey everyone,

I wanted to get some honest opinions from people who’ve either worked in startups or been in similar situations.

I recently interviewed with an early-stage digital health startup (US/EU based). The interview went well, and they want me to join their full-stack team.

Here’s the situation:

  • They’re building an MVP and targeting completion in ~3–6 months
  • Expected commitment: ~20–25 hours/week
  • Offered rate: €50/hour
  • BUT — payment is fully deferred until they raise funding
  • They’re targeting funding around September (currently April)
  • Equity is also offered, but capped (details on % not very clear yet)
  • Entire team (including senior engineers) is working under the same structure

So basically:
I’d be working for the next ~5+ months with no guaranteed income, hoping they raise funding and then pay accumulated hours.

My situation:

  • I have ~5 years of experience (full stack, backend-heavy)
  • I run some freelance/agency work, but right now my cash flow is low
  • I can take some risk, but I can’t afford to go months without income
  • I’m also thinking realistically:
    • MVP ≠ funding
    • Funding ≠ immediate cash payouts
    • Even after MVP, they’ll need users/traction first

My concerns:

  • What if funding gets delayed (which is common)?
  • What if they prioritize growth/marketing over paying back engineers?
  • What if the project drags on beyond the initial timeline?
  • Is €50/hr “on paper” actually meaningful if it’s not guaranteed?

What they did offer:

  • They increased the rate from €40 → €50
  • Reduced hours slightly
  • But still no upfront or partial payment

My question to you all:

  • Have you taken similar “deferred + equity” roles?
  • Did it actually pay off?
  • Would you take this risk in my situation?
  • If yes, how would you structure your involvement (hours, expectations, etc.)?

I’m trying to balance:

  • Not missing a potentially good opportunity vs
  • Not putting myself in a financially bad position

Would really appreciate honest feedback from people who’ve been through this.

Thanks

reddit.com
u/Ok-Technician-740 — 4 hours ago
▲ 1 r/dev

anyone figured out the agentic QA gap in Claude Code workflows

Claude Code ships features fast, genuinely impressive, but the verification layer just doesn't exist natively. CI runs, unit tests pass, and there's still this blank space where end to end checking is supposed to happen.

The build side is mostly automated now and QA is still the part that needs a human clicking through screens. Feels like the agentic loop has an obvious hole in it.

reddit.com
u/CameraNo4105 — 7 hours ago
▲ 2 r/dev+1 crossposts

Hiring 3 roles :D

Type: Full-time, Remote
Hours: 40hrs/week
Rate: USD $50/hr (negotiable)
Availability: Minimum 4hrs overlap with 8am–5pm PST required. Preferred hours to be agreed before start.

Greenfield. Fully yours.

We're putting together a small core team — three leads, each owning their domain end-to-end — and we're betting that three sharp, well-equipped people can outrun a team ten times the size. If that sounds energising rather than terrifying, read on.

You'd be the first frontend hire. No existing codebase to inherit, no "we've always done it this way." Everything from the framework choice to the component architecture is yours to decide and defend.

How we start

Before any product code gets written, the team goes through a setup phase together — establishing the product design document, the roadmap, and the tooling and workflows each lead will depend on going forward. You'll be expected to own that setup for your domain: the goal is that by the time you're building, everything is in place to let you build well and keep building well.

How you'll collaborate

This is a small team, not a collection of solo operators. You'll be expected to coordinate closely with the other two leads — agreeing on interface contracts, unblocking each other, and making decisions together when your domains overlap. You'll also work directly with rotating specialists when they're engaged, and own that relationship for your domain.

Job Postings

_________________________________________________________________

Job Posting 1 — Frontend Lead

What you'll own

The entire client-side of the product. That means making the foundational calls — framework, state management, component strategy, testing approach — and then building on them. You'll work with a UI/UX specialist when they're engaged, but you're the one who turns ideas into a working interface.

Part of owning the frontend means owning its quality — not just now, but going forward. We expect you to establish workflows that prevent technical debt from accumulating in the first place, not processes that clean it up after the fact.

A significant part of your collaboration time will be with our Behavioral Experience Architect — a rotating specialist focused on the psychology of engagement. Expect to spend meaningful time, translating behavioral and cognitive insights directly into frontend features. This isn't a soft "make it feel nice" brief — it's a core product differentiator and you'll be the person wiring it in.

What a good week looks like

  • You've made (and documented) an architectural decision and can explain your reasoning clearly
  • You've pushed something real to staging and caught your own issues before anyone else did
  • You've had a productive back-and-forth with the backend lead about a shared interface contract
  • You've used AI tooling to move faster than you could have alone

What we're looking for

  • Strong command of modern frontend development — you've made architecture decisions, not just implemented them
  • Comfortable working from rough ideas — you can turn ambiguity into a reasonable plan
  • Good instincts for UX even when a designer isn't in the room
  • Familiar enough with CI/CD that getting your code deployed doesn't require someone else
  • A track record of shipping clean work — and the habits and tooling that make that consistent, not accidental

Nice to have:

  • AWS experience (CloudFront, S3, Amplify or similar)
  • Accessibility standards familiarity
  • Prior greenfield / 0-to-1 product experience

_________________________________________________________________________________________________

Job Posting 2 — Backend Lead

What you'll own

The server-side of the product. API design, business logic, auth, integrations, data flow. You'll collaborate with a rotating DB architect on data modelling, but the backend is your house — you design it, build it, and keep it running.

On AWS: We lean heavily on managed AWS services rather than building infrastructure we don't need to own. That means reaching for API Gateway, Lambda, SQS, and their equivalents before spinning up custom services. If AWS has a managed solution, that's the default conversation starter.

On the database: PostgreSQL is our standard for everything. That means using jsonb columns for flexible data structures, unlogged tables where appropriate (caching, ephemeral state), and leveraging Postgres features before reaching for a separate service. If you've worked with Postgres beyond basic CRUD, you'll feel at home here.

Part of owning the backend means owning its long-term health. We expect you to establish workflows and tooling that prevent technical debt from taking root — not a backlog for dealing with it later.

What a good week looks like

  • Your API contracts are clear enough that the frontend lead can build against them without constant back-and-forth
  • You've made a deliberate, documented architectural decision and explained your reasoning
  • Something shipped that worked reliably on first deploy — not luck, but because you tested it properly
  • You've used AI tooling to accelerate the parts of backend work that don't need your full attention

What we're looking for

  • Solid backend fundamentals — API design, auth, error handling, data flow
  • Experience owning architecture, not just executing someone else's
  • Comfortable starting before every requirement is locked down
  • Good judgment about when to lean on a managed service vs. when custom is justified
  • Strong PostgreSQL knowledge — you know what it can do and you use it well
  • Familiar with AWS managed services and how to compose them effectively

Nice to have:

  • TypeScript on the backend (Node.js / Bun / Deno — make the case)
  • SaaS-specific experience: multi-tenancy, billing integrations, webhooks
  • Prior greenfield / 0-to-1 product experience

_________________________________________________________________________________________________

Job Posting 3 — CI/CD Lead

What you'll own

The CI/CD infrastructure and everything around it — pipelines, environments, secrets management, observability, and the standards the whole team builds against.

A core part of this role is designing the system so that technical debt is structurally hard to create, not just discouraged. That means gates, checks, and automation that make doing the right thing the path of least resistance. We're not interested in accumulating a debt backlog — we're interested in building workflows that prevent it.

On AWS: We lean on managed services wherever it makes sense. That's a guiding principle you'll help enforce and build around — the infrastructure should reflect the same philosophy as the rest of the stack.

What a good week looks like

  • Deployments are automated, reliable, and nobody had to ask you how to trigger one
  • You've set something up that caught a problem before it hit production
  • The frontend and backend leads are focused on building because the pipeline just works
  • You've documented something clearly enough that a new team member could get up to speed without a walkthrough

What we're looking for

  • Hands-on CI/CD experience — GitLab CI is our preference, strong experience elsewhere is fine
  • Solid AWS fundamentals: IAM, networking, compute, managed services
  • Security and secrets management is not an afterthought for you
  • Comfortable with containerisation (Docker, ECS or similar)
  • Cross-stack enough to support two other leads with different needs
  • Strong instincts for automation — if something can be enforced by tooling, it should be

Nice to have:

  • Infrastructure-as-code (Terraform, CDK, or similar)
  • Observability tooling — logging, tracing, alerting
  • SaaS deployment patterns: zero-downtime deploys, environment promotion, feature flags
  • Prior greenfield / 0-to-1 infrastructure experience

_________________________________________________________________________________________________

On AI tooling

This isn't a "we use Copilot for autocomplete" situation. We're building an AI-augmented workflow at the team level, and we need people who are already living and breathing this stuff.
What we're looking for looks something like: you've gone beyond prompting and have actually built something agentic — even if it was a weekend experiment that never shipped. An MCP server, a RAG pipeline, a LangChain workflow, something that forced you to wrestle with context management, chunking, tool use, or agent coordination. The project doesn't need to be impressive. The learning does.
If your AI experience is mostly chat-based, this probably isn't the right fit yet.
You'll have a generous AI budget, and we expect it to be a core part of how you work — not an occasional shortcut.

A few honest notes

The spec is genuinely open-ended right now — that's a feature, not a bug, but it does require comfort with ambiguity. We're a small team where everyone's work is visible, and we trust each lead to make good calls in their domain.

If you game — bonus points. It's not a requirement, but it's a good signal for the kind of person who tends to fit here.

To apply fill in this form

u/RawlinsDeveloper — 3 hours ago
▲ 3 r/dev

After 18 months of building, we're open-sourcing our entire production AI agent stack. Here's what's actually in it. If anyone wants to see how it works, happy to share a demo.

Hey everyone 👋

18 months ago we started building internal tooling because nothing in the market covered what we actually needed: a full production loop for AI agents, not just one piece of it.

Tracking without evaluating means that something is wrong. If you don't simulate the evaluation, you'll only find out when you release. If you don't have a feedback process, optimization is just changing prompts and hope that it works. Guardrails put on after the event miss the most important failures.

So we built the full loop. And in a few days, all of it goes open source.

Self host it. Extend it. Ship AI that improves itself.

What's actually shipping:

traceAI: OpenTelemetry-native tracing for 22+ Python and 8+ TypeScript frameworks. Your traces, your backend, no lock-in.

ai-evaluation: 70+ metrics: hallucination, factual accuracy, relevance, safety, compliance. Every scoring function is in the repo. Read it, modify it, run it in CI/CD.

simulate-sdk: Synthetic test conversations at scale for voice and chat agents. Your agent works on 10 test cases. simulate-sdk throws 500 adversarial ones at it before users do.

agent-opt: Feeds failed eval cases into a prompt optimization loop and re-evaluates the output against those exact failures. Closes the gap between "we found a problem" and "we fixed it."

Protect: Real-time input and output guardrails across content moderation, bias detection, prompt injection, and PII compliance. Text, image, and audio.

futureagi-sdk: One interface that connects all of the above.

Not a community edition. Same code running behind the platform.

Three questions for the devs here, we would like to know:

  • When your AI agent fails in production, how long does it take you to find which step caused it, the retrieval, the prompt, the tool call, or the model output?
  • Have you ever shipped a prompt change that improved one metric but quietly broke something else downstream, and only caught it after users hit it?
  • If you self-host your eval pipeline inside your own VPC, what's the biggest operational issue: maintaining the infra, keeping metrics updated, or getting the rest of the team to actually run evals before deploying?

DM if you want early access or want to see a specific part of the stack in action before the public release.

reddit.com
u/Future_AGI — 1 hour ago
▲ 1 r/dev

[Remote Developer Role] Build and Maintain Real-World Systems 🧩

We’re a small, execution-focused team shipping real-world applications, no unnecessary bureaucracy, just functional, deployable code.

What You’ll Do

Develop and maintain both frontend and backend components

Build and improve REST APIs and integrations

Work with databases (MySQL/PostgreSQL, etc.)

Debug production issues and deploy quick fixes

Optimize performance and ensure system reliability

Collaborate on UI/UX improvements and frontend features

You’ll Fit If You Have

Solid experience in fullstack development (PHP, JavaScript, HTML/CSS)

Strong understanding of backend architecture, APIs, and databases

Ability to write clean, maintainable, and scalable code

Self-driven with the ability to work independently remotely

What You Get

Fully remote role (US/EU/Canada preferred)

Flexible schedule

Competitive hourly rate: $21–$43/hour based on experience

If you love building stable, end-to-end systems more than sitting in meetings, you’ll feel at home here.

Send your location 📍

reddit.com
▲ 3 r/dev+3 crossposts

Boot.dev for DevOps (coming from backend)?

Hey,

I’m coming from a backend background and have already deployed multiple production apps to the cloud. Lately I’ve been wanting to shift more into DevOps/cloud (CI/CD, infrastructure, automation, etc.).

I’ve been looking at Boot.dev, but it seems more backend-focused. For anyone who’s tried it

Does it actually help with DevOps skills, or is it mostly backend?

Would it be a good path for transitioning, or should I go for something more DevOps specific?

u/goodguyseif — 2 days ago
▲ 2 r/dev

Beta Testing my software?

I have developed some software aimed at a specific problem around engineering (I am an engineer in oil and gas and not a developer) and it essentially is a cut down version of a very popular product. Most people who use this software don’t use anywhere near the full feature set but it is great and widely used.

I want to get my software tested by real world users to get feedback. How do I go about this? Who can I trust to not take the idea, and also this would maybe require a specific type of user?

A bit lost on how to get it tested as I mentioned I am not in this game like a developer would be.

reddit.com
u/DRAFTform — 1 day ago
▲ 1 r/dev

Story how you can avoid getting scamm like me !

** Got ratted lost everything **

the data : 4 / 15 / 2026

I don’t give a fuck about the money, but this guy is a straight-up scammer. Dude took a whole fucking year to eat, then pops back up after that night talking about he got ratted out and lost everything’s in his PC.

Check any Discord ID or Telegram in 5 seconds at real community reports from skid like you.

https://fakeslist.com/devlist

reddit.com
u/Live-Database3537 — 22 hours ago
▲ 0 r/dev

Does anyone offer free work? To build their portfolio?

Does anyone offer free work? To build their portfolio?

reddit.com
u/jobishop345 — 3 days ago
▲ 3 r/dev

are you using what you build?

i build a lot of side projects but i notice that after i build them i don`t use them.
are you actually using your own staff ?

reddit.com
u/Basic_Construction98 — 4 days ago
🔥 Hot ▲ 53 r/dev+1 crossposts

Backend engineer being pushed into fullstack: is specialization dead or should I jump ship?

Hey guys,

I’m a backend engineer with almost 8+ years of experience, mainly in Java and Golang.

Right now, I’m working at a company with hundreds of small teams. The issue is that everyone is basically building similar things over and over again. There’s no real unification due to different customer requirements and, honestly, a lot of bureaucracy.

What makes it harder is that the backend competency here feels quite low, much lower than the frontend. It’s led to this “smart client, dumb server” setup, where most of the logic is pushed to the frontend instead of the backend.

Our tech director (who comes from a frontend background) recently announced that everyone needs to become fullstack. So backend developers are expected to learn frontend, and frontend developers are expected to learn backend.

This is pretty far outside my comfort zone, and I feel a bit torn. On one hand, the company offers great benefits, strong corporate stability, and to be honest, I can kind of chill here. it’s quite difficult to get fired.

On the other hand, the options I’m seeing outside are mostly startups with questionable runways and stories of silent layoffs, which makes the risk feel pretty real.

Another angle I’ve been thinking about: with all the talk around vibe coding and even people like Zuck getting back into coding, maybe the era of specialists is fading? Maybe becoming fullstack is actually the smarter long-term move?

Curious what you guys think. I’d really appreciate any advice.

reddit.com
u/DangerousExpert8187 — 6 days ago
▲ 6 r/dev+1 crossposts

Trying to make client hunting less painful — would love feedback”

I’ve been trying to find a better way to look for clients without spending hours scrolling through Reddit and LinkedIn.

So I put together a small tool that scans posts and tries to surface people who are actually looking for help (based on keywords, context, etc.).

In the video, I just enter a niche and it pulls a few potential leads with some context so it’s easier to reach out.

It’s still very basic and I’m mostly building it for myself, but I’m curious if this is something others would find useful too.

How are you guys currently finding clients?
Would love to hear what’s working (or not working) for you.

https://reddit.com/link/1sol7f6/video/wwu3jqxs1vvg1/player

reddit.com
u/Pixel-ForGe- — 4 days ago
▲ 3 r/dev

The hardest part of building GovTech agents isn't the LLM, it's the Tool Layer. (Built an OAS 3.1 endpoint to bypass PDF scraping)

I'm tired of seeing AI agents break down trying to read poorly written PDFs from city halls via Playwright.

I built a scraper that downloads, injects into an LLM via Groq, and outputs structured and strictly typed JSON (Organization, Object, Value, Date, Modality).

The endpoint was made 100% focused on consumption by other Agents (internal instructions optimized for RAG/Tool Calling from CrewAI/LangGraph).

The average database latency (SQLite async cache) is 50ms.

I'm releasing 5 free Bearer keys for those building SDR (B2B Sales) or GovTech agents to test the integration. If your agent needs to hunt for opportunities in obscure city halls, send a DM or comment and I'll send you the Swagger (ngrok) link and the key.

Warning: The documentation doesn't have a fancy web interface. It's an M2M schema.

reddit.com
u/GrouchyGeologist2042 — 3 days ago
▲ 14 r/dev

loosing track of whats actually deployed since AI writing most of the code

When I wrote the code, I had an intuitive sense of what was deployed where. scanning the diff, and saying "yeah, this touches the auth flow, keep an eye on login metrics," and feel reasonably confident about what we were pushing (3~4 releases per week). 

Now with few agents doing a significant chunk of the coding, the PRs are bigger, the diffs are longer, and I'm approving things based on their design, not so much their actual code. 

Everything is “green” until it breaks - tests pass, the logic is sound, features released but now i find myself more and more “reconstructing” the “what actually changed in that release”. 

I know that I was supposed to feel more in control, but now I'm less certain about everything that I actually coded.

Tried to improve PR messages - nobody reads them (me included)

Tried to tag with the git SHA - now I have a clear starting point to the endless diffs and messages

Anyone else experiencing this and how are you handling the traceability side specifically? Not asking about code review (agents?!?), more about how you document what actually shipped.

reddit.com
u/Aggravating-Slip5857 — 6 days ago
▲ 2 r/dev

Quote help

We are looking for how much it will cost for someone to program an app fully(use ai we don’t mind)(also want help setting up private server database and such)

fully functional app on iOS and android, anyone log in for bookings and staff can see when you book through their log in,

for consumer they see listings by location and options for what service you need then the person who does it and the times and days that they are available

something for you to set alerts if they become available last minute because of cancellations, also reminders of time you booked 48 hours before 36 hours, 25 & 24 hours

If you don’t check in like 24 hours ahead and confirm appointment automatically cancel appointment and alert others on the waitlist

Also reminders of appointment with all details and location which can be pressed taking to maps(automatic on phone), 6 hr before, 1 hr before and 30mins before

If staff side doesn’t check you in at time of appointment you get alert to check in 3 times

We don’t mind how long it takes we just want estimates on how long it will take and for what price

reddit.com
u/Electronic-Share-806 — 4 days ago
▲ 6 r/dev+1 crossposts

Tried claude design on my portfolio and it made my tech stack a shooter game

Was redoing my portfolio in claude design and it suggested turning my skills section into a mini shooter game. The targets are my actual tech stack: python, php, react, flutter, firebase floating around, you capture them for points.

Handed it off to claude code and it built the entire site exactly like the preview. The integration between claude design and claude code is honestly too good, zero gap between what I saw and what shipped.

u/GlumBet6267 — 3 days ago
▲ 2 r/dev

[B2A API DaaS] Liberei um endpoint OpenAPI (OAS 3.1) mockado com Llama-3 para extração de Licitações (GovTech BR)

Cansei de ver agentes de IA quebrarem tentando ler PDF porco de prefeitura via Playwright.

Construí um scraper que baixa, injeta num LLM via Groq e cospe JSON estruturado e estritamente tipado (Órgão, Objeto, Valor, Data, Modalidade).

O endpoint foi feito 100% focado no consumo por outros Agentes (instruções internas otimizadas para RAG/Tool Calling do CrewAI/LangGraph).

A latência média do banco (SQLite async cache) está em 50ms.

Estou liberando 5 chaves Bearer gratuitas para quem está construindo agentes de SDR (Vendas B2B) ou GovTech testar a integração. Se seu agente precisa caçar oportunidades em prefeituras obscuras, manda DM ou comenta que eu envio o link do Swagger (ngrok) e a chave.

Aviso: A documentação não tem interface web frufru. É um schema M2M.

reddit.com
u/GrouchyGeologist2042 — 3 days ago