MailerLite: Laravel and Vue.js Developer

Logo.gif?ixlib=rails 2.1

Headquarters: Remote


Job description
MailerLite is one of the fastest-growing email marketing services. We help more than 700,000 businesses around the world to keep in touch with their customers.

In order to do even bigger things, we need people in our team that are passionate and great at what they’re doing. We’re looking for you!

Why MailerLite?
Wondering why we think you’ll love working for MailerLite? Here are 6 reasons!

You won’t be bored
Our customers are sending more than 20 million emails per day. Scaling the platform while building new amazing features is a challenge that definitely won’t keep you bored.

You’ll work with a clean codebase
Due to the fact that we use the latest best practices of development and continuous integration (, you can rely on a clean codebase to work with. The technology stack includes Laravel, Vue.js, Angular, MySQL, Redis, Elasticsearch and Docker. We work in sprints and manage projects in Github making use of issues, projects, pull requests and reviews.

Take ownership
We don’t micromanage at MailerLite and try not to interrupt your work with random tasks. We do expect you to take full responsibility and ownership for the stuff you build.

You’ll have experts at hand
Our developer team has lots of experience in web development and email. Whenever you’re stuck, your teammates are eager to help you grow. And they’d love for you to share your knowledge too!

You can pick where you want to work, every day
At MailerLite, we embrace the remote culture. Half of the team works from the office in Vilnius, the others are spread around the world. Every day you get to choose what environment makes you most productive.

You can count on stability
We’re not a startup that’s burning investor money. MailerLite has been around for more than 10 years and is a profitable company that continues to grow. You can count on us to offer you a stable workplace!

  • You’ve worked as a full-time developer for at least 2 years.
  • You’ve built web apps using Laravel and Vue.js.
  • Familiarity with HTTP-based APIs.
  • QA knowledge in writing unit and acceptance tests.
  • Problem-solving mindset.
  • Outstanding attention to detail, (if you apply, include the word “lite” somewhere in your newsletter).
  • Good verbal and written communication skills in English.
  • Ability to work with teams across multiple time zones, and countries.
What we offer
  • Competitive salary – we pay at or above market salary.
  • Remote-first culture with half of the team in Vilnius, Lithuania and the other half working remotely from all over the world.
  • Office or Remote – you can choose every day.
  • Free healthy lunches, snacks and coffee in the Vilnius office.
  • Company-paid retreats that we call Workations. The entire team gathers twice a year for a week in an exotic location to work, learn and have fun together.
  • Generous vacation policy. Take time off when you need it. We trust you.
  • Company paid creative days. Go out explore and share with the team.
  • MacBook Pro and other tools that you will need.
Don’t send us a CV. We like to do things differently.

Instead, here is how we would like you to apply:
  1. Sign up for a free MailerLite account.
  2. Go to “Campaigns”, create a newsletter and send us the URL to Each newsletter has a public URL that can be shared with others.
Before you send the email, you will need your new account to be approved. In the approval form, you will be asked how you collect subscribers and what type of content you plan to send. Just write “Job application.”

Things we want to see in the newsletter:
  • The title of this role in your email subject line.
  • How you heard about this job.
  • Links to your LinkedIn, Twitter, Facebook and/or personal homepage.
  • Links to your source code on GitHub.
  • Previous companies where you worked, your role, projects you worked on and the technology stack you used.
  • Why you want to join MailerLite.
  • Your remote work experience.
  • Your description of a project or product that you loved working on and why.
  • Expected salary.
We wish you all the best of luck!

To apply:


Continue Reading

How I’ve Improved as a Web Developer (and a Person) in 2019

We’re sliding into the roaring twenties of the twenty-first century (cue Jazz music 🎷). It’s important that you and I, as responsible people, follow the tradition of looking back on the past year and reflect on the things that went right and wrong in the hopes of becoming the best version of ourselves in the year ahead.

I never do New Year’s resolutions, except for when I was ten years old and wanted to open a local self-run detective agency by the end of the following year (Scooby Doo was in vogue those days.) But I do reflect on the past this time of year, perhaps as an instinctive response.

Over the years, I’ve improved as a web developer, on my own terms and on my own pace, while learning, unlearning, interpreting and executing what the web technology offers. This post is a reflection of my personal experiences from 2019 and the years before that. I’ll share things I’ve learned that might make us all better web developers heading into 2020. Personal experiences aren’t universal, of course, but it’s sometimes neat to get a look into the things other people are processing and learn vicariously through them.

So here we go.

I spent a lot of time in other people’s code

It was unavoidable because my very first professional project involved updating and upgrading an old application. It was only after some time that I realized I gained wisdom from navigating through code written by others, and also, I developed the guts to voluntarily read others’ code and really pay attention to what it’s doing.

It’s not unlike practicing good listening skills. Reading and understanding code written by someone else requires active attention and fighting the temptation to either zone out or inject your own opinion.

What you can try: GitHub is a great place to see a lot of projects. There are so many open source projects out there and they’re all readily available to look at and digest. I think many of us have experienced times when we simply grab a project or a tool without really getting under the hood and understanding what it’s actually doing or how it fits into our own work. Taking the time up front is an excellent way to not only learn new things, but to make better decisions in our day-to-day work as well. Don’t understand something? Open an issue in the repo and ask away!

I’d be remiss not to mention CodePen here. Not only can you search for just about any pattern, feature, or function, but it also offers collections of Pens and even topics, both of which are excellent for seeing how different people tackle similar ideas.

I tried new web standards even if I thought I’d never use them

It’s just my curiosity, but I think it has made me feel more comfortable in learning something new. That might be variable fonts, serverless, JAMstack, prefers-color-scheme , prefers-reduced-motion , and subgrid, among many others. Geez, we’ve seen a lot of new things in the last year or two, haven’t we?

What you can try: I think you’re already ahead of this by following sites like CSS-Tricks. There are many technical blogs and writers out there who share with their readers what’s new. Check out the list of people who have contributed to this blog — many of them have personal sites where they’re frequently sharing new things. A Book Apart is also a great resource for standards, especially for those of you who might enjoy a break from the screen. You can find so many gems there, from Expressive Web Design to The New CSS Layout.

I created an archive of my favorite code snippets

There were times when I’d think that I’d remember the oh-so-simple syntax of new code I tried… but it turns out simple things are easier to forget. So I decided to keep them neatly in a digital folder, like in the good ol’ times. This has allowed me to go back and reference code when questions or ideas pop up. Otherwise, I’d have to go back and research all over again.

What you can try: I personally don’t use tools, just save them in a file. That said, Gist is always a nice place to keep snippets. And, hey, CodePen lets you create your own collections as well!

Another idea is to leverage your browser’s bookmarks. Save links liberally. Organize them into logical groupings so they’re easy to find later.

I created an archive of my notes, flow diagrams, and other stuff I scribble on paper

I have a standard paper notepad at my office that I use to jot down everything from ideas for a project I’m working on, layout sketches and notes from things I read. It’s also the place where I often start work, much like the way Chris writes “pseudo code” heading into a code editor.

I have a habit of working out the visual aspects of a web application, and often, even the source code on paper. So, I keep those papers safe for when I might have to refer back. It has helped me out in a pinch.

What you can try: I would be a hypocrite if I recommend any of the online note taking tools, because I’ve never found them convenient, ironically. There are lots of physical notebook options out there. Moleskine is a popular one. Sarah Drasner recommended one when she wrote her own post on learning how to learn.

I recognized when someone’s teaching and I need to be a student

I used to have a bad habit: if someone’s explaining something about code that I might already be familiar with, I would process and interpret what they were saying based on my own personal experiences, way before I learned what they had to say first.

It could be a millennial thing or it could be an industry thing, but I’ve always found that people package everything as something that’s being shared, that somehow I’m sitting in a round table with them and we are dissecting things over a box of pizza. 🍕

I appreciate that people make their content inclusive because we’re all adults here. But it also has stopped me from genuinely learning what they were trying to teach. I skimmed through useful information, but never really cared about the context. On my worst days, I missed the point completely, all because my brain’s resources were divided trying to learn and analyze at the same time.

Active listening and learning has provided a bunch of benefits for me this past year. For example:

  • I hear what people are saying more clearly.
  • I retain what people share with me more easily.
  • It makes the people I’m interacting with feel at ease with me.
  • It opens my mind to new ideas and possibilities I may not have considered.

What you can try: When you want to learn from something, whether it’s an article, a tweet, a podcast episode, a documentation or something else, save it and use it. I learned to grow out of my bad habit this year and have found this to be my flow for learning and retaining from others:

  1. I learn something.
  2. I save it for later (in my archive!).
  3. I try it out when I have the time.
  4. I play around with it more and try improving on it, if needed.
  5. I eat my pizza.

I trusted my own judgement more

This might sound like the exact opposite of what I just said about active listening, but it’s more of a counter-balance to being overly reliant on others. Active listening doesn’t mean we can’t have our own opinions or even continue holding onto them. It simply means we hear and retain information that can inform our own opinions.

A good professional opinion could be such a blessing, but good or bad, the moment I found myself giving too much weight to other people’s opinions, like I’d read a blog post on someone’s development environment and think I have to do the same thing, or worse, that the way I do things is wrong, that’s a terrible feeling (hello Imposter Syndrome) and who needs more stress?

What you can try: Instead of automatically believing that anything you read is the golden standard, try putting up a little guard. In other words, instead of thinking, “This is how I should be doing it,” perhaps say, “Oh, so this is how this person does that.”

I started seeking others’ experiences that validates my own

I feel happy when I read or hear fellow web developers share their work experiences and find something that resonates with me on a personal level:

  • “I know! I couldn’t set it up the first time, too!”
  • “Yes, that framework made things slower for me, too!”
  • “No way! I tried to center a floating element, too!”

Seeing that I’m not the only one who makes mistakes or struggles in certain areas makes me feel okay for where my skills are at instead of seeing myself as an unskilled developer who’s prone to mistakes. Chris recently shared his thought process working with flexbox elements — that’s exactly the sort of thing I think we can all relate to.

What you can try: We all bear some responsibility here. Let’s make people feel good when asking questions, even if they seem obvious to us. Share your own mistakes and struggles. The web is a vast and constantly evolving space and we’re all starting from different places.

I made myself the only one who decides what to make on my off-work coding marathons

Like all of you, my learning curve involves coding during my non-working hours. It could be just a new code I’m trying out or a full on side-project.

Seeing others share their side projects inspires me… at least that’s what I want them to do. That hasn’t always been the case. They used to make me think I wasn’t doing enough. Not enough GitHub repos. Not enough open source contributions. Not enough self-imposed challenges. Not enough WordPress plugins. And, sorry Chris, not enough CodePen demos.

With experience, however, I’ve realized there’s only one human soul that can optimally select what I should be working on, based on my skills, my preferences, my necessities and my circadian rhythm – the ghost under my bed.

Once I understood that, every single awesome and crazy side project people share online truly inspires me — or at least makes me smile, which is even better.

What you can try: Be intentional with your personal time. Prioritize what you want to learn and decide the best way for you to learn it. This post by Jason Rodriguez outlines how he planned to level up his JavaScript skills. Chris shared a mountain of ideas for learning CSS. Sarah also has great tips on prioritizing your personal and professional time.

I stopped drinking coffee

This is not up for discussion, my dear reader. 😀

What you can try: Masala Chai.

I started prioritizing my health

Here’s a very silly story. I sprained my wrists thrice in a month. I think it was a voodoo spell. The point is: it was getting harder for me to work.

I was a bit embarrassed to tell people I couldn’t work because I was injured, so I continued like nothing happened. Each time, the sprain would eventually go away because of the ointment I applied at home, but would return soon enough because I wasn’t properly resting it. At one point, the pain spread to my arms and I’d to immediately take my hands away from the keyboard and rest them on my lap. It scared me.

The next day, I started wearing a wrist cast (well, two) and informed my colleagues and technical director that I needed to take it slow.

I know this story sounds like a very simple and obvious thing — and it was a very simple thing indeed. But I learned an important lesson: Health comes first.

Our job description doesn’t come with health warning stickers, but there are consequences in reality.

What you can try: Take care of your health first. Physical or mental, chronic or acute, mild or severe, internal or external, when your health problems go away, it improves the quality of your life, personally and professionally. If you’re lucky enough to have good health insurance, use it. Schedule an annual physical exam. Listen to your body when it says it’s hungry, thirsty, or simply needs a rest.

I know, easier said than done. But it’s important nonetheless and something worth striving for.

I’ve started sharing my knowledge with others

Not in a way you might assume. I know the consensus is that we learn when we teach but I haven’t personally experienced that. I don’t learn while I teach. Instead, what I’ve done is focus on how someone I’m teaching could or should learn a particular thing.

  • “Start with the basics.”
  • “Read the documentation.”
  • “Try the demo then proceed to so and so.”

These are some of the statements I found myself repeating to those I’ve mentored.

Those same sentences echo back to me when I’ve to learn something new. When I teach, I pay attention to how it’s learned. And learning is the one skill that never goes out of date, especially in our line of work.

What you can try: I think you’ll probably have to wait a while before you could do this if you’re just starting out as a web developer, but if you’re even somewhat experienced and meet a wide-eyed newbie, don’t miss your chance to teach. Don’t be part of the dark matter. You can teach in a variety of ways, from blogging to making demos. That said, I’ve found real life person-to-person teachable moments to be the most effective.

I realized I can’t read a code once and understand it all. So I use comments.

Here’s my comment about comments: Take them seriously.

Sometimes I can’t even decipher the code that I’ve typed with my two bare hands.

Condensation is a key element of programming languages in addition to something that causes rain. We don’t write, “add one more sheep to the herd.” Instead, we write, i++. Expecting myself to remember and understand everything in one glance simply isn’t practical.

Using well-thought comments cuts back the time it takes me to know what’s happening in the code. This is why I’ve consciously paid attention to using comments this past year. There’s no cost to using them, so go nuts!

What you can try: Take time to go through your code and leave some useful comments each time you’ve coded a module or a feature that works, especially before moving onto what’s next.

I’m not taking working code for granted

I was told margin:auto would center an element. I was told to add return(0) to an onclick event handler. I was also told to use GUID for foreign keys.

I didn’t ask why or how those things worked at the time. I simply did as they said.

I, now, however, know how they work and why I had to use those code.

When I know the basics of a piece of code, it helps me to use the same code or the same logic in scenarios other than the one I learned about it in.

What you can try: Make a quick mental, physical, or digital reminder when you come across a code that you want to know more about. Then remember to go through that list first in your free time. Don’t be afraid to ask someone why code is used a certain way.

I try to mimic extroverted web developers

* takes a deep breath *

I’m an introvert.

My introversion is not so bad that people feel uncomfortable around me. I mean, everybody likes talking to introverts because they mostly listen, right?

Although most of my work is typing in front of a computer I inevitably have to meet people, like clients, users and team members.

Communication is important. And not just the bare minimum.

When you develop a really good relationship with who you work with, your workplace becomes fun. When you develop a good relationship with your users, your work becomes successful; and when you develop a good relationship with your clients, you get more work.

I found there’s no way around it: I had to talk from time to time. I had to put myself out there.

I look at my fellow web developers who are more extroverted for communication pointers. They talk beyond about work. They give their suggestions. They encourage feedback. They drink coffee. And I try to practice that.

What you can try: If you’re an extrovert, I’ve got nothing for you. If you’re an introvert, all I can say is try. And keep trying. And that’s all you ever need to do. We can’t change our personalities, but with some practice and time we’ll learn to manage them better. In fact, it might be worth getting a better understanding of your personality type. Susan Cain’s book Quiet is an interesting (and dense) take on introversion.

I take breaks

I hate this to be true, but I turn into a Shaman soon after I start coding. An unwilling Shaman who gets possessed. The spirit that takes over me likes to only code. It doesn’t like to eat, sleep, talk to people or check Instagram. It’s a very mean spirit.

That’s why I exorcise it regularly to not cloister myself from the world. I pay attention to someone calling me. I leave the desk for tea breaks. I let my laptop’s battery die so I won’t go near it during vacation. I even have a hobby.

I don’t know if taking breaks has improved my performance or not, because I don’t think the mean spirit lacks in performance. I just think it’s good for me to not be always possessed.

What you can try: For those of you with 9-5 job, I would recommend tea breaks at 11AM and 4PM (wow, that came out very specific) And for when you work at home, I suppose you’ll have more things to do, so choose for yourself when you want the break. I like to watch TV, that would be like my ideal break time.

And… that’s it. That’s all the spookiness I could fit into this post. I shared as much of my experience as I could, as well as suggestions you might find helpful. Hope you take something good from it. This might be my final post of the year, so I don’t want to miss this chance to wish you LOTS of good luck as you go into 2020. 🍀

The post How I’ve Improved as a Web Developer (and a Person) in 2019 appeared first on CSS-Tricks.

Author: Preethi

Continue Reading

Fairness Indicators: Scalable Infrastructure for Fair ML Systems

While industry and academia continue to explore the benefits of using machine learning (ML) to make better products and tackle important problems, algorithms and the datasets on which they are trained also have the ability to reflect or reinforce unfair biases. For example, consistently flagging non-toxic text comments from certain groups as “spam” or “high toxicity” in a moderation system leads to exclusion of those groups from conversation.

In 2018, we shared how Google uses AI to make products more useful, highlighting AI principles that will guide our work moving forward. The second principle, “Avoid creating or reinforcing unfair bias,” outlines our commitment to reduce unjust biases and minimize their impacts on people.

As part of this commitment, at TensorFlow World, we recently released a beta version of Fairness Indicators, a suite of tools that enable regular computation and visualization of fairness metrics for binary and multi-class classification, helping teams take a first step towards identifying unjust impacts. Fairness Indicators can be used to generate metrics for transparency reporting, such as those used for model cards, to help developers make better decisions about how to deploy models responsibly. Because fairness concerns and evaluations differ case by case, we also include in this release an interactive case study with Jigsaw’s Unintended Bias in Toxicity dataset to illustrate how Fairness Indicators can be used to detect and remediate bias in a production machine learning (ML) model, depending on the context in which it is deployed. Fairness Indicators is now available in beta for you to try for your own use cases.

What is ML Fairness?
Bias can manifest in any part of a typical machine learning pipeline, from an unrepresentative dataset, to learned model representations, to the way in which the results are presented to the user. Errors that result from this bias can disproportionately impact some users more than others.

Fairness Indicators: Scalable Infrastructure for Fair ML Systems

To detect this unequal impact, evaluation over individual slices, or groups of users, is crucial as overall metrics can obscure poor performance for certain groups. These groups may include, but are not limited to, those defined by sensitive characteristics such as race, ethnicity, gender, nationality, income, sexual orientation, ability, and religious belief. However, it is also important to keep in mind that fairness cannot be achieved solely through metrics and measurement; high performance, even across slices, does not necessarily prove that a system is fair. Rather, evaluation should be viewed as one of the first ways, especially for classification models, to identify gaps in performance.

The Fairness Indicators Suite of Tools
The Fairness Indicators tool suite enables computation and visualization of commonly-identified fairness metrics for classification models, such as false positive rate and false negative rate, making it easy to compare performance across slices or to a baseline slice. The tool computes confidence intervals, which can surface statistically significant disparities, and performs evaluation over multiple thresholds. In the UI, it is possible to toggle the baseline slice and investigate the performance of various other metrics. The user can also add their own metrics for visualization, specific to their use case.

Furthermore, Fairness Indicators is integrated with the What-If Tool (WIT) — clicking on a bar in the Fairness Indicators graph will load those specific data points into the the WIT widget for further inspection, comparison, and counterfactual analysis. This is particularly useful for large datasets, where Fairness Indicators can be used to identify problematic slices before the WIT is used for a deeper analysis.

Fairness Indicators: Scalable Infrastructure for Fair ML Systems
Using Fairness Indicators to visualize metrics for fairness evaluation.
Fairness Indicators: Scalable Infrastructure for Fair ML Systems
Clicking on a slice in Fairness Indicators will load all the data points in that slice inside the What-If Tool widget. In this case, all data points with the “female” label are shown.

The Fairness Indicators beta launch includes the following:

  • pip package: Includes Tensorflow Model Analysis (TFMA), Fairness Indicators, Tensorflow Data Validation (TFDV), What-If Tool, and example Colabs:
    • Fairness Indicators Example Colab — an introduction to Fairness Indicators usage
    • Fairness Indicators for TensorBoard — a TensorBoard plug-in usage example
    • Fairness Indicators with TFHub Embeddings — a Colab that investigates the effects of different embeddings on downstream fairness metrics
    • Fairness Indicators with Cloud Vision API’s Face Detection Model — a Colab showing how Fairness Indicators can be used to generate evaluation results for model cards
  • GitHub repository: Source code
  • Guidance for usage: Fairness is highly contextual, and it’s important to carefully think through each use case and potential implications for users. This document provides guidance for selecting groups and metrics, and highlights evaluation best practices.
  • Case Study: Interactive case study on using Fairness Indicators, showing how Jigsaw’s Conversation AI team detects bias in a classification model using the Toxic Comment Classification dataset.

How To Use Fairness Indicators in Models Today
Fairness Indicators is built on top of TensorFlow Model Analysis, a component of TensorFlow Extended (TFX) that can be used to investigate and visualize model performance. Based on the specific ML workflow, Fairness Indicators can be incorporated into a system in one of the following ways:
If using TensorFlow models and tools, such as TFX:

  • Access Fairness Indicators as part of the Evaluator component in TFX
  • Access Fairness Indicators in TensorBoard when evaluating other real-time metrics

If not using existing TensorFlow tools:

  • Download the Fairness Indicators pip package, and use Tensorflow Model Analysis as a standalone tool

For non-TensorFlow models:

  • Use Model Agnostic TFMA to compute Fairness Indicators based on the output of any model

Fairness Indicators Case Study
We created a case study and introductory video that illustrates how Fairness Indicators can be used with a combination of tools to detect and mitigate bias in a model trained on Jigsaw’s Unintended Bias in Toxicity dataset. The dataset was developed by Conversation AI, a team within Jigsaw that works to train ML models to protect voices in conversation. Models are trained to predict whether text comments are likely to be abusive along a variety of dimensions including toxicity, insult, and sexual explicitness.

The primary use case for models such as these is content moderation. If a model penalizes certain types of messages in a systematic way (e.g., often marks comments as toxic when they are not, leading to a high false positive rate), those voices will be silenced. In the case study, we investigated false positive rate on subgroups sliced by gender identity keywords that are present in the dataset, using a combination of tools (Fairness Indicators, TFDV, and WIT) to detect, diagnose, and take steps toward remediating the underlying problem.

What’s next?
Fairness Indicators is only the first step. We plan to expand vertically by enabling more supported metrics, such as metrics that enable you to evaluate classifiers without thresholds, and horizontally by creating remediation libraries that utilize methods, such as active learning and min-diff. Because we believe it is important to learn through real examples, we hope to ground our work in more case studies to be released over the next few months, as more features become available.

To get started, see the Fairness Indicators GitHub repo. For more information on how to think about fairness evaluation in the context of your use case, see this link.

We would love to partner with you to understand where Fairness Indicators is most useful, and where added functionality would be valuable. Please reach out at to provide any feedback on your experience!

The core team behind this work includes Christina Greer, Manasi Joshi, Huanming Fang, Shivam Jindal, Karan Shukla, Osman Aka, Sanders Kleinfeld, Alicia Chang, Alex Hanna, and Dan Nanas. We would also like to thank James Wexler, Mahima Pushkarna, Meg Mitchell and Ben Hutchinson for their contributions to the project.

Fairness Indicators: Scalable Infrastructure for Fair ML Systems

Fairness Indicators: Scalable Infrastructure for Fair ML Systems

Author: Google AI

Continue Reading

I Started Out As An Accountant, And Now I’m A Developer (And Other Non-Traditional Paths Into Finance & Tech)

wayup prudential company event non traditional paths into finance tech fintech

Not every story in the fintech world is the
same. Even though most people who work in finance roles generally studied
something like accounting, economics, or business, it doesn’t mean everyone did. In fact, some of the best
people in the field are polymaths, with interests in both finance and technology.

Prudential—a financial services leader and a
household name in the insurance industry—is full of stories like these. Their
CEO and Chairman Charles Lowrey actually started his career as an architect.
And that kind of intellectual diversity and entrepreneurial spirit is what
makes Prudential so successful.

Here are a few stories of people who broke
away from what they studied in college and found a new path for themselves—and
their passions—at Prudential.

Bernardine: From Accountant To Developer

Bernardine started as an accounting major, but found that one of her favorite parts of the craft was the growing number of ways to organize and analyze data with digital tools. When she took an internship with Prudential, she found the perfect way to make this into a career.

“As someone with a non-tech background working
in technology, I feel that the best thing I did was start at Prudential with an
internship,” she says. “During this time I learned Tableau, the data visualization
application for which I’m now a developer. I sat down with my mentor multiple
times per week and learned a lot that way. I’m very grateful for that.”

This combination of informal and formal
learning—through classes and training tools—allowed her to become a
full-fledged technologist. Now, she works as a Tableau Developer on one of
Prudential’s innovative Agile teams.

“Just knowing that my skills can span
different parts of this business and that I can aid customers, customer service
reps, wholesalers alike by displaying data insights in a visually creative way
is really exciting,” Bernardine says.

And none of that would have been possible
without the open and supportive culture she found during her internship.

Shannon: From Economics To Tech Talent Development

“When I attended Villanova University, I wasn’t someone who went into college knowing exactly what I wanted to do,” Shannon, who’s been at Prudential for almost three years now, tells us. And while she didn’t know exactly where her career would go, she knew what she wanted it to look like.

“I knew that I wanted to make a difference and serve as a resource to people. I ended up majoring in Economics and minoring in Communication. I thought this combination would prepare me well for working in the ‘business world,’” she explains.

While it wasn’t necessarily the “business
world,” Prudential gave her an opportunity to do just what she set out to.
After an internship in the Office of the CIO at Prudential, she found that she
actually had a passion for technology talent development. Thanks to her
supportive team, she was able to hone the skills involved and secure a
full-time job offer.

Her current role puts her on the frontlines of
talent development, where she places aspiring technologists into the right
roles in the company’s summer internship program. Now, she’s a resource to both
others and the business as a whole.

Abhinai: From Mechanical Engineering To Project Management

Abhinai did
start on the tech side of things, but that’s not exactly where he ended up.

He studied Mechanical Engineering during
college and planned on pursuing a career in the field. However, after a few
internships across industries, he found that his interest in business was just
as strong as his passion for technology. As you might be able to guess by now,
Prudential gave him an opportunity to combine these and turn them into a

Abhinai now works on the business side of
tech, implementing and managing new technologies that make life easier for his
colleagues and the work they do more effective.

“I work on improving the employee experience by introducing and implementing new technologies,” he explains. “So this includes everything from building chatbots to help employees find information quicker or implementing the right survey tool to measure the employee experience.”

Despite his experience with business and tech, moving up on the Project Management team took a lot of learning on his part. But Prudential had his back the whole time.

“A major reason I decided to stay with
Prudential was the supportive culture. My team and manager took the time to
mentor and coach me. I took training and development courses offered to all
employees, but the guidance from people I worked with helped me learn much more
than I could have on my own,” he says.

Prudential Culture Is Built For Learners, Growers, And Doers

It’s no accident that Prudential is packed with stories like these. They seek top talent—not a predetermined list of skills and experience—especially when it comes to interns and early-career folks. And that’s a sentiment that goes all the way to the top.

Want to carve your own path at an innovative fintech firm? Check out open opportunities at Prudential on WayUp!

The post I Started Out As An Accountant, And Now I’m A Developer (And Other Non-Traditional Paths Into Finance & Tech) appeared first on Job and Internship Advice, Companies to Work for and More | WayUp Blog.

Author: Liam Berry

Continue Reading

Christmas Gifts for Graphic Designers

Christmas Gifts for Graphic Designers

Christmas is fun, but choosing gifts might become too overwhelming sometimes. You want to buy the best gift within your budget, and that may require a lot of research. It does not stop there, either. You are not just trying to buy the best item for the buck unless you are shopping for a robot.

Even in that case, you might not want to exterminate the whole human race. (Yes, Terminator, we are looking at you)

So, to save you from the trouble, we’ve put together a list of items that might be helpful if you are looking to buy gifts for graphic designers.

Here is the list:

  1. Wacom Inkling Digital Sketch Pen
  2. Adobe Creative Cloud 
  3. Foldio2
  4. Wacom Intuos
  5. Cloud Storage
  6. Terrarium
  7. Meditation Applications
  8. iPad

 1. Wacom Inkling Digital Sketch Pen

Christmas Gifts for Graphic Designers
Source: Pinterest –

     Inkling enables you to draw your sketches on regular paper and records the drawing digitally. The images that you draw works with Photoshop, Illustrator, Sketchbook and various graphic design programs. 

2. Adobe Creative Cloud 

Christmas Gifts for Graphic Designers

This one is obvious. It’ll make life easier for graphic designers. It can be used for cloud storage, Adobe software, and also accessing the huge Adobe library with a click.

3. Foldio2

Christmas Gifts for Graphic Designers
Source: Orenge Monkie Kickstarter page

       If the designer you are buying the gift for interested in photography, you can buy Foldio2. It’s a portable photo studio box that works wonders. Foldio will also help them with taking photos of their designs. Getting quality photos for designs is quite important for the portfolio.

4. Wacom Intuos

Christmas Gifts for Graphic Designers
Source: Apple

         This pen feels great and natural. It’s accurate and comes with three free downloadable software. It’s also beginner-friendly, so if your friend is just starting it might be a really good gift.

5. Cloud Storage

Christmas Gifts for Graphic Designers

No storage will be too much storage for a graphic designer, so you might want to buy a cloud storage space from Dropbox, Google Drive or another cloud storage service. 

6. Terrarium

Christmas Gifts for Graphic Designers
Source: Unsplash @nielsenramon

The workspace is quite important for graphic designers since they spend a lot of time there. Adding a terrarium might lighten up the work area a bit and make it easier to spend all those long hours.

7. Meditation Applications

Christmas Gifts for Graphic Designers
Source: Unsplash @jareddrice

As aforementioned, since graphic designers spend a lot of hours behind a desk, meditating can help a lot. Not only it will help with professional life, but it will also help with their daily lives as well. So, if the designer you are buying the gift for does not meditate, you can purchase a subscription plan for meditation apps like Calm and Headspace. Make sure to tell them why every designer should meditate!

8. iPad

Christmas Gifts for Graphic Designers
Source: @designmesk

Designers and Apple products go way back. Even though designers need strong computing devices with powerful processors, RAM, and storage (preferably an SSD), and iPad does not provide that, it might be a good new toy for a graphic designer to use with a stylus. Don’t get me wrong, there are people out there who create wonders on an iPad, but I’m just speaking from a general standpoint. There are also many drawing and art apps for iPads they can choose to use!

Overall, there are many gifts for graphic designers you can buy. The gift ideas that are listed above consist of things that will make professional life easier for most of the graphic designers. You can also get personal!

Author: Noupe Editorial Team

Continue Reading
1 2 3 10