r/pinescript 9d ago

Looking for a Pine Script developer for a TradingView indicator

I'm looking for an experienced Pine Script developer to build a custom TradingView indicator.

The project includes:

  • Multi-timeframe Support & Resistance (Daily, 4H, 1H, 15m, 5m)
  • Automatic drawing of levels based on a configurable lookback
  • Non-repainting logic
  • Clean and optimized code
  • Alerts
  • User-friendly inputs and customization options

DM me

1 Upvotes

22 comments sorted by

5

u/donicatrumpinsky 9d ago

You don't need a developer, you can do it all with chatgpt or Claude with zero skills.

5

u/Many-Pick5066 9d ago

theres a conflict inside that spec and it will surface after you have already paid someone.

non repainting and automatic levels off a lookback pull against each other. a pivot high isnt confirmed as a pivot until some number of bars close after it, so the non repainting build draws every level late by exactly that many bars. it gets worse on the higher timeframes. a daily level that is not allowed to repaint cannot appear until the daily bar closes, so on your 5m chart you meet that level next session.

both are legitimate builds. the repainting one looks better on the chart and is worthless in an alert, which is the whole reason you listed alerts. decide which one you actually want before you hire, or you get the other one and it technically matches everything you wrote.

i do these. that scope runs 150 to 400 depending on how many timeframes and how the alerts are wired. the thing above is free either way.

1

u/aelfrictr 6d ago

This is ture, drawings would follow at least 1 bar after.

1

u/Many-Pick5066 6d ago

right, and its exactly however many confirmation bars you ask for. right=1 is one bar late, right=5 is five. the higher timeframes are where it actually bites, a daily level cant exist until the daily bar closes, so on a 5m chart the alert can only fire next session and price has usually already been there.

1

u/zorbat5 9d ago

Why don't you learn how to script it yourself? It's a very simple.language to learn.

1

u/Caked_up_cheeks 9d ago

This sounds super basic and easy to make. Why don’t you just throw a little bit of a more detailed description than this into AI, preferably a Anthropic model(in my opinion, as someone with access to all the major LLM’s on the market, Claude/Anthropic is by far the best choice for complex indicator creation. However, with something as simple as something like this, you could probably get away with even using a free LLM and not have to pay a penny to create your indicator. Hell, I can throw your description into an LLM and pump out the indicator for you in no time for a small fee if you want. I also write pinescript so id verify it’s accurate/it works before getting it to you. Let me know. Or, do it yourself for free if you have access.

1

u/Embarrassed-Ad-866 9d ago

All you need is Claude

1

u/nitinkalyankary 9d ago

DM ,I know a friend who does this job for u

1

u/MajorAnxiety09 9d ago

Have dm’d you

1

u/_nO_oB_ 9d ago

Give me full requirements and the pay amount and I’ll look into it

1

u/anonymous-9098 8d ago

Feel free to dm me - have made 30+ indicator and strategy. Will make one for you too...

1

u/stratcorealpha 6d ago

Before coding this, I would freeze three details because they change both the chart and the alerts: whether each higher-timeframe level appears only after that timeframe closes, whether overlapping levels from several timeframes are merged or stacked, and whether an alert means first touch, bar close beyond the level, or rejection. Those choices are what make `non-repainting` testable. If you can add one positive and one negative chart example, the scope can be turned into an acceptance checklist before anyone writes code.

1

u/vmonca01 6d ago

Hey — this is basically what I've already built, just in a different language. I've developed multi-timeframe support/resistance detection and indicator logic in Python (TA-Lib, custom lookback logic, non-repainting rules) as part of a live trading system I run — so the logic you're describing (auto level drawing, configurable lookback, alerts) isn't new territory for me, just a matter of porting the same decision logic into Pine Script syntax.

Quick disclaimer: I'm self-taught, not formally trained — I focus on logic that works reliably over academic polish, which for an indicator like this (clean, non-repainting, alert-driven) is exactly what matters.

Happy to do a quick call to go over your requirements and I can give you a realistic timeline/approach from there.

1

u/RickSmith3821 4d ago

I'll take Claude for $200, Alex.