You have read this page elsewhere. High-value projects, respect for your independence, transparent communication. Everyone writes it; nobody commits to it.
We are taking the opposite approach: our terms — commission, payment period, contract clauses — are put to you in writing with every offer, before you commit to anything.
Hconsul is a recently founded company. Our pipeline is being built. If you are looking for something starting next week, we are not the right people today, and we would rather say so now than collect your details and forget them in a database.
We are assembling a small pool of senior engineers ahead of our first engagements, for a specific reason: we refuse to place someone we do not know on a project we are contractually answerable for. It means that when work arrives, we already know who to offer it to.
We will not ask for your résumé to pad a database and reassure a client about our capacity. We will not send your profile anywhere without telling you which client, for what work, and without your prior agreement. If nothing matches for six months, we will tell you rather than leave you in a silence you will read the wrong way.
You get them before you commit, not after.
Our commission is put to you before you accept the work, together with the client rate. So you know exactly what we take, and on what basis.
What it covers: business development, contracting, invoicing, collection, and carrying the risk of the client not paying. We pay you whether or not the client has paid us.
Our payment period is set in the framework agreement and does not depend on the terms the client gives us. Cash flow is an independent’s first problem; we absorb the gap rather than passing it on.
You work with whoever you want, alongside us and afterwards. No exclusivity clause, no obligation to show us your other opportunities.
When an engagement ends, you are free to work directly with the client if they want that. We include a time-limited non-solicitation clause on the work we brought you — that is what protects our business development — but it never stops you practising your trade.
We tell you what the client is billed at the same time as we offer you the work. No gap discovered later, no negotiation where you cannot see the real room to move.
Your contact is an engineer. You will not spend thirty minutes explaining the difference between CQRS and event sourcing to someone ticking boxes on a spreadsheet.
These terms are written into our subcontracting framework agreement, which we send you before any commitment. You are welcome to have it reviewed.
We are not trying to place as many people as possible. Our model rests on work where technical depth makes a measurable difference: architecture, modernization of existing systems, high-volume platforms, taking over critical applications. If a client only wants production capacity with no technical stake, that is not our market.
On site, hybrid or remote depending on the client. Full time or part time where the work allows. We pass on the client’s actual constraint, not a hardened version of it "to be safe".
A check-in at three weeks, then monthly. Not to supervise you — to catch early any gap between what was sold and what you are living on site. When the work does not match what was described, that is our qualification error, and ours to fix.
We run regular sessions between network members: what people ran into, architecture decisions, problems encountered. Deliberately modest in format — there are few of us and we prefer a useful conversation to an event.
We pass on what we see at clients: what is genuinely deployed, what is causing trouble, what is rising. Field information beats a general technology watch.
A readable framework agreement, simple invoicing, chasing clients when they drag. We carry the commercial and administrative relationship so you only have the technical work to deal with.
We are addressing experienced engineers. The criterion is not a technology list but a way of working.
Backend development
The .NET ecosystem mainly, though we also talk to Java, Node and Go people where the context fits.
Software architecture
DDD, CQRS, hexagonal architecture, event-driven design, breaking up monoliths.
Cloud and DevOps
Azure, AWS, containerization, CI/CD, infrastructure as code, observability.
Data engineering
Modelling, pipelines, distributed systems, Kafka, relational database tuning.
Security
Application security, security-focused code review, secrets management, compliance.
Artificial intelligence
Integrating models into production systems, RAG, industrialization. We are looking for people who can ship, not only experiment.
Technical leadership
Tech lead, team reference point, supporting others as they level up.
A consultant who accepts every request without pushing back costs us more than they bring in. We expect you to flag it to the client — and to us — when a direction looks wrong.
Faced with a performance problem, you instrument rather than assume. It is a reliable marker of seniority.
Architecture decisions, operations documentation, written summaries. A substantial part of a senior consultant’s job is leaving a usable trace.
You do not build your position on being the only one who understands the system. That one is disqualifying here.
Nobody masters everything. Saying "I don’t know, let me look" in front of a client beats a confident approximation somebody will have to unpick later.
In practice, 5 to seven years of experience minimum, with a substantial share in production on systems that have real users. We do not work with junior profiles: our positioning does not allow it, and it would not serve you.
A short form: background, areas, availability, rate. No motivation questionnaire, no online coding test. We read what you send, including your public repository if you have one.
A reply within 5 working days, refusals included and explained.
An hour with an engineer. We talk about real projects you have run, technical decisions you made and the ones you regret. It is not a job interview: we are trying to understand where you are strong, not to catch you out.
No coding exercise imposed. If you would rather show code, we are glad to look at it.
We record your strong areas, your context preferences, your geographic constraints and your rate. That document goes to you: you can correct it. It is what we use to offer you work, not an impression at the end of a conversation.
The qualification document is sent to you and stays editable.
When something matches, you get the client context, the scope, the duration, the format, the client rate and our commission. You decide. Turning something down has no bearing on what we offer you next.
We never send your profile out without your explicit agreement on that specific client.
A check-in at three weeks, then monthly. We handle the contractual relationship, invoicing and collection. If something is wrong on site, we step in — that is the part our commission pays for.
A check-in at three weeks, then monthly.
Six differences from how a placement agency usually operates.
You are told it with the offer, not by accident six months later.
Your profile goes to a client only after you agree to that specific client. Blind submission — the reason the same profile lands three times on the same desk — will not happen.
Five working days, with the reason. Prolonged silence is a form of disrespect we refuse to practise.
The technical conversation is with an engineer. You will not have to translate your experience into keywords.
No exclusivity, no non-compete. Non-solicitation is limited to the clients we brought you, for a bounded period.
Our payment period does not depend on theirs. The cash-flow risk sits with us.
No. No exclusivity clause. You can work with other intermediaries, work directly, and run several engagements in parallel if your setup allows it. We only ask that you tell us when you are unavailable, so we do not offer you something you cannot take.