Networking Guide – How to Rock Your LinkedIn Profile in 11 Steps.

Featured by: William Gilliver (Senior Client Solutions Manager @LinekdIn)

Do you still see LinkedIn as a collection of digital business cards? Then, your writing desk is probably pretty dusty…

What’s the Essence of Digital Networking?

The goals to be active in a business network, as a private person, or with a company profile are as diverse as there are different companies.
The platform can be used to find

  • a new job
  • stay up to date with news
  • put a face to the company
  • engage in interactive business discussions
  • generate leads
  • and much more…

The LinkedIn user numbers are proof of this relevance. In 2021, LinkedIn counts over 740 million members and over 57 million registered companies. This makes LinkedIn the largest business platform for networking worldwide.


Tell Your Story.

The large number of users worldwide (status as of December 2021) and a constantly growing number of participants, increase the risk of getting lost in the network.

Therefore, it is important to update your profile and stand out.

You are wondering now how to attract the attention of other networkers? Just follow the tips of our “11 steps to a successful LinkedIn profile guide”.


11 Steps to Your Successful LinkedIn Profile.

How do we know what the perfect LinkedIn profile looks like? We asked Senior Client Solutions Manager William Gilliver about that.

Step 1: Add a Photo

Members with a photo get up to:

9x more connection requests

21x more Profile views

36x more messages

Step 2: Record Your Name

Pronounce your name for others and make a great impression

  • Update on your mobile device
  • 10 secs, limit background noise
  • Hold the phone close to your mouth

Step 3: Add Your Industry

Members with industry information receive up to 9x more Profile views

More than 300K people search by industry on LinkedIn every week

Step 4: Show You’re Open to Work

  1. Add by clicking ‘add profile section’ and selecting ‘intro’
  2. Specify job preferences
  3. Over 30 million members have used this tool.

Step 5: Draft a compelling summary

Featured in your ‘About’ section

  • Your “elevator pitch”
  • Focus on career accomplishments and aspirations
  • 40+ words

Step 6: Feature Content

Bring your story to life by pinning rich media content you’re proud of to your ‘Featured’ section

Don’t forget to feature-rich media content throughout your profile

Step 7: Detail Your Work Experience

Member with up-to-date positions receive up to:

5x more connection requests
8x more Profile views
10x more messages

Step 8: Add Volunteer Experience

Members who add volunteer experience get up to 6xmore Profile views than those without

Step 9: Add Skills & Get Endorsed

Members who add 5or more skills receive up to

17x more Profile views

Step 10: Request a Recommendation

Recommendations help build your credibility and validate your skills

Step 11: Become Active!

  • Share links, articles, images, quotes, or anything else your followers might be interested in
  • Deeply explore topics that matter to you, then watch the comments to see your impact

And Now: Follow, Follow, Follow.

Follow companies and influencers and always get the most important news first. Do you have a great network already? Bring it to the platform and connect with colleagues and other business contacts to engage and stay in touch.

Now It Is Up to You.

We hope the article was useful for you! And now: register on LinkedIn, suspend or complete your profile and network with us!

Thanks for taking the time to read the CheMondis blog.

Nine things you don’t know about our Supplier Badges.

You’ve probably seen it in our marketplace, right?

Suppliers can now earn badges that will be displayed in different areas on CheMondis. This helps suppliers to stand out from the competition.

Buyers can actively look for suppliers having the badge that is important to them to ensure that all individual requirements are met.

Let’s take a closer look at the badges and their meanings…


There Are Nine Different Badges That Can Be Earned.

As you know, on CheMondis every supplier is individually verified by us. We attach great importance to this to ensure a high-quality standard on CheMondis.

We introduced the Supplier badges for two main reasons

1. to give you as a supplier the chance to outperform the competition

2. and to give some incentive to be active on CheMondis, for example getting the badge as a reward for always responding to requests fast.

This will help every Buyer to find our highest-performing suppliers immediately.


Following Badges Can Be Earned and Are Visible on Chemondis – When Received.


Rising Star: Provides not just full company information but also requirements around Incoterms, package types, and quantities to enable filtering.

Premium Seller: Actively conducted orders on CheMondis within the last 90 days.

Store Owner: Lists all products in an own brand shop.

ERP Connected: Automates order entries and order responses between ERP system and CheMondis to make order information available in real-time.

Documents Available: More than 90% of the active products have a TDS uploaded.

Reliable Replier: Takes care of always responding to requests.

Fast Replier: Ensures to always reply within 5 working days.

Power Seller: At least 50 products published on CheMondis.

Descriptions available: More than 90% of products have a product description.

You Are Curious to See Some Badges in Action?

You’re probably already a CheMondis customer, right? Then, the badges are displayed in different areas on CheMondis. Mainly on the product search pages, the product details pages, and during the negotiation.

You are not registered on the marketplace yet? You can register now and start earning your badges today – or simply benefit from the badges suppliers already earned.

How to Earn a Badge as a Supplier?

 Please login to your CheMondis account first. Then, find your dashboard and the badges details page.

Now you will be able to see green badges, that you already earned, and grey badges that are still open. Each grey badge will show you transparently what needs to be done to get the next badge.

Now It Is Up to You.

If you have any comments, questions, or wishes regarding this feature, please contact us: hello@chemondis.com


 

 

Job Profiles @CheMondis: What makes the job of an Engineer at CheMondis? Sufyan explains.

This is CheMondis.

At CheMondis, every single employee (of currently 56) is constantly working towards our common goal to shape the digital future of one of the largest B2B markets in the world. CheMondis is building the marketplace for the Chemical Industry, combining deep industry know-how with the latest digital technology. We connect verified professional buyers and suppliers in one trusted marketplace to facilitate the digital trade of chemicals, deliver efficiency and data-driven insights.

To make this possible, CheMondis is structured in five teams:

Our People and Organization Team

  • Our Commercial Team
  • Our Engineering Team
  • Our Product Team
  • Our BI Team

Each of these teams follows the logic of agility. Meaning that tasks are shaped and prioritized regularly. This applies to each team individually but also to interdisciplinary work. For many projects, we build project teams with colleagues from various disciplines.

Job Profile Insights.

With this new series of blog articles, we’d like to give you insights into different job profiles at CheMondis, as well as into our organization. We kicked off the series with the article about Umut, one of our Business Development Managers followed by Torben’s article about the profile of a Product Owner. Today we’ll continue with the series with one of our Engineers.

How do you get the best insights, you ask? Well, by asking one of our Engineers directly, of course.

Who is Sufyan?

  • Age: 30
  • Previous job experience: 2 years working as a Java backend Engineer before resuming his studies to get a Masters’s degree in Computer Science back in 2016
  • Responsibilities: Implementation of applications on our marketplace
  • Joined CheMondis in October 2018
  • Why did you join CheMondis? I find the concept of digitizing an “old-school” industry very exciting. But also, the great team culture and opportunity to learn and involve in building something great from the very start.


Is the engineering team organized in any specific structure?

The team is organized into different development teams, consisting of 4-6 teammates. Each team has the skill set to work independently and autonomously. Within each team, there is a Product Owner, a Product Designer, Frontend Developers, and Backend Developers. By structuring into different development teams, we ensure to design our development processes in a fast and efficient way.

Let’s take a quick look into the responsibilities of the two typical roles of our Engineering team:

Frontend Developer: The Frontend Developer takes care that any internet browser can display the CheMondis marketplace and enables the user to interact with our website.

Backend Developer: The Backend Developer is responsible for any kind of logic that is happening in the background of CheMondis to enable the user to benefit from the CheMondis services. 


What do you think is important to bring along in terms of experience to fulfill the job of an Engineer?

Of course, the basis of fulfilling the job is becoming familiar with the tech stack. There is no way around it. Within the team, we work closely together and are always facing new challenges, in which one or the other is already experienced. Therefore, you need to be able to learn, adapt and grow day by day. Perhaps one thing in the area of development may concern only pure coding. But that is not correct. You need business acumen to develop e.g. a new feature properly. Since we develop in two-week sprints, time management is of course also an important skill.


What are the typical tasks of an Engineer at CheMondis?

  • Collaborating with the product team to refine development requirements and estimate the work ahead.
  • Communication and alignment among the development teams and with the in-house stakeholders.
  • Coding new exciting features and testing them before pushing live.
  • Presenting the features in in-house review meetings to make everyone aware
  • Always hunting down the bugs crawling in the codebase
  • Code reviews of other developers

What would you say are the top 5 skills you need to become a successful Engineer?

  • Compatible and efficient knowledge of the targeted tech stack
  • Ability to learn
  • Team player
  • Interpersonal skills
  • Always up for a challenge


How does your typical working day look like?


10:00 Starting the day with a coffee

10:15 Checking the mails

10:30 Daily SCRUM meetings

11:00 Code reviews and coding

12:00 Lunch

13:00 Having a look at the Monitoring dashboards to see if everything is going fine

14:30 Another intense session of coding a feature or fixing a bug

15:30 Attending meetings if any for that day (every second Wednesday is full of meetings as we finish the previous sprint and plans/kick-off the next one)

16:00 Having a chat with the colleagues (about some issue or feature or just on some random stuff, be it related to tech or CheMondis or movies and music or games perhaps) while grabbing a snack from the kitchen

16:30 A final run of coding and before closing the day

What do you value the most about being part of #teamchemondis?

Our great team spirit is what I value the most. Everyone is motivated and pulling in the same direction to drive CheMondis to the best chemical marketplace and that makes the difference. Besides that, everyone helps everyone for the best possible result. I appreciate this learning environment very much. In addition, efforts are seen and recognized so that one’s own work is appreciated.


What are your biggest challenges?

I would say there are three major challenges we tackle in the Engineering team.

1. Never ending technological advances

We need to always make sure that every framework and library we are using is up to date. With every update, we need to make sure it’s compatible with all other integrations. In a time where developments never stand still, this is a special challenge.

2. Develop with deliverables

Whenever we work on a feature that cannot be done in a single sprint we divide the task into multiple parts, so-called iterations. This gives us the opportunity to learn from the previous iterations for further improvements. For each iteration, we must make sure that the iteration has something valuable for the stakeholders and that’s a deliverable. We provide a basic feature first with just the most necessary parts and then, in the upcoming iterations, we keep on adding until it’s finished. So that’s always a challenge to divide the feature into multiple iterations that each iteration has something to deliver to the stakeholders.

3. Bringing together the best implementation designs with user-friendliness

Since the design team is always concerned about how a feature could be the most pleasant to a user’s eyes, engineers always must debate the future implementation of the feature in multiple aspects like performance, architecture, capacity, and maintainability on more realistic grounds – a middle ground must be found here.

Thank you, dear Sufyan, for taking us through your day and sharing important insights into your daily routines, tasks, and challenges.

Now It is Up to You.

You would like to become part of #teamchemondis as well?

Check our open positions and Irene Prinz is happy to meet you in a first interview.

 

Event Guide: What Does It Take To Make the Chemondis Digital Summit Happen?

For the second time this year, we are hosting our CheMondis Digital Summit. The event is planned for one day and takes place online on November 4th, 2021. Therefore, our preparations are currently running on full speed.

But what does it take to organize such an online event? We share our best practices, tips and tricks around the event and project planning. If you want to have a look at the lineup or buy a ticket before reading this article, you can do that by clicking the button below:

When it comes to the organization of such a big event, we generally recommend going through a step-by-step planning. Of course, there are different approaches and best practices. However, this is how it works best for us:

1. Defining the event goals

2. Creation of the concept

3. Organization of the event

4. The Event Day

5. Taking care of the follow-up tasks

Where lies our focus in each of the individual steps? When do we start with the individual phases and what are our biggest learnings so far? Sit back and read through it: we summarized it for you in the following sections.

 

Defining the Event Goals.

Usually, this is the very first step for us when starting with the preparations. No matter if it’s the 2nd or 3rd time we are hosting an event. As we re-evaluate our business goals every quarter and flexibly adapt them to the market, it is not unusual that we have 3 different goals for the same event – even if we host it several times.

When it comes to defining goals, there are different approaches. One common method is the SMART-goals method:

S = specific (goals must be clearly defined)

M = measurable

A = appropriate (reasonable for what is to be achieved)

R = realistic (the achievement of the goal must be possible)

T = terminable (deadline must be achievable)

We like to create our goals accordingly to this concept. Within CheMondis, we pay particular attention to making goals measurable by means of KPIs (Key Performance Indicators) and making results comparable. Thus, we would like to go into this point in a bit more detail.

Event KPIs are set up at the very start of the planning process. To do this, we usually look at the achievement of goals from the previous event and our internal KPIs. It is important to ensure that the goals are ambitious but also realistic. This balance must be maintained. In addition, it should always be possible to keep track of everything. Setting 3-5 goals is recommended.

 

Creation of the Concept.

Once the goals are defined, we start the creation of the concept, which is significantly influenced by our goals. First, of course, the question of the budget should be clarified, because many points of the concept will depend on it.

Now it’s a matter of going into the exact planning of the conditions – in our case, we start with the leading topic. We usually base this on current topics, occasions, events that are interesting for our target group. For example, in the past we had a paints & coatings edition, a digitization special and currently we are planning a sustainability & innovation edition. As soon as the leading topic is set, we go into more detail.

Starting from the leading topic, we define sub-topics for the individual streams. In doing so, we try to find possible subtopics. This will be particularly important later when researching suitable speakers.

Conceptually, it also goes to the planning of the formats. Which event formats are best suited to the content? Workshops? Roundtables? Talks? How long should the individual sessions be? What is a good number of slots?

Since in our case it is an online event, our location is an online event tool. What requirements do we have for the tool and which provider is best suited for this? Where do we get the best price-performance ratio?

As soon as we have found answers to those questions and have set the framework of the event, we can continue with the detailed planning of the content.

Organization of the Event.

A full day event with 3 streams and over 20 talks from external speakers requires careful pre-planning. Of course, it’s not just one person doing it alone. For our summit preparations, we have put together an interdisciplinary team. It consists of marketing experts, designers, and business development managers.

About 3 months before the summit, we start with weekly meetings, which we use to work out certain questions together. Of course, we also have a project plan in which all tasks and milestones are scheduled.

During the organization phase, it is time to get down to the details! The concept on paper is put into action. Potential speakers are identified and contacted, slots coordinated, marketing materials designed, the event page built, attendees invited…

Our internal deadline to be ready with everything is about 2 weeks before the event to have an emergency buffer for unwanted surprises.

 

The Event Day.

 And then the time has come. The day of the event. The day before, we calmly prepare the technology and test everything to make sure that everything works properly. On the event day itself, we meet in the office about 1.5 hours before the official start of the first session. Then we have breakfast with everyone from the task force, but also moderators and CheMondis’ speakers. Afterwards there will be a final briefing for the day and a briefing on the location. Everyone grabs a last coffee and then it’s time to go.

What we have learned in the past that it is necessarily important to have two firefighters who take care of the so-called emergencies – on the phone and by mail. Someone has misplaced his event password, can’t find his way around the event page, needs a special invoice and so on. If something goes wrong, it is usually not a problem if the participants are helped immediately. We want everyone to feel that they are in good hands and that we live up to our own quality standards. Therefore, it is very important to us to provide a good service here.

After the first 3 hours is the official lunch break on all streams and we have a little time to breathe. We order pizzas for the whole team and briefly discuss how things are going until it’s time to move on.

At the end of the day, we all come together for a short wrap up. How many participants were there? What specials were there? How was the feedback? Such an event always brings us forward as a team.

Afterwards we usuqlly have a delicious dinner in a great restaurant. We will take care of the office clean up and the follow up tasks another day…

Taking Care of the Follow up Tasks.

For us, after the Summit is as busy as before the Summit. The day after the event there is a lot to do, from thanking the speakers, writing invoices, taking advertisements offline and of course checking how far the goals we set at the beginning have been achieved.

During the week following the event, when everything is still fresh in our minds, we also have a feedback session with all participants, where we analyze feedback, note improvements, and collect ideas for a next event.
 

Now it is Up to You.

In this sense, we are looking forward to meet you on November 4th in one of our session! The registrations are still open.

For already registered CheMondis marketplace customers the registration for the event is free of charge. For all others: in the first ticket phase we offer early bird tickets for 49 EUR with a “buy one get two” special. *only available until end of October 2021.

 

Job Profiles @CheMondis: What makes the job of a product owner at CheMondis? Torben explains.

At CheMondis, every single employee (of currently 56) is constantly working towards our common goal to shape the digital future of one of the largest B2B markets in the world. CheMondis is building the marketplace for the Chemical Industry, combining deep industry know-how with the latest digital technology. We connect verified professional buyers and suppliers in one trusted marketplace to facilitate the digital trade of chemicals, deliver efficiency and data-driven insights.

To make this possible, CheMondis is structured in five teams:

  • Our People and Organization Team
  • Our Commercial Team
  • Our Engineering Team
  • Our Product Team
  • Our BI Team

Each of these teams follows the logic of agility. Meaning that tasks are shaped and prioritized regularly. This applies to each team individually but also to interdisciplinary work. For many projects, we build project teams with colleagues from various disciplines.

Job Profile Insights.

With this new series of blog articles, we’d like to give you insights into different job profiles at CheMondis, as well as into our organization. We kicked off the series with the article about Umut, one of our Business Development Managers. Today we’ll continue with the profile of a Product Owner.

How do you get the best insights, you ask? Well, by asking one of our Product Owners directly, of course.

Who is Torben?

  • Age: 40 years old
  • Previous job experience: Torben started his career in the gaming industry, where he stayed for 14 years. His top experience is in product- and project management
  • Responsibilities: Improving the CheMondis marketplace by continuous development of new features and services
  • Joined CheMondis in: July 2020
  • Why has he joined CheMondis? It is a very interesting challenge and opportunity to connect different parties from the chemical industry and to change the market to get a more digital approach.

Is the product team organized in any specific structure?

The team is organized into different development teams, consisting of 4-6 teammates. Each team has the skill set to work independently and autonomously. Within each team, there is a Product Owner, a Product Designer, Frontend Developers, and Backend Developers. By structuring into different development teams, we ensure to design our development processes in a fast and efficient way.

Let’s take a quick look into the responsibilities of the roles:

Product Owner: Responsible for the product roadmap and making sure the product vision of CheMondis gets implemented. The roadmap is divided into different small task which need to be created and prioritized constantly for each development team.

Product Designer: Takes care that each service or feature that is created is solving a customer problem and follows high user experience standards in terms of usability and design of our marketplace.

Frontend Developer: The Frontend Developer takes care that any internet browser can display the CheMondis marketplace on any kind of device (mobile, tablet, desktop etc.) and guarantees a great user experience at any interaction.

Backend Developer: The Backend Developer is responsible for any kind of logic that is happening in the background of CheMondis to keep the page fast and responsive. All activities take place in the infrastructure of the marketplace.

What do you think is important to bring along in terms of experience to fulfill the job of a Product Owner?

I don’t think experience is that important. But if someone already has knowledge from working in the chemical industry, for example, that is of course an advantage in order to better understand customer needs. In the product team and in the company as a whole, we are a group of experts from different industries, which is, of course, the best-case scenario in order to incorporate different perspectives.

But for the role of a product owner, I think very good communication and analytical skills are very important. That’s because you’re constantly serving a number of stakeholders. On the one hand, every development of the marketplace has to meet the needs of the business. For this purpose, regular interviews are conducted with customers to understand their needs, challenges, and goals. On the other hand, it has to be technically feasible.

What are the typical tasks of a Product Owner at CheMondis?

A major part of the tasks lies in creating and maintaining the product backlog. There, tasks are stored for a certain period before being implemented. For us, these tasks usually relate to the technical improvement of the marketplace, whether through new features or changes to existing ones.

 

What would you say are the top 5 skills you need to become a successful Product Owner?

  • Communication skills
  • Empathy
  • Business thinking
  • Problem solver mentality
  • Must be able to look over the edge of the plate


How does your typical working day look like?

I start my day by checking through new messages and emails. Of course, then I get a nice coffee to prepare the scrum meetings I have that day. These meetings include:

Daily Stand-Up’s: This kind of meeting takes place every day for 15 minutes with the entire scrum team to update each other, align on the next task and solve any possible issues.

Reviews: Each development presents the outcome of the last sprint to all stakeholders within CheMondis in a defined rhythm. Feedback and ideas for further sprints and optimizations are discussed together.

Retros: The team examines how the just-completed sprint went on different levels: personal feelings, relationships, processes, and tools. The main idea is to improve on these factors in the next sprint.

Planning: The team determines the tasks they will work on during the next sprint and discusses their plans for completing those.

When everything is set for the day / upcoming sprint, I try to solve customers’ problems by digging into collected data and communicating with stakeholders.

 

What do you value the most about being part of #teamchemondis?

At CheMondis, the focus is clearly on the team. We have colleagues from all over the world here in our office in Cologne. Diversity is a huge driver for us. Also, I find working on our product, the marketplace, incredibly exciting. The opportunity to work on something new which can move an entire market.

 

What are your biggest challenges?

Sometimes, it is a challenge to understand the customers’ behavior and needs as the chemical industry is still very traditional. To get a better understanding, we conduct customer interviews and ask specific questions and find out about their needs. Moreover, we do testing directly on our marketplace to measure if a feature is valuable for our customers. By doing so, we get a better understanding of how the platform should look like for an optimized customer-centric approach.

Thank you, dear Torben, for taking us through your day and sharing important insights into your daily routines, tasks, and challenges.

Now It is Up to You.

You would like to become part of #teamchemondis as well? Check our open positions and Irene Prinz is happy to meet you in a first interview.

Thanks for taking the time to read the CheMondis blog.