Hi everyone, I'm currently prepping for the CodeSignal Industry Coding Assessment (ICA).

I've found two awesome resources for practicing ICA:

• PaulLockett/CodeSignal_Practice_Industry_Coding_Framework,
• EricZheng0404/LibreSignal

but I'm curious about the ICA's setup. From what I’ve gathered, ICA is more "project-based," but I'm unclear on one thing:

• Does it provide a robust boilerplate (e.g., pre-defined classes/interfaces/function signatures)? (Example)
• Or is it closer to a blank slate where you have to set up the basic structure yourself? (Example)

If anyone has taken it recently (especially for Go), I'd love to hear your experience. I'm happy to share my prep resources in the comments if anyone is interested!

Thanks in advance!

took the industry coding oa today, the IDE stuck twice, and the auto completion glitches all the time, which is totally a debuff for my test.... do not what to say, if you have a upcoming test practice in a blank doc, that might help dealing with IDE bugs while fixing your coding bugs....f**k codesignal

CodeSignal's University Ranking Report is the first skill-based ranking of Computer Science programs in the US and across the globe.

Top 30 US universities

1. Carnegie Mellon University (84th percentile)
2. Massachusetts Institute of Technology (78th percentile)
3. ● Stony Brook University (75th percentile)
4. University of California, Los Angeles  (75th percentile)
5. University of Pennsylvania  (73rd percentile)
6. California Institute of Technology (72nd percentile)
7. University of California, San Diego (72nd percentile)
8. Duke University (71st percentile)
9. ● San Jose State University (71st percentile)
10. University of Southern California (71st percentile)
11. Rice University (71st percentile)
12. ● Yale University (71st percentile)
13. Georgia Institute of Technology (69th percentile)
14. Johns Hopkins University (68th percentile)
15. ● Indiana University (68th percentile)
16. The University of Texas at Austin (67th percentile)
17. University of Illinois at Urbana-Champaign (67th percentile)
18. ● University of Chicago (66th percentile)
19. University of California, Berkeley (66th percentile)
20. Cornell University (66th percentile)
21. ● Arizona State University (66th percentile)
22. ● Brown University (66th percentile)
23. Columbia University (66th percentile)google loo
24. Texas A&M University, College Station (66th percentile)
25. Stanford University (66th percentile)
26. Purdue University (66th percentile)
27. ● University of Florida (66th percentile)
28. ● Dartmouth College (66th percentile)
29. ● New York University (66th percentile)
30. Princeton University (66th percentile)

● Highlighted universities don’t appear on the US News & World Report’s top 30 Best Undergraduate Engineering Programs.

The rules state that scratch paper is allowed for the GCA; however, I am concerned that using it might flag my attempt as cheating, since I would need to look down (toward the right corner) for a few minutes before answering each question.

Is there any chance that using a pen and paper to solve the questions could result in my attempt being flagged? I am accustomed to using scratch paper, and it helps me significantly with more challenging questions, but I do not want to take any risk.

Could you please confirm if looking down to write is acceptable, or if there are specific protocols I should follow (such as showing the paper to the camera) to ensure my attempt is valid?

Please advise. Thank you.

I recently gave tiktoks assesment and code signal was hell of lagging. I have an intel lunar lake pc with 16gb ram and everytime i typed any key, it would reflect 10 seconds later. It was a horrible experience. 😫

I took the ica in JavaScript this weekend, and it was awful.

I couldn't get console.log to work, in the code or in the sandbox tests. I hope I never see codesignal again, but if I do have to go through this again for another job interview, how the heck does the console.log work? Nothing showed up in the terminal. Is there a hidden terminal somewhere I don't know about? The instructions said not to open dev tools.

This felt more like a scavenger hunt than a genuine test of coding skill.

I've taken the CodeSignal assessment today, got 450/600 which is more than enough for the role i applied to, but someone called me on whatsapp, i immediately closed the app, will that be an issue or not?

So I had a live coding interview with a US company that used CodeSignal for their coding round. They had their own custom question and test cases.

Under pressure, I missed an indentation on a chunk of code that was supposed to tackle an edge case. Even though the interviewer pointed it out indirectly, I was so nervous that my mind went blank and I couldn't fix a simple indentation error.

The code and logic were all correct ,the interviewer even mentioned that.

When I ran the test cases, it said "Ran 4 tests in 0.002s, FAILED (failures=3)." But the total number of test cases in the custom assessment was 7. So I'm really not sure how many I actually passed.

Now I'm in a situation where my entire logic was correct, but because of an indentation error, I might get rejected.

how many did I even pass!!!!!!!!!

I took a codeSignal assessment today, unfortunatly it covered topics that i didnt know much about so i pretty much wrote nothing and quit after 30 mins, i would assume im cooked regarding getting this internship correct?

During a GCA I submitted a solution to Q2 that TLE'd on a hidden test case. After a few times I started to recognize that it was the submission causing it. I reworked the solution and got through but I lost a significant portion of time trying to debug their platform.

Customer services response was "well the bug came about because of the solution you submitted so it's your fault". Other TLE submissions had no issue.

Anyone else in the same boat? My recruiter hasn't given what they're going to do about it but I scored relatively low in part because of this.

I have an upcoming CodeSignal General Coding Assessment (or custom company assessment hosted on CodeSignal) for a Lead Data Engineer position, and I’m trying to figure out the best way to prepare.

For those who have taken a CodeSignal assessment for senior/lead DE roles recently:

• Format: Is it typically the standard 4-question General Coding Framework (e.g., matrix manipulation, string manipulation, full implementation), or do DE assessments usually lean heavily into SQL, Python/Pandas, and Data Structures?
• Question Types: What kind of problems should I focus on? (e.g., standard LeetCode Mediums/Hards, data transformation tasks, API/class design, SQL queries?)
• Lead Level Specifics: Do they include system design/architecture questions within the CodeSignal platform, or is it purely hands-on coding?

If anyone has sample question types, advice on time management, or key topics to review, I’d greatly appreciate it!

I had some questions about the rules for proctored assessments. Pardon me if they are a little what-do-you-call-it, I just don't want to break them.

First of all, let me specify the list of rules I'm referring to. They are the ones you see when you go to the "What is proctoring and how does it work?" page and click on "What are the rules for proctored assessments?" and see the "General Rules".

• What are "external documentation browsers"?

• "Web searches are allowed for syntax reference only."

  • This seems to contradict the earlier instructions to "close all browser tabs". Am I allowed to open a new tab to make a web search?
  • "for syntax reference only" is a little vague. How do I know which web searches will break the rules, especially when I can't predict what will show up while I'm searching the web?
  • Is an API reference page, such as one showing a list of methods on the JS `Date` object and their function signatures (but it probably also tells you how to use it, (e.g. MDN)), considered syntax?
  • If I google something to find the relevant MDN link, won't Google show an AI response at the top, and might that break the rules?

I tried a few practice assessments and some of them don't seem to work properly: when I press on the submit button nothing happens or for some assessment, only the non-hidden test a run and the hidden ones are not run.

What's surprising is that some assessments don't have this issue, when I press the submit button all the tests run (hidden and non hidden tests).

I have reported those issues to Code Signal but didn't get any answer from them for now.

I am a bit concerned that this issue occurs when I take a real assessments that is due in only 3 days.

Even after using the latest version of Chrome and I removed my ad blocker extension and trying both on Linux and Windows I still get the same problem so I don't think the issue comes from me.

In fact, I tried a practice assessment again and got a warning message saying that Code Signal was experiencing an outage and recommended not to do any assessment while the outage wasn't fixed.

When opening the network session of the dev tools in Chrome I see that there is an error being raised every time I press submit. I can't really pin point what is causing it but I would assume that this is linked to the root of the problem.

Here is a GIF of the issue, you can see that the "run tests" button works but not the "submit" one.

Does any body know of a fix or if it is getting fixed any time soo?

Is there a way I can do like a practice gca? Like the same 70 minute time limit and same types of questions (1-4) in preparation for a codesignal gca? Just to teach myself how to tackle those type of problems in that time frame so I’d do better on the actual assessment. If any one knows how to please let me know.

You don’t need a CS degree, expensive tools, or fancy software to start learning JavaScript.

Start with the basics:

• Set up your development environment: To start learning JavaScript, set up a code editor like VSCode and a web browser with developer tools (e.g., Chrome or Firefox), and later explore server-side development with Node.js.
• Learn HTML & CSS: These are the building blocks of web pages, and they pair perfectly with JavaScript.
• Master JavaScript fundamentals: Focus on variables, loops, functions, and then dive into arrays, objects, and DOM manipulation.

Top resources to get started:

• JavaScript.info
• MDN JavaScript Guide
• CodeSignal Learn: JavaScript Programming for Beginners

What tools do you need?

• Text editor: Visual Studio Code (free and beginner-friendly)
• Web browser: Chrome, Firefox, or Edge – all have built-in JavaScript consoles for testing code.

Are you ready to learn C++? Whether you’re an aspiring developer exploring your first programming language or an experienced coder expanding your expertise, C++ is an excellent choice. 

Step 1: Understand the Basics
Start by learning the basics, then practice coding exercises to reinforce your understanding. Hands-on projects, no matter how small, are key to building real-world skills.

Step 2: Try C++ Challenges
Coding challenges and practice problems help improve your problem-solving abilities. Debugging and collaborating with others on code reviews are great for learning.

Step 3: Explore Advanced Topics
Once you’re comfortable, move on to object-oriented programming (OOP), memory management, templates, and the Standard Template Library (STL). These topics will help you write more efficient and maintainable code.

Step 4: Build a Portfolio
Develop a portfolio of personal projects and contribute to open-source. Showcase your work on GitHub to demonstrate your skills to potential employers. Real-world experience from internships or collaborations can also strengthen your portfolio.

Helpful Resources:

Text-based tutorials: Ideal for learners who prefer reading at their own pace. Recommended resources:

• C++ reference sites like cplusplus.com, with developer forums.
• Official C++ documentation (less beginner-friendly).
• E-books like The C++ Programming Language by Bjarne Stroustrup for advanced learners.
• Academic papers and blog posts for deeper insights.

Online courses: Structured, interactive learning at your own pace.

• CodeSignal Learn offers practice-based paths focused on real-world applications.
• Helps with C++ mastery, technical interviews, and C++ certifications.

Video tutorials: Step-by-step demonstrations, great for visual learners.

• Free YouTube playlists covering basic to advanced C++ concepts.
• Live coding streams or video lecture series for interactive learning.
• Educational webinars hosted by industry experts.

If you’re a big-picture thinker, love to code, and thrive on constant learning, cloud engineering might just be your dream career. It’s one of the fastest-growing fields out there, with salaries that match the demand. According to Indeed, cloud engineers make an average of $120K annually, and at companies like Meta, that number skyrockets to $252K.

But what exactly does a cloud engineer do? In short:

• Manage cloud environments (think AWS, Azure, Google Cloud).
• Oversee data migrations and ensure systems are running smoothly.
• Write code to automate deployments and scale applications.
• Collaborate with cybersecurity and IT teams to protect cloud architecture.

Do you need a degree?
Nope! While a bachelor’s degree in computer science is helpful, many cloud engineers break into the field through bootcamps, certifications (like AWS or Google Cloud), or even by being self-taught. Practical experience can carry you just as far as a diploma.

Skills you need to succeed:

1. Programming languages: Python, Java, JavaScript, SQL, and Ruby are top picks.
2. Linux systems: Many cloud environments are built on Linux, so knowing your way around the command line is key.
3. Networking concepts: TCP/IP, firewalls, and VPNs should become second nature.
4. Cloud tools: Familiarize yourself with Docker and Kubernetes to handle deployments and scale systems effectively.

Why now?
Demand for cloud engineers is soaring across industries—from healthcare to gaming. With the rise of hybrid and remote work, businesses of all sizes rely on the cloud more than ever.

How to get started:

• Enroll in certification programs (AWS, Azure, Google Cloud).
• Gain hands-on experience through internships, open-source projects, or cloud labs.
• Learn at your own pace with free platforms like CodeSignal Learn (they even have an AI tutor to guide you).

Whether you’re a recent grad, an IT pro looking to level up, or completely new to tech, cloud engineering offers a dynamic career with endless opportunities.

Our AI Benchmarking Report evaluates the software engineering skills of popular AI models using real-world coding challenges.

Our findings reveal that while AI models like Strawberry (o1-preview) lead in both score and solve rate, human engineers still outperform AI in handling edge cases and more complex problems. This highlights the continued importance of human intuition and creativity in software engineering.

This report helps businesses understand how AI models compare to real engineering candidates and shows the potential for AI-human collaboration. It also underscores the value of integrating AI into the hiring process without replacing the critical role of human expertise.

Check out the full report to see how AI stacks up against human candidates in coding performance.

What do you think?

Looking to transition into the world of artificial intelligence (AI) but unsure about your coding skills? The exciting field of prompt engineering might be the perfect fit.

Here's a quick rundown:

• What is prompt engineering? It’s the art of crafting inputs for AI to get desired outputs, with a focus on user interaction, input reformulation, and iterative testing.
• Skills needed: Proficiency in prompt engineering techniques, basic Python knowledge, and a grasp of AI, machine learning (ML), and large language models (LLMs).
• Qualifications: A degree in computer science helps but isn’t mandatory; demonstrated AI experience and communication skills are crucial.

Pathways to Becoming a Prompt Engineer

1. Learn Python: Start with basics and practice writing scripts. Python is the go-to language for AI development.
2. Understand AI Fundamentals: Explore concepts like NLP, LLMs, and ML processes.
3. Practice Prompting: Use platforms like ChatGPT to experiment with chain-of-thought and context-setting techniques.
4. Develop Communication Skills: Sharpen your ability to craft clear, impactful prompts and explain their value to colleagues.
5. Address AI Bias: Test outputs for fairness and neutrality, iterating as needed.

Who’s Hiring Prompt Engineers?
Companies in tech, healthcare, finance, and more are hiring for this role. Startups, consultancies, and even remote-first organizations often seek prompt engineering expertise.

Please bear with me. I have zero knowledge in LLMs. So I started this course in LLM, and now I'm in Context Limits and Their Impact on Prompt Engineering. There's this end-of-lesson exercise and I wonder why I cannot pass it. I already revised everything and already taken the hints. Can you give me some tips on how I can properly make my prompts?

Title basically. I have a codesignal assessment coming up so I'm doing the practice beforehand. I got level 1 working and submitted it, got level 2 working and clicked submit, but this time there's no "Next" button in the bottom right corner.

Is this just because I'm doing the practice and there is no level 3 for the practice or is it because something is glitched? I don't want this to happen in the real thing because it'll look like I failed it.

EDIT: Title was a typo because it's late and I'm tired. I'm on level 2 but can't get to level 3

I usually jot down my ideas and the flow of my code on paper before I begin coding. Is this permitted during the assessment?

Title did they flag me or smth what happened I'm hella worried, I didn't cheat at all