Wissen Technology
Buying intent
174 tracked signals | Top 15 topics are below | Engineering and HR are carrying most of it.
Attention by team
LinkedIn activity, by teamWhere Wissen Technology's own people are actually spending their attention, by team, by topic. Bands run Low to High against the busiest pairing on this page, and each cell also shows how much of that team's own activity it represents.
Topics being researched
30-day windowEvery tracked topic, ranked by volume, not by our guess at what matters. Confidence is the classifier's own certainty that a signal belongs where we've filed it.
11d ago
8d ago
13d ago
13d ago
10d ago
22d ago
14d ago
13d ago
14d ago
19d ago
18d ago
18d ago
20d ago
22d ago
8d ago
Need intent for a specific topic or industry?
We track the full taxonomy across every account in the graph — including themes not shown on this page.
Who's active at Wissen Technology
verified title on fileTitles, seniority and topic straight from each person's own activity, with a LinkedIn link so you can check any of them yourself.
See everyone, not just the first 10
48 people across every department at Wissen Technology, plus a LinkedIn profile link for each.
Primary products / business lines
LinkedIn company profileAt Wissen Technology, we deliver niche, custom-built products that solve complex business challenges across industries worldwide. Founded in 2015, our core philosophy is built around a strong product engineering mindset—ensuring every solution is architected and delivered right the first time. Our commitment to excellence translates into delivering 2X impact compared to traditional service provid
New capability sought
Employee posts (LinkedIn)Cloud Computing; CI/CD; Data Engineering; Employee Recognition; Generative AI; AI Agent Software; Agentic AI System; Developer Experience
Top accounts researching Wissen Technology
names withheld on the public pageThese are companies whose own people brought up Wissen Technology unprompted, not accounts we guessed might be interested. We can't yet tell an implementation partner from a genuine buyer here, names unlock along with the buyer profile below.
75,708 companies · 411,263 people are researching Hiring
Wissen Technology's own team shows 22 signals on this topic. No one outside Wissen Technology has been seen researching the company by name yet — so this is the market it sits in, not a list of its buyers.
- Artificial Intelligence151,426 cos · 839,012 people
- Career Development71,482 cos · 516,730 people
Buyer profile
company size · seniorityCompany size and how senior the people involved are, the two things that decide whether this is a real deal. Competitor overlap isn't computed yet for this account.
Buying committee functions
Employee job titles (LinkedIn)Engineering — 12 people; HR / Talent — 6 people; Sales — 1 person
What's been said
public posts by Wissen Technology's teamNo public post naming Wissen Technology has surfaced in the past year, so this is what Wissen Technology's own team is posting about publicly — their topics, in their words.
Developers are scared, they are trying hard to justify their role. Which is fine, it's a good survival instinct. But many senior developers are doing it at the expense of junior developers. Some version of "they desperately need me for XYZ". One common theme "I saved the codebase from getting bloated by his/her vibe coding". Well, to all these junior developers - before pushing the code just use a prompt like "analyse and report code bloat in recent changes". The tools are "scary" good these days! In addition to the normal PR review process, it's good to have some "pre-push prompts". To all the senior developers - instead of painstakingly fixing every single mistake, try to 𝗰𝗼𝗺𝗽𝗶𝗹𝗲 𝗮 𝗹𝗶𝘀𝘁 𝗼𝗳 𝗽𝗿𝗲-𝗽𝘂𝘀𝗵 𝗽𝗿𝗼𝗺𝗽𝘁𝘀 for juniors/everyone. Some effort can be saved, and the tools might surprise you.
May 2026As I wrap up my journey at Capital One, I want to say a huge thank you to this incredible team. It's been amazing working with you all. I will truly cherish the memories made and the friendships we've developed along the way. I'm excited for what's next, but I hope our paths cross again soon!
May 2026Yesterday I visited Bright Energy Investments ’ Warradarge Wind Farm Stage 2 project, where Vestas is currently constructing an additional 30 x V136–3.6 MW wind turbines, increasing the site’s total capacity to 283 MW 💨⚡ It was great to reconnect with Tom Frood and the BEI team, and to sit in on the monthly project meeting. It was clear that everyone—from our teams to contractors—is working closely together to deliver strong outcomes, particularly across both delivery and safety. April was a big month, with an impressive six turbines installed, bringing the project to the halfway milestone—15 of 30 turbines now complete. On the safety front, the project is approaching 250,000 hours with zero Lost Time Injuries—an outstanding achievement 🎉 The team marked the milestone with a site lunch, which was a great opportunity to connect with the different contractors and learn more about the roles everyone is playing on site. I wrapped up the day by ticking off a long-time bucket list item—my very first turbine climb! A shoutout to Mark, one of our experienced travelling service technicians, who walked me through everything from safety to construction, operations and maintenance—and reassured me that the elevator noises were completely normal 🤣 Thank you to Jocelyn Dobson and Callum Webb for inviting me out, and to everyone on site for the warm welcome, knowledge sharing, and answering all of my questions!
May 2026“Exactly once” is a lie. You send a request. It times out. Now you don’t know: - did it fail? - or did it succeed but response got lost? So you retry. If it actually failed → retry is correct. If it actually succeeded → you just created a duplicate. There is no third option. You can’t avoid both: - data loss - duplication At the same time. And this shows up everywhere: - payments getting charged twice - duplicate orders - repeated emails - same Kafka message processed again Retries don’t remove uncertainty. They convert it into duplication. So real systems don’t try to be “exactly once”. They assume: - retries will happen - duplicates will happen And design accordingly. - same request shouldn’t create 2 orders - same event shouldn’t update state twice “Exactly once” isn’t a guarantee. It’s something you simulate. #DistributedSystems #SystemDesign #BackendEngineering #Kafka #Scalability #SoftwareEngineering
May 2026Did we mention that Delta Goodrem is representing Australia in the world’s biggest song contest #Eurovision ? You can see her perform her track Eclipse LIVE from Vienna in Semi-Final 2 on Friday 15 May at 5:00am AEST or catch up on the coverage Saturday 16 May at 7:30pm on SBS and SBS On Demand
May 2026